Orchestration & Holarchy
Recursively coordinate work without depending on permanently fixed agent seats.
Primitive's control model treats orchestrators and workers as holons: bounded whole/parts that can create up to three children, inherit scoped authority and collapse or expand as work changes.
Imagine a team where any team lead can split one problem into at most three smaller teams. Each smaller team gets only the keys and time it needs, and when the work is done the extra structure can disappear.
The Rule of Three is a branching cap, not a requirement to always run three agents. Holarchy makes the same control pattern reusable at different scales. The programme defines leases, permits, boot receipts, heartbeats, escalation, topology changes and a gateway for consequential actions. It is formalized in Control, but should not yet be described as one fully integrated production runtime.
Holon contract
A holon has a scale, domain, charter, parent, zero to three children and a lease. A child receives authority through a scoped work permit chained to its parent's authority.
Adaptive topology
The topology is intended to expand when parallel work is justified and fold, park or close lanes when it is not. Three is a maximum local fan-out, not a fixed seat count.
Blocked work
Heartbeats and severity escalation are intended to prevent silent blocking. A blocked holon should signal its parent/orchestrator, which can escalate or allocate a repair lane within its authority.
Consequential boundary
The programme places the main gate at consequential actions such as write, merge, deploy or spend. Internal reasoning can remain freer while authority is enforced at the effect boundary.
Where this description comes from
These pointers are the authority behind the status and technical description. If implementation and documentation disagree, the canonical implementation or Control contract wins and this page should be corrected.