Deletion Evidence and Consume Outcome¶
The subsystem that answers "what do we actually know about this version, and who is responsible?". It distinguishes an authorization to delete, an actor's signed claim that it deleted, and an observer's signed statement that the version was absent. It also sequences the consume operation and states its postcondition honestly.
Identifier and encoding terms live in the shared-types context; this context owns only the concepts specific to deletion evidence and the consume sequence.
Language¶
Deletion Intent: A signed, key-free authorization to attempt cleanup of one exact version by a deadline. It is not a tombstone and not a report. Avoid: tombstone, delete request, order, lease Subsystems: Deletion Evidence and Consume Outcome, Backend Admission and Durable Arming Files: crates/ksp-types/src/evidence.rs, crates/ksp-deletion/src/intent.rs Relates to: Record Version (targets), Durable Arming (is written by), Deletion Report (is fulfilled by) History: - 2026-10-21 (001-keyspout-mvp): Term introduced. "tombstone" is explicitly avoided because the design spec forbids treating an intent as one.
Deletion Report: A separately retained, signed, version-scoped statement by the deleting actor, written after backend acknowledgement, binding intent, actor, signer key ID, reason, outcome and the claimed time. It attributes a claim; it does not prove destruction. Avoid: deletion proof, receipt, attestation, certificate of deletion Subsystems: Deletion Evidence and Consume Outcome Files: crates/ksp-types/src/evidence.rs, crates/ksp-deletion/src/report.rs Relates to: Deletion Intent (fulfils), Actor (is signed by), Absence Observation (is distinct from) History: - 2026-10-21 (001-keyspout-mvp): Term introduced.
Absence Observation: A signed statement by an authorized observer that a version was absent at a stated observation time. It names no deleting actor and invents no deletion time. Avoid: missing record, negative report, evidence of deletion Subsystems: Deletion Evidence and Consume Outcome Files: crates/ksp-types/src/evidence.rs, crates/ksp-deletion/src/observation.rs Relates to: Deletion Report (is distinct from), Record Version (observes) History: - 2026-10-21 (001-keyspout-mvp): Term introduced.
Actor: The principal that performed a deletion and signs its own deletion report. Avoid: deleter, executor, agent, operator Subsystems: Deletion Evidence and Consume Outcome Files: crates/ksp-deletion/src/report.rs Relates to: Deletion Report (signs), Authorized Deleter (must be) History: - 2026-10-21 (001-keyspout-mvp): Term introduced.
Authorized Deleter: The set of actors permitted to sign a report for one specific version. A report signed by anyone else is rejected even when the signature is valid. Avoid: permission, deleter list, approver Subsystems: Deletion Evidence and Consume Outcome Files: crates/ksp-types/src/evidence.rs Relates to: Actor (is drawn from), Deletion Report (is scoped by), Record Version (is scoped by) History: - 2026-10-21 (001-keyspout-mvp): Term introduced.
Missing Unconfirmed: The state of a version that is absent without an authenticated actor report. It is reported as unconfirmed, never upgraded to a deletion. Avoid: deleted, gone, expired, confirmed deleted Subsystems: Deletion Evidence and Consume Outcome Files: crates/ksp-deletion/src/observation.rs Relates to: Absence Observation (may follow), Deletion Report (is distinguished from) History: - 2026-10-21 (001-keyspout-mvp): Term introduced.
Acknowledgement Journal: The durable record of a delete acknowledgement, allowing an idempotent retry of a report write by intent, version, actor and event without restoring ciphertext. Avoid: retry log, outbox, write-ahead log, dead letter queue Subsystems: Deletion Evidence and Consume Outcome Files: crates/ksp-deletion/src/journal.rs Relates to: Operation Identity (is keyed by), Deletion Report (is retried via), Durable Arming (mirrors) History: - 2026-10-21 (001-keyspout-mvp): Term introduced.
Field Projection:
The single reduction of one decoded log-record payload to printable fields, where
a field name that may hold a secret becomes Redacted and every other value
keeps only its type and shape.
Avoid: field scrubber, redaction pass, preview
Subsystems: Deletion Evidence and Consume Outcome
Files: crates/ksp-deletion/src/audit.rs
Relates to: Log Projection (is consumed by), Audit Event (reduces)
History:
- 2026-10-25 (002-file-os-split-sweeper): Term introduced.
Consume: The ordered operation that retrieves a version, decrypts it, hands plaintext to the child without persisting a recovery copy, deletes that exact version, and signs a report after acknowledgement. Avoid: consume-once, read-and-delete, burn, one-shot read Subsystems: Deletion Evidence and Consume Outcome Files: crates/ksp-deletion/src/consume.rs Relates to: Record Version (is removed by), Deletion Report (is produced by) History: - 2026-10-21 (001-keyspout-mvp): Term introduced. "consume-once" is avoided because the operation is explicitly not exactly-once.
Lost Fresh Fetch: The condition in which a version has been removed but a later fresh fetch still finds it, or in which a removal succeeded and the child then failed. The run exits with its own distinct code and never auto-remints. Avoid: lost capability, lease lost, expired lease, re-mint needed Subsystems: Deletion Evidence and Consume Outcome Files: crates/ksp-deletion/src/consume.rs Relates to: Consume (is a state of), Record Version (is removed), Fresh Fetch (is the counterpart of) History: - 2026-10-21 (001-keyspout-mvp): Term introduced.
Fresh Fetch: A retrieval that happens after a removal, from an honest store. It fails because the version is gone, not because a token was revoked. Avoid: later read, refetch, subsequent fetch Subsystems: Deletion Evidence and Consume Outcome Files: crates/ksp-deletion/src/consume.rs Relates to: Lost Fresh Fetch (is the counterpart of), Record Version (is fetched) History: - 2026-10-21 (001-keyspout-mvp): Term introduced.
Recovery Copy: A persisted duplicate of a delivered plaintext, kept so a failed run could be retried. Consume never creates one. Avoid: backup, spool, shadow copy, cache Subsystems: Deletion Evidence and Consume Outcome Files: crates/ksp-deletion/src/consume.rs Relates to: Consume (is forbidden by) History: - 2026-10-21 (001-keyspout-mvp): Term introduced.
Pinned Key: A public key a host trusts because it was pinned outside the log — the admin anchor, the user policy the admin signed, or an enrolment record the operator read a fingerprint from. Verification resolves a signer here and never from the record's own key id, filename or fingerprint. Avoid: trusted key, known key, allowlist entry Subsystems: Deletion Evidence and Consume Outcome Files: crates/ksp-deletion/src/audit.rs, crates/ksp/src/audit_verify.rs Relates to: Audit Record (is verified by), Unpinned Signer (is the absence of), Head Digest (is read beside) History: - 2026-10-24 (002-file-os-split-sweeper): Term introduced. A verifier that reads the key out of the artifact it checks answers its own question (Misfit W).
Unpinned Signer: A record whose named signing key no pin holds. It is a finding of its own, not a bad signature: the remedy is to find the key and pin it, or to distrust the record. A key retired by rotation is reported this way on a host that keeps no public archive, because claiming "archived" would mean trusting the record. Avoid: unknown key, invalid signature, bad key Subsystems: Deletion Evidence and Consume Outcome Files: crates/ksp-deletion/src/audit.rs Relates to: Pinned Key (is the absence of), Audit Record (is a finding about) History: - 2026-10-24 (002-file-os-split-sweeper): Term introduced.
Head Digest: The digest of a chain's last record, written down outside the log. It is the only thing that turns a shortened but internally valid chain into a mismatch; without one the honest answer is that completeness is unknown. Avoid: checksum, hash, log pointer Subsystems: Deletion Evidence and Consume Outcome Files: crates/ksp-deletion/src/audit.rs, crates/ksp/src/audit_verify.rs Relates to: Audit Record (is the digest of one), Chain Break (is distinguished from) History: - 2026-10-24 (002-file-os-split-sweeper): Term introduced.
Relationships¶
- A Deletion Intent authorizes a Deletion Report for one record version
- An Actor signs a Deletion Report only if it is an Authorized Deleter
- A Deletion Report and an Absence Observation are different evidence for the same record version
- Missing Unconfirmed is the state when neither exists
- Consume produces a Deletion Report and may end in Lost Fresh Fetch
- The Acknowledgement Journal makes the report write retryable by operation identity
- Consume never persists a Recovery Copy
- An Audit Record verifies only against a Pinned Key; the record never supplies its own
- A Head Digest turns a shortened chain into a Head Mismatch, and its absence leaves completeness unknown
- An Unpinned Signer and a bad signature are different findings with different remedies
Flagged Ambiguities¶
- "deletion" was used to mean both the act and the evidence of the act — resolved: "delete" is the backend operation; "Deletion Report" is the signed claim; "Absence Observation" is the signed absence.
- "deleted" was used to mean both "the store no longer returns this version" and "an actor has claimed responsibility" — resolved: the first is Missing Unconfirmed until a report exists; the second is a Deletion Report.
- "consume" was used to imply exactly-once — resolved: Consume promises only that later Fresh Fetch fails.