01 / PURPOSE
What it is for
Find bounded routes between declared capabilities, retain local traces, and admit graph growth through explicit evidence gates.
06 · TOPOLOGY PROFILE
Rhizome
Persisted capability graphs, bounded routing and verified growth.
A revisioned capability graph retains local traces, ranks eligible multi-hop routes under the selected variant policy, and admits graph changes only after provider execution and verification.
IMPLEMENTED · IMPLEMENTED · VERIFIED GROWTH PATH02 / SELECTION
When to use it
Choose Rhizome when persisted capability relationships, bounded multi-hop routes, or versioned graph growth help the mission. Route planning is callable through the session API; provider execution still requires an eligible host adapter.
03 / SCIENTIFIC BASIS
Inspiration
and limits.
The model draws on graph routing and stigmergy. The implemented route ranking and trace updates are software operations, not proof of biological equivalence or production performance.
RUNTIME PATH
What is wired
The provider-backed growth path resolves an eligible provider, instantiates a capability, verifies its output, admits it and persists the resulting route with telemetry and replay support.
KNOWN BOUNDARY
What this does not imply
The host must register real providers and verifiers. Composition alone does not start them, and an admitted route does not prove a generally correct mission outcome.
01 / MODELThe principle
The principle
and its equation
Rhizome maintains a versioned capability graph with local traces. It can diagnose gaps, rank bounded routes, and admit a capability change after budget, provider, and evidence checks.
SIMPLIFIED FORMALIZATION
Gₜ = (Nₜ,Eₜ) ; route₁(c) = arg maxᵢ score(cᵢ, need) ; ρₜ₊₁(e)= (1−λ)ρₜ(e)+Δ(e)
G is the revisioned capability graph and ρ a trace. GenOS exposes bounded path planning and deterministic scoring through a topology-session operation; a selected route does not guarantee that a provider started.
02 / VARIANTS AND USE CASES
Choose a policy
Select a variant to explore steps based on its documented contract. This illustration does not run agents or call runtime services.
LOCAL SIMULATION · ILLUSTRATIVE01 / 12
exploratory POLICY IMPLEMENTED
A mission whose needs are unknown at first and emerge during exploration.
TOPOLOGY MAP · ILLUSTRATION ONLY · NO AGENT EXECUTED
1/4 · Diagnose the capability gap
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.
FAILURE MODES
What can go wrong
- A route can be absent, stale, or over its cost and trust limits.
- A signed admission receipt does not prove an external worker started.
- Route selection and graph admission do not by themselves promote a mission result.
EVIDENCE AND BENCHMARKS
What has been checked
Working slice: The provider-backed path resolves, executes, verifies and admits a capability before adding it to persisted routing; the 36-suite Rhizome profile includes an SQLite growth-and-routing E2E.
Still open: Hosts must still register real providers and verifiers; composition alone does not start them or prove mission quality.
Linked evidence: end-to-end. A policy for a variant does not establish a successful end-to-end mission or comparative performance.
No topology-specific benchmark protocol is linked from this profile.
Read the latest evidence ↗Read the product completion contract ↗