Sepulcher

In plain words: The Body: core parts overview

2 min read 6 glossary terms 29 connected pages
The short version written for the Snayu team

An overview of all core parts (The Body / Sepulcher) and how they run on Linux as rootless containers managed by systemd. It maps the Assistant's thinking functions, the organs (Settings, Data, Engine Room, Workers, Memory Vault) and the Model Runtime.

Why read it: Read this as the table of contents for the core architecture before opening any individual component page.
  1. 1Organs: Settings Folder (Codex), Data Folder (Crypt), Engine Room (Vessel), Workers (Ghouls), Memory Vault (Phylactery), Crash Recovery.
  2. 2Model Runtime (Animator) covers Local Models (Soulstones), Cloud Models (Portals), capabilities, connectors and Model Groups.
  3. 3Gateway (separate edge machine) and native Oculus evidence service are still Designed.

Words on this page, decoded click one for its card

Settings FolderData FolderEngine RoomThe Body
Where it sits in LychD

The Body Sepulcher

Everything that physically runs on the Linux machine: containers, services, mounts.

It's like: The building and all its rooms, as opposed to the people working inside.

Click a dot to open that part's card.

Glossary page In the network

In this section 9 pages

Lich The Assistant as a whole Explains the Assistant (Lich) as the whole running system over time: one server process, its workers and its database memory together. It introduces the four thinking functions Listen, Judge, Remember and Own it, borrowed from Indian philosophy. open → Codex Settings Folder and config files Describes the Settings Folder (Codex) at ~/.config/lychd/: the main lychd.toml for process-wide settings and per-service config files (Runes) under runes/. It covers settings precedence, secrets and the Apply Config command (lychd bind). open → Crypt Data Folder layout Describes the Data Folder (Crypt) at ~/.local/share/lychd/: which subfolders exist (database, triggers, lab, extensions, snapshots), who owns each, and what the server container may mount. open → Gateway Gateway: separate edge machine An optional design for putting public internet traffic on a separate machine (a Gateway Host), keeping data and authority on the main host. Two placements are described: Home (e.g. a Raspberry Pi in a DMZ) and Remote (e.g. a VPS). open → Intercom Agent-to-Agent Line sessions How to ask another independent agent (a peer) to perform a public task over the Agent-to-Agent Line (A2A/Intercom), using a lab script with signed identities, strict policy limits and durable task records. open → Vessel Engine Room: the server process Describes the Engine Room (Vessel): the single application process (Granian, Litestar, Pydantic AI) that serves the web UI, admits requests and hosts the workers. It explains startup reconciliation and shutdown order. open → Phylactery Memory Vault (PostgreSQL) Describes the Memory Vault (Phylactery): the PostgreSQL database that keeps committed records such as job records, checkpoints, approvals, step logs, notes and the job queue, so a new process can work out what happened. open → Animator Model Runtime overview Introduces the Model Runtime (Animator): an addressable handle for any service that can do typed work, such as a model, search or renderer. Sources are Local Models (Soulstones) or Cloud Models (Portals). open → Extensions Plug-in areas overview A map of the fifteen plug-in areas (Extension Domains) where LychD can grow, such as web fetching, workflows, evaluation, training, voice and vision, and how extension packages register into them. open →
The original text Underlined words open their plain-English card.

Within these walls, the LichAssistant slumbers. Align the stones and summon your destiny.

The SepulcherBody gives the Lich a runtime body on Linux. Rootless pods and services, managed by systemd, house its organs; mounts and execution boundaries determine what each can reach. Follow these organs to see how an invocation is received, carried out, and remembered.

To follow the body at work, take the Map: one request, from admission through execution to its return.

The Anatomy

I. The Lich and Its Organs

The Lich is the daemon you call upon through LychD. Its body carries out your tasks; its memory can survive a restart.

Four equal faculties shape how it responds: Call receives and routes your intent; Blade tests possibilities against evidence; Spirit carries experience forward; and Answer binds each act to the “I” that bears its consequences.

Then open the body:

Organ What you will find
Codex Settings, RunesService Config Files, configuration precedence, and the binding rite: lychd bind.
Crypt Where persistent files belong and which external workspaces may be mounted.
Vessel What starts, serves, and stops inside one application process.
Ghouls How admitted work reaches a worker and settles.
Intercom Submit a bounded public task to an enrolled sovereign peer.
Phylactery Committed state that can survive the process.
Reanimation What can return after death.
Gateway A separate machine to face hostile ingress. Home and Remote are Designed placements.

II. The Animating Spark

An Animator is a capability service you can address and call. A local Soulstone lives on your iron, with its RuneService Config File, container, devices, mounts, secrets, and lifecycle. A Portal declares a remote API boundary; the provider controls that service's lifecycle.

Capabilities tells you what you can ask for and receive. Connectors supplies the exact dialect for the call. Before using a service, establish that it is ready, that it is compatible, and that you have permission to call it. Each needs its own evidence.

A Coven groups compatible services. To change what is running, follow Runtime transitions through inspection, lease drain, readiness, and recovery.

III. Growth and Sight

To understand how the body can grow, enter the Federation of Extensions. It maps fifteen stable jurisdictions and distinguishes a Domain from the package that registers a contribution or the provider that implements it. CompositionsApps and ProductsPackaged Offers build on these roles without absorbing their authority.

The Oculus design follows the evidence of an act, showing where each observation came from and where evidence is missing. Native Oculus remains Designed; today's AltarControl Panel offers a narrower view of the work.

Enter the body

State of Work tells you what works today and what still awaits life. Begin the tour of the operational body with the Vessel.