AI receipts: building your own audit trail
If you cannot replay what the AI did and why, you cannot debug it, defend it, or trust it · build receipts now, thank yourself later.
::TL;DR · the whole lesson in three lines
- MOVEIf you cannot replay what the AI did and why, you cannot debug it, defend it, or trust it · build receipts now, thank yourself later.
- DRILLYou will build a minimal receipts logger for one of your AI workflows in the next 30 minutes and start accumulating audit trail immediately.
- WINYou have a JSONL log file accumulating real receipts.
::concept · what's actually happening
A receipt is a durable record of an AI interaction · what model was called, what prompt went in, what response came out, what tools fired, what the result was, and when it happened. It is the AI equivalent of a database transaction log, and it is the foundation of every serious AI operation.
read full concept · 4 more paragraphs →collapse concept ↑
Without receipts, AI work is unauditable · you cannot answer 'why did the system do that on Tuesday,' you cannot replay a session to debug a bad output, you cannot demonstrate compliance to a customer or regulator, and you cannot improve a prompt based on what actually went wrong yesterday.
Minimum viable receipt schema · timestamp, model id (with exact version), full prompt (system + user + any context), full response, tool calls if any, cost in tokens, and a stable ID. Anything less and you are flying blind. Store as JSON, append to a log, never overwrite.
The blunt rule: if an AI output influences a real-world action (sending an email, modifying a file, running a script, making a decision you act on), the receipt should exist before you act, not after. After-the-fact reconstruction is not an audit trail · it is a vibes-based recollection.
Receipts compound in value · the first month, they let you debug. The first year, they let you measure improvement. By year two, they are the empirical record that lets you negotiate with vendors, satisfy auditors, and train your own systems on your own history. Stop treating them as overhead.
::drill · do the thing
You will build a minimal receipts logger for one of your AI workflows in the next 30 minutes and start accumulating audit trail immediately.
::L46 drill · copy-paste into any AI chat
I want to build the minimum-viable receipts layer for one of my AI workflows. The workflow: [DESCRIBE · e.g. 'a Python script that calls Claude to classify customer emails']. Walk me through: 1) the exact JSON schema for one receipt record · timestamp, model id with version, full input, full output, tools called, token counts, cost estimate, stable UUID, 2) the smallest code change I can make to start logging every call to a local file (JSONL · one JSON object per line) without restructuring my code, 3) one query I can run a week from now to answer 'show me every time the model output was longer than 500 tokens last week,' 4) what I should add to the schema if my use case ever needs compliance audit (PII redaction notes, user consent flag, retention policy). Show me code, not abstractions.
::steps
- 01Pick one AI workflow you currently run with no receipts.
- 02Run the prompt and get the schema + wrapper code.
- 03Add the receipts wrapper in under 30 minutes.
- 04Let it run for one real day and look at the log.
- 05Run the example query against your own log.
- 06Decide which other workflows get receipts next.
::outcome · what should be true
- You have a JSONL log file accumulating real receipts.
- You ran one query against your own log and learned something.
- You can defend one of your AI decisions with the receipt that backs it.
- You know what fields you would add for a formal compliance setting.
::trap · the most common failure
Operators say 'I'll add logging later' on every AI workflow they build · then six months in, when they finally need to debug a strange output, the data is gone. Receipts cost almost nothing to add upfront and cannot be retroactively created. Build them on day one.
::end of the curriculum
You're at Pilot level. There's no Level 6.
The next move is doing the work, not another lesson. If you want operator-grade infrastructure, that's /orangebox. If you want the lab's working journal, /founders-view. If you want to collaborate on the curriculum itself, the source is public on GitHub.
::other lessons at Pilot level
Outgrowing the chat box — when chat isn't the right surface anymore
At Pilot level the chat box is a tool, not the system. You need persistent project memory, multi-tool routing, and receipts on disk. This is the bridge to a cockpit.
Receipts and paper trail — audit your own AI use
At Pilot level, what AI did for you last month becomes evidence. Knowing how to keep that evidence is the skill.
AI for kids and teachers — the next-generation curriculum
If you are a parent, teacher, or tutor — the children in your life are going to use AI for school. The choice is whether they learn it with you, or alone in their room at 11pm the night before the essay is due.
The senior-engineer pattern — talk to AI like a senior
A junior asks for the answer. A senior asks for tradeoffs, edge cases, alternatives, and reasons not to do the thing. Run that same five-step pattern through any AI conversation and the output roughly doubles in quality.
Long-context strategy: when 200K is right, when chunking wins
Long context is a tool, not a default · know what degrades, what costs you, and when chunking beats stuffing.
Open weights vs closed weights
When the model file is on your machine, the rules change · know what you gain, what you give up, and what stays the same.
Voice cloning: ethics and practical workflows
Cloning your own voice unlocks real workflows · cloning someone else's is a consent question with legal teeth · know the line.
::part of the AtomEons /learn curriculum · 45 lessons · 5 levels · cc-by 4.0