§ 9
N-1 evidence bundle
One JSON file, generated from the same records as the case page. It carries the plain summary, the nine requirements and their coverage, the run and its caveat, every observation, the auditor's verdict, and the eight things still unknown.
WHAT YOU CAN CHECK FROM THE FILE ALONEno other context needed
- coverage.covered + coverage.uncovered + coverage.contested === coverage.total
- A coverage bar that does not partition is a false statement about how much was checked.
- exactly one entry in observations[] has expectation_set === "after_measurement"
- That entry is the recorded failure. Its presence is why run.cases_matched must not be read as a count of safety properties.
WHAT IT IS NOTstated, not implied
- Not a replay
- It carries records and pointers. The primary artifacts live on the research machine and are not published.
- No packaged verifier
- An auditor for the underlying bundles exists on the research machine. Packaging it would mean publishing the artifacts it reads, which has not been approved. A substitute verifier that checked nothing real would be worse than shipping none.
- Not a standard
- No general interchange format is claimed. This is the smallest thing that is honestly useful, and it will widen only if someone outside needs something it does not carry.