NORNR mark NORNR Public schemas, versioning and provenance for export-safe governed records.

NORNR / Artifact standards

Public schema surface

Public schemas, versioning and provenance for the records NORNR exports.

Trust manifest, proof packet and finance close bundle should all be legible outside NORNR. These standards define the public packet shapes and the provenance rules that keep them attributable later.

The export layer should be inspectable before anyone trusts it.

These are public because the packet shapes matter outside the control room.

Trust manifest schema

Verification envelope for one governed workspace

Defines the public shape for subject, verification level, metrics, digest and provenance.

Open JSON schema ↗

Proof packet schema

Canonical packet for one governed action

Defines the public shape for intent, policy decision, approval state, settlement state, receipt trail and audit export.

Open JSON schema ↗

Finance close bundle schema

Finance-safe packet for close, retention and export

Defines the public shape for statement export, signed bundle, retention posture, provider payloads and reconciliation posture.

Open JSON schema ↗

Every exported artifact should say what it is, which version it follows and where it came from.

That is what makes packets verifiable later instead of merely readable now.

Kind

Each packet declares its public artifact kind

Examples: nornr.trust_manifest, nornr.proof_packet, nornr.finance_close_bundle.

Schema version

Each packet declares a public schema version

The packet must carry the version it claims so another system can verify against the same public contract later.

Provenance

Each packet carries workspace, source lane and export timestamps

Workspace id, source lane, exported at, policy version and packet id should travel with the artifact so provenance survives outside NORNR.

Digest

Each packet can be re-validated against a digest-backed envelope

Digest and signature make the export more than a pretty PDF. They make it checkable later.