Skip to content

Extensions and The Nine Archons

"The Lych is the Father; the Extensions are the Children. The first nine are the Archons—the fundamental organs through which the Daemon perceives, protects, and perfects itself."

The LychD is a sovereign entity built upon a Federation (ADR 05) of independent repositories. While any Magus can forge a new organ, the system recognizes Nine Archons—the primary extensions that define the system's core capabilities.

🏛️ The Ennead of Power

Archon Domain Icon The Artifact
The Smith Assimilation :material-hammer-anvil: lychd-smith
The Oculus Observability lychd-oculus
The Soulforge Training lychd-soulforge
The Veil Proxy lychd-veil
The Thread VPN lychd-thread
The Echo Audio lychd-echo
The Prism Vision lychd-prism
The Mirror Identity lychd-mirror
The Paradox Simulation lychd-paradox

🧩 The Nature of the Binding

Every Archon, whether it provides the "Voice" or the "Will," is subject to the Anatomy of the Flesh. They are birthed in the Lab (ADR 16), tested in the Shadow Realm (ADR 25), and sealed by the Forge (ADR 17).

They are not "plugins"; they are Substrate Injections. When an Archon is summoned, it modifies the very nature of the Daemon's physical and cognitive reality.

Structure & Anatomy

"The Lich cares not if the soul is a single spark or a raging sun. It cares only that it fits the Binding."

The Daemon is agnostic to complexity. Whether an Extension is a single-file script or a sprawling enterprise architecture, the Binding Ritual remains the same. The ExtensionContext is the universal adapter that allows the Daemon to assimilate any form of code into its physical and cognitive body.

I. :material-sword-bolt: The Shiv (Simple Binding)

For simple tools—a single agent, a few commands, or a basic model utility—the Extension is structured as a flat, high-velocity module.

my_agent/
├── .git/              # Required: Mandatory Version Control.
├── __init__.py        # The Cortex: register(context) is here.
├── logic.py           # The reasoning logic.
└── templates/         # The scrying fragments (Jinja2).

In __init__.py, the logic is imported and bound to the ExtensionContext. This is the Shiv: a sharp, focused instrument for a single purpose.

II. The Fractal (Complex Binding)

For high-level Archons—systems that manage other systems or provide complex sensory inputs—the anatomy expands into a Fractal structure following Domain-Driven Design.

enterprise_agent/
├── .git/                   # Required: The root of the Sovereign Repository.
├── __init__.py             # The Gateway (Registration hook).
├── core/                   # Shared types and internal utilities.
├── infrastructure/         # DB Models (Phylactery) & Jobs (Ghouls).
├── interface/              # Web Routers (Altar) & CLI commands (The Hand).
└── agents/                 # Cognitive Topologies (Graphs).

🛠️ The Extension Context (The Senses)

The ExtensionContext is the genetic code of the daemon. It provides the methods required to graft new logic onto the Core.

Method The Grant ADR Reference
add_models(list[Base]) Memory. 06. Persistence
add_agent(Agent) Cognition. 19. Agents
add_graph(Graph) Topology. 22. Graph
add_worker_rites(list) Action. 14. Workers
add_router(Router) Voice. 15. Frontend
add_command(Group) Will. 18. CLI

🌐 The Federation (Git Management)

Extensions are managed as a Federation of Git Repositories, ensuring absolute modularity.

  1. Isolation: Every directory in the extensions/ sphere is a standalone repository. Updates are performed via git pull without risk to the Core kernel.
  2. The Lockfile: The Daemon maintains lychd.lock in the Crypt root. It tracks the specific commit hash of every active organ, ensuring the body is deterministic and revertible.

🧪 The Ritual of Assimilation

The workflow of Autopoiesis (self-creation) follows a strict path from the volatile to the immutable:

  1. Genesis (Drafting): The Agent (guided by The Smith) or Magus creates code in the Lab (ADR 16).
  2. Speculation: The code is executed and tested in the Shadow Realm (ADR 25) against temporary schemas.
  3. Validation: The Ghouls (ADR 14) execute the "Rite of Albedo" (Pytest/Ruff).
  4. Promotion: The code is moved to the Crypt (ADR 13) and hashed in the lockfile.
  5. The Rebirth: The system triggers Packaging (ADR 17) and restarts the container into its new body.