
Academy track
Work that survives the interruption

Long jobs that outlive a dropped session: what actually landed, saving before the cut, switches actually switched off, docs fixed in the same change, a one-line resume.
- 5 steps
- 2 hours 40 minutes in total
- A check you run at the end of every step
Step one is open to everyone, in full. No account, no card.
The other 4 steps open with a Vault membership, £29 a month.Join the Vault
By the end of this track you will have
- Step 1Two lines written before any work resumes: what the live system proves landed, and what the chat announced that is not there.
- Step 2A task sheet a stranger could resume from cold, a done-means line at the top of it, and nothing the job needs sitting only in a chat.
- Step 3Every temporary thing your job created listed in one register, switched off inside the system it lives in, and a line of proof beside each one, read back after the flip.
- Step 4Every sentence your last change made false already corrected, in the same sitting as the change, and a checked date at the top of the notes your AI reads.
- Step 5Every sitting ending on one resume line, a stand-down line for anything you are waiting on, and proof that a fresh chat picks the job up from that line alone.
The running example
Every worked example follows one invented case from the first step to the last: a one-person homeware shop moving its catalogue.
Who it is for
You run long jobs with AI and the session drops, the connection dies or you get called away halfway.
Who it is not for
Not for you if every job you give AI finishes before you stand up. Come back when one does not.
The steps
Each one ends with a check you run yourself. The box is yours to tick when it passes.
0 of 5 steps ticked, kept in this browser
- Step 1.Trust what landed, not what the chat says30 minutesOpen to everyone
Done means
Your two lines are written and dated above the first new instruction. Landed plus missing equals the number of rows in your master list. The landed-once total matches the count the live system shows on its own screen, and the more-than-once total reads 0. If any of those disagree, you have gaps, duplicates or strays, and nothing gets imported until you know which.
- Step 2.Save before the cut, and before any wait40 minutes
Done means
With the chat closed, you can name the next unstarted task from the sheet inside ten seconds, and every file a row names opens from the folder. If a row says saved and the file is not there, or the next task only makes sense with the chat open, the checkpoint failed. Fix it tonight.
- Step 3.Flip the switch, do not write done next to it45 minutes
Done means
Every row in the register has a proof line copied from the system after the flip, and every timed thing shows a last run from before the flip and none since. A row whose proof says off from memory is still open. So is a timed thing with any run after your flip time.
- Step 4.Fix the note in the same change25 minutes
Done means
Search the notes for the main word your last change touched. Every hit is true of the live system today, and the checked date at the top is today's. Then open the live system and confirm one of those sentences by eye. If any hit describes how things used to be, the change is not finished.
- Step 5.One line that lets anyone pick it up20 minutes
Done means
The fresh chat names the task your sheet shows as the first one not started. It asks you for nothing already written in the sheet or the notes. If it asks you to explain the job, the line, the sheet or the notes is missing something. Add it and run the test again.
I keep this tick in this browser and send it nowhere. It goes when you close the browser.
Members only
The rest of this track opens with a Vault membership.
Step one is open to everyone, in full. Every step after it opens on a member account.
Membership is £29 a month.
What comes next
Your long jobs survive a cut now. Next is making the big edits inside them reversible.
See all the tracks