What it is for
Compose specialist capabilities around a host that keeps authority, resource allocation, and lifecycle state visible.
An orchestrating host composes specialist symbionts around mission capabilities, governs their lifecycle, and constrains execution through resource and capability contracts.
PARTIAL · PARTIAL · HOST VETO VERIFIEDCompose specialist capabilities around a host that keeps authority, resource allocation, and lifecycle state visible.
Choose Holobiont when a mission needs a set of bounded specialist services coordinated by a host. Every capability and executor must be supplied under the run contract.
The host–symbiont relationship is an ecological analogy translated into contracts, provisioning, execution, and health records. It does not imply automatic immunity or biological equivalence.
The shared mission runtime connects admission, supplied capabilities, independent verification, immune gates, quotas, health sanctions and atomic contribution/memory updates.
The host adapters still supply physical isolation and real measurements. Passing the bounded runtime does not demonstrate biological symbiosis or a general longitudinal gain.
The protocol must record host authority, admitted resident capabilities, resource allocation, action receipts, health, contribution and succession. A supplied capability does not imply that an immune veto ran.
Read the canonical mission protocol ↗The longitudinal benchmark is a protocol, not a completed comparative campaign. The historical four-role composer does not automatically use the persistent host runtime.
Read the dedicated benchmark protocol ↗A host coordinates specialist symbionts under capability and resource contracts. The host sets boundaries and composes skills; veto or immune mechanisms are not guaranteed in every execution path.
Cₘ ⊆ ⋃ᵢ Cᵢ ; allocationᵢ ≥ 0 ; Σᵢ allocationᵢ ≤ budgetₘ
Required capabilities Cₘ must be covered by symbiont capabilities Cᵢ. Budget compliance depends on the allocation contract; this formula does not model full safety.
Select a variant to explore steps based on its documented contract. This illustration does not run agents or call runtime services.
Decompose a system into highly specialized symbionts around a coordinating host.
The drawing changes with the topology and variant to show their documented structure and policy. It is an explanatory model; maturity labels and runtime limits still apply.
This status follows the maturity of the variant policy in GenOS’ canonical catalog. “Policy implemented” does not certify end-to-end execution: topology maturity, required adapters, permissions, and evidence remain separate runtime conditions. This illustration does not run agents; its selector is manual. In the runtime, mission signals may select a preset automatically when its preconditions are met.
Working slice: The shared mission runtime connects capability admission, independent verification, immune gates, quotas and atomic contribution/memory updates; the 55-script suite includes robust host-veto cases.
Still open: Physical isolation and measurements remain adapter responsibilities; no general or longitudinal gain is established.
Linked evidence: integration. A policy for a variant does not establish a successful end-to-end mission or comparative performance.
Read the benchmark protocol ↗Read the latest evidence ↗Read the product completion contract ↗