Evidence Layer
Build verifiable evidence from fingerprints, hashes, timestamps, provenance, sources and evidence-chain relationships.
One function. Explicit trust boundaries.
Evidence is represented as verifiable technical and provenance material, not merely as uploaded content.
Every material state transition should remain attributable to an authenticated actor, an authority context, a timestamp and the evidence required to reconstruct what happened.
Evidence functions.
The domain is separated into explicit functions so status, authority, evidence and lifecycle transitions can be inspected independently.
Fingerprint
Represent a deterministic fingerprint used to reference content or data without requiring PAR to custody the source file.
Explore →02Hash
Display hash algorithm, digest, canonicalization context and verification result.
Explore →03Timestamp
Record verifiable time evidence and renewal/migration metadata where applicable.
Explore →04Provenance
Describe where evidence originated, who supplied it and how it entered the verification chain.
Explore →05Source
Reference the originating system, authority, registry, file, device or institution behind an evidence item.
Explore →06Evidence Chain
Show how evidence items depend on, supersede, corroborate or derive from one another.
Explore →07Evidence Status
Expose valid, superseded, disputed, revoked, migrated or unavailable evidence states.
Explore →Evidence lifecycle.
Acquire source reference
Canonicalize / fingerprint
Timestamp evidence
Bind provenance
Preserve verification metadata
Minimum verification context.
The exact schema can vary by object class and policy version, but the verification layer should be able to resolve these core dimensions.
- Evidence ID
- Fingerprint / digest
- Algorithm profile
- Timestamp
- Source
- Provenance
- Chain links
- Status
Designed for progressive activation.
Production status must always be sourced from the deployed service and published through System Status; this static package does not claim backend activation.