← System handbook

Holarchy & Rule of Three

Partialsystem

Bound recursive organisation so Primitive can expand without becoming an uncontrolled swarm.

TL;DR

A holon is both a whole and part of a larger whole. Authority-bearing orchestrators may create 0–3 direct child holons. Three is a hard maximum, not a target, voting rule or mandatory team size. Scale, authority, spend and worker concurrency are separate constraints.

ELI5

A department can act like one team while also being part of a company. If it needs help, it can create up to three smaller teams. Those teams can do the same, but nobody gets unlimited keys or unlimited subteams just because they can recurse.

Synthesis

The Rule of Three bounds local fan-out while recursive levels provide scale. Rolling three-level topology windows stop 3^n explosion, and explicit OPEN/FOLD/PARK/CLOSE operations let unused structure disappear. Cryptographic permits/leases are about provenance and enforceable delegation, not cryptocurrency or voting.

Scale

Canonical orchestration scale

Principal → Unit
PrincipalHuman/root authority
UniversalWhole operating environment
ClusterMajor programme/domain branch
GalaxiasFamily of systems
SystemBounded coherent system
CellLocal operational group (formerly Local)
UnitSmallest authority-bearing orchestrator
Workers / RunsExecution resources unless separately delegated
Topology

Three is a cap, not a quorum

A holon may have zero, one, two or three direct authority-bearing children. Descendants cannot widen the inherited cap. The default unconstrained rolling three-level population is 1 + 3 + 9 = 13, and a parent can impose a lower topology-window cap.

ValidMeaning
0 childrenNo delegated orchestration needed
1 childOne bounded lane
2 childrenTwo independent/parallel lanes
3 childrenMaximum direct fan-out
Lifecycle

Topology should contract as readily as it expands

Topology decisions
OPENCreate justified capacity
KEEPCapacity remains justified
FOLDAbsorb work without erasing history
PARKSuspend while retaining identity
CLOSEEnd future authority
Delegation

Permits, leases, boot receipts and gateways

Delegated authority path
Parent authorityWhat the parent actually holds
Scoped permit / leaseNarrower paths, budget, expiry, child cap
Boot receiptRequired context/tools acknowledged
Gateway / kernelDeterministic admission
Effect + receiptTraceable consequential transition
Explicit non-decisions

What Rule of Three does not mean

  • It is not a requirement that three agents agree.
  • It is not a voting quorum.
  • It is not a Primitive cryptocurrency or staking system.
  • It does not make every UI/data structure use groups of three.
  • It does not make model intelligence a source of authority.
Keep reading

Related pages

Reference / evidence

Canonical sources

These pages are explanatory read models. Where wording conflicts with implementation or a Control decision, the linked implementation/decision is authoritative and this page should be corrected.