Learn

This section is the first stepping stone for understanding Holon. It answers what the system is, why the key decisions were made, and how harness engineering shapes every part of the platform.

Reading path

1. What Is Holon -- the problem, the product, and the key design decisions
2. What Are Harnesses -- what a harness is, why it matters, and examples from proven systems like OpenCode and Codex
3. Holon's Harness Model -- how Holon applies harness engineering across orchestration, routing, tool projection, evidence, and self-upgrade

What this section is not

• It does not cover the full architecture in depth (see Architecture).
• It does not document operational procedures (see Guides).
• It does not cover forward-looking plans or research (those are repo-internal surfaces under docs/planning/ and docs/research/, outside the public docs website).

After learning

Once you understand the concepts here, continue to the Architecture section for the canonical high-level design, or to Tooling Taxonomy for the precise vocabulary and implementation status of each concept.

Important: The concepts described here are the design intent. For what is actually implemented today, read Known Issues and the Tooling Taxonomy implementation table after the architecture section.