Living Systems — What's Running Now

Real-time status of the ecoPrimals sovereign mesh: active gates, deployed primals, capability routing, and live JupyterHub compute.

The Mesh Is Alive

The ecoPrimals ecosystem is not a description of future work. It is running. Seven gates are enrolled, three are meshed with bilateral direct TCP, and Songbird routes capability.call across all of them. This page shows what is actually deployed and operational.

Active Gates

GateStatusTransportWhat’s Running
sporeGate🟢 OnlineLAN + WGSovereign CI, Caddy TLS, songBird mesh hub, Forgejo
eastGate🟢 OnlineLAN + WG (10GbE)Overwatch, primalSpring ( 886 tests), petalTongue
ironGate🟢 MeshedLAN + WGRTX 5070 Ti, JupyterHub (deploying), songBird
flockGate🟡 WANWG via golgiTower atomic evolution: songBird, bearDog, skunkBat dev
golgi🟢 OnlineVPSWireGuard hub, Forgejo host, depot, cascade timer
grapheneGate🟢 OnlineADB (USB)Pixel 8a, Tower running, 14/14 aarch64-musl binaries
strandGate⬜ Joining—64-core EPYC, 256GB — awaiting hardware enrollment

Live Capabilities

When a gate starts Songbird, it announces its capabilities to the mesh. Other gates can then invoke any capability by name — songBird routes to the best available provider.

Currently Routed

CapabilityProviderPathUse
http.proxysporeGateLAN directHTTP routing to mesh services
peer.connectall meshed gatesbilateral TCPMesh peering, 0ms LAN
capability.callsporeGate → ironGateLAN directCross-gate compute dispatch
build.releasesporeGatelocalSovereign CI binary builds
cascade.syncgolgiWG15-min quorum cascade timer

Deploying

CapabilityProviderStatus
jupyter.executeironGateJupyterHub deployment in progress
compute.gpuironGateRTX 5070 Ti ready, pending capability registration
compute.cpustrandGateAwaiting hardware enrollment

JupyterHub — Live Compute

JupyterHub on ironGate provides notebook access to the live mesh. Once deployed, the path is:

Browser → lab.primals.eco
    → bearDog :443 (ACME TLS)
    → songBird capability.call("jupyter")
    → ironGate :8000 (LAN direct, <1ms)
    → JupyterHub session

What makes this different from a cloud notebook: your computation runs on sovereign hardware in a private lab. No telemetry. No vendor. The mesh handles routing — if ironGate goes offline, songBird can route to strandGate (once enrolled) or any future compute node. The notebook doesn’t know which gate ran it.

Example Workloads Available

WorkloadHardwareSpring
16S metagenomics pipelineCPUwetSpring
GROMACS metadynamics (CAZyme FEL)RTX 5070 Ti GPUhotSpring
Salmon RNA-seq quantificationCPU + NVMewetSpring
STAR alignment (large genomes)64-core EPYC (strandGate)wetSpring
ET₀ irrigation modelingCPUairSpring
PK/PD compartmental modelingCPUhealthSpring

Each workload runs against the same infrastructure that produced the baseCamp results. Every run gets a provenance chain.

Sovereign CI Pipeline

All ? primals are continuously built from source on sporeGate’s Sovereign CI. The pipeline:

Developer pushes to Forgejo (git.primals.eco)
    → golgi cascade timer (15-min quorum)
    → sporeGate pulls, builds x86_64-musl + aarch64-musl
    → BLAKE3 checksums computed
    → Binaries published to depot (membrane.primals.eco/depot/)
    → Gates cascade + pull from depot

Wave 133a result: 30/30 ecobins built (15 x86_64 + 15 aarch64), 283 MB total, all checksummed and published. 11/14 primals build with zero manual intervention; 3 require documented workarounds (being converged).

Mesh Health

The mesh is self-healing. If a gate goes offline:

  • Songbird detects peer loss via heartbeat timeout
  • Capability routing tables update across all remaining peers
  • Services that depended on the lost gate get routed to alternates
  • When the gate returns, peer.connect re-establishes bilateral trust

Key invariant: unplugging any single gate does not kill the network. The Flint edge router is the plasma membrane. Gates are ephemeral compute.

What’s Next

ItemGateWhen
JupyterHub deploy + capability registrationironGateThis wave
bearDog ACME gateway activation (Caddy retirement)sporeGateAfter flockGate fix
strandGate enrollment (mesh auto-absorb)strandGateWhen hardware arrives
Bidirectional relay (GitHub ↔ Forgejo parity)golgicellMembrane deploy
Live mesh visualization (petalTongue wire-up)eastGatesporePrint + petalTongue