Ho System, Actually Build the software. Develop the judgment.

build record

definition
depth 3/4 − deeper + surface

A running, add-only list at the bottom of the build plan recording what each step actually finished and where the build stands.

The append-only log grafted onto the tail of the K4 ho overview: one entry per ho close and per replan checkpoint, each shaped as a state-summary block, never rewritten. Cold and forward-only—the human-facing, canonical ledger of what a build actually did, the counterpart to the hot working-memory handoff.

Ho Overview. What it is: The sequence plan. What hos are needed, in what order, with what dependencies. This is the project arc made concrete—it turns the System Design and README scope into a buildable sequence of bounded sessions.

The Ho Overview is possible precisely because the upstream documents have already made the hard decisions. You can't plan a build order for a system whose architecture is undecided. You can't scope sessions for a project whose boundaries are undefined. The Seed established the core idea. The System Design committed to architecture. The README defined scope. The Ho Overview sequences the execution.

What it's NOT: The individual hos themselves. The Ho Overview says "Ho 3 implements the backup workflow: wake, SSH, syncoid, verify, shutdown." It does NOT provide the step-by-step instructions for doing that work. Those come from writing the actual ho using the appropriate template.

What "done" looks like:

The Ho Overview should define: […]