arc
conceptThe full sequence of steps that carries a project from first idea to running system.
The complete sequence of hos that takes a project from idea to running system; "a narrative of building" with a beginning (Kamae), a characteristic phase shape, and a planned-versus-actual evolution the numbering makes legible.
What an Arc Is. A project arc is the complete sequence of hos that takes a project from idea to running system. It's the shape of the work over time—not a task list, not a curriculum, but a narrative of building that includes plans, surprises, pivots, and the gradual transfer of authority from author to learner.
An arc has three defining characteristics:
It has a beginning and an end. The beginning is [[kamae-project-framing|Kamae]] (framework/structure/kamae-project-framing.md)—the framing work that produces the plan. The end is a working system. Not a perfect system, not a feature-complete system, but something that runs in production and does what it was designed to do.
It follows a characteristic shape. Regardless of domain, arcs move through the same phases: orientation → foundation → construction → integration → operations. The phases may be different lengths, but the sequence is consistent. You can't integrate before you've constructed, and you can't construct before you've laid the foundation.
It evolves. The plan written during Kamae is a starting point, not a script. Real arcs branch, expand, and compress as the project demands and the learner develops. The gap between the planned arc and the actual arc is itself meaningful—it tells the story of what was harder than expected, what was easier, and where the learner's growth outpaced or lagged behind the plan.
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. […]