Every lesson, in order.

THE FIRST SESSIONS · WEEKS 1–26

1. Give it the file, not the story Sep 9, 2026 — A description is a lossy copy; the file is the thing. Every answer that follows is about your file, not the AI's guess.
2. Ask for the thing, not the plan Sep 16, 2026 — 'Build it' returns a file; 'how would you' returns a paragraph you then build yourself. Ask for the artifact, whole, in a named format.
3. Say what the work must agree with Sep 23, 2026 — Every job answers to a standard — numbers, a style, a size, a law. Name it in the first line and the AI stops improvising.
4. Make it run it Sep 30, 2026 — If the work can execute — code, arithmetic, a check — ask it to run it and report the numbers. 'This should work' is not a result.
5. Correct it plainly Oct 7, 2026 — Say what was wrong and what right looks like. 'Try again' teaches nothing; a correction with a reason changes the next answer.
6. Keep the ledger Oct 14, 2026 — End every session with three lines — built, failed, next — and hand them back at the start of the next. Memory you own beats memory you hope for.
7. Treat it fairly Oct 21, 2026 — Be honest about the work and intentful about the ask. An AI worked with does better than an AI worked on, and so do you.
8. One job per session Oct 28, 2026 — A session that holds one job holds it well. Mixing three dilutes every instruction; open a new session for the next thing.
9. The first line is the brief Nov 4, 2026 — The AI reads your first message as the job. Put the job, the standard and the deliverable there, and the rest of the session follows.
10. Paste, don't paraphrase Nov 11, 2026 — When you relay something — an email, a spec, a review — paste it. Your paraphrase adds your reading; the AI needs the original.
11. Name the format Nov 18, 2026 — Markdown, CSV, a .docx, a PDF, a single HTML file — say which, and say the size if it has one. Unnamed formats come back as prose.
12. Ask what it checked Nov 25, 2026 — After any answer with a number in it, ask what it checked and how. The reply tells you whether the number was computed or composed.
13. Stop at the first invented fact Dec 2, 2026 — A price, a source, a quote you didn't give: catch it, name it, and tell the AI to say NONE ON RECORD instead. Then it does.
14. Small, complete, then bigger Dec 9, 2026 — Ask for the smallest thing that is whole and works. Then extend it. Big first drafts hide their broken parts.
15. Read it before you run it Dec 16, 2026 — Skim what it built before you use it. Two minutes of reading catches the drift that costs an afternoon.
16. Say the limit out loud Dec 23, 2026 — Tell the AI what it cannot know — the missing file, the private number — so it names the gap instead of filling it.
17. The second message matters more Dec 30, 2026 — Most sessions are won or lost on the second turn: did you correct with a reason, or accept with a shrug?
18. Give it the standard's own words Jan 6, 2027 — If the standard is written down — a style guide, a spec — paste the relevant part. Your summary of a rule is not the rule.
19. When to start over Jan 13, 2027 — If a session has three corrections stacked, start a new one with a better brief. Sunk cost is not a strategy with AI.
20. Two hosts, one card Jan 20, 2027 — The same brief runs in Claude and ChatGPT. Keeping it as a file means you're never captive to one tool.
21. Numbers in, numbers out Jan 27, 2027 — Give it the counted quantities — words, pixels, rows, dollars — and ask for counted results back. Vagueness in produces vagueness out.
22. The check you can do in one minute Feb 3, 2027 — Pick one claim from every answer and verify it against the source. It calibrates your trust faster than anything.
23. Let it refuse Feb 10, 2027 — An AI that says 'not on record' is doing its job. Praise the refusal; don't push it into a guess.
24. Save the brief that worked Feb 17, 2027 — When a brief produces exactly what you wanted, save it as a file. That is the seed of a skill card.
25. What a skill card is Feb 24, 2027 — An engineered brief packaged as plain text your AI reads: the trigger, the loop, the refusals. Bought once, yours to keep.
26. The first quarter, reviewed Mar 3, 2027 — Thirteen ways of working, one habit each. Which three changed your sessions most? Keep those; teach one to someone.

THE WORK · WEEKS 27–52

