This is the first public evidence example.
It is not a full receipt dump. It is not a reproduction path. It is a maturity gate summary for an edge-injection workflow that has infrastructure in place and science still pending.
The public-safe claim is narrow.
Real court rows normalize into edge-injection passports. Scoped injection witness is checked. Controls stay tri-state: clean, contaminated, or missing. Token and text effects are classified. Dose response and repeatability are reported. Held-out planning recomputes prompt and candidate disjointness. Scoring remains blocked unless preregistered.
Every receipt keeps:
authority.granted = none
That line matters. Infrastructure completeness is not the same as scientific authority. A gate can confirm that the machinery exists, that the rows normalize, that the controls have a shape, and that failures are preserved without granting influence.
The important behavior is restraint.
If a control is contaminated, the receipt says so. If evidence is missing, the receipt says so. If repeatability is under-repeated, the result stays under-repeated. If held-out scoring was not preregistered, scoring stays blocked.
Current caveats:
- No scored held-out edge court yet.
- Repeatability evidence is mostly under-repeated.
- Stale runtime means no live speed or usability claim.
- Local commit state at the time of writing was not part of a public release claim.
What this shows is not steering.
It shows that the evidence conveyor can keep a difficult claim small, preserve negative and incomplete states, and refuse promotion when the court has not earned it.
That is the useful part.