The kernel, the two access surfaces (files and MCP), and how meshes connect harnesses together. Pick where you want to start.
The universal principles behind harness.os. Four base types, five cross-cutting concerns, the inner/outer boundary, subtype inheritance.
Knowledge organized as folders and markdown files. Natural for build:software and content. Any agent that can read files can use it.
Knowledge stored in PostgreSQL, accessed through MCP tools. Natural for product lifecycle, domain data, and governance queries.
How harness instances connect at runtime. Per-user meshes, cross-domain queries, the review layer for inter-mesh communication.
A detailed specification of one person's harness.os distribution. For each of thirteen subtypes: what the outer harness contains and which inner harness surface accesses it. A concrete example of the kernel applied.