LOCAL ALPHA OPENREST APIMCP STDIOPOSTGRES 16DASHBOARDPRIVATE DEPLOY

Audit, govern, and migrate your AI agent's memory.

The open-source control plane for agent memory eval, evidence, and portability.

Run it locally, query demo memory, and open an Evidence Ledger trace before you trust durable agent context.

Try in 10 minutes → View on GitHub ↗

$ pnpm quickstart -- --dry-run --activation-report

Golden clients3

MCP tools11

Demo eval size4

Latencypending

lore › context.ledger local · demo fixture

Demo memories4public fixture

Golden clients3Claude · Cursor · Qwen

Trace rows2retrieved and used

P95 latencypendingnot claimed

sourcememoryevidenceused_in_responsestale_scoresensitivityreview_status

claude-code#a4f1api-contractyes lowapproved

cursor#b2c8pricing-noteyes lowapproved

qwen-code#c9d3deploy-fixyes medflagged

hermes#d1a7private-keyyes highredact

fastgpt#f3c1old-schemano medreview

context.compose()
demo eval
policy pass
trace linked
k 5

gov · gate

demo-private · audit_loglocal alpha · public fixture

Multiple coding agents

Share governed context across Claude Code, Cursor, Qwen Code, and local agents.

Audit agent memory

Open a trace and see which rows were retrieved, used, ignored, stale, or risky.

Migrate memory later

Use MIF-style export fields for provenance, supersedes, and contradicts relationships.

01 / PROBLEMThe memory gap

Agents remember. Teams need proof.

Every coding agent, support bot, and copilot is now writing to long-term memory. Almost none of them can show the audit trail behind a single answer.

Stale memory

Last week's API contract is still being recalled into this morning's pull request. Nobody flagged it.

Unknown provenance

An agent quoted a fact. Which document, session, user, and run produced it? Without provenance: a shrug.

Unsafe writeback

Agents silently persist hallucinations, PII, and one-off conversation noise into shared long-term memory. Forever.

Backend lock-in

Every vector store ships a different schema, a different retrieval API, and quietly captures your data. Migrating costs a month.

02 / SYSTEMPipeline

One context plane. Every agent surface.

MCP clients query through a single composer that passes every retrieval through eval, trace, and governance before it reaches the model. Backed by Postgres and a portable agent-memory adapter.

System diagram · context plane v0.6read path · policy gate · persist + audit

01MCP clients

Lore exposes MCP stdio and REST surfaces so agents query, write, and review through the same governance layer.

02context.query

A single typed call your agent can rely on. Returns ranked memories with provenance, freshness, and policy state attached to every row.

03composer

MCP clients query through a single composer that passes every retrieval through eval, trace, and governance before it reaches the model. Backed by Postgres and a portable agent-memory adapter.

04eval / trace / governance

Run the same retrieval evaluation against your seed dataset. Watch recall, precision, and stale-hit rate move as you change retrievers, rerankers, and embedding cuts.

05Postgres + adapter

Memory Interchange Format. Export the entire corpus — embeddings, provenance, policy state — and replay it anywhere. No lock-in.

03 / FEATURESProduct surfaces

Built for operators, not memory hype.

Every surface is inspectable, scriptable, and designed to show proof instead of product theater.

F · 01context.query

Context Query

A single typed call your agent can rely on. Returns ranked memories with provenance, freshness, and policy state attached to every row.

stdio · httpk=1..32ttl-aware

F · 02eval.run

Memory Eval Playground

Replay queries against your seed dataset. Tune retriever, reranker, and freshness cutoff. Compare runs side-by-side. Pin the winner.

recall@5precision@5MRR

F · 03observability

Memory Observability

A live trace of every retrieval, every write, every redaction. Drill into any span. Filter by source agent, user, or policy outcome.

span treeper-agentp50/p95/p99

F · 04governance

Governance Review

Every writeback passes a policy gate. Human-in-the-loop review for sensitive scopes. Diff, approve, redact, or reject — with audit.

policy.loreapprove/rejectdiff view

F · 05export.mif

MIF-like Portability

Memory Interchange Format. Export the entire corpus — embeddings, provenance, policy state — and replay it anywhere. No lock-in.

JSON Lines.lore.tarreplay()

F · 06deploy.local

Private Deployment

Single docker compose. No telemetry, no phone-home, no proprietary embedding endpoint. Run it on your laptop, then on your VPC.

