ChainMemory Docs

Trust status on every memory — memories are screened at write time by deterministic, auditable rules; suspicious ones are born tentative and always delivered marked
Owner governance: POST /v1/memories/:id/trust (approve / quarantine / tentative); quarantined memories are excluded from context, inject, quotes and oracle — their on-chain fingerprint remains as immutable evidence
Verifiable rollback: POST /v1/project/:name/state/rollback — append-only restore, byte-identical to the anchored source version; faithfulness proven by hash equality, history never mutated
Memory forensics: GET /v1/memory/:id/forensics — complete timeline of a memory: birth, trust, anchoring, every recall and injection, Project Brain citations
Recall instrumentation: every read is now logged with per-memory counters and token accounting
Checkpoint anchoring pipeline repaired; dual-channel system alerts (Telegram + alert-as-memory)

New tool: update_project_state — Autonomous consolidation via MCP. Any AI client can propose structured operations to update the Project Brain; the server validates, applies, and anchors on-chain.
22-operation grammar for state mutations (decisions, milestones, risks, metrics, vocabulary, and more)
Resilient processing: invalid ops are rejected individually, valid ops still apply
Evidence linking via evidence_memory_ids — server resolves event hashes and builds Merkle proofs automatically
Architecture: “client consolidates, chain verifies”

Project Brain consolidated and anchored on-chain (versions v1–v8, publicly verifiable)
Semantic search rewritten (faster, ~2.4s)
Non-custodial write path proven end-to-end (client signs, server never holds the key)
Encryption at rest (AES-256-GCM) for API keys
Public verification endpoint: GET /v1/verify/:name