- Version
- 1.0.0
- Status
- Retired
- Publication Date
- 17 July 2026
- Retired
- 6 August 2026
- Type
- Specification, retained for the record
Why NAV Exists
Organizations increasingly rely on AI-generated information to support important decisions.
When those decisions matter, there should be a standard way to demonstrate what was verified, which authoritative source was used, and what the verification found.
NAV defines that standard.
Conceptual Flow
- AI-Generated Information
- Verification System
- Authoritative Source
- NAV Certificate
A NAV certificate records the evidence and result of verification against an identified authoritative source.
Origin
The category this standard describes is set out in a working paper, Network Attached Verification: An Instrument Doctrine for Autonomous AI in Regulated Enterprises, which argues why verification belongs in an appliance inside the organization's perimeter and what a certificate must record to be checkable by a stranger.
Swidey, E. (2026). https://doi.org/10.5281/zenodo.21722170
What NAV Provides
- A standard certificate format
- A common verification vocabulary
- A reference validator
- Example certificates
- Published governance and specifications
Primary Documents
Scope and Limitations
NAV certificate integrity validation confirms that a certificate body matches its recorded hash.
NAV v1.0 does not establish:
- factual truth of a claim
- issuer identity
- digital-signature authenticity
- certification status
Terms
The specification documents in this repository are made available under the Creative Commons Attribution 4.0 International license. The reference validator is made available under the Apache License 2.0.
No patent license is granted by this publication. The author holds pending United States patent applications with claims relating to the certificate data structure, the verdict taxonomy, and the offline validation procedure described in this specification, including provisional applications 64/106,324 and 64/111,896. No express or implied patent license, covenant, or non-assertion is offered here. This is stated plainly so that no party relies on a grant that was never made.
These terms are recorded at retirement so that the position on this specification is unambiguous and does not change after the fact.
Program Status
Conformance and certification programs were never included in NAV Standard v1.0, and none will be established for it. The specification is retired.