Receiz/Standards/Reference Contract

Standards

Canonical by design. Deterministic by default.

These files are the public verification contract for files and sealed file/package flows. They are versioned, deterministic, and built for long-lived integrations where outcomes must stay stable. Base schema files preserve historical compatibility; trusted integrations should also enforce the Trusted Verification Profile.

CanonicalStableDeterministicAuditablePublicAny-FilePackage-AwareCanonicalDeterministicIntegrityPortableVerifiableCanonicalStableCanonicalDeterministicAuditablePublic

Back to Receiz Identity Trust Center

Authority Model

Artifact First

The file is authoritative. Proof lives with file bytes, never in screenshots or render-only copies.

Trusted Profile

Trusted verdicts apply an explicit hard-fail profile over the base schema: Receiz signature v4 cert-chain verification, real g16 proof checks, and anchor coherence.

Offline scope

Record, Seal, and Verify all run offline. Account access is optional and not required for core verification operations.

Offline Reference

The offline verifier is the reference implementation for verification behavior.

API Mirror

Online APIs mirror the same verification logic for automation. They are convenience, never dependency.

Reference Runtime

Verification reference implementation: Offline Verifier.

Canonical Files

Canonical payload contract

Receiz Schema v1

Defines canonical proof payload fields used across file verification primitives and sealed document/media files. Backward-compatible for historical bundles; trusted verdict mode is signature v4 under the trusted profile.

Open JSON

Trusted verdict contract

Trusted Verification Profile v1

Hard requirements layered on schema v1 for trusted verification: required Receiz signature v4 verification (payload hash, root-key policy, device cert-chain, cert validity), real g16 proof envelope, and anchor identity fields.

Open JSON

Stable machine outcomes

Error Codes v1

Enumerates deterministic failure classes so verification systems can route decisions safely.

Open JSON

Conformance baseline

Test Vectors v1

Reference vectors for deterministic implementation checks across environments.

Open JSON

Container contract

Bundle Envelope Schema v1

Defines receiz.bundle.v1 containers used when proofs are carried as envelope artifacts.

Open JSON

ZK proof codec contract

Real Groth16 Envelope v1

Defines the decoded g16 envelope inside proof bundles for runtime Groth16 verification.

Open JSON

API response contract

Document Verify Response v1

Defines POST /api/document-verify response shape, including file kinds, bundle/anchor payloads, and folder-package summaries. The envelope keys are stable across success and failure statuses.

Open JSON

API response contract

Document Seal Metadata v1

Defines deterministic metadata headers and error envelopes returned by POST /api/document-seal for all supported seal carriers.

Open JSON

Artifact Carrier Coverage

Current standard contracts cover multiple proof carriers so files keep usage semantics while remaining independently verifiable.

PNG metadata chunksPDF embedded updatesSVG metadata channelJSON trailing channelTrailer marker (media/binary)Folder package ZIP + manifests

Capability Matrix

Carrier	Seal	Verify	Stamp
PNG	Native chunk embed	Online + offline	Visual stamp supported
PDF	Embedded metadata update	Online + offline	No visual stamp (header note)
SVG	Metadata channel	Online + offline	No visual stamp (header note)
JSON	Whitespace trailer channel	Online + offline	No visual stamp (header note)
Binary/Media	Trailer marker	Online + offline	No visual stamp (header note)
Folder ZIP	Manifest + sealed artifacts	Online + offline	N/A (container flow)

Versioning Rule

Breaking changes ship under a new versioned filename and payload version. Existing versions remain stable and continue to verify historical artifacts.