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

The Kamae chain

chain

6 steps, in order — start anywhere

  1. seed The founding document that states a project's problem, vision, constraints, and guiding idea, revised deliberately as it evolves.
  2. system design (Kamae 2) The document that settles how the system works—its parts, connections, and technology choices—before any code is written.
  3. README (Kamae 3) The project's front-page description, written before the code exists as if the finished thing had already shipped—so the scope has to be decided in order to write it.
  4. ho overview The build's directional plan, grouping the planned steps into themed clusters with checkpoints and named milestones.
  5. ho document The written scope for one working session—its decisions, boundaries, and checks—read by the person doing the work.
  6. state memory (Kamae 6) One always-present file per project holding where the build is, so any new session can pick it up.