Crypt

In plain words: Data Folder layout

Available 2 min read 5 glossary terms 7 connected pages
The short version written for the Snayu team

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.

Why read it: Read this before touching file paths, mounts or anything that creates or deletes data on the host.
  1. 1Each subfolder has one owner; PostgreSQL data is mounted only into the database unit.
  2. 2Location grants no authority: ambiguous symlinks or ownership make operations fail closed and preserve data.
  3. 3The snapshots folder is reserved; whole-system snapshot and restore are still Designed.

Available Layout is in use; snapshot/restore and external workspace mounts are not delivered.

Words on this page, decoded click one for its card

Memory VaultSettings FolderThe BodyData Folder
Where it sits in LychD

Data Folder Crypt

Where durable files live: database storage, the workspace, private extensions.

It's like: The basement storage room. Things kept here outlast any one shift.

Click a dot to open that part's card.

Glossary page On the system map In the network
The original text Underlined words open their plain-English card.

The CodexSettings Folder writes the law. The CryptData Folder keeps what must survive it.

The CryptData Folder is LychD's durable data and workspace root. By default it lives at ~/.local/share/lychd/; XDG_DATA_HOME may move the root. It is not mounted wholesale into the VesselEngine Room.

~/.local/share/lychd/
├── triggers/
│   ├── inbox/
│   └── journal/
├── postgres/
│   ├── init_db.sh
│   └── data/
├── snapshots/
├── lab/
├── extensions/
└── core/

Each chamber has one owner:

Chamber Purpose Runtime boundary
triggers/inbox/ Host Reactor transition intents VesselEngine Room read-write when the Host Reactor is selected
triggers/journal/ Terminal Reactor receipts VesselEngine Room read-only when the Host Reactor is selected
postgres/data/ PhylacteryMemory Vault storage PostgreSQL unit only
snapshots/ Reserved recovery-snapshot shelf No whole-body snapshot rite is delivered yet
lab/ Operator workspace VesselEngine Room read-write
extensions/ Private Extension source Runtime read-only
core/ Reserved Core source Runtime read-only

A location in the CryptData Folder grants neither execution nor deletion authority. Geography is not authority: lifecycle receipts and live identity checks determine what LychD may replace or remove. When a symlink, mount, receipt, or identity is ambiguous, the operation fails closed, preserves the object, and returns typed recovery or blocking evidence. Proximity cannot make external projects, model shelves, foreign mounts, or operator data LychD-owned.

The Phylactery

PostgreSQL owns postgres/data/. On a suitable Btrfs host, initialization may create that exact target as a verified subvolume and apply No-COW inheritance for new database files. On other filesystems it remains an ordinary directory. Existing files are never retrofitted, and neither case proves that coordinated snapshot and restore exists.

State of Work records that the whole-body rite is still designed. Snapshots defines the future checkpoint protocol; Layout owns present creation and deletion safety.

The Spheres

Use the Lab as LychD's internal workbench. The accepted Outlands design would also admit operator-selected external workspaces beneath ~/work/ inside the VesselEngine Room. Native VesselEngine Room generation currently supplies no Outland mount selector. A read-only Outland could serve as a reference library under that design without becoming a new trust domain.

The trusted VesselEngine Room receives these mounts:

  • the CodexSettings Folder read-only and the Lab read-write, independent of the active task;
  • private Extensions and reserved Core source read-only; and
  • no blanket mount of the CryptData Folder, PostgreSQL data, binding sites, or model shelves.

Unsafe hand-work does not become safe because its files are in the Lab. Trusted orchestration remains in the VesselEngine Room; the future TombSandbox must receive only task-scoped workspace and artifact paths.

The exact map, ownership receipts, Btrfs identity rules, and mount contract live in Layout.