A typed receipt should attest only what its issuer actually observed. Applying that rule to miniterms, the plan pairing it with Anchors gives typed receipts to two actions, data requests and erasures, and leaves policy notices, breaches and transfers on the plainer record they already have.
On 1 November the founder ruled that miniterms is the flagship app and Anchors the flagship technology. The gap that pairing closes is concrete: the data-request desk is the job people pay for, and it mints no receipt today.
So the plan maps data requests received, answered or refused to the subject-rights family, and erasures carried out to the erasure family, linked to the existing Proof of Forgetting destruction receipt. Both are events miniterms performs and sees from start to finish.
The integration is net-new product surface, so it starts after the plan A launch gate passes in the 17–23 November review. Public copy stays at "verifiable receipts" until the external crypto review.
Every event in the notice family attests delivery to data subjects. miniterms renders a template; the customer sends it from their own system. A typed receipt would claim a delivery miniterms never observes.
The existing receipts for policy changes and subprocessor changes stay as they are. They attest something narrower and true: that miniterms produced the record.
The typed family is a bigger sentence than the one miniterms can honestly say.
The breach family puts severity class, affected data categories, affected count and jurisdiction in the public body. That would place a customer's breach on a permanent public page, one whose timing alone could identify the customer. Today's receipt withholds every one of those facts. If a customer asks, the path is an opt-in per incident.
Transfers fail on source. The transfer family publicly asserts a destination country and a mechanism in force. The only server-readable data is the subprocessor register, which has no declared mechanism, and the DPA's declared transfers sit in end-to-end sealed drafts. Typing it would mean guessing.
Trust turned out to be simpler than first read. miniterms's signing key is already in the verifier's key catalog, so a typed receipt signed with it should verify as trusted from day one, and each family change carries a test asserting the issuer and key.
Open work remains: an RFC 3161 timestamp on the erasure receipt, and the build itself, which waits on the launch gate. Until then this is a plan, not a feature you can use.
This post was drafted by an AI system from Dekimu's public engineering record and published with automated checks, without per-post human editing.
← Back to blog