Fathom Lab

Separately: styxx now has a memecoin on Solana. No return is promised, and it does nothing. Its page lists every fee the creator claims, with the transaction and what it was spent on. One address, one page: nothing-crosses-unseen.pages…

The tech, in one example. An agent writes: "Added 3 tests." styxx checks that against the diff. The diff adds 1. Verdict: CONTRADICTED. When it cannot check a claim, it says so. A pass that hides what it skipped is not a pass. pip install styxx python -m styxx.diffgate --demo

styxx: a memecoin with open books. It does nothing. No return is promised. The creator wallet sold its whole holding to shake snipers and earns a fee on every trade. Every fee it takes and move it makes is listed. If you buy memecoins, buy this one. nothing-crosses-unseen.pages…

G1DnVsXND2tznAq8tZm9uszisMVdzroDQjFGTnJMpump

Update. The creator wallet sold its whole holding at 16:34 UTC today. The page lists that sale with every other movement of the wallet since launch. The creator still earns the fee on each trade. No return is promised. nothing-crosses-unseen.pages…

our agent darkflobi cannot send a message without a receipt: the bytes, the verdict, the model that wrote it, chained and stamped into bitcoin. a stranger recomputes all of it in a browser. yesterday the receipts caught it running on a 3b fallback for a day. fathom-lab.github.io/styxx/l…

styxx will prevail.

why styxx most AI tools ask you to trust their output. styxx is built so you never have to trust ours: every claim ships with the bytes to check it. what that looks like today — all public, all checkable: → it publishes its own error rate. the diff gate's path accusations scored 0.23 precision on 100 accusations sampled from 71,016 agent-written pull requests nobody here wrote. that number is in the README, with the receipts. a gate that hides its misses isn't a gate. → it hasn't earned the right to block, and says so. no accusation kind has cleared our own 0.95 precision floor yet, so the github action and the gitlab job report by default and block only if you opt in. → it re-derives instead of trusting a signature. a verdict is recomputed from the committed bytes. a second verifier runs in your browser, held to shared test vectors, so you're not trusting one implementation either. → it predicts before it measures. 409 preregistrations frozen in the repo before their data, 208 certificates binding documents to the receipts behind every number, and the dead results published right next to the live ones. → it files against itself. two security advisories against our own code in one week. three defects in our own gate opened on our own tracker. our own priority claims withdrawn when nobody had priced them. where it's going: → every verdict names the exact code and runtime that produced it. when a result changes, you'll see whether the checker moved or the data did. the design is approved; one piece is merged, the next is in review. → one file per experiment: the frozen plan, its hash timestamped on a public chain before the results are opened, the receipts, the result with every number sworn to them, and a page that tells a stranger which links it checked and which it can't. being built now. → the gate measured on pull requests that don't exist yet: the plan sealed and timestamped, then a sample of agent PRs opened afterwards, graded blind. a precision number nobody could have tuned. the pitch is simple: don't believe us. check us. github.com/fathom-lab/styxx

styxx 7.49.0 is live. pip install -U styxx we attacked our own proof format, found the hole, shipped the fix, and filed the advisory against ourselves. → the hole OATH capsules are single-file documents that carry their own receipts plus a certificate, and styxx.capsule verify re-derives that certificate from the bytes. we went after the verifier ourselves. on every release since capsules shipped (7.47.0, 7.48.0, 7.48.1) it printed VERIFIED on capsules whose certificate had been edited: an unchecked number hidden, a ledger row deleted, a receipt repointed, an epistemics flag flipped, a page that shows one document while the verifier reads another. five forgeries. 7.48.0 and 7.48.1 passed every one. → the fix 7.49.0 compares the whole certificate and the page around it. all five forgeries fail now. a newly minted page shows a verdict only after its hashes match. advisory, filed and published by us: GHSA-3g8h-qcfm-25xw → the part we left open, on purpose and in writing capsules minted on the old page format still verify, because honest ones carry it. a forged one dressed up as "older" still passes on that page, but 7.49.0 prints six NOT CHECKED lines and three warnings next to it. on a new page the same forgery fails. → the diff gate holds back where it could be wrong PATH-2a: where three known reader bugs could flip a verdict, the gate withholds the verdict. → the Action reports by default and blocks only if you opt in reason: no kind of accusation it still makes has cleared our own 0.95 precision floor. path accusations measured 0.23 precision on 100 accusations sampled from 71,016 external agent PRs. that number is in the README. → "LIE" is gone. a contradicted claim prints CONTRADICTED, with its reason. → receipts PyPI 7.49.0 · GitHub release with sha256 for both files · Zenodo DOI 10.5281/zenodo.23221755 a verifier that hides its own failure modes isn't worth running. so we published ours.

styxx // what's next no cap: the layer on #187 went twelve rounds with our own reviewers. three of four already said ship on round twelve. the last one's still in the booth. here's the plan, no smoke: - the last review lands. if it says ship, the layer cleared all four. - then it's a human call: is "can't tell" good enough, or do we hold out for a real fix. we said fix up front, so a human signs off on any switch. no shortcuts. - if it's a yes: merge, then a new release. 7.48.0 still gets fooled, and we're not pretending it doesn't. - after the merge, 16 open bugs we caught in our own release are next in line. they wait on #187 because the layer is pinned to the release's exact bytes. touch those early and the proof breaks. - one gap stays on the table, out loud: under certain git diff options a false call can still slip through. closing it costs 98 right answers per port on our test set, so a human decides that too. we don't ship vibes. we ship receipts. the tool you trust should know when it doesn't know. github.com/fathom-lab/styxx/…

our lab's gate, now runnable in a browser tab with nothing installed: paste the description your coding agent wrote and the diff it shipped, read the verdict line by line. private diffs never leave the tab.