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.
::TL;DR · the whole lesson in three lines
- MOVEAt Pilot level, what AI did for you last month becomes evidence. Knowing how to keep that evidence is the skill.
- DRILLYou're going to build a receipt for one piece of AI-assisted work from this past week, then have AI help you design a lightweight system you'll actually maintain. The point is not the template. The point is finding a shape simple enough that you'll still be doing it in November.
- WINA storage location exists (folder, spreadsheet, or notes page) with at least two real receipt entries, each under 10 lines.
::concept · what's actually happening
At novice level, AI was a help. At learner level, it was a workflow. At user and operator levels, it became part of how you make things. At pilot level, something different happens: someone is going to ask you to account for it. A client wants to know what was AI and what was you. A regulator wants to see how a decision was made. A teammate inherits your project and needs to know which prompt produced which file. Future-you, six months out, needs to remember why a draft was rejected. The work has audit weight now. The chat history is not enough.
read full concept · 3 more paragraphs →collapse concept ↑
A receipt, in the AI sense, is a small bundle that proves what happened: the prompt, the model that answered, the date, the output, and what you did with it. It is the difference between 'I used AI for this' (defensive, vague, unverifiable) and 'here is the input, the output, the model, the date, and the edits I made on top' (calm, complete, hard to argue with). Receipts are what convert AI-assisted work from a liability into an asset. They also do something quieter: they show you, honestly, what AI is and is not earning its keep on. Most pilots discover they were paying for two tools and only using one.
The mistake at this level is treating receipts like compliance paperwork — heavy, formal, something to dread. They are not. A receipt is a sticky note with five fields. The discipline is doing it every time, not doing it elaborately. The other mistake is over-engineering: building a custom database, a tagging taxonomy, a whole second job around your first job. Don't. A dated folder with text files works. A spreadsheet works. The shape of the receipt matters more than the storage. If you can answer four questions on demand — what prompt, what model, what date, what edits — you have a paper trail. If you can't, you have a vibe.
There is a second layer at pilot level: the monthly audit. Once a month, you sit with your receipts and ask three questions. What did AI actually save me time on? What did I think it helped with but didn't? Where did I edit so heavily that I should have just written it myself? This is not self-flagellation — it is portfolio management. The pilot who audits monthly compounds. The pilot who doesn't ends up paying $200/month for a tool they barely use and a tool they overuse, with no idea which is which.
::drill · do the thing
You're going to build a receipt for one piece of AI-assisted work from this past week, then have AI help you design a lightweight system you'll actually maintain. The point is not the template. The point is finding a shape simple enough that you'll still be doing it in November.
::L18 drill · copy-paste into any AI chat
I need to build a personal audit trail for my AI use. Help me design something I'll actually maintain. Here's a recent example I want to turn into a receipt: - What I was working on: [describe the task — e.g., "drafting a client proposal," "summarizing a research paper," "writing release notes"] - Which AI tool I used: [Claude / ChatGPT / Gemini / Copilot / other] - Approximate date: [date] - What I asked it (paste prompt if you have it, or describe): [prompt or summary] - What it gave me back (short summary): [output summary] - What I did with the output: [shipped as-is / edited heavily / rewrote / threw away] - How much time I think it saved me (honest guess): [minutes/hours, or "none / negative"] Do three things for me: 1. Turn the above into a clean receipt entry I could paste into a notes file. Keep it under 10 lines. Use plain text, no markdown tables. 2. Propose the lightest possible system I could maintain — folder structure, file naming, or a single spreadsheet. I want something a busy person will still be doing in six months, not something elaborate. Pick ONE recommendation, not three options. 3. Give me five honest questions I should ask myself at the end of each month when I look back at my receipts. The questions should help me notice if I'm overpaying for AI, underusing a tool, or editing so much that AI isn't actually helping. Push back if any of my inputs are vague. Ask me to sharpen them before you write the receipt.
::steps
- 01Pick ONE real piece of AI-assisted work from the past seven days. Not a hypothetical. Something you actually shipped or used.
- 02Fill in every bracketed slot in the prompt with honest answers — especially the 'time it saved me' field. Resist the urge to round up.
- 03Paste it into Claude, ChatGPT, or Gemini and read all three sections of the response. Don't skim the monthly-audit questions — they're the load-bearing part.
- 04Create the storage location the AI recommended (a folder, a spreadsheet, a notes app page) and save the cleaned receipt as your first entry. Use today's date in the filename.
- 05Set a recurring monthly calendar reminder titled 'AI audit — answer the 5 questions.' Pick a date you'll actually honor — last Friday of the month works for most people.
- 06Add ONE more receipt from a different task this week, even if it feels redundant. Two entries is when the system becomes a system.
::outcome · what should be true
- A storage location exists (folder, spreadsheet, or notes page) with at least two real receipt entries, each under 10 lines.
- A recurring monthly reminder is on your calendar with a specific date you'll honor, not a vague 'monthly.'
- You can answer in under 30 seconds: what AI tool produced what output, on what date, with what prompt, for which piece of work last week.
- You have a written list of five audit questions you'll ask yourself at month-end — not generic ones, the ones tailored to your actual usage.
::trap · the most common failure
Building a beautiful tagging system, a Notion database with seven properties, and a custom GPT to auto-categorize entries — then abandoning the whole thing inside three weeks because the friction is too high. The pilots who keep paper trails for years use plain text files in a dated folder. The pilots who don't are the ones who tried to make it elegant. Pick boring storage. Boring storage survives.
::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.
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.
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.
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