After a note leaves the list: async saves, disk removal and remote copies differ

List removal proves neither deletion of every copy nor recoverability

Note deletion refuses the current recordingID. For other notes it records an in-memory deleted id, pauses transcription if needed, attempts directory removal, updates the list and clears progress. save checks deleted against async rewrites. Removal uses try?, so list changes do not independently verify disk deletion, permanent tombstones, secure erasure or remote recall.

Different from minimization and audio/text mapping

Minimization decides what to retain; mapping identifies material. Here local removal state, async-save guards and retention evidence matter. No actual file deletion, restore or internal-state bypass is performed.

Check Verified scope Manual review Not established
Active recording Matching recordingID returns Actual recording state Lossless deletion at any moment
deleted set In-memory removed IDs This instance’s save scope Permanent cross-restart tombstone
Async save Skip deleted IDs Old work versus originals All disk/sync copies erased
Transcribing note Pause then resume other pending work Actual task/content state Every recording/transcription permanently stops
Directory try? removal attempt List alone is not disk verification Secure/irrecoverable erasure
List/progress Remove notes/clear progress Presentation versus physical result Never reappears under any condition
Prior handoff Uploads/drafts/service separately Destination/receipts Local deletion recalls remote files
Retention decision Existing purpose/authority/policy Necessary originals/approval scope Checklist authorizes all evidence destruction

Synthetic removal note

Observed: sample note absent from current list. Unknown: directory-removal success and other destinations. Report list state only, not complete erasure or available backup recovery.

Real deletion still needs actual authorization; do not destroy material for demonstrations. This read-only guide offers no permanent erasure, disaster recovery, compliance certification or handoff recall service.

FAQ

Does absent-from-list prove successful file deletion?

Not independently. Attempted removal/list updates do not verify disk state.

Is deleted a permanent deletion certificate?

No. It is an in-memory save guard, not a permanent tombstone/erasure certificate.

Does deleting recall a previously shared attachment?

No inference follows. Destination copies/service policy need review.

Can this entry delete the active recording?

The source has a recordingID guard; not every state is deletable.

Does removal failure guarantee recovery?

No. Actual files/copies/permissions need evidence; do not assume a backup.

Was any data deleted/restored here?

No. Actual deletion/restore needs authorization; source scope only.

Reading and source

Minimization · Audio/text mapping · Prior effects/receipts · Start · Privacy

Delete/save/recordingID · Metadata/handoff marker