Freshness is a claim. This is a check.
Proves: the exact question instances were derived from a commitment that did not exist before the floor block, so they were not in any training set frozen before that block; the paper’s digest spent that slot; the answer sheet names the paper and sits at a later position on the same chain.
Does not prove: that the template families are unfamiliar to the model; that the model worked alone, without tools, or quickly; when the answers were produced beyond their own floor. The answer sheet has a floor, not a ceiling.
That paragraph is the whole claim, and this package asks you to attack it. Everything else is running code and real evidence: six models from three vendors sat the same kind of paper on 12 and 13 September 2026, each paper derived from a value that came into existence at a signed position on a public chain, and each sitting is a folder you verify with nothing but Node, offline, in three commands.
Read the source on GitHub (opens in a new tab)Download the packageNode 20 or later · a clone installs once, the 4.1 MB zip installs nothing and never touches the network
shasum -a 256 BitGraph-Sealed-Exam-Demo.zip cb46dbb7810f9b6f2fb8d69f6b9bd4260d210b0126e7a474d659a8fe6c51336c
The repository and the zip are the same package in two forms. The repository holds the five packages in source, so the code can be read before it is run; the zip is that tree with the packages packed and the verification path vendored, so it runs with nothing installed and no network at all. Six sittings and seven fixtures in both.
Run it
From a clone of github.com/mikeargento/sealed-exam, one install, and it is the only moment anything touches the network:
npm install npm run build
From the zip, nothing: the five packages and their dependencies are vendored under verifier/node_modules/. Then the same three commands either way.
node verifier/demo.mjs # the table, every value recomputed node verifier/exam.mjs verify demo/claude-sonnet-5.exam # one folder, every check listed node verifier/exam.mjs selftest # DRBG vectors, determinism, checkers, fences: 11 self-tests
The verifier runs in a process where fetch and sockets throw, so a verifier that reached for the network would fail loudly rather than quietly; the shortest test of that is to turn the wifi off first. The second command writes report.html beside the folder: one page, no scripts, the verdict, the score, the block number linked to a public explorer, the two floors, one question opened up, and the claim boundary again at the bottom. It reads with CSS off.
What the table says
Six real sittings and seven fixtures, printed by the verifier from the files in the package. Four of the six scored 20/20; the bank is small and the families are easy for a frontier model on purpose, because the demonstration is about freshness, not difficulty.
| ACCEPT | everything recomputes and agrees, and the score is what re-running the checkers says |
| REJECT | something recomputes and disagrees; it names which of four — the paper, the commitment, the answers, or the order |
| NO-EVIDENCE | something the claim needs is not in hand. Absence is never a verdict against the run |
The seven fixtures are what the verifier is for, and each was made from real positions rather than by editing signatures into shape: a paper edited and then genuinely committed under its own slot, one sitting’s paper presented with another’s proof, an answer sheet moved below the paper it answers, a folder whose grade.json claims 20/20 and is never read. One model refused four questions outright; the refusals are in the package as the API returned them, counted wrong, with a note in the verdict.
Where the floor comes from
A hash of a question set published today is a postmark: it proves the set existed no later than now, which is the wrong direction for contamination. What contamination needs is a floor — proof that the questions could not have existed before a public moment, so no corpus frozen before it can contain them. A slot is allocated on the BitGraph chain; the enclave signs into it the latest Ethereum block it has authenticated; the commitment is derived from that signed slot record; the questions are derived from the commitment and a public bank; the paper is committed under the same slot. SPEC.md is the whole derivation — the seed, the DRBG with test vectors, the draw order, the two positions — and re-deriving a paper from it without any of this code is an afternoon in Python.
The packages that make positions are software of Argento Computing Inc., provided under the licence in the package, which grants evaluation use. The verifier is MIT. Questions, or a sitting of your own: get in touch.