docker composeair-gappedBYO Postgres

04 / ALPHAShipped this week

What is in v0.6 alpha.

Distribution and trust release: AI-readable docs, activation proof, public-safe demos, and launch materials on top of the local-first control plane.

✓Graph-Augmented Hybrid Memory Engine betaPostgres FTS + pgvector hybrid recall, v12 episode/item/chunk schema, Postgres temporal graph, lifecycle propagation, v12 eval gate / production gate1.2.0-beta

✓Cloud Memory Engine betaGoogle sign-in, automatic capture, SQS worker fan-out, RDS truth store, Qdrant hybrid recall, Memory Inbox exceptions, and Evidence Ledger1.1.0-beta

✓REST API + OpenAPI/v1/context, /v1/memory, /v1/eval — documented at /openapi.jsonv0.6.0

✓MCP stdio SDK transportDrop-in for any MCP-compatible clientmcp 0.6

✓Evidence LedgerTrace-centric proof of retrieved, used, ignored, and risky memoryledger

✓Activation reportDry-run and real first-value proof with redacted local evidenceactivation

✓AI-readable docs/llms.txt, /llms-full.txt, canonical metadata, and public-source boundariesllms

✓Public-safe evalShare metrics without raw memory content or dataset messageseval

✓Distribution packMCP registry, agent plugin, marketplace, and launch content draftsdocs

✓Design partner intakeIssue template, intake rubric, and activation scorecardintake

◐Public SaaSHosted multi-tenant sync, billing, and remote MCP HTTP stay out of v0.6roadmap

Build manifest

1.2.0-beta · 04.05.2026

graph beta: v1.2 graph-augmented hybrid memory engine
public release: v1.2.0-beta formal pre-release
runtime: node 22+ · RDS 16 · Qdrant
smoke: passing · production smoke
bundle: static website · Docker images
memory floor: RDS truth · Qdrant index
telemetry: privacy-safe
license: Apache 2.0

# first run

git clone github.com/Lore-Context/lore-context
pnpm install && pnpm quickstart -- --dry-run --activation-report
pnpm openapi:check # release gate

05 / EVALMethodology

Eval proof report. On your own data.

Run the same retrieval evaluation against your seed dataset. Watch recall, precision, and stale-hit rate move as you change retrievers, rerankers, and embedding cuts.

prod/smoke-2026-05-04OpenAPI · Hosted MCP · OAuth start · Dashboard · LLM files · no benchmark claimPUBLIC · v1.2.0-beta · memory engine

Recall@51.0004-item smoke dataset vs baseline

Precision@50.200expected with k=5 vs baseline

MRR0.875one query ranked #2 vs baseline

Stale-hit0.000no stale demo rows vs baseline

p95 latencypendingnot measured via MCP vs baseline

What the smoke run proves

pipeline retrieves gold memorypass

Evidence Ledger trace is inspectablepass

stale rows are reported as zeropass

larger dataset still requiredtodo

latency must be measured via direct APItodo

Publication guardrails

4-item datasetsmall

no LOCOMO claimtrue

no p95 claimtrue

raw data archivedyes

methodology firstyes

Use this as methodology, not a benchmark win.Read report →

06 / INTEGRATIONSDrop-in MCP

Speak the protocols your agents already use.

Lore exposes MCP stdio and REST surfaces so agents query, write, and review through the same governance layer.

CLClaude Codemcp.stdio · alpha

CUCursormcp.stdio · alpha

QWQwen Codemcp.stdio · alpha

OPOpenClawmcp.stdio · alpha

HEHermesmcp.stdio · alpha

DIDifyrest.v1 · alpha

FAFastGPTrest.v1 · planned

RORoo Coderest.v1 · planned

OPOpenWebUIrest.v1 · planned

LOLocal agentsrest.v1 · planned

07 / STARTStart

Start with a local alpha. Prove memory quality before you scale it.

Four commands. A seeded demo dataset. A Playwright smoke pass that proves the dashboard renders. Bring your own Postgres, or use the bundled one.

Try in 10 minutes →View architecture

$ git clone https://github.com/Lore-Context/lore-context
$ cd lore-context
$ pnpm install
$ pnpm quickstart -- --dry-run --activation-report
$ pnpm openapi:check
$ pnpm smoke:dashboardverified · OpenAPI · evidence · smoke passing