Transcend and Include
Koestler's two faces
A holon has two faces - whole and part. Looked at from inside, it's a complete thing with its own contract and behavior. Looked at from outside, it's a participant in something larger. Both are true at once. That's the property that lets the same shape scale: a Capability is whole, and it's part of an Operation; an Operation is whole, and it's part of a Steward.
Transcend and include
When a larger whole forms, it transcends its parts - it does something none of them could do alone - but it also includes them. The parts don't dissolve into the whole; they keep their identity inside it. (The phrasing is Ken Wilber's: each level transcends and includes the one below.)
A Workshop transcends a Workbench but includes it. The Workshop coordinates work across people that a single Workbench can't - and the Workbench inside it is still the same Workbench, still yours, still complete. That's what lets a system grow without its parts losing their meaning. Compose without collapsing.
The 4-tier bound
The holarchy is bounded - four tiers, no more:
Workbench → Workshop → Studio → Platform.
| Tier | Scope | What it is |
|---|---|---|
| Workbench (YOU^AI) | Personal | Your individual capabilities, operations, and context |
| Workshop (TEAM^AI) | Team | Shared capabilities and collective context |
| Studio (PRODUCT^AI) | Product | Production guardrails and shipping logic |
| Platform (ENTERPRISE^AI) | Enterprise | Organizational standards and shared policy |
The architecture is identical at every tier - what changes is the scope. A Steward is complete at the Workbench scale; nested inside a Workshop it stays independent. The bound is deliberate: deep enough to model any organization, bounded enough to stay legible. An unbounded holarchy would be a fractal you could never hold in your head; four named tiers is the canon that keeps the whole thing stable.
The core package,
@fathym/steward, calls the top-level composition entity a Steward;@fathym/power-ainames the same concept by tier - Workbench, Workshop, Studio, Platform. The architecture is the same; the vocabulary differs between packages.
One shape, every product
The code is public; what compounds is the architecture. One shape runs from the engine behind fAI to the substrate under OpenIndustrial - so every product, and every new holon, is built the same way as the last. Each new holon makes the next one easier to build, because there's only ever one shape to learn.
- Before and After → - five contrasts between ordinary code and a holon