Supersede
A new version links back to the prior record so history remains inspectable.
Data plane
After the Smithy accepts a source event, the deposit gateway commits exact accepted bytes, signs a receipt and appends evidence. Changes never silently overwrite history.
Deposit pipeline
Replayed sourceEventId is rejected, not double-committed.
Payloads capped (1 MB) and constrained to allowed media types.
Binary evidence passes a fail-closed scanner before acceptance.
recordClass, legalBasis and purpose must be declared.
Exact accepted bytes stored at an opaque acceptedResource URL.
ES256 JWS acceptance receipt returned in the deposit report.
Exchange recorded in the append-only evidence ledger.
Immutability
A new version links back to the prior record so history remains inspectable.
A record is retired with an auditable marker rather than a silent delete.
Where permitted by retention policy: retained-then-unrecoverable deletion.
Recent work adds DurableEvidenceLedger and WORM storage audit ledger paths for stronger retention guarantees.
Access & retrieval
Record sensitivity is enforced against the assurance of the current authentication — identity proofing, authenticator strength, freshness — not merely account ownership. A profile may require step-up before payload access, and may suppress existence where an exception requires it.
The program deposits a record; the Databox sends a minimal notification; the person’s agent authenticates and pulls the record into storage of their own choosing. Organisation credentials never become authority to browse the consumer Pod.
Consumer-initiated corrections and contested records go through governed review. Signed dispositions (corrected, statement-associated, partially-corrected, denied, …) remain linked to the evidence chain. Where CKAN publication is enabled, dispositions can propagate to the open-data portal.
Related