Automation should leave a receipt

I trust automation more when it leaves a receipt.

Not a dashboard. Not a notification for every successful run. A plain record of what changed, what was skipped, and what I can do next.

2026-07-13 08:12
workflow: draft-title-cleanup
changed:
  posts/old-agent-note.md -> posts/agent-runbooks-need-failure-examples.md
skipped:
  posts/untitled.md, missing title
next:
  review skipped file manually

That is enough to keep a small script understandable after the novelty wears off.

Silent automation ages badly because authorship disappears. If a folder looks different, I eventually stop knowing whether I changed it, a cron job did, an agent did, or a script I wrote during a burst of optimism did it. The output is present. The reason is gone.

Skipped items belong in the receipt. They show the edge of the system:

• ambiguous filename
• missing frontmatter
• past date
• unreadable metadata
• manual edit would be overwritten

I would rather see five skipped files than watch a script confidently guess.

Undo should be written down too. For moves, keep source and destination. For text edits, preserve the diff. For generated files, record the command and inputs. For external actions, keep the returned identifier. A full rollback button is not required. A clear path back is.

My default notification policy is quiet:

• no alert for routine success
• a summary where I naturally review work
• an alert for failure or surprising changes
• a loud alert for destructive actions

Agents need even better receipts because their path can vary from run to run. Include the request, resources inspected, resources changed, commands run, checks, assumptions, and unfinished work.

The receipt is the part that lets automation remain useful after I forget how it works.