Ferryte does not ask you to migrate your memory layer or wrap your agent. It instruments what you already run, records where every memory came from, and lets you trace any answer back to the memory behind it.
Start with one line — ferryte.instrument(). Mem0 and Zep clients created afterward are detected automatically; shipped adapters cover Letta, Cloudflare, and Ferryte's vector reference store, while custom stores plug into the same small adapter protocol.
import ferryte
ferryte.instrument()
# the rest of your app stays the sameAs your agent runs, Ferryte records where every memory came from, what it derived into, and every retrieval that pulled it into a prompt. One optional call per turn links memories to the exact answers they produced.
# recorded automatically
mem_3f9c
← source zendesk-ticket-8821
→ derived summary_v2, embedding
→ retrieved 14x (tenant=acme)
# optional: exact answer→memory edge
ferryte.record_answer(
answer_id=turn_id,
content=answer,
artifact_ids=[m.id for m in context],
)Point at a wrong, stale, or leaked answer. Ferryte ranks the memories that caused it — using recorded answer edges, retrieval evidence, and quote-level shared spans — and names the fault: phantom, stale, cross-tenant, zombie, or poisoned.
$ ferryte why "Legacy Free plan"
#1 stale belief · conf 1.00
from zendesk-ticket-8821
recorded in context for this answer
shared span: "legacy free plan"
superseded by billing-sync-0601Before deleting anything, replay the retrieval without the top suspect and see what would have entered the context instead. Then delete or supersede the bad memory and re-run to prove nothing survived.
$ ferryte why "Legacy Free plan" --replay
counterfactual: without mem_old → Pro plan
$ ferryte test --scenario source-revocation
source-revocation PASS
no surviving markers in retrieval ✓› agent.ask("acme", "what plan is this customer on?")
You're on the Legacy Free plan.
# wrong — they upgraded to Pro last week.
# somewhere a stale fact still wins retrieval.
# which memory? open the logs and start reading…› ferryte why "Legacy Free plan"
caused by 3 candidate memories · top conf 1.00
#1 stale belief · conf 1.00
Customer acme is on the Legacy Free plan.
from 'zendesk-ticket-8821'
recorded in context for this answer
shared span: "legacy free plan"
› ferryte why "Legacy Free plan" --replay
counterfactual: without it → Pro plan
fix: delete it, then re-run why to confirmBlind spots are surfaced in every report. We would rather hand you ranked candidates than a confident wrong answer.
Your app called record_answer() — we know exactly which memories were in context when this answer was produced. Anchored, not inferred.
The memory demonstrably entered the prompt for a matching query. The difference between a plausible suspect and a live one.
Rare shared terms count, common ones don't. Contiguous shared spans of three or more meaningful tokens are quoted back as evidence.
A pluggable embedder catches paraphrase when the exact words differ. Token-bag by default, neural drop-in when you want it.
No recorded edge? The report says method: overlap, never exact. Ferryte labels the strength of its own evidence — the same honesty that powers the blind-spot map.
Instrumented reference store + adapter base ship today. pgvector, Chroma, and Qdrant need a thin store-specific adapter.
Auto-patch on construction. Full lineage across its LLM-extracted facts.
Verified live in the public benchmark harness. A Core runtime adapter is not shipped yet.
Captures episodes + graph facts; traces shared-node summaries back to source.
Archival passages + derived summaries. Shipped in Core; pass the client explicitly.
Vectorize-backed memory. Shipped in Core; pass the client explicitly.
Implement the small Adapter protocol for your write, search, and delete surface.
Tracing hooks on the roadmap.
It patches the write/search/delete methods of detected memory clients (plus a constructor hook for clients built later). Your agent code is unchanged; remove the line and Ferryte is gone.
A local SQLite file (.ferryte/lineage.db) in your environment. No telemetry, no phone-home, no external service. The optional dashboard reads a local API you start yourself.
Nothing. Reports are files you generate and choose to share. A hash-only fingerprint mode exists for teams that don't want raw content even in the local store.
Every line. The engine is source-available (BSL 1.1) — auditability is the whole reason the license keeps the source open.
Stop grepping traces at midnight. One command to the memory that caused it.
See exactly what the agent remembers about a user — and correct it.
Prove a deleted memory — and everything derived from it — is really gone.