The Kamae chain
chain6 steps, in order — start anywhere
- seed The founding document that states a project's problem, vision, constraints, and guiding idea, revised deliberately as it evolves.
- system design (Kamae 2) The document that settles how the system works—its parts, connections, and technology choices—before any code is written.
- 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.
- ho overview The build's directional plan, grouping the planned steps into themed clusters with checkpoints and named milestones.
- ho document The written scope for one working session—its decisions, boundaries, and checks—read by the person doing the work.
- state memory (Kamae 6) One always-present file per project holding where the build is, so any new session can pick it up.