Module 1 recap
Two minutes to lock in the module: what you can now see, what you set up so you could see it safely, and what module 2 does next.
You started with a statement you had probably never read line by line. You are ending with a month in plain categories, one number named, and a way of working that does not hand your account details to anyone.
The order mattered. Privacy came first: Incognito, a deliberate decision at Settings > Privacy, and a redaction habit that removes what identifies the account and keeps what describes the money. Then the wall almost nobody clears alone: an upload needs an unencrypted PDF, and a locked statement opens with your bank's own convention and prints to a clean copy. Then the win: a fixed category list, transfers separated from spending, every total showing its lines. Then one number, stated plainly, with the moralising banned in the prompt itself.
That last habit is the one to carry. Every prompt here tells Claude what it may not do, and that is what makes the output something you can rely on rather than something that merely sounds good.
Where this goes next
Module 2, Make it true. The three ways an AI silently gets money wrong: screenshots too small to read properly, arithmetic done in its head instead of checked, and totals that look identical whether right or wrong. You get the one sentence to append to every money calculation, and a spot check that takes under a minute.
What you just learned
- Privacy is a setup, not a disclaimer: Incognito, a deliberate privacy setting, and a redaction rule applied in seconds.
- A locked statement is the commonest dead end, and printing to a fresh PDF clears it.
- A month in categories is trustworthy only when every total shows its lines and unreadable lines are quoted.
- The uncomfortable number is a measurement, named without advice attached.
practice
Open Claude Cowork on your own computer and try this on real files. Each module ends with a checkpoint where you submit what you made.
Open in ClaudeNext
Three ways it goes wrong