MemPalace — Infrastructure Status

Classification: Internal AAF system. Not an off-the-shelf service.

What MemPalace is

Per the canon: institutional memory — searchable, verbatim, append-only, never automatically loaded, referential authority: architecture, reports, prompts, decisions, sessions, history, artifacts, and rejected ideas with their reasons. It is the archive plane of the AAF Knowledge OS, distinct from Hermes (current intelligence) and Honcho (reflection).

Ground truth on the box

• No mempalace process, container, image, port, or CLI.
• repositories/aaf-holdings/src/mempalace/ — empty placeholder.
• engineering/mempalace/ — empty placeholder.
• No public package named MemPalace corresponds to this concept; it is an AAF design term, not OSS.

Install method

None — nothing to install. MemPalace is a system to be built (likely a search index + append-only store over the artifact/report/history corpus that already lives under /srv/aaf/). Building it is out of scope for an additive infrastructure bring-up.

HQ01 reachability

N/A until built. The raw substance MemPalace will eventually index already exists on the filesystem (missions/, assets/, reports, artifacts) and HQ01 reads it directly today. No MemPalace runtime is required for current HQ01 function.

Blocker

Requires a build mission (define store + index + retrieval API, honor append-only and plane-separation invariants). No env var or placeholder needed yet.