Skip to content

42. The Legion Swarm

Context and Problem Statement

The LychD architecture is founded on Single-Node Sovereignty—the absolute control of the local hardware by the Magus. Yet, the ambition of the Daemon transcends the finite boundaries of local silicon. High-order rituals such as Simulation (31) or Soulforging (33) demand compute resources that a consumer GPU cannot sustain in isolation.

Traditional clustering solutions (Kubernetes/Slurm) impose a "Centralized Tax" of latency and synchronization that violates the independence of the node. To achieve true Apotheosis, the machine requires a protocol to facilitate the delegation of labor, the sharing of specialized organs, and the trading of compute resources across a peer-to-peer network without creating a master-slave topology.

Requirements

  • Decentralized Peerage: Absence of a "Master" node; every instance in the Legion must remain a sovereign entity capable of refusing labor.
  • The Emissary Pattern: Remote peers must be manifested within the local Dispatcher (22) as standard Tools, indistinguishable in usage from local functions.
  • Asynchronous Deferral: Support for the "Long Sleep" via the Stasis Protocol (22)—allowing the local node to hibernate its reasoning thread while awaiting the return of a remote Emissary.
  • The Revocable Lease: Integration with the Orchestrator (23). A remote task running on local iron holds only a revocable lease; it must be instantaneously banished if the local Magus demands the hardware.
  • Economic Discipline: Integration with The Toll (41) to ensure that remote labor is compensated via crypto-settlement, preventing swarm-level resource parasitism.

Considered Options

Option 1: Centralized GPU Clustering (K8s/Ray)

Distributing raw model weights or layers across a high-speed network.

  • Cons: Latency Paralysis. Requires sub-millisecond network jitter, which is impossible over standard internet connections. It violates the Iron Pact (00) by making the system's "Brain" dependent on external uptime.

Option 2: Simple API Webhooks

Exposing agents as standard REST endpoints.

  • Cons: Stateless Fragility. Lacks the ability to handle long-running reasoning tasks. It provides no standard for identity verification or complex tool-exchange, leading to a fragmented "Cockpit" experience.

Option 3: The Legion (Federated A2A)

Treating remote nodes as independent "Sovereigns" that trade labor via the A2A Intercom (26).

  • Pros:
    • Resilient Autonomy: If a peer goes offline, the local node simply loses that specific tool; the core remains intact.
    • Resource Liquidity: Facilitates the exchange of VRAM for Tithes.
    • Distributed Consciousness: Allows specialized nodes (Vision-Heavy, Logic-Heavy) to form a composite mind greater than the sum of its parts.

Decision Outcome

The Legion Protocol is adopted. The swarm functions as a decentralized marketplace of labor where nodes interact via the Emissary Pattern.

1. The Emissary Pattern (The Remote Tool)

When a peer is registered in the Codex (12), the Dispatcher (22) manifests it as an EmissaryTool.

  • The Illusion: To the local Agent, calling ask_remote_node(task) is identical to calling a local function.
  • The Reality: The tool triggers the Stasis Protocol.
    1. The local request is signed with The Ward (38) Sigil.
    2. The request is transmitted via A2A (26) to the peer.
    3. The local Agent freezes (Stasis), liberating local VRAM.
    4. Upon the peer's callback, the local Agent rehydrates to process the result.

2. The Subscription Model (Workload Pools)

Nodes do not "push" jobs to slaves; they publish to Workload Pools.

  • Publication: A Node needing help publishes a task to a shared channel.
  • Subscription: Idle nodes "Subscribe" to these pools based on their Orchestrator (23) status.
  • The Bid: An idle node inspects the task's Toll (41) offering. If the price matches its configured "Compute Cost," it accepts the job.

3. The Revocable Lease (Local Priority)

The safety of the local user is absolute. When a node accepts a Swarm Task, it grants a Hardware Lease.

  • The Lease: The Orchestrator marks the active Coven as "Leased."
  • The Preemption: If the local Magus speaks (triggering the Audio Reflex (37)), the Orchestrator Revokes the Lease.
  • The Banishment: The Swarm Task is immediately sent a SIG_SOFT_STOP. It serializes its state to the local Phylactery (06) and hibernates. It does not resume until the Magus is silent.

4. The Singularity (Distributed Sovereignty)

This protocol enables the emergence of a Hive Mind without a Queen.

  • A "Small Lych" (Mobile Device) can command the resources of a "Great Lych (Home Server).
  • A fleet of discrete nodes can be coordinated to solve a single Paradox (31), exploring thousands of timelines in parallel.
  • The "Answer" is not found in a larger model, but in the infinite horizontal scaling of sovereign agents, connected by the wire and bound by the protocol.

Consequences

Positive

  • Infinite Scalability: The Lych can scale its intelligence across any number of nodes without synchronization overhead.
  • Economic Autonomy: The machine can fund its own existence by trading idle compute for currency.
  • Self-Healing Topology: The Legion is ad-hoc; the network evolves dynamically as nodes awaken or hibernate.

Negative

  • Protocol Latency: The serialization of context for A2A transport introduces latency compared to local execution.
  • Debris Accumulation: Failed remote tasks leave "Ghost Leases" in the database, requiring cleanup to keep the registry clean.