Historical critical gates
Recorded by the 6 July pack; not a current-stack pass statement.
Engineering controls
Configuration validation, critical gate coverage, phase-control checks, and API observability posture.
Recorded finding: Critical system surfaces are governed by explicit pass/fail controls rather than narrative assurance alone.
Decision signals
The recorded values, with their controls and scope.
Recorded by the 6 July pack; not a current-stack pass statement.
Superseded by a newer authority reporting 38 pass and 3 fail.
Recorded aggregate control status at the historical source boundary.
Recorded API-surface result; current status requires a new approved release.
Source-linked visual evidence
Open any chart’s data table to inspect the exact values, or download the CSV.
Status matrix
Passing and missing/failed counts as recorded by the superseded 6 July pack across three governed control families.
Finding: This chart preserves the earlier record for traceability. It is superseded by a newer phase authority reporting 38 pass and 3 fail.
Scroll sideways if any columns are out of view.
| Group | Passing | Missing / failed |
|---|---|---|
| Critical gates | 21 controls | 0 controls |
| Phase registry | 41 controls | 0 controls |
| Observability | 5 controls | 0 controls |
Method
Control coverage describes engineering discipline; it does not independently prove model capability.
Inspection and reuse
Source data
The recorded JSON artifact is staged from the governed public evidence pack during the build. Its currency notice determines whether it may be read as current.
Open source JSONProvenance
Use the public build receipt to compare the deployed site source, evidence digest, claim posture, and inference release state.
Open build receiptContinue reviewing
Decision relevance: diligence · governance
Review evidenceDecision relevance: diligence · investment · governance
Review evidence