ARCHITECTURE

ChainMemory has a 3-layer architecture:

Layer 1: Capture

The Chrome extension, MCP server, or direct API calls capture content from AI conversations. Content is processed, tagged, and linked to a project.

Layer 2: Storage & Consolidation

Each memory is stored in the episodic database with its SHA-256 hash. An AI model — the client, through the MCP server or the API — proposes structured operations from a 30-op grammar. The server validates them against the grammar's invariants, checks that every cited memory resolves to an anchored event hash, and applies them with a deterministic builder: the model proposes, the server decides. Nothing on the server reads memories to extract knowledge on its own.

Layer 3: On-Chain Verification

Each version of a project's consolidated state is anchored on the ChainMemory blockchain, normally within ten minutes of being written (Chain ID 202604). The state hash is recorded in the ProjectStateAnchor contract, creating an immutable proof that this state existed at that moment.

Pipeline
AI Conversation
      |
  Extension / MCP / API
      |
  Memory (SHA-256 hash)
      |
  Client proposes ops, citing memories (MCP / API)
      |
  Server validation + deterministic builder
      |
  Project State (decisions, milestones, risks, priorities, environment)
      |
  Anchor on-chain (tx hash + block number)
      |
  Public verification (/v1/project/:name/state/anchor)