WorkAkashic Records
SHARED MEMORYINTELLIGENCE

Akashic Records

Shared context that survives the next agent session.

Engineering case study · architecture and capabilities, not a live service-status page.

Private repository · public architecture below
Akashic Records concept artwork

Concept artwork · not a product screenshot.

MCP + REST
Access
4
Memory types
19
MCP tools
Sep 27, 2026
Inventory
// What It Does

Akashic Records provides a shared memory layer for project knowledge, lessons, operational notes and agent context. MCP and REST access let tools retrieve relevant information instead of rebuilding context from scratch at the start of each task.

The design combines semantic retrieval with structured records for sessions and events. Four memory categories separate episodic events, semantic knowledge, procedural rules and short-lived working context. Deterministic identity keys support repeatable writes; they are not a guarantee that differently worded records never overlap.

The MCP inventory checked on September 27, 2026 contains 19 tools. Alongside query, write, recall and context assembly, it includes progressive search, timeline and deep retrieval, updates and history, health and insights, and closeout context. This is a dated interface snapshot, not a live monitor of index coverage or test results.

The architectural value is continuity: agents can discover relevant evidence, retrieve detail and carry a better-grounded context into the next task. Memory still needs source checking, lifecycle management and appropriate access boundaries.

// Illustrative Interface

Sample data · not connected to a live service. Displayed trades and P&L are illustrative, not verified results.

AKASHIC RECORDS
sample retrieval results
$mind_query"indecision bias"top_k=3 · 42ms
proceduralmem_a4b2
★ 0.94
InDecision bias interpretation rules
Directional conviction is an input; execution requires separate risk checks.
episodicmem_c8d1
★ 0.89
Foresight warm reload incident (Feb 2026)
Checkpoint recovery restores selected state after restart; recent changes may require reconciliation.
semanticmem_f3e7
★ 0.86
PolyEdge snipe window parameters
5m=20s, 15m=45s, 1h=120s, daily=300s. Returns None if ttc > window — signal logged but no trade.
// Architecture
System design · simplified flow
  1. 01 →Memory write
  2. 02 →Validation & storage
  3. 03 →Semantic retrieval
  4. 04 ✓Context assembly

Validated memory writes feed semantic retrieval and context assembly. Lifecycle tools manage updates, history and expiry; namespaces scope access.

// Ecosystem Connection

Design relationships across the documented systems; these links do not indicate current service uptime.