Receipts Registry
Every published claim of governance must resolve to a receipt or a declared absence.
This registry is the public-tier index of receipts the publication has produced. Each row is hash-anchored where an anchor exists. Where no anchor exists, the field reads not recorded — the discipline never invents a hash to fill a gap.
Active receipts
| Receipt ID | Date | Subject | Status | Tier | Source artifact | Verification | Link |
|---|---|---|---|---|---|---|---|
RDL-012 |
2026-05-13 | GovernedAI.ai launch | Sealed | Tier 0 | git commit · ias-znm/governedai-web · 0ed0f1c |
Verified | view |
UI-v2.3.2-SEAL |
2026-05-13 | UI Identity v2.3.2 sealed | Sealed | Tier 0 | git commit · ias-znm/governedai-web · 2e88059 |
Verified | view |
RDL-013 |
2026-05-13 | Institutional backbone v1.3 | Sealed | Tier 0 | commit:f1f0867 |
Verified | view |
Field discipline
| Field | What it records |
|---|---|
receipt_id | Globally unique identifier (numeric RDL, sealed, or UI-version seal) |
date | Date the receipt was created (sealed or sealed-marked) |
subject | Short human-readable subject |
status | SEALED · CANDIDATE · DRAFT · RETIRED · SUPERSEDED |
tier | Disclosure tier of the receipt itself (not its contents) |
source artifact | Reference to the underlying artifact (commit SHA, tarball, deployment) |
verification | Verified · Pending · Not applicable · Failed |
link | Public link to the receipt document or rendered artifact |
RDL-012 · GovernedAI.ai launch
UI Identity v2.3.2 · sealed
The visual identity is frozen. No further UI changes without a production defect. Subsequent receipts build on top of v2.3.2; they do not modify it.
RDL-013 · institutional backbone v1.3 (sealed)
Adds six routes (/institutional/, /access/, /api/, /schemas/, /diligence/, strengthened /receipts/) plus this registry-table upgrade. Sealed by Sovereign on 2026-05-13 after all 10 apply-time gates passed and post-deploy smoke confirmed routes and schemas serve correctly.
Discipline
- Every receipt is hash-anchored where an anchor exists; missing anchors read
not recorded - No hash is ever invented to fill a gap
- The registry is append-only at the SEALED tier; SEALED entries are never edited, only superseded
- CANDIDATE and DRAFT entries may be revised before sealing
- The registry's own schema is published at /schemas/rdl_registry.schema.json
For receipts referencing git commits: clone the repo, check out the commit, run the documented replay command. For receipts referencing tarballs: download the tar from the published source artifact, verify the SHA-256 against the recorded value, extract and inspect. For partner-tier receipts: request access at /access/.