Verify it yourself. That is the product.
Every package below carries a standalone verifier (Node.js ≥ 20, no network, no dependencies), the signed records, the signed delivery manifest binding every file, and the canonicalization recipe. Each round is frozen history the moment it is cited: we supersede, we never rewrite.
- CURRENTStrict-parser verifier (current by default, expiry enforced, temporal policy), the re-run engagement package with its GENERATED review cover, and the re-derivable corpora. Supersedes r4.
- HISTORYAs fetched, verified, and cited by the independent reviewer (303 receipts · computed from the reviewer's receipt package). Byte-identical; never mutated. Superseded by r5.
- HISTORYThe round-three artifact set. Byte-identical; never mutated. Superseded by r4.
The engagement package (findings, closure receipts, the published comparison laws, the labor ledger) ships inside each round's set under engagement-mock/, with the source corpora and the transformation machinery under engagement-corpora/ — a reviewer re-derives any finding without accepting our extraction as authority.
The package sets frozen under /verify/astra-r3, /verify/astra-r4, and /verify/astra-r5 are historical packages: each is the byte-identical artifact set of one completed, independently cited review round. They do not establish anything about the present — not the current site, not current practice, not any present capability, and not the state of any live record or authority source today. A passing verifier run inside a frozen package establishes only that the package's own bytes were internally consistent at the time of that round; it does not show, and is not a measure of, anything since. For what the live operation establishes, read the records ledger — each record carries its own signed limit statements, and nothing here establishes anything a record does not state itself.