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

ri (離)

concept
depth 3/3 − deeper + surface

The stage where the form has been so internalized the practitioner moves past it, working from mastery rather than rules.

"Transcend the form." The stage where structure is internalized; and the ho shape for well-defined work: Problem → Solution → Changes → Results.

Ri Stage—Transcend the Form. > "The system is yours. Maintain it, extend it, keep it running."

Learner Characteristics

The ri-stage practitioner has internalized the methodology's principles. They don't need a template to structure their work—they naturally scope tasks, verify outcomes, document decisions, and maintain quality standards. The principles of the ho (bounded work, clear deliverables, honest self-assessment) have become how they work, not something they follow.

Ri-stage practitioners:

  • Have full operational understanding of their system
  • Can diagnose problems, propose fixes, and evaluate outcomes independently
  • Treat AI as an implementation accelerator, not a thinking partner—the thinking is already done
  • Self-assess automatically (they know what they know and what they don't)
  • Focus on maintenance, extension, and optimization rather than foundational learning

Ho Characteristics

Ri-stage work often doesn't look like a "ho" at all. The formal structure has dissolved into a lighter format—what the Kanyō pilot called "agent tasks" or simply concise problem/solution documents: […]