Concepts
One shape, at every scale. These pages explain what a holon is, how you define and run one, and why the same shape holds from a single Capability to a whole Platform.
What is a Holon
Every entity is whole and part at once - it runs on its own and composes into something larger without losing what it is. The two tendencies (Self-Assertion and Integration), and the no-aggregation rule that makes composition safe.
Builder, Runner, Engine
How a holon goes from definition to execution. You define with the builder, run with the runner, and never touch the engine. Types flow from your schemas.
Transcend and Include
Why a larger whole never erases the smaller one, and how the 4-tier bound - Workbench, Workshop, Studio, Platform - keeps the holarchy stable.
Before and After
Five contrasts: a function vs a Capability, a service class vs a Steward, a raw LLM call vs an Agent. What a holon carries that ordinary code doesn't.
Synaptic-Oriented Programming
The practice: you declare what things are and what they do; structure emerges from how they compose. Guardrails as part of an entity, not a gate in front of it.
Once the concepts click, the Patterns show the per-holon-type building blocks, and the Guides walk through creating and testing your own.