Skip to content

Sepulcher

“Every organ receives a place, a boundary, and one burden it must answer for. No organ is the whole.”

The Sepulcher is LychD's rootless runtime body: the services, mounts, and execution topology that house its organs on a Linux host. Read this map when your question is which part owns this? Follow the burden, not the nearest filename: each chamber leads to the page that explains it. Together they sustain the recurrent whole called the Lich.

The Anatomy

I. The whole, its law, body, and memory

  • Lich — the recurrent whole. Enter its First Invocation, then meet the four coequal functions of its inner instrument: Call, Blade, Spirit, and Answer.
  • Codex — editable configuration intent. Read this when changing settings or Runes, resolving configuration precedence, or preparing lychd bind.
  • Crypt — managed persistent files. Read this when locating LychD's XDG data home, filesystem boundaries, or mounts.
  • Gateway — an optional separate ingress host. Read this when placing Veil on Home or Remote iron while keeping data and application authority behind one exact backend path.
  • Vessel — the application process. Read this when tracing Litestar composition, application lifecycle, the web surface, or in-process runtime services.
  • Phylactery — committed database truth. Read this when asking which PostgreSQL records and checkpoints survive a process boundary.
  • Ghouls — background units of work. Read this when following how a run is queued, claimed, advanced, cancelled, or settled.
  • Reanimation — return after process death. Read this when distinguishing service restart from recovery at a committed Phylactery boundary.

II. The Animating Spark

  • Animator — an addressable capability service. Read this for the common service contract and adapter boundary. Model inference is one kind of capability, not the whole category.
  • Capabilities — what an Animator can do and whether it is ready. Read this for semantic interfaces, immutable profiles, typed demand, grant variants, identity, and the readiness words shown by the Nexus.
  • Connectors — how one admitted surface is invoked. Read this for exact dialect drivers, partial OpenAI-compatible profiles, native calls, durable jobs, sessions, probes, and the boundary between transport and capability meaning.
  • Soulstone — a local service. Read this when declaring a Quadlet-backed runtime, its models, mounts, devices, secrets, and lifecycle intent.
  • Portal — a remote connection. Read this when declaring an external API or service boundary, its credentials, and egress implications.
  • Coven — named runtime grouping. Read this for target membership and break-glass aggregation.

III. Growth and Sight

  • Federation of Extensions — organs that extend the body. Read this for extension jurisdictions, assimilation, and compatibility boundaries.
  • Oculus — LychD's native evidence plane. Read this for the intended evidence model and Altar-facing observability surface.

Enter the body

State of Work records the present boundary of the whole.

With first life witnessed, enter the Vessel and follow the body inward.