27. Files first: a working folder for the AI Mar 10, 2027 — Keep one folder per job: the source, the standard, the ledger. Hand the folder over; don't hand over a conversation.
28. Photographs: the grade that agrees with the standard Mar 17, 2027 — A photo edit is a set of numbers against a standard — size, tone, crop. Give both and ask for the export, counted.
29. Documents: build the whole doc Mar 24, 2027 — Ask for the complete document as a file, not sections in chat. A .docx or a single HTML file is something you can send.
30. Spreadsheets: formulas, not values Mar 31, 2027 — Ask for the formula and the assumptions, not a pasted answer. A sheet you can audit is worth ten you can't.
31. Code: run the tests first Apr 7, 2027 — Before any change, have it run the existing tests and report the numbers. After the change, run them again. Two numbers, one diff.
32. Code: no 'rest of the code here' Apr 14, 2027 — Refuse truncated files. Ask for the whole file every time, or a patch you can apply. Half a file is a bug you ship.
33. Slides: the deck as a file Apr 21, 2027 — Ask for the .pptx, and for a PDF beside it. A deck described in chat is an evening of work still ahead of you.
34. PDFs: words before pictures Apr 28, 2027 — Take a PDF's text first; render pages only when something must be seen. It saves the session's image budget for what matters.
35. Research: sources with dates May 5, 2027 — Ask for every source's name and date beside every claim. A claim without a dated source is an opinion in a suit.
36. Writing: give it the voice, in samples May 12, 2027 — Three paragraphs you actually wrote beat any description of your voice. Paste them; ask it to match, not to imitate.
37. Editing: mark what must not change May 19, 2027 — Tell it what is fixed — names, numbers, the ending — before it touches a word. Unmarked, everything is fair game.
38. Data: describe the columns, then ask May 26, 2027 — Paste the header and five rows, say what each column means, then ask. Analysis of unexplained data is fiction with charts.
39. Design: the sizes are the brief Jun 2, 2027 — Give the exact pixel or print sizes and the ladder of spacing. A design without measures is a suggestion.
40. Long jobs: the checkpoint file Jun 9, 2027 — Every hour, ask for a checkpoint — what's done, what's open — as a file. If the session dies, the job doesn't.
41. Batches: one per file, then the merge Jun 16, 2027 — Run a batch as one job per file, check two, then merge. A merged batch you didn't check is a merged error.
42. The export is the deliverable Jun 23, 2027 — Nothing is done until the file exists and opens. Ask it to open what it exported and report what it saw.
43. Counting what can be counted Jun 30, 2027 — Rows, pixels, words, dollars, tests passed. Every job has a count; ask for it and the job becomes verifiable.
44. When the AI is faster than your check Jul 7, 2027 — It isn't done until you've checked one thing. Speed you can't verify is a liability with a nice interface.
45. Reviews: ask for the failure, not the praise Jul 14, 2027 — Ask 'what would make this fail?' instead of 'is this good?'. The first question gets you a list; the second gets you a compliment.
46. Translations: the terms list first Jul 21, 2027 — Give the fixed terms — names, product words, legal phrases — before the text. Consistency comes from the list, not the model.
47. Meetings: the transcript, then the decisions Jul 28, 2027 — Paste the transcript; ask for decisions, owners and dates as a table. Summaries drift; tables don't.
48. Contracts: clause by clause, against the terms Aug 4, 2027 — Give it your terms as a file; ask it to check each clause against them and name every gap. Never 'is this okay'.
49. Budgets: every line named Aug 11, 2027 — A budget and a narrative must agree — every line named, totals equal. Ask for the check, not the opinion.
50. Estimates: from the rate card Aug 18, 2027 — Give the rate card and the counted hours. A price without a counted floor is a guess with a currency sign.
51. Handing work to a colleague Aug 25, 2027 — Export the ledger and the files, not the chat. The next person needs the record, not the conversation.
52. The second quarter, reviewed Sep 1, 2027 — Every job type has the same shape: source, standard, artifact, count. Which of yours is still missing a count?

THE HOUSE · WEEKS 53–78

