THWIP

Scrapers do not crash, they rot. This is the back page of the issue: the pitch, the coupon that installs it, what to do with it once you have, and the lab where you break one yourself. Every command here is one that runs. No pseudo-code, no placeholders.

What to do with it

The coupon above got you the repository. These are the five things worth doing with it — two in a browser, three in a terminal. None needs an API key, touches the network, or spends a cent.

  1. Watch a real incident replay itself

    The console opens on inc_003 — a break the cron found overnight, healed on its own, and got wrong. The false diagnosis is still in the record. Scroll to Incident Feed: every card is a comic issue with its own permalink, and the note above them counts the breaks that happened on sites nobody here controls. Open the watch →

  2. Drag the black off a panel

    The substance covers exactly the share of its contract a Spider stopped delivering. Hold the pointer on the darkened half of the diptych and pull: underneath are the values that actually came back: null, a literal "undefined". Nothing there is written for the reveal. Prefer to break one yourself? The CHAOS LAB poster below is three clicks and no install.

  3. Make it prove requirement 4

    Every phase of one repair, printed beside the collector_id that did not change, then the per-field verification table. This is the MCP server answering over stdio, with the same eight tools the ad lists.

    printf '%s\n%s\n' \
  '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"x","version":"1"}}}' \
  '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"heal_receipt","arguments":{"incident_id":"inc_001"}}}' \
  | node mcp/server.js

  4. Print the evidence trail

    node tools/evidence-report.js

    For each incident: the collector id on both sides of the repair, asserted identical; the stage durations; the value every field held before and after; the verdict; and SHA-256 digests recomputed from the committed files at call time. A check, not a claim.

  5. Count what no human did

    git log --author="thwip watch" --oneline | wc -l
node tools/numbers-audit.js

    The first counts commits the workflow authored rather than a person. The second recomputes every number the console shows from the committed JSON. It is a second implementation that shares no code with the console, so a disagreement would show.

The console needs a real HTTP origin: serve the repo with python3 -m http.server 8000 and open /web/. Opening the file directly shows an error plate, because the page fetches two JSON files and browsers block fetch on file://.

Break it yourself

ONE CLICK · NO INSTALL · NO KEY

THE CHAOS LAB

The fleet in this mode is synthetic and the page says so at the top. The mechanics running it are the same code the live console uses: the same break, the same spread, the same receipt.

  1. BREAK BODEGA The substance climbs the panel; its spread is the integrity deficit, so the black is the number rather than an effect.
  2. DRAG ACROSS IT The black tears away, showing the values that actually came back.
  3. RE-WEAVE The receipt prints, carrying the per-field was and now table.

OPEN THE CHAOS LAB →

Add ?capture=1 to hide every control for a clean screenshot. The real console lives on the plain route and never falls back to synthetic data; it shows honest empty states until the cron has committed a scan.