Receipts and audit

Anyone can verify any receipt.

Twelve receipt classes stand behind every state on the network: source, extraction, consent, disclosure, agent action, human decision, Work Activation, monitoring, implementation, invalidation, dispute and correction, integration and write-back.

Checking one entry never requires replaying the whole chain.

Dispute and correction receiptreceipt structure
Class
Dispute and correction
While open
suspended from use, not deleted
On resolution
corrected everywhere it went
Chain position
appended, original entry preserved
tamper-evident · tenant-verifiableChecked on its own.

The twelve receipt classes.

A closed taxonomy, not a running list.

  1. 01Source
  2. 02Extraction
  3. 03Consent
  4. 04Disclosure
  5. 05Agent action
  6. 06Human decision
  7. 07Work Activation
  8. 08Monitoring
  9. 09Implementation
  10. 10Invalidation
  11. 11Dispute and correction
  12. 12Integration and write-back

The compliance black box

A hash chain is one control, not the whole story.

Authorized people can reconstruct what Rōvn knew at any prior date without rewriting history from later information. The record is append-only, tamper-evident, tenant-verifiable, exportable, retention-aware, and bound to signed checkpoints. The Work Activation receipt, the signed projection of a named human decision, is the artifact your surveyors read.

Corrections are a duty, not a ticket

Honesty has enforcement.

A wrong fact gets corrected everywhere it went, with a receipt. A disputed fact is suspended from use while the dispute is open. And incompleteness stays visible: empty requirements read INCOMPLETE, never satisfied, and no state silently implies start, practice, or bill.

Trust, with the paperwork to prove it.

Read the doctrine and the record behind it.