Skip to content

4.5 The Builder Loop, End to End

Time to zoom out. The agent runs gather-act-verify; you run something bigger — the Builder Loop: Vision → Context → Build → Verify → Ship. This lesson runs your quick win through the whole thing and finishes with the project live on the internet. Yes, today.

What you will learn

  • Connect the agent's inner loop to your outer Builder Loop.
  • Execute a complete build cycle on a real project without hand-holding.
  • Deploy to the public internet with GitHub Pages — free, in minutes.

Builder principle

A project isn't done when the code works. It's done when someone who isn't you can reach it.

Two loops, one machine

YOUR LOOP:      VISION → CONTEXT → BUILD → VERIFY → SHIP
                            │        │        │
                            ▼        ▼        ▼
AGENT'S LOOP:            (brief)  gather→act→verify, repeating

You set vision and engineer context; the agent turns them into work through its inner loop; you verify at the boundary and ship. Every chapter that follows upgrades one station of this machine — Chapter 5 turbocharges Context, Chapters 7–9 upgrade Build, Chapter 10 parallelizes it, Chapter 11 industrializes Ship.

Today you run the whole assembly line once, by hand, so you know what all those upgrades are for.

The run

Station 1: Vision (10 minutes, no agent)

Open your journal. Your quick win already has a brief (2.3) and done-means clauses (4.4). Tighten them into a shipping order:

SHIPPING TODAY: (one sentence — what goes live)
FOR: (who clicks it)
DONE MEANS: (your three clauses from 4.4)
NOT TODAY: (two things you're explicitly cutting — scope-killer)

The NOT TODAY line is new and mighty: pre-cutting scope beats mid-build willpower every time.

Station 2: Context

Pre-flight (3.5). Then start the session by feeding the vision forward:

Read the file SHIPPING.md — that's today's goal and scope.
Look at the current state of the project, then give me a plan
to close the gap. Plan only.

(Yes — put the shipping order in a file first: SHIPPING.md in the project root. You've just done primitive context engineering: instructions as files the agent reads instead of chat it might lose. Chapter 5 makes this a whole discipline.)

Station 3: Build

Review the plan with the four questions (4.2). Negotiate. Approve. Watch the inner loop run — steering with ++esc++ if needed, reading the gates, letting boring be boring.

Station 4: Verify

Full pyramid (4.4): agent's evidence per done-means clause, then your five-minute human pass, rude test included. Loop specific failures back. When it's green and right: commit.

Station 5: Ship

The new move. GitHub Pages turns any repository into a live website, free:

Set this project up to deploy on GitHub Pages. It's a static site
in a GitHub repo already. Walk me through anything you can't do
from here, step by step.

The agent will handle what it can and hand you the one or two clicks it can't (enabling Pages in the repo's settings). Within a few minutes you'll have:

https://YOURNAME.github.io/quick-win/

Open it. On your phone, too. That's your work, on the actual internet, with a URL you can text to anybody.

Pause on this. Three chapters ago you had never used a terminal. You just specified, directed, reviewed, verified, and deployed a website. The distance from here to "I build things for clients" is repetition and taste — not some missing gene. Post the link somewhere. You earned the flex.

Trivial deploy, sure — the point was the assembly line, not the artifact. Now run the same five stations on something real from your world this week: a small internal tool, a docs site, a script with tests. Measure the difference the stations make against your usual freestyle. That measurement is what Chapters 5–10 will keep improving.

The retro: close the loop on the loop

Ship isn't the last step — learning is. Three journal lines:

  1. Slowest station? (That's your personal bottleneck — watch it over coming chapters.)
  2. What did the agent need that it didn't have? (That answer is literally Chapter 5's syllabus.)
  3. What would you tell yesterday-you before this build?

Check your understanding

  • Draw the two loops from memory and mark where they connect.
  • What does the NOT TODAY line prevent, and at what point does it do the preventing?
  • Why did putting the shipping order in a file beat pasting it into chat?
  • What's your slowest station — and which chapter upgrades it?