Selected verification¶
These records substantiate bounded claims, decisions or unresolved gates. They are curated evidence, not a chronology of every development run. Original source IDs, dates and measurements remain associated with their original tests. No record here qualifies the current branch merely because it was moved. Old release assets/tags are retired; external run links may expire. Sanitized records state their transformation limits; independent observations, generated fixtures and private captures are not interchangeable.
| Record | Why retained | Limit |
|---|---|---|
| FCC corpus | Storage/data-plane decision and comparative benchmark | Dated Chrome/corpus workload, not today's startup default |
| Viterbi | Algorithm correctness and performance comparison | Frozen workload, sampled attribution, no >4-GiB proof |
| CPU efficiency | Per-candidate and combined measurements, weak-signal invariance | Live intervals differ; restart loss retained |
| NRSC-5 | Pinned FM, source-mapped diagnostic replay and partial live reception | Positive AM and full operator/fault/isolation matrix remain open |
| GOES HRIT | Independent versus generated receive/product evidence | Live imagery, isolation and broader acceptance remain open |
| Record delivery | Protected memory, exact records, measured cost and correction | RAM retention is not durable storage |
| Onboarding | Pairing/authority and installed lifecycle regression | Unresolved sanitizer helper timeout retained |
| Ingestion | Durable ACK, recovery/readback and fixture failures | Phase 6 performance and hardware power loss unqualified |
| Browser records | Legacy/shared-core parity failures and corrections | Native/WASM agreement is not universal legacy parity |
| Products | Admission, WAL, imagery, browser import and installed outcomes | Watchdog anomaly and platform/resource limits remain |
Necessary supporting JSON lives beside its report in data/. These files are
readable evidence, not current CI proof inputs. Local consumer inspection found
no executable dependency on their old paths. Future runs write ignored build/
or explicitly private evidence directories; publication requires a scoped
report with reviewed support, not uploading an entire diagnostic directory.
Current qualification procedures live in validation and build/release policy. Open acceptance obligations live in the roadmap.