CODE VERDICTS

Every change to this site's code is reviewed: each pull request into the site's branches at its head, where the pnd-review check it posts is required before the merge, and every push to a branch once it lands. A push whose code is exactly a pull request head that read clean carries that verdict (the verdict names the pull request); any other push is read again. A review runs fixed rules (among them fee recipients, keys and network calls, outside scripts, dependencies and builds with no source) and an AI reviewer's own reading of the diff, looking for supply-chain attacks. Each verdict, with the reviewer's reasoning, is written to a hash-chained public record, and this page re-checks that chain in your browser. The record's head is timestamped in Bitcoin through OpenTimestamps, and this page walks the newest proof to the block itself: once a verdict is under an anchor in a block, nobody, the keeper's operator included, can rewrite it unseen. Each verdict, and each instructions text, links the Bitcoin block that first holds it, and "check this block" walks that block's own proof here too. Every verdict written since the reviewer's instructions were published carries their fingerprint and links their exact text on the Instructions tab, so a change to them is public. Each branch's record opens with a review of its complete code (shown as not reviewed yet until the reviewer answers it). The keeper also compares the files this site serves with the files committed to its branch every minute, and pauses the site when they stay different. A pull request whose review is not clean cannot merge, so it never reaches the site; a malicious change that reaches a branch some other way pauses the site.

The keeper judges each change itself: it sends the published instructions and the change, page by page, to the review model each verdict names (its name and the host it was asked at), and records what came back. No one else can answer for it. Verdicts before 8 November 2026 were given by a Claude task through a tool on the owner's account; that tool is gone. Each verdict below links the exact instructions it was reviewed under on the Instructions tab, checked here against the fingerprint the verdict names.

The record: /verdicts. Save a copy: a record rewritten later no longer matches the hashes you kept, or the Bitcoin anchor.