Frame the mission
Turn a request into explicit work, constraints, budgets and evidence obligations.
THE RUNTIME · A WORKING MODEL
An execution history
you can return to.
GenOS is an open-source runtime for supervised multi-agent work. Supported paths can version workspace state and retain selected receipts. Recovery, verification and promotion depend on the selected mode, adapter and available evidence.
REFERENCE LIFECYCLE · STEPS MAY HOLD OR FAIL
Choose an organization
Select a topology and compatible workers for the coordination problem at hand.
Version the state
Capture a snapshot and keep candidate trajectories isolated when the mission calls for comparison.
Execute under supervision
Run through declared permissions, workspace boundaries, resource budgets and observable handoffs.
Inspect the evidence
Review outputs with their provenance and apply the relevant validation and promotion gates.
Promote, hold or recover
A result can be promoted, rejected, left uncertain or used to start a new branch from a known state.
STATE IS THE DIFFERENCE
From one mutable
timeline to branches.
ONE TIMELINENew work overwrites context
VERSIONED STATEBranches can be compared and replayed
DESIGNED WITH BOUNDARIES
Every capability has a contract.
Tool access follows explicit leases and known allow-lists. Admission can refuse a mission before any worker runs.
Execution can stop when its declared event, time or resource budget expires.
A worker receipt or completed cycle can still require review. Promotion rules depend on the path and profile.
Snapshots cover supported state; they do not automatically restore external effects or processes. A registered topology does not activate every listed capability.
Read the topology contracts →