← Runtime & memory separation plan
Checkpoint 000 · 24 July 2026

Baseline discovery and architecture recommendation

No runtime, profile, service, dependency, or memory-store changes were made. This checkpoint records the live facts that shape the separation plan.

Status: discovery complete Risk: read-only inspection Next gate: human architecture choices

Verified observations

1
Personal and Game Assist profiles are both running.

Their profile state is isolated, but they share one patched Hermes executable and dependency environment.

2
Both profiles configure Mnemosyne.

Hermes reports that the provider plugin is not installed, so structured external memory capture, recall, and consolidation are inactive.

3
Built-in profile memory is present and injected.

Personal and Game Assist profile memory files exist. This is smaller, prompt-resident memory—not the expected organised provider loop.

4
Nagato has substantial active local knowledge stores.

Campaign state, Recall, Codex, source corpus, extraction manifests, and observability stores are populated; the bridge already injects bounded campaign/Codex/retrieval context.

5
The installed fork is intentionally pinned.

It carries Nagato patches and cannot follow the normal upstream update path without a deliberate refresh and verification cycle.

6
The existing /plans route is live and public.

It already serves this static plan directory, so publishing sanitized HTML requires no proxy restart. Private operational detail still needs authentication.

Recommendation

Use two durable Hermes installations: a clean upstream personal runtime and a pinned Nagato service runtime. Keep a third, disposable lane for gateway and memory experiments. Install structured memory through Hermes’ supported provider interface in each durable runtime, with isolated stores and explicit, curated sharing only.

Why this precedes the gateway contest

The gateway candidates should be evaluated against the behavior that matters: active memory, Recall-derived evidence, scope isolation, replay, and update safety. Building that contract after choosing a runtime would reward whichever candidate happens to mimic today’s accidental installation layout.

Next checkpoint

Checkpoint 001 should follow the four human choices in the main plan. It will freeze the target directory/service layout, update channels, memory-sharing policy, test matrix, rollback commands, and exact cutover gates—still before modifying the live gateways.