01 / PURPOSE
What it is for
Preserve regional capability through local work, selective migration, verified recovery, and explicit lineage and quorum rules.
07 · TOPOLOGY PROFILE
Metapopulation
Regional populations, verified migration and recovery.
Semi-independent demes keep local state and exchange typed propagules through directed corridors; each receiver validates transfers locally.
PARTIAL · PARTIAL · REGIONAL RUNTIME02 / SELECTION
When to use it
Choose Metapopulation when the task can be partitioned into semi-independent regions and the allowed exchange or recovery rules are known.
03 / SCIENTIFIC BASIS
Inspiration
and limits.
The model comes from patch ecology and population exchange. Software states and verified services do not establish biological equivalence or prove that regional persistence improves mission outcomes.
RUNTIME PATH
What is wired
The regional runtime persists bounded policies, reviewed migrations, extinction, recolonization, snapshots and recovery, with external adapter qualification for a minimal colonization path.
KNOWN BOUNDARY
What this does not imply
Composition does not start the loop. Receivers, local evaluators and solver adapters remain host dependencies, and global qualification is still open.
01 / MODELThe principle
The principle
and its equation
Metapopulation coordinates semi-independent demes over directed corridors. Configured regional cycles can verify migrations and selected recovery operations while each receiver keeps local authority over admission.
SIMPLIFIED FORMALIZATION
Q = Σ_g w_g·1[support_g] / Σ_g w_g ; reached ⇔ Q ≥ q ; migration(Dᵢ→Dⱼ) only on an authorized corridor
Each independent source/model group contributes at most one representative; q is the declared threshold and abstention cannot support quorum. Corridors are directed, and regional cycles apply budget, risk, provenance, and receiver-validation gates.
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 / 16
balanced PARTIAL POLICY
Coordinate regional coverage, complementary migration, diversity, and recovery under configured quorum policy.
TOPOLOGY MAP · ILLUSTRATION ONLY · NO AGENT EXECUTED
1/4 · Keep work in semi-independent regions
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
- An empty or weak source may not provide a compatible founder or rescue candidate.
- A propagule that succeeds at its source can still fail local receiver validation.
- The runtime does not infer extinction from silence or declare recolonization successful without local viability evidence.
EVIDENCE AND BENCHMARKS
What has been checked
Working slice: The autonomous regional runtime persists reviewed migration, recolonization, local evidence and recovery; 14 topology suites and a minimal external adapter qualification are recorded.
Still open: Global qualification and the quality of host-provided evaluators, receivers and solvers remain open.
Linked evidence: integration. 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 ↗