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

phase

concept
depth 3/3 − deeper + surface

A named stage of work, used at three scales—the whole project's progression, a cluster of related sessions, and the steps within a single session.

Used at three scales, context-disambiguated: (1) arc phases—the universal progression (orientation → foundation → construction → integration → operations); (2) overview phases—project-specific clusters of hos sharing a theme, the primary cognitive unit of Kamae 4, each ending in a release tag; (3) session phases—Think, Execute, Reflect inside a ha ho.

The Five Phases. Every project arc passes through five phases. They're not rigid boundaries—work blends between them—but the progression is consistent.

Orientation (Hos 0–0.5)

Focus: Tooling, environment, mental models.

The learner gets their bearings. What tools will they use? How does the development environment work? What's the shape of the project? Orientation hos are almost always shu-stage—the learner is encountering new tools and needs guided setup.

The deliverable isn't impressive. It's "the tools work, I can run a test, I know where things live." But without it, everything that follows is unstable.

Kanyō evidence: Ho 0.5 (Tool Mastery) covered Claude Code workflow, Git basics, and development environment setup. Ho 00 (Overview) was the project plan itself—the first output of Kamae.

Typical duration: 1–2 hos. Shorter for experienced practitioners starting a new project; longer for learners encountering an entirely new tool ecosystem.

Foundation (Hos 1–2)

Focus: Project structure, core infrastructure, first working component.

The learner builds the skeleton. Directory structure, configuration system, logging, testing framework, the first piece of real functionality. Foundation work is unglamorous but load-bearing—everything that follows depends on these decisions. […]