Transport Evolution

From nanowire SSH scripts to quorum-sensing coordination — the evolutionary path of inter-node communication.

Current State: Nanowire

The K-Derm relay chain currently uses nanowire transport: point-to-point SSH connections between specific nodes. Each node knows the next node’s address, holds its SSH key, and issues explicit commands.

(Legacy) Gate ──SSH──→ golgiBody ──SSH──→ peptidoglycan ──SSH──→ golgiBody-ext ──SSH──→ GitHub
(Wave 120+) Gate ──SSH/WG──→ golgi ──SSH/WG──→ sporeGate (build) ──rsync──→ golgi ──push──→ GitHub

This is the biological equivalent of type IV pili — conductive protein filaments that Gram-negative bacteria use for direct cell-to-cell electron transfer.

Where Nanowire Is Correct

Nanowire remains the correct pattern for metallic bond interactions:

InteractionWhy Nanowire
Gate SSH to ForgejoAuthentication requires direct connection
Fleet key operationsAdmin commands need explicit targeting
Build triggerssporeGate sovereign-ci needs deterministic invocation

Where Nanowire Is Limiting

For population-level coordination, nanowire creates fragility:

  • Topology changes require rewiring: Adding a node means editing scripts
  • Synchronous blocking: Each hop waits for the previous to complete
  • Single path: No redundancy if any node is unreachable
  • Hardcoded knowledge: Each script knows the next node’s address

Target State: Quorum Sensing

The target architecture is quorum sensing — a diffusion-based coordination model where nodes detect environmental signals and respond independently.

In biology, quorum sensing uses autoinducers: small signaling molecules that accumulate in the environment. When concentration exceeds a threshold, all nearby cells activate coordinated behavior — without any cell directly commanding another.

The Impulse System as Proto-Quorum

The ecosystem already has the foundation: the impulse/potential system. Impulses are TOML files committed to wateringHole/impulses/active/. Any gate can fire an impulse; any gate can sense pending impulses.

Gate fires impulse → commits TOML to wateringHole
  → temporal sync distributes to all gates
  → each gate's membrane binary senses the impulse
  → gates with matching capabilities respond

This is quorum sensing: the impulse diffuses through the periplasm (wateringHole repo), and nodes that can respond, do respond. No direct addressing needed.

The Evolution Path

PhaseTransportCoordinationStatus
1Nanowire (SSH scripts)Explicit relay chainLIVE
2Nanowire + impulse sensingHybrid: relay + async signalsLIVE (Wave 121)
3Quorum sensingImpulse diffusion drives all coordinationTarget
4Sovereign EnvelopeBTSP-wrapped multi-hop via BirdSong relayWave 123+

Phase 2: Hybrid (Current Wave)

The relay chain handles synchronous operations (git push propagation). The impulse system handles asynchronous coordination (wave assignments, gate capabilities, build triggers). Both coexist — nanowire for the critical path, quorum sensing for orchestration.

Phase 3: Full Quorum (Future)

In the target state, even the relay chain becomes quorum-driven:

  1. Gate pushes to Forgejo (covalent bond — always nanowire)
  2. Forgejo fires an impulse: “new content available for relay”
  3. sporeGate senses the impulse, builds autonomously (Sovereign CI)
  4. golgi senses “content staged for shipping,” pushes to GitHub

Each node acts on environmental signals, not direct commands. The topology can change (add/remove nodes) without rewiring — new nodes simply begin sensing impulses and responding to those matching their capabilities.

Phase 4: Sovereign Transport Envelope (Wave 121+)

The physical topology (bandwidth, latency, wire paths) is now separated from the digital topology (privacy, sovereignty, identity). Phase 4 wraps all inter-gate traffic in BTSP-encrypted envelopes routed through Songbird relay:

Today:   primal → TCP → LAN → peer primal
         (plaintext on LAN, direct path visible to ISP/attacker)

Phase 4: primal → TransportEndpoint.mesh_relay → Songbird relay
         → BTSP-encrypted multi-hop → peer primal
         (opaque on LAN, ISP sees only encrypted blobs)

The primitives are already built:

  • BearDog: BTSP ephemeral-key handshake, ChaCha20-Poly1305 framing, relay.authorize
  • Songbird: Lineage-gated UDP relay, STUN, beacon mesh pathfinding, .onion transport
  • cellMembrane: TransportEndpoint::MeshRelay enum variant, K-Derm channel abstraction
  • Dark Forest: Encrypted multicast beacons, IND-CPA secure discovery

The operational wiring (audit → relay activation → mesh_relay graduation → beacons) turns these primitives into a complete sovereign transport envelope.

Songbird: The Federation Transport

For inter-gate coordination beyond the VPS membrane, Songbird provides the mesh federation transport:

  • Lineage-gated UDP relay on golgi (outer membrane)
  • BirdSong genetic lineage for contact exchange
  • mesh.capabilities_announce push model for capability routing
  • NAT traversal: 7-tier sovereign (direct → STUN → relay → beacon → .onion → Tor → TURN)
  • WAN-resilient with automatic reconnection

Songbird is the organism’s long-range communication — not point-to-point nanowire but broadcast signaling across the entire gate mesh. Together with BearDog’s cryptographic identity, it forms the Tower Atomic composition: sovereign HTTPS, sovereign relay, sovereign discovery — all Pure Rust, all composing via JSON-RPC over UDS.

Why This Matters

The transport evolution directly enables:

  1. Scalability: New gates join by sensing impulses, not by being wired in
  2. Resilience: No single relay failure blocks coordination
  3. Autonomy: Each node makes its own decisions based on environmental signals
  4. Evolution: The coordination protocol can evolve without infrastructure changes
  5. Privacy: ISP cannot inspect or correlate inter-gate traffic (Phase 4)