Expand description
#3769: the README’s release matrix, rendered from the ladder receipts (never typed). The README’s release-verification matrix, RENDERED from the ladder receipts.
#3769, operator 2026-09-21 verbatim: “ensure our post-release always updated README.md and apr-cookbook with SHACL validated recipes”.
The matrix is data, not prose. Every cell comes from
evidence/dogfood/models/<version>/<host>.json — the receipts scripts/model_ladder.sh
writes and scripts/check_model_ladder.sh judges. Nothing here is typed by hand, because
a hand-maintained table is the leak the operator has ruled on twice: a claim nobody
re-derives drifts silently and then gets quoted. The same shape as
docs/GPU-SUPPORT.md, which is generated from capability.rs and gated the same way.
§The two guards, and why the second one is the one that matters
the_committed_readme_section_matches_the_receipts proves the README equals the render.
On its own that is weak: a renderer that emitted a constant would satisfy it forever.
the_table_discriminates_rather_than_saying_yes_everywhere is the anti-vacuity control.
It mutates a receipt and requires the output to change. A table that says the same
thing whatever the receipts say is not a report, and every “green that cannot go red” in
this repo’s history has that shape.
Asserting “some cell is red” would be the obvious anti-vacuity test and it is the WRONG one: a clean release is legitimately all-green, so that assertion would fail for a good reason and be deleted by whoever hit it. Mutation survives a perfect release.
Structs§
- Receipt
- One host’s ladder receipt for one release.
- Rung
- One model rung as the ladder receipt records it.
Constants§
- BEGIN
- Marker opening the generated block in
README.md. - END
- Marker closing the generated block in
README.md.
Functions§
- render
- Render the matrix for
receipts, which must all be for the same version.