The Four Layers: Habitat, Project, Mesh, Harness

Choose your door

• Builder — Builder Track: sort real objects onto layers.
• Architect — Architect Track: the stack and the flywheel.
• Translator — Bridge below.
• Validator — Gates at the bottom.

The four layers (bottom-up)

And the flywheel that connects them: lessons flow up (a hard-won lesson in any project gets packaged into the harness as a skill or doctrine), and doctrine flows down (every fresh session inherits the harness, zero re-explaining). The whole point: memory lives in the builds, not in any one chat, machine, or vendor.

Translator Bridge

A school district. Habitat = the buildings — a school is not its building; if one floods, classes move. Project = each course, with its own binder and gradebook (Lesson 1's chassis). Mesh = the schedule and staffing rules — who teaches, who substitutes, who signs off on grade changes. Harness = the district's teaching philosophy and teacher-training program: no single course owns it, every course inherits it, and when one teacher discovers a technique that works, the training program absorbs it and every future classroom gets it.

Builder Track (DO FIRST)

Sort these onto layers 1–4 (answers at the bottom of the lesson; no peeking until committed):

1. RESUME.md in the repo of a tool I built
2. The nightly-diary-sweep scheduled task
3. The rule "only I merge"
4. A fresh VM stood up for a clean-state kill test
5. The teaching skill that produced this lesson
6. The anti-false-positive law in that tool's tests
7. START_HERE.md

Then walk one real flywheel loop: find a lesson in this tier that started life inside one repo (Lesson 3's law, in a tool I built) and name where it lives now (this lesson set — harness).

Architect Track (MODEL FIRST)

        ▲ lessons up                    doctrine down ▼
   L4 HARNESS  ── skills, START_HERE, KB, diary ── inherited by every session
   L3 MESH     ── roles, laps, PR→CI→human gate ── how any work moves
   L2 PROJECT  ── repo + chassis, born together ── where work lives
   L1 HABITAT  ── disposable machines, VMs      ── where work runs

Two design insights. First, each layer protects the one above from the one below: projects don't care which machine (L1 is cattle); the mesh doesn't care which project (same loop everywhere); the harness doesn't care which agent (doctrine is text). Second, the harness is the flywheel's hub, which makes it the highest-value target — the adversarial review caught exactly that: the most-leveraged layer had the least protection (no git, no backup). The fix was a private repo for the shared doctrine — the harness now wears the same chassis it prescribes. A system that exempts itself from its own laws isn't a system yet.

Validator Gates

1. Gate 1: Name the four layers bottom-up and give one resident of each.
2. Gate 2: Which direction do lessons flow, and which direction does doctrine flow? What's the payoff of that loop?
3. Gate 3: Why is "the harness wasn't in git" a more serious finding than a bug in any single project?
4. Gate 4 (own words): Explain "machines are cattle" to someone who keeps everything on one laptop.

Builder answers: 1→L2, 2→L4, 3→L3, 4→L1, 5→L4, 6→L2 (enforced by L2's CI; the pattern it teaches lives in L4), 7→L4.