This page is the exception surface because it defines the register map itself. The phrase "re-judgeable canonical-byte evidence" appears here as the technical-register term; it is intentionally not the homepage lead, contracting-officer lead, or business-development lead.
The Register Map
Capture, primes, contracting, institutional diligence
"Independently re-judgeable release evidence."
Used for the homepage first screen, capability statements, diligence shortcuts, and briefing language.
CLI, packaging, UX, release files
NERV Release Evidence Bundle
Used for product surface names, bundle packaging, verifier commands, manifest headers, and signed release evidence.
Engineers, assessors, AI governance leads
"Re-judgeable canonical-byte evidence."
Used in architecture briefs and due-diligence engineering conversations where byte identity, policy binding, and verifier behavior matter.
Formal architecture and conformance
Canonical-Byte Re-Judgment Invariant
Used in conformance vectors, mechanically implementable specs, proof obligations, and formal register entries. Do not paraphrase when cited as a normative term.
Slides and live walkthroughs
"One canonicalization rule. Byte-exact evidence. Same policy pack. Same verdict."
Used for short demonstrations where the mechanism must be visible without requiring formal notation.
How The Homepage Applies This
- The first screen uses buyer-register language and scope boundaries.
- The 10-year replay-stable backfill is treated as the lead diligence artifact.
- Seismic is declared as the live production lane; maritime AIS and geomagnetic storm are labeled with bounded maturity states.
- Technical terms remain available through Technical view, the glossary, protocol pages, and the evidence architecture surface.
- GUL values are framed as deterministic modeled loss proxies, not payout or final claims amounts.
Where To Go Next
- Homepage for buyer-facing orientation and live evidence.
- Verification for independent replay steps.
- Evidence Architecture for the governed evidence map.
- Protocol for product and technical vocabulary.
- Glossary for acronym expansion and term boundaries.