ECOSYSTEM · EXTERNAL REPOSITORIES

24 repositories,
each with a clear status.

Each card connects the original repository to GenOS: current relationship, concrete code impact, and resulting capability. For projects not integrated, the capability is explicitly prospective.

24source repositories

3in pinned revision

3in local v3

18not integrated

Reviewed October 4, 2026. GenOS revision pinned by this site: 5091f706; Cedar and the two additional SHEV sensors are in local v3 through commit b0e64d6e. A similar GenOS mechanism does not imply use of the external repository.

01 / 06

Evolution and causal learning

Ideas for choosing organizations, evolving bounded heuristics, and assessing effects.

01 / 24Not integrated

icaros-usc/pyribs

Relationship to GenOS: Quality-diversity research candidate for Morphogenesis, Biome and Metapopulation.
Observed impact: No direct code impact: GenOS selects topologies with its own services, without a pyribs archive.
Potential experiment: Could keep a repertoire of organizations differentiated by cost, robustness and mission fit, then select a measured candidate.

Open repository

02 / 24Not integrated

SakanaAI/ShinkaEvolve

Relationship to GenOS: Reference for bounded evolutionary search around GVX heuristics.
Observed impact: No direct code impact: ShinkaEvolve does not generate or promote GenOS heuristics.
Potential experiment: Could propose variants of worker selection or budget allocation while GVX independently evaluates and approves promotion.

Open repository

03 / 24Not integrated

jennyzzt/dgm

Relationship to GenOS: Research comparison for self-modifying coding-agent lineages.
Observed impact: No direct code impact: GenOS already keeps AgentDNA, forks and lineages without running DGM.
Potential experiment: Could serve as a controlled rival for GVX on identical tasks and budgets, including intermediate candidates in the comparison.

Open repository

04 / 24Not integrated

py-why/dowhy

Relationship to GenOS: Candidate method for estimating whether SHEV interventions caused observed effects.
Observed impact: No direct code impact: GenOS records and verifies effects, but does not run DoWhy estimators or refutation tests.
Potential experiment: Could estimate and challenge an intervention effect when longitudinal data and explicit causal assumptions are available.

Open repository

02 / 06

Independent evaluation

External comparisons, generated counterexamples, and agent benchmarks.

05 / 24Executable pilot

UKGovernmentBEIS/inspect_ai

Relationship to GenOS: Optional external Python evaluation harness, separate from the GenOS runtime.
Observed impact: Added four deterministic tasks and three paired arms: model alone, fixed topology and Morphogenesis. The scorer sits outside GenOS.
What GenOS can do: Can run an independently scored comparison once a real multi-arm runner is supplied; no model or topology result is published yet.

In GenOSbenchmarks/inspect-ai/

Open repository View GenOS code ↗

06 / 24In GenOS code

dubzzz/fast-check

Relationship to GenOS: Direct backend development dependency for property-based tests.
Observed impact: Added seeded generated cases for MCP leases, local Morphogenesis limits and promotion transitions, with counterexample shrinking.
What GenOS can do: Can find short sequences that violate these safety invariants. Test adapters do not prove real worker execution or restoration.

In GenOSbackend/tests/test_property_invariants.js

Open repository View GenOS code ↗

07 / 24Not integrated

ethz-spylab/agentdojo

Relationship to GenOS: Possible external security benchmark for tool-using agents.
Observed impact: No direct code impact: GenOS has internal adversarial tests but no AgentDojo task or attack runner.
Potential experiment: Could measure whether untrusted web, tool or memory content redirects a GenOS agent while also measuring legitimate task completion.

Open repository

08 / 24Not integrated

ServiceNow/BrowserGym

Relationship to GenOS: External web-task environment for comparing agent organizations.
Observed impact: No direct code impact: Playwright verifies bounded journeys, but GenOS does not run BrowserGym suites.
Potential experiment: Could compare a single worker, fixed topologies and Morphogenesis on the same browser missions and budgets.

Open repository

03 / 06

Authority and isolation

Policies, delegated rights, sandboxing, and protected state.

09 / 24Local v3 only

cedar-policy/cedar

Relationship to GenOS: Direct local-v3 authorization dependency through the official Cedar WASM package.
Observed impact: Added a validated policy and StartMission/Control checks in the agent authority service; family or cooperation links do not grant permission by themselves.
What GenOS can do: Can refuse unauthorized mission starts and agent control at those boundaries. This policy does not yet cover every GenOS tool.

In GenOSbackend/src/services/cedarAgentAuthority.js

Open repository

10 / 24Not integrated

eclipse-biscuit/biscuit-rust

Relationship to GenOS: Candidate for attenuated delegation between orchestrators and workers.
Observed impact: No direct code impact: GenOS leases are internal and no Biscuit token is issued or verified.
Potential experiment: Could pass a verifiable token that a downstream worker may restrict but cannot expand.

Open repository

11 / 24Not integrated

bytecodealliance/wasmtime

Relationship to GenOS: Potential WebAssembly isolation layer for executable organs and plugins.
Observed impact: No direct code impact: GenOS does not run plugins inside Wasmtime.
Potential experiment: Could execute bounded candidate code with explicit imports and resource limits before GenOS promotion gates review its results.

Open repository

12 / 24Not integrated

jedisct1/libsodium

