How these reports are made

Every number traces to a pinned call

Every figure in a report is computed from Ethereum data read at one fixed block. Each value is stored with the contract call that produced it, so anyone can repeat that call on their own node, at that block, and get the same number. An AI model writes the explanatory text around the figures. It never supplies a number: its text is checked against the report's data table before anything is published.

Gates, and why their log is public

A gate is a check that must pass before a report is published. A minor finding publishes with a visible notice; a serious one withholds the report, except where a recorded ruling published a page regardless. The two cases on this site are stated under Open notices. Every time a gate fires, a public log records the date, the token, what kind of check fired, how serious it was, and how it was resolved. Anyone can say their work is checked; a log of checks stopping reports is the evidence. The log below holds 37 entries.

The written summaries on each page come from a local language model under a guard that only lets through figures printed in the data table; no second model reviews them. When a draft does not pass that guard, its section shows a notice in place of the summary and the page still publishes, so the figures stay current. The deterministic checks run on every page.

One revision, no hand edits

A report gets one revision when a judge finds a defect in its prose. In the local configuration the judge is withdrawn, so there is no revision pass: a page that fails a deterministic check is not published, and the fix goes to the template, never to the page. No report is edited by hand, and no gate can be switched off for a single run.

Same scenarios, each protocol's own mechanics

The archetype fixes the scenarios so the three pages are comparable; what happens under each shock is modelled from each protocol's own contracts.

Checked by hand

For each token, the analyst repeated a sample of the stress calls through an independent node at the report's block and compared the results with the published artifact. Each token's verify page lists the calls, so you can repeat them too.

Open notices

crvUSD's, GHO's and LUSD's pages passed every check.

The behavioral tier

The behavioral tier shows how each token trades: how far its price has strayed from the peg over the last seven days, how much DEX liquidity Webacy counts for it, how its supply changed over seven days, and how concentrated its holders are. It comes from Webacy, an external monitoring service, and is fetched at a timestamp printed on each page. Unlike the structural figures, it is not read at the report's block, and this pipeline neither computes nor verifies it.

References such as P-7.11

The appendix pages cite entries such as P-7.11. These are entries in the project's decision log, PROGRESS.md, where every ruling and implementation step is recorded in the order it was confirmed.