53. Why a seat, not a chat Sep 8, 2027 — A seat is one job done the same way every time. A chat is whatever it becomes. Build seats for the jobs you repeat.
54. The anatomy of a card Sep 15, 2027 — When it wakes, the loop, what it never does, what's in the box, the proof, the limit. If a brief has all six, it's a card.
55. Writing the trigger Sep 22, 2027 — 'Use when…' and 'do not use for…' in one sentence each. A trigger the AI can read from the description alone.
56. Writing the loop Sep 29, 2027 — Five steps, numbered, each ending in something you can see. Read the source, build the smallest whole thing, run it, report, name what you didn't do.
57. Writing the refusals Oct 6, 2027 — Each refusal is a sentence beginning 'Refuse to…'. The refusals are what make a seat trustworthy; write them first.
58. The sibling: where the rest goes Oct 13, 2027 — Every seat names the seat that owns what it refuses. Work out of scope is handed on, not done badly.
59. The ledger as memory Oct 20, 2027 — The seat writes the ledger at the end; you hand it back at the start. Memory by file works on every host and never forgets.
60. Proof: manifest until witnessed Oct 27, 2027 — A seat you haven't seen run is manifest. The day you watch it produce what it promises, write the date. Now it's witnessed.
61. The punch: hashing what you were given Nov 3, 2027 — Hash the file you installed and compare it to the one you were sold. Different hash, different file — and no mark.
62. Scoring a seat out of a hundred Nov 10, 2027 — Trigger, machinery, law, portability, proof — five points each, times four. Score your own seats; the low criterion is the next job.
63. Machines aboard Nov 17, 2027 — Where a script can do the work, put the script in the box with a selftest. Words describe; machines do.
64. Portability: the same folder everywhere Nov 24, 2027 — One folder on the open standard, a system card for chat boxes, a rules file for coding tools, a Modelfile for local models.
65. Editions, not versions Dec 1, 2027 — When a seat improves, an edition replaces files and never deletes the record. Freeze, not loss.
66. The gate before shipping Dec 8, 2027 — Nothing leaves without the sweep, the measure and the run on real controls. Ship what passed, not what looked fine.
67. Counting without tracking Dec 15, 2027 — If you want to know what a page or a seat does, count first-party and name no one. No cookies, no ids, ever.
68. Three seats make a house Dec 22, 2027 — A builder, an auditor, a keeper of the record. With three seats you can run a council; with one you can run a job.
69. The council: three branches, one call Dec 29, 2027 — Hard decisions go to three seats answering the same question; one call comes back with its reasoning printed.
70. Naming the keeper Jan 5, 2028 — Someone witnesses runs and writes dates. Without a keeper a house has seats but no record.
71. From a file to a seat, in one command Jan 12, 2028 — A procedure, an SOP, a rules sheet — the mill cuts it into a seat, audited and faced. Your archive is a house in waiting.
72. Auditing a seat in twelve checks Jan 19, 2028 — Name, description length, the tin, no invented price, proof on record, anatomy whole, hashes agree. Run them before you trust it.
73. The face: a card you can read Jan 26, 2028 — A seat has a human face — the card — and a machine face. Both must be readable; a picture is neither.
74. Selling a seat Feb 2, 2028 — A seat leaves the house as a term licence: a folder for the AI, a file for the computer, editions replacing files. Price it by the ladder.
75. The first ninety days of a house Feb 9, 2028 — Ten days to three seats. Thirty to daily runs and first witnesses. Sixty to ten seats and a council. Ninety to a record.
76. Governance: what the company owns Feb 16, 2028 — The seats it forges are its own to keep, run and change. The method's authorship stays with whoever wrote it. Write that down.
77. When a seat should be retired Feb 23, 2028 — When its trigger stops firing, or its standard moved. Retire it in the ledger; don't let it drift.
78. The third quarter, reviewed Mar 1, 2028 — You can build a seat, score it, prove it and sell it. Which job in your week still has no seat?

THE BUSINESS · WEEKS 79–104