Relationship to GenOS: Cryptographic library candidate for sealed and transportable agent state.
Observed impact: No direct code impact: GenOS capsule hashes detect alteration, but libsodium is not a dependency.
Potential experiment: Could add authenticated encryption for transported spores or capsules once key management and restoration rules are defined.

Open repository

04 / 06

Software and web work

Coding workers, browser journeys, technical quality, and accessibility.

13 / 24Not integrated

OpenHands/software-agent-sdk

Relationship to GenOS: Possible adapter or comparison for software-development workers.
Observed impact: No direct code impact: GenOS coding workers use their own execution interfaces, not the OpenHands SDK.
Potential experiment: Could provide a common software environment interface to compare GenOS workers with an external coding-agent baseline.

Open repository

14 / 24In GenOS code

microsoft/playwright

Relationship to GenOS: Direct browser automation dependency in the GenOS web journey verifier.
Observed impact: Added bounded Chromium actions and assertions, host allowlisting and hashed evidence receipts; newer local v3 reuses the verifier in SHEV audits.
What GenOS can do: Can check that a real page journey still works after an intervention and report confirmed, regressed or inconclusive.

In GenOSbackend/src/services/webJourneyVerifier.js

Open repository View GenOS code ↗

15 / 24Local v3 only

GoogleChrome/lighthouse

Relationship to GenOS: Direct local-v3 web quality sensor called from the SHEV audit flow.
Observed impact: Added thresholded Lighthouse category scores to stored web audit receipts and before/after effect checks.
What GenOS can do: Can detect a measured regression in selected performance, accessibility, best-practices or SEO scores; results depend on the browser environment.

In GenOSbackend/src/services/webAuditSensors.js

Open repository

16 / 24Local v3 only

dequelabs/axe-core

Relationship to GenOS: Direct local-v3 accessibility sensor through @axe-core/playwright.
Observed impact: Added rule-violation counts and explicit thresholds to SHEV web audit receipts and effect checks.
What GenOS can do: Can catch automated accessibility regressions after a change; a passing audit does not replace human accessibility review.

In GenOSbackend/src/services/webAuditSensors.js

Open repository

05 / 06

Continuity and shared state

Durable workflows, concurrent data, incremental updates, and transport formats.

17 / 24Not integrated

temporalio/temporal

Relationship to GenOS: Reference architecture for long-running distributed workflows.
Observed impact: No direct code impact: GenOS persists and retries workflow state with SQLite, without a Temporal server.
Potential experiment: Could supply durable activity histories and recovery when external operations span workers or machines, after an explicit integration study.

Open repository

18 / 24Not integrated

automerge/automerge

Relationship to GenOS: Possible CRDT library for Syncytium shared state.
Observed impact: No direct code impact: Syncytium has its own Lamport-ordered CRDT operations; Automerge is not connected.
Potential experiment: Could merge concurrent offline annotations or work maps, while authority and promotion decisions remain outside the merged document.

Open repository

19 / 24Not integrated

TimelyDataflow/differential-dataflow

Relationship to GenOS: Potential incremental computation engine for Rhizome and dependency propagation.
Observed impact: No direct code impact: GenOS does not use Differential Dataflow for its graph updates.
Potential experiment: Could recompute only consequences of a changed belief, worker or relation if profiling shows full recalculation is costly.

Open repository

20 / 24Not integrated

capnproto/capnproto

Relationship to GenOS: Transport-format candidate for typed high-volume internal messages.
Observed impact: No direct code impact: GenOS uses MessagePack and protobuf-related tooling, not Cap’n Proto.
Potential experiment: Could reduce message size or latency in measured hot paths if its schema and binding costs justify migration.

Open repository

06 / 06

Proofs and observability

Formal methods, constrained output, and diagnostic telemetry.

21 / 24Not integrated

lean-dojo/LeanDojo-v2

Relationship to GenOS: Specialized reference for Lean proof-state traces and tactic search.
Observed impact: No direct code impact: GenOS has Lean-related verification work but no LeanDojo-v2 pipeline.
Potential experiment: Could retain failed proof states and retrieve relevant tactics or lemmas; Lean itself would still validate the final proof.

Open repository

22 / 24Not integrated

dafny-lang/dafny

Relationship to GenOS: Formal-methods candidate for small critical runtime state machines.
Observed impact: No direct code impact: GenOS does not compile or check a Dafny model of its leases, budgets or promotion gates.
Potential experiment: Could verify a reference model and run conformance tests against the existing implementation; this would not automatically prove the JavaScript or Rust code.

Open repository

23 / 24Not integrated

mlc-ai/xgrammar

Relationship to GenOS: Potential constrained-decoding component for a compact command language.
Observed impact: No direct code impact: GenOS validates structured outputs but does not invoke XGrammar during model decoding.
Potential experiment: Could force syntactically valid commands with a compatible inference engine; GenOS would still check meaning and authorization.

Open repository

24 / 24Not integrated

open-telemetry/opentelemetry-collector

Relationship to GenOS: Possible collection layer for GenOS traces, metrics and logs.
Observed impact: No direct code impact: GenOS persists internal spans but has no native Collector exporter or uniform W3C propagation.
Potential experiment: Could correlate mission, worker, topology, cost and recovery telemetry across services after instrumentation and sensitive-data filtering.

Open repository