Skip to content

The Federation of Extensions

"The Core provides the skeleton; the Extensions provide the organs. LychD exists not as a monolith, but as a Federation of independent, sovereign capabilities bound together by the ExtensionContext."

LychD employs a strict philosophy of Dogfooding. The core kernel remains a minimal vessel for routing and state. Every advanced capability—from the API Proxy to the Swarm Protocol—functions as an Extension.

This architecture proves the Federation Protocol (ADR 05): the system constructs itself using the same tools available to the Magus.

🏛️ The Federation of Fourteen

Fourteen official extensions form the complete body of the Daemon. They reside in the extensions/ directory, each a standalone repository within the Federation.

Name Domain Sigil Function ADR
The Oculus Observability Records the Thought Trace and monitors physical hardware health. 29
The Tether VPN Establishes a Wireguard tunnel for secure, remote access. 39
The Veil Proxy Manages automated TLS and shields the Vessel via Caddy. 40
The Ward IAM & Auth Governs Sigils and Scopes to secure the Inner Circle. 38
The Intercom A2A Implements the Long Sleep handshake for peer-to-peer labor. 26
The Conductor Workflow Orchestrates multi-step Litanies and weaves memory into context. 28
The Scout Ingestion Wields a Dual-Mode browser to harvest internet knowledge. 30
The Smith Assimilation Drafts code and executes the autonomous Evolution of the system. 35
The Soulforge Training Transmutes Karma into model weights via LoRA fine-tuning. 33
The Riddle Training Evaluates the performance of the models in the agentic harness 33
The Toll Economics Enforces x402 payments and trades VRAM for Tithes. 41
The Prism Vision Manages the Vision Coven to perceive and analyze pixel data. 36
The Echo Audio Operates the Resonance Pipeline for real-time speech. 37
The Paradox Simulation Runs parallel Shadow Realms to verify complex reasoning. 31
The Mirror Identity Maintains persistent Personas and shifts Bayesian Priors. 32
The Legion Swarm (A2A) The Hive. 42

🧬 Anatomy of the Flesh

Every extension, from simple script to complex multi-module architecture, adheres to the laws of the Federation.

I. The Extension Hook

An extension must provide a valid pyproject.toml and an entry point exposing the register(context) hook. This handshake prevents organ rejection during the system boot sequence.

II. The Genetic API (ExtensionContext)

The ExtensionContext provides the methods to graft new logic onto the Daemon's anatomy.

Method Grant System Target
add_models(list[Base]) Memory Phylactery (06)
add_rune(RuneDefinition) Body Runes (08)
add_router(Router) Interface Vessel (11)
add_worker_rites(list) Labor Ghouls (14)
add_command(Group) Command The CLI (19)
add_agent(Agent) Reason Dispatcher (22)
add_graph(Graph) Logic Graph (24)
add_caddy_fragment(str) Shield The Veil (40)

III. Federated Persistence

The system manages extensions as a Federation of Git Repositories. The lychd.lock file in the Crypt root tracks the specific commit hash of every active organ, ensuring the system remains deterministic and revertible.

IV. The Ritual of Assimilation

Autopoiesis follows a strict path from the volatile to the immutable:

  1. Genesis: The Magus or The Smith drafts logic in the Lab (13).
  2. Speculation: The system executes the code within the Shadow Realm (25).
  3. Validation: The Ghouls execute the "Rite of Albedo" (Linting, Typing, Testing).
  4. Promotion: Upon Sovereign Consent (25), the system moves code to the Crypt and updates the lockfile.
  5. Rebirth: The system triggers Packaging (17) and restarts into its new physical body.