2.5
The Ladder
Why this exists
Everything so far has been about how the thing works. This lesson is about where it goes — a map of the whole territory, so that from here on you always know which part of the problem you're standing in.
It also settles something. Before you started this, you sketched out five levels of what you could do with AI. That sketch was almost entirely right, and it's worth being told that plainly. There's exactly one thing on it that needs moving, and moving it takes the biggest obstacle off the board.
The idea
Five rungs. Each one adds exactly one new ability.
| Rung | What it does | What's new |
|---|---|---|
| 1 · Ask | You ask, it answers | Nothing yet — it just talks |
| 2 · Act | It uses tools and touches real things | It can do, not just say |
| 3 · Remember | Files and structure give it your world | It knows your context without being told again |
| 4 · Repeat | Skills — teach it once, it does it forever | Consistency, without you re-explaining |
| 5 · Run alone | Agents — it works while you're not there | Your absence stops being the bottleneck |
Nothing skips. Rung 4 without rung 3 is a skill with no context to work in. Rung 5 without rung 4 is an agent improvising every time, which is a different thing from an agent working.
The rest of this course is just climbing it. Level 1 already put you on rung 2 — you've been there all week. Level 3 is rung 3. Levels 5 and 6 are you working at rungs 2 and 3 on things that matter. Level 7 is rungs 4 and 5.
The one that needs moving
Your sketch had five levels, and four of them map straight onto this: research, connecting tools, skills with files and folders, and agents running 24/7. That's genuinely the shape of it. Most people who've been at this for months couldn't draw it that cleanly.
The one to move is coding. You had it as rung four — a wall between skills and agents, and the bit you said you had no clue about.
It isn't a rung.
Coding isn't a level you climb to. It's something that starts happening on its own the moment you're on rung 2, because writing and running code is one of the tools it uses. You'll have code running on your machine in week two. You won't have written it.
What you actually need is a different skill, and a much smaller one: reading code well enough to tell whether it's doing what it claims. That's it. Not writing it from memory, not knowing a language, not the four-year version. Reading, and checking. And you already know how to do the hard part of that, because checking whether something does what it claims is your whole professional instinct — you're just going to point it at a different kind of document.
So the wall you've been standing in front of isn't there. What's there is a habit, and you started building it in lesson 2.1.
Where each rung breaks
| Rung | Fails when | Covered in |
|---|---|---|
| 1 · Ask | It confidently makes something up | 2.1 |
| 2 · Act | It's pointed at the wrong folder and can't see what you're asking about | 1.4 |
| 3 · Remember | Your structure is a mess, so it reads everything and understands nothing | Level 3 |
| 4 · Repeat | A skill was written once, never tested, and quietly does the wrong thing | Level 7 |
| 5 · Run alone | Something runs unattended and nobody's watching | Level 6 |
The pattern is the point: the higher you climb, the longer it takes to notice you've fallen. At rung 1 you see the bad answer immediately. At rung 5, something's been wrong for three days and you hear it from someone else. That's why Level 6 is the biggest level in this course.
Do
- Make a file called
my-ladder.md. - Write out the five rungs in your own words. Not copied — your words. If you can't phrase a rung yourself, that's the one to reread.
- Now take five real tasks from your own working week. Actual things you do. Put each one on the rung it belongs to.
- For each, write one line: what would have to be true for it to move up a rung?
- Pick the one you most want to climb. Note which level of this course covers it.
- Last: find one thing you'd have called "coding" before this lesson, and write one line on whether it still is.
Step 3 is the one that makes it stick. An abstract ladder is a diagram; a ladder with your actual Tuesday on it is a map. And step 4 is quietly the most useful thing in this lesson — "what would have to be true" is the question that turns a nice model into a plan.
Done when
That's week one done. Next week you get your hands on the thing.