Client-Safe Provenance Summary
Decision Provenance Record
This is a client-safe provenance summary. It does not expose internal review notes, suppression details, or raw governance events.
Sample data for demonstration purposes. Not a live record.
Accountability statement
6 evidence inputs captured; 3 evidence inputs operator or third-party verified; 1 operator review completed; 1 field suppressed for safety; delivery sent; outcome recorded; 1 provenance gap remains.
Provenance hash
a3f5c8e1b2d7f9a0c4e6b8d2f1a3c5e7b9d0f2a4c6e8b1d3f5a7c9e0b2d4f6
SHA-256 of the canonical internal record. The client-safe summary carries the same hash.
Posture
Delivery
Delivered
Outcome
Recorded
Gaps
1 warning
Anchor
Hash verified
Evidence confidence
Operator-verified
3
System-inferred
2
User-reported
1
Confidence tiers are never upgraded. System-inferred remains system-inferred. Operator-verified means a human confirmed the finding.
Milestone timeline
14 May 2026
Evidence captured
14 May 2026
Governance review completed
15 May 2026
Oversight brief delivered
28 May 2026
Outcome verified
Gap classes
Gap severity classes are exposed without internal stage names or remediation details.
Anchor status
Hash
Verified
Chain
Not yet included
External anchor
Not configured
WORM storage
Not configured
Related surfaces
Chain boundary
This provenance record is hash-verified against the internal Decision Provenance Record. The hash is stored in the oversight cycle archive and can be independently verified by the platform operator upon request. External WORM storage or public blockchain anchoring is not yet configured. Until then, the hash provides tamper evidence rather than tamper prevention — any change to the record produces a different hash, enabling detection.