Phylactery
In plain words: 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.
- 1The Run ledger owns job lifecycle truth; step rows are best-effort evidence only.
- 2A checkpoint is saved step-map state; it cannot restore live connections, leases or event streams.
- 3One cluster on one host; planned vector, trace and queue schemas are named but not delivered.
Partial Persistence works locally; crash and full deployment recovery remain unqualified.
Words on this page, decoded click one for its card
Memory Vault Phylactery
The database. Anything committed here survives crashes and restarts.
It's like: The bank vault. The branch can close, the vault keeps your money.
Click a dot to open that part's card.
In this section 1 pages
The VesselEngine Room passes. What it inscribed waits in the dark.
When the Vessel dies, another process must discover what happened before it may continue. The PhylacteryMemory Vault holds the committed records from which that judgment begins: the PostgreSQL database cluster assigned to one application partition.
Domains give those records meaning and govern their lifecycle. PhylacteryMemory Vault owns the engines, codecs, transactions, migrations, and schema admission through which they are stored.
What the inscription keeps
Different inscriptions answer different questions:
| Record | What a returning VesselEngine Room can establish |
|---|---|
| Run and delivery ledger | Canonical lifecycle and exact publication intent for each fresh or resumed worker hop. |
run_checkpoint |
One replaceable JSONB record per RunJob Record, containing validated GraphStep Map snapshot history and cascading with that RunJob Record. |
| Consent and delegated-owner records | The exact authority whose settled result may permit a parked RunJob Record to return. |
Ordered step rows |
Best-effort structural evidence; the RunJob Record ledger still owns lifecycle truth. |
session, karma, soulstone_record, codex_preauthorization |
Domain records admitted by application migrations; each row establishes only its own contract. |
| Public-note ArchiveLong-term Memory | Explicit namespace ownership, note revisions and lifecycle, intake identities and text-free recall receipts; optional generation tombstones and latest derivation attempts. |
SAQ saq_* tables |
Durable broker state through a separate autocommit pool. Queue publication and RunJob Record admission remain separate transactions. |
Today these records use PostgreSQL's default schema and search path. Persistence
owns exact table admission and migration history. Planned vectors, traces, and isolated queue
chambers describe governed memory, cognitive evidence, and broker separation; naming those
chambers does not deliver their services.
Read a checkpoint as declared GraphStep Map state. It cannot restore the process's image, runtime dependencies, or event stream. Subscribers, leases, provider handles, and uncommitted frames end with the process.
Terminal RunJob Record status commits before ContextBriefing Pack release and best-effort checkpoint cleanup. A checkpoint left behind by failed cleanup therefore grants no replay permission. Reanimation must judge canonical truth before anything can return.
One cluster, one custody boundary
PostgreSQL runs in its dedicated unit. PGDATA occupies the exact admitted postgres/data mount
in the Crypt. The default design enlarges one cluster on one host; storage can move beneath
that mount without moving application authority. Process-local and in-memory profiles provide
bounded execution or test substitutes. Loose files cannot become a shadow database.
Plan growth through lifecycle policy first. Neither age nor disk pressure grants deletion rights, and ShadowWhat-if Simulator's Reaper does not collect database records. If later measurements justify local hot and cold tiers, partitions or tablespaces must preserve PostgreSQL's single query boundary. Additional mounts would first need Layout, container, whole-cluster capture, and restore support.
No scale-out topology has been selected. A future named Domain store requires its own custody or projection contract, rather than becoming an interchangeable PhylacteryMemory Vault backend. Follow the topology and scale seam when the choice becomes necessary.
Read the evidence before claiming continuity
First-light persistence is Partial. Read the named receipts according to what each observed. The lifecycle test uses offline collaborators. Actual warm-model reply/history retention includes two normal source-CLI/native TCP boots. These source-profile receipts establish neither a Consent-plus-Checkpoint restart, a current installed body, nor crash recovery.
A separate trusted source-browser journey retains its fixed useful reply after normal restart under an explicit test composition. The trusted installed-hybrid receipt retains identical complete SDK history, IntentRequest capability, and exact PatternWorkflow manifest across two normal installed native boots. Its private Docker and borrowed-model scope still applies. General retention, compaction, and physical tiering remain incomplete.
The bounded public-note Archive adds explicit intake, lifecycle, and lexical recall; old KarmaLessons Learned rows stay inert. An independently selected derivation path retains bounded vectors and invalidation fences. Its durable status describes only the latest attempt, and expiry requires an explicit retry.
Separately selected semantic recall and BridgeChat revision 5 have fixed native lifecycle and attributed-answer/empty-recall observations. Their exact model, authority, and source scopes bind the claims. They do not establish general retrieval quality, automatic curation, sharing, or a formation path.
Follow Ghouls to see the workers that write these records, or Reanimation to cross the death of their process.