Run a bounded scenario.
Or connect GenOS.
Try a deterministic teaching scenario, inspect recorded campaigns, or connect a tenant-scoped GenOS endpoint for a supervised mission.
Three bounded
ways to explore.
The public scenario model below accepts only registered inputs. These teaching simulations do not call GenOS; recorded campaigns show historical evidence, while a connected endpoint runs a real mission.
Change evidence, cost, and risk in the Trinity teaching model.
Open Trinity simulation →Move quorum and dissent in the Biocenosis teaching model.
Open Biocenosis simulation →Historical mission summaries and newer Biocenosis runs, including failures and unverified outcomes.
Inspect campaigns →Every score states its question, environment, and reproduction path.
Open the registry →One bounded scenario.
Limits in view.
Try one of three deterministic teaching scenarios. They model a rule and do not execute a GenOS mission. The server accepts no user code or external tool calls. The receipt stays in this page's memory for ten minutes.
See how a fixed evidence threshold holds or rejects a claim.
Your runtime,
your mission.
Use an HTTPS GenOS endpoint and a short-lived, tenant-scoped access key with `mcp:execute_safe`. The page sends one foreground orchestration request to `genos_orchestrate` using the local executor. Prefer narrowly scoped credentials — never a production bearer token in browser code.
Your runtime,
your mission.
Connect a GenOS server and submit a mission to its local orchestrator. GenOS enforces permission and tenant scope. The request goes directly from your browser.