Ho System Index
Master navigation map for the complete Ho System framework.
How to Use This Index
Every document in the Ho System has an ID in the format {layer}.{sequence} — the layer number locates it in the hierarchy below, the sequence number reflects reading order within that layer. IDs appear in each document's frontmatter and throughout this index.
The layers, each with a distinct role:
| Layer | What it contains | Who needs it |
|---|---|---|
| 0. Repo Meta | The map, the changelog, the contribution guide | Anyone orienting to the repository itself |
| 1. Foundation | Core philosophy and evidence | Any new reader; the conceptual anchor |
| 2. Structure | Specifications for how the system works | Practitioners and ho authors |
| 3. Templates | Fill-in structures for hos, devlogs, seeds | Anyone starting a session or project |
| 4. Guides | Practical orientation | New practitioners |
| 5. Examples | Concrete instances of the methodology | Learners and facilitators |
| 6. Agent Tasks | Delegated implementation specs | AI agents and their supervisors |
| 8. Practitioner | The operating discipline and environment architecture | Practitioners configuring their practice |
| 9. Skills | The skill catalog that operationalizes the methodology | Practitioners and their agents |
Layer 7 (Project Artifacts) is retired (2026-07-03, ho-09): its occupants were
archived or live gitignored in ho-process/. The number stays dead — no new 7.x IDs are
assigned (forward-only).
Entry points by intent:
- New to the system? → Start at 1.1
- Starting a project? → Read 2.1 → 2.2 → open 3.2
- About to run a session? → Go to 3.1
- Unclear on a concept? → Scan Layer 2 by topic
0. Repo Meta
The repository's own navigation and record-keeping.
| ID | Document | Description |
|---|---|---|
| 0.1 | Ho System Index | This map — master navigation for the framework |
| 0.2 | Changelog | The framework's version story — structural changes, newest first |
| 0.3 | Contributing | What contributions the framework wants and how to send them |
1. Foundation
Core philosophy and evidence base. Everything else is grounded here.
| ID | Document | Description |
|---|---|---|
| 1.1 | The Ho System | Full methodology overview — the definitive introduction |
| 1.2 | Foundations & Evidence | Intellectual basis, research grounding, and pilot evidence |
| 1.3 | Glossary | The framework's working vocabulary — every term, with its defining document |
2. Structure
Conceptual specifications. Ordered to follow the practitioner's actual experience — framing before building, unit before progression, practice before quality.
| ID | Document | Description |
|---|---|---|
| 2.1 | Kamae: Project Framing | The pre-ho phase — from idea to buildable plan |
| 2.2 | Project Arc | How hos sequence into complete projects |
| 2.3 | Ho Structure | The fundamental unit of work — what a ho is and isn't |
| 2.4 | Shu-Ha-Ri Progression | How the system adapts as the practitioner develops |
| 2.5 | Tiered Understanding | Framework for calibrated comprehension |
| 2.6 | The Devlog | Structured reflection as a learning practice |
| 2.7 | Verification Practices | Quality assurance in AI-augmented development |
| 2.8 | Ho-Task Decomposition | How hos and agent tasks compose one architectural thought |
| 2.9 | Artifact Type Registry | The taxonomy of every artifact type the practice produces |
| 2.10 | Kamae Addenda | Mid-build architectural decisions without rewriting history |
| 2.11 | Design Work | Design tuning — the design method; design that happens partly outside the chain |
| 2.12 | External-Project Contribution | Running Ho against someone else's codebase |
| 2.13 | The Idea Log | The forward-only idea/feature backlog, reviewed at every ho boundary |
3. Templates
Reusable document structures. Start with the selection guide if you're unsure which to use.
Navigation
| ID | Document | Description |
|---|---|---|
| 3.1 | Template Selection Guide | Which template to use and when |
Kamae (Project Framing)
| ID | Document | Description |
|---|---|---|
| 3.2 | Project Seed Template | First Kamae document — project philosophy and framing |
Ho Sessions
| ID | Document | Description |
|---|---|---|
| 3.3 | Shu Ho Template | Prescriptive learning sessions |
| 3.4 | Ha Ho Template | Decision-driven development sessions |
| 3.5 | Ri Ho Template | Practitioner-level recording format |
| 3.9 | Design Ho Template | In-chain wrapper for landings and design-session batches |
Devlogs (Reflection)
| ID | Document | Description |
|---|---|---|
| 3.6 | Shu Devlog Template | Structured reflection for shu stage |
| 3.7 | Ha Devlog Template | Decision record for ha stage |
Delegation
| ID | Document | Description |
|---|---|---|
| 3.8 | Agent Task Specification | Delegating implementation work to AI |
4. Guides
Practical orientation for new and continuing practitioners.
| ID | Document | Description |
|---|---|---|
| 4.1 | Getting Started | Draft — the first arc, concretely: install, seed, walk the chain, open and close the first ho |
| 4.2 | Choosing a Project | Draft — what makes a good first project, sizing, the black-box discipline, worked shapes |
| 4.3 | AI Collaboration | Draft — the operating posture: planning mode, watching, bounded sessions, verification, ownership |
5. Examples
Concrete instances of the methodology in practice.
| ID | Document | Description |
|---|---|---|
| 5.1 | Learning Process Reflections | Post-project learning reflections |
| 5.2 | Kanyō Pilot | Production falcon detection system — the founding project |
6. Agent Tasks
Delegated implementation tasks handed to AI agents.
| ID | Document | Description |
|---|---|---|
| 6.1 | Integrate Verification Practices | Task spec for verification integration into the framework |
| 6.2 | Integrate Ho-Task Decomposition | Task spec for placing the ho-task-decomposition document into the framework |
| 6.3 | Fable Audit Brief | Historical — the 2026-07 framework-audit brief handed to Fable |
| 6.4 | Fable Audit Prior Findings | Historical — prior-audit findings packaged as context for the Fable audit |
| 6.5 | Opus Audit Merge Brief | Historical — the merge-session brief that turned audit findings into decisions D1–D20 |
7. Project Artifacts — retired
Retired 2026-07-03 (ho-09). The layer held active project seeds and working documents;
its occupants were archived to practitioner/archive/ or live gitignored in
ho-process/. No new 7.x IDs are assigned.
8. Practitioner
The operating discipline and the environment it runs in — practitioner-scope, not project-scope.
| ID | Document | Description |
|---|---|---|
| 8.1 | The Operating Discipline | The operational rules a practitioner works under — verification, posture, workflow |
| 8.2 | Operating Discipline — Rationale | The philosophy and argument grounding the operational rules |
| 8.3 | Environment Architecture | How the practitioner's setup fits together — the four locations and their roles |
| 8.4 | Module Structure | The ~/.claude/ layout — files, scopes, and what imports what |
9. Skills
The skills that operationalize the methodology. Individual skills are cataloged by 9.1, not indexed row-by-row.
| ID | Document | Description |
|---|---|---|
| 9.1 | Ho System Skills — Overview | The skill catalog — what exists, what each one does, and where it sits |
Rendered from the corpus, verbatim · source on GitHub →