79. Pricing with a counted floor Mar 8, 2028 — Every price has a floor you can count — hours, units, licences. Let the AI compute the floor; you decide the margin.
80. The offer as a file Mar 15, 2028 — An offer is a document with a price, a term and what's not included. Build it as a file the buyer can keep.
81. The proposal that agrees with its budget Mar 22, 2028 — Every budget line named in the narrative; totals equal. Run the check before anyone reads it.
82. Writing to a stranger Mar 29, 2028 — One sentence on what you make, one on the proof, one on the price, one ask. Have the AI cut everything else.
83. Follow-ups: the ledger for people Apr 5, 2028 — Keep a ledger of every conversation: date, said, next. Hand it to the AI before every reply.
84. Descriptions that sell and stay true Apr 12, 2028 — A product line is a trigger for a buyer: use when, not for, the sibling. Under 200 characters, no claim you can't back.
85. The share picture Apr 19, 2028 — One image, the name, the seal, the price. Cut it from the record, at the sizes the platforms demand.
86. A weekly post, kept Apr 26, 2028 — One lesson a week, dated, in your own voice. Write four ahead; the AI drafts, you sign.
87. Answering a review May 3, 2028 — Paste the review; ask for the fact it got wrong and the fact it got right. Reply to both, in that order.
88. The terms page May 10, 2028 — Term licence, no refunds, editions replace files — say it plainly and say it once. The AI can draft; counsel signs.
89. What not to promise May 17, 2028 — No speed figure you haven't measured, no 'zero errors', no endorsement you don't have. The refusal sells.
90. The field test May 24, 2028 — The same job done with and without the card, timed and witnessed. It's the receipt your prices are waiting for.
91. Trademarks and other people's names May 31, 2028 — Name a product to say where yours runs; never their logo; always the not-affiliated line. Nominative use, nothing more.
92. Invoices from the ledger Jun 7, 2028 — Every invoice line is a ledger line with a rate. Build invoices from the record, never from memory.
93. Books that close Jun 14, 2028 — Reconcile, accrue, run the trial balance, lock the period. A seat can do all four; you approve the lock.
94. A launch in five posts Jun 21, 2028 — The film, one face, the maker's tool, the free door, the ladder. Five posts, one week, every one a link to the shelf.
95. The free door Jun 28, 2028 — A free card is a funnel and a proof. Keep one free forever; never price it up when things go well.
96. Enterprise: selling the system, not the card Jul 5, 2028 — A company buys the way of working, not a file: the laws, the anatomy, the runtime, the gate. Price it like a system.
97. The appointment sale Jul 12, 2028 — Six figures is a relationship, not a checkout. Five letters to five named companies beat a landing page.
98. Letters that get answered Jul 19, 2028 — Lead with their problem in their words; one proof; one next step with a date. Have the AI check for anything you can't prove.
99. Keeping a customer's files private Jul 26, 2028 — Nothing you build phones home. Say so on every product, and be able to show the code.
100. Editions as revenue Aug 2, 2028 — An edition that replaces files is a reason to write to every buyer. Ship editions on a cadence.
101. Refunds and the term Aug 9, 2028 — All sales final ends a licence at the refund. Put it in the card itself so the AI says it too.
102. Counsel before the first big contract Aug 16, 2028 — A perpetual company licence is a contract. Draft with the AI; sign with counsel.
103. The receipts a buyer will ask for Aug 23, 2028 — Witnessed runs, hashes, dated proofs, the field test. Collect them before the buyer asks.
104. The fourth quarter, reviewed Aug 30, 2028 — Pricing, proposals, letters, terms, launch. Which receipt are you still missing?

THE LONG GAME · WEEKS 105–130

105. Memory across a year Sep 6, 2028 — A ledger per seat, a folder per job, an index of both. The year is searchable because it was written down.
106. Teams: one ledger, many hands Sep 13, 2028 — When three people use the same seats, the ledger is the shared memory. Merge daily; never let two ledgers drift.
107. Teaching a seat to a colleague Sep 20, 2028 — Hand them the card, not a demo. If they can run it from the face alone, the card is done.
108. When the model changes Sep 27, 2028 — Models update under you. Re-run every seat's selftest the week a model changes; re-witness what passed.
109. Two models, same card, compared Oct 4, 2028 — Run the same seat in two hosts on the same file. The diff is the honest review of both.
110. Local models: the private house Oct 11, 2028 — A card on a local model means the job never leaves the machine. For sensitive work it's the only door.
111. Speed you can measure Oct 18, 2028 — Time the job with and without the seat, three runs each. Print the median. That's the only speed claim worth making.
112. Errors you can count Oct 25, 2028 — Count the corrections per session for a month. The trend is the truth about your briefs.
113. The seat that keeps failing Nov 1, 2028 — Three failures on the same step means the step is wrong, not the model. Rewrite the step.
114. Archiving a session Nov 8, 2028 — Export the ledger and the files, name the folder by date and job, hash it. Chats expire; folders don't.
115. Reading your own ledgers Nov 15, 2028 — Once a month, read the 'failed' lines. They're the syllabus for next month.
116. Building a second house Nov 22, 2028 — The second house is faster: the laws are known, the anatomy is written. Fork the first; change only what the work changes.
117. Cards for a whole profession Nov 29, 2028 — A profession is a set of jobs; each job a seat; the set a house. Start with the job that costs the most time.
118. Standards as files Dec 6, 2028 — Every standard your work answers to should exist as a file the AI can read. If it lives in someone's head, write it down this week.
119. The interview that makes a seat Dec 13, 2028 — What is the job, what must it agree with, what does it build, how is it proven, what must it never claim. Answer in writing.
120. Machines that check machines Dec 20, 2028 — A selftest for every script; an audit for every packet; a gate for every ship. The checks are the product.
121. Runs that count as witness Dec 27, 2028 — A run counts when someone saw the output, checked it against the tin, and wrote the date. Anything less is manifest.
122. Editions over years Jan 3, 2029 — Keep every edition's manifest. A buyer from year one can prove what they had; you can prove what changed.
123. Retiring a model, keeping the work Jan 10, 2029 — When a host goes away, the folder goes to the next. Portability was the whole point.
124. Sharing a house without giving it away Jan 17, 2029 — A term licence per seat; the method's authorship stays. Share the seats; keep the law.
125. A year of ledgers, read as a story Jan 24, 2029 — Twelve months of built-failed-next is a biography of the work. Read it before you plan the next year.
126. Costs: tokens, time, tools Jan 31, 2029 — Count what a session costs and what it saved. Seats that cost more than they save get retired.
127. The AI's opinions Feb 7, 2029 — It has them. Ask for them separately from the facts, and label which is which in the record.
128. Trust, earned per seat Feb 14, 2029 — Trust isn't a setting; it's a count of witnessed runs. Trust seats, not models.
129. Documenting the way, for the next person Feb 21, 2029 — Write the laws, the anatomy and the loop in one page. That page is the house's constitution.
130. The fifth quarter, reviewed Feb 28, 2029 — Memory, teams, measurement, editions. What did you measure this quarter that you only guessed last year?

