The layer above Convergence Studios' five standalone systems. Not a submission itself — the umbrella that proves the five submissions are one operating environment.
01 discovers. 02 operates. 03 remembers. 04 decides. 05 builds. Genesis OS asks all of them at once — and never lets any of them depend on it.
A federated mission takes a Studio Head objective, dispatches it across the standalone systems through one-way contract adapters, aggregates their evidence without re-verification (every item keeps its producing system and the verification state that system computed), assembles a governed proposal for the decision system, passes the Studio Head's authorization through to 04's own durable signal, and closes with a dossier promoted to DataHub carrying cross-system lineage — one decision traceable through four independent evidence systems in a single graph.
Objective → plan → [01 signal ∥ 02 operational ∥ 03 institutional] → aggregate → proposal → 04 governance → Studio Head authorization (pass-through) → Authorized Software Objective → 05 construction → dossier
| Rule | What it means in code |
|---|---|
| No standalone depends on Genesis OS | Adapters are HTTP consumers of public APIs; contracts are vendored documents; no code is shared, and a sibling never calls back. |
| No re-verification, no upgrades | VERIFIED / CONFLICTED / CONTESTED / WEAK pass through exactly as produced into the proposal 04 governs. |
| No autonomous authority | Sibling investigations are evidence, closed with a machine-noted rejection (bookkeeping, not judgment); the only approvals in a mission are the Studio Head's own. |
| Honest degradation | A capability that is down is recorded UNAVAILABLE and the mission continues or fails INCOMPLETE — never fabricated evidence. The masthead reports partner substrates from observed calls, not configured strings. |
This is the Deterministic Scaffold's composition rule at hackathon scale: engines built independently, joined by contract, judged by their own gates, with the human authority boundary held in exactly one place. The standing rule for the whole Genesis build was that every included component gets built and run for real — Temporal, NATS, PostgreSQL, DataHub, the observability trio, hosted on Cloud Run with its memory — never downgraded to "optional" or "staged"; conflicts with the locked architecture get surfaced, not self-resolved.
Four curated missions plus free-form objectives: render-capacity expansion (the continuity anchor), title greenlight, operational crisis response, strategic response. Sequential-active; every completed mission stays on the ledger.
cd ops && docker compose up -d && cd .. # PG · NATS · Temporal · Redis · MinIO python3.12 -m venv .venv && .venv/bin/pip install -e ".[dev]" cp .env.example .env # sibling API URLs + Vertex config .venv/bin/uvicorn app.main:app --port 8040 # federation API .venv/bin/python -m app.workflows.worker # durable mission worker cd frontend && npm install && npm run dev # the bridge on :3040
GENESIS_MOCK=1 runs the loop from a clean clone. Live mode expects the
sibling systems running from their own repos.
Built August 12–26, 2026 for the Google Cloud Agentic Cinema hackathon. Parked on September 12, 2026, when the league took the table. The repositories stay public.