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

mind / hand

concept
depth 3/3 − deeper + surface

The core principle of splitting one idea into its thinking (the mind) and its doing (the hand), so the doing can be handed off cheaply.

The framework's central operating principle: one architectural thought held at two registers—mind (the thinking: the Kamae chain at project scale, the ho's Think phase at session scale) and hand (the doing: the Kamae-5/per-ho layer at project scale, the agent task at session scale). The thinking is extracted into a durable artifact so the hand can be delegated—cheaper model, later session, agent—without re-litigating the mind. Latin epigraph: mens et manus. Diagnostic: a hand problem is execution fighting you with the design sound; a mind problem is the design itself being wrong.

The two-tier separation of thinking from coding—mind and hand. The registers are the session-scale instance of the methodology's central operating principle, which runs at two scales:

  • Project scale—the Kamae chain. Thinking artifacts (seed, system design, README, overview: Kamae 1–4) are separated from doing artifacts (per-ho documents: Kamae 5). Thinking happens in discursive sessions; the documents carry the conclusions into build sessions.
  • Session scale—the Ho ↔ AT split. Architectural thinking (the ho's Think phase) is separated from executable delegation (the AT). The ho is authored in a discursive register; the AT is executed in an agentic IDE by whatever executor is cheapest that satisfies the spec.

The same move at both scales: extract the thinking into a durable document, so the doing can be delegated, verified, and repeated without re-litigating the thinking.

This principle is named mind / hand: mind is the thinking (the Kamae chain at project scale, the ho's Think phase at session scale); hand is the doing (the Kamae-5/per-ho layer at project scale, the agent task at session scale). One architectural thought held at two registers—the thinking extracted into a durable artifact so the hand can be delegated (cheaper model, later session, agent) without re-litigating the mind. The Latin epigraph is mens et manus. The distinction earns a diagnostic phrase: a hand problem is the execution fighting you while the design is sound; a mind problem is the design itself being wrong.