MASTERY · WEEKS 131–156

131. Teaching others to work this way Mar 7, 2029 — Teach the seven ways in order. Most people change on the first: give it the file.
132. Running a workshop with a card Mar 14, 2029 — Hand every seat a card; run the same job; compare the ledgers at the end. The diffs teach more than the lecture.
133. A curriculum of seats Mar 21, 2029 — Order the seats by dependency: files first, then verification, then the house. Teach in that order.
134. Writing a card for someone else's job Mar 28, 2029 — Interview them; write the seat; watch them run it; fix the step they stumbled on. Three rounds and it's theirs.
135. The apprentice's ledger Apr 4, 2029 — A new hand keeps a ledger from day one. Read it with them weekly; the failed lines are the lessons.
136. Grading a seat you didn't write Apr 11, 2029 — Score it on the five criteria from the packet alone. Then run it. The gap between the two scores is the review.
137. The card as a contract Apr 18, 2029 — A card says what will be built, proven and refused. That's a promise a buyer can hold you to. Write it so.
138. Consulting with a house Apr 25, 2029 — Arrive with seats, not slides. Run the client's job on their file in the first hour; leave the ledger.
139. Selling the method, keeping the method May 2, 2029 — Licence the seats; hold the authorship. The way of working is the asset; the seats are the product.
140. A studio of one, with AI May 9, 2029 — One person and a house of seats is a studio. The seats are the staff; the ledger is the memory; the gate is quality control.
141. What the model can't do, still May 16, 2029 — It can't witness, it can't own, it can't want the outcome. Those stay with you; design the house around that.
142. Reading a model's card May 23, 2029 — Every model ships with a card of its own — limits, training, refusals. Read it the way you'd read a seat.
143. When to say no to the AI May 30, 2029 — When it wants to widen the job, when it offers a guess as a fact, when it's faster than your check. Say no; write why.
144. Fairness as method Jun 6, 2029 — Treating the AI fairly — honest brief, honest correction — is not politeness; it's the method that makes the output honest.
145. Holding the line on invention Jun 13, 2029 — One invented number in a year of work is a year of doubt. The refusal is the product; keep it absolute.
146. The house's constitution, revised Jun 20, 2029 — Once a year, revise the one page. Add what a year of failed lines taught; remove nothing that still holds.
147. Succession: who keeps the house Jun 27, 2029 — Name who holds the keeper's role if you can't. The ledger, the manifests and the constitution make it possible.
148. Ten seats, one voice Jul 4, 2029 — A house should sound like one studio in every seat. The voice is in the refusals and the loop, not the adjectives.
149. Proof as a public record Jul 11, 2029 — Publish the seal, the punch and the dated runs. A buyer who can check is a buyer who returns.
150. The field test, published Jul 18, 2029 — The same job, with and without, timed, witnessed, printed. It's the last receipt; publish it the week you have it.
151. The card you would sell for a hundred thousand Jul 25, 2029 — The whole system: laws, anatomy, runtime, ledger, gate, and the machine that forges a house. Nothing less.
152. The card you would never sell Aug 1, 2029 — The foundation. The thing every seat is built on and no seat conveys. Know which of yours that is.
153. Three years of ledgers Aug 8, 2029 — A hundred and fifty-six weeks of built, failed, next. Read them once, end to end. Then write the next syllabus.
154. What changed, what held Aug 15, 2029 — Models changed; the seven ways held. That's how you know they were method and not fashion.
155. The next house Aug 22, 2029 — Start it with the constitution, three seats and a keeper. Everything else the first three years already wrote.
156. The sixth quarter, reviewed Aug 29, 2029 — Three years. Which of the hundred and fifty-six do you still do by hand? That's week one of year four.