EchoNet.ing
PHASE D / CORE ARCHITECTURE

Memory Vault

Durable knowledge stays human-readable, portable, and yours. Temporary facts live in session or inbox.

Humandecides what to keep
Obsidiancanonical source
OpenVikingrebuildable retrieval
Hermes memorycompact hot-cache
Session/Evidenceoperational trace
IMPLEMENTATION

Define a memory lifecycle where durable knowledge stays in Markdown

Split memory by lifetime: canonical facts in Markdown, temporary task state in session, and operational evidence separately.

Split memory by lifetime

Separate canonical facts, temporary task state, and operational evidence.

Use Obsidian for canonical

Store durable knowledge in ordinary Markdown with minimal frontmatter.

Use OpenViking for retrieval

Build an index over approved canonical material only.

Keep Hermes memory small

Save only stable preferences and environment facts that improve most sessions.

Isolate session history

Treat conversation logs as operational evidence, not permanent knowledge.

STRUCTURED REFERENCE

Decision matrix

| Fact type    | Destination     | Reason                     |
|--------------|-----------------|----------------------------|
| Stable preference| Hermes memory + optional canonical note | Improves most sessions   |
| Durable project decision| Canonical Obsidian note/map | Source of truth          |
| Temporary task   | Session transcript                   | Not durable              |
| Unreviewed fact  | Memory Inbox                         | Review before promotion  |
| Secret value     | Encrypted secret manager             | Never in notes/indexes   |
FAILURE MODES

Common pitfalls and mitigations

Promoting unreviewed facts

Only move items from Inbox to canonical after review and expiry.

Bloating Hermes memory

Keep it small; rebuild from canonical when needed.

Indexing inbox or session

Never index raw temporary or operational traces.

Copyable public prompt

Design an Obsidian and retrieval setup for [PROJECT]. Use ordinary Markdown, separate canonical notes from inbox and archive material, add minimal metadata, and preserve manual navigation.
Public boundary

Use placeholders for paths, accounts, endpoints, identities, and credentials. Never publish secret values, private records, or a live control surface.

Verification gate

  • Verify scope and inputs
  • Run a focused test
  • Check outputs and evidence
  • Confirm no private data leaked