Research pass identified temporal conflict, supersession and provenance as central failures in agent memory.
Tool profile · provisional profile
Zep / Graphiti
Temporal graph direction is highly relevant for memory that changes. Strong candidate for contradiction, entity and lifecycle-heavy applications.
Provisional fit
78/100
Best for: Applications where entity relationships and time matter more than flat semantic recall.
Avoid if: you need a fully governed, citation-complete knowledge architecture without adding policy, evidence capture, and review workflow around the tool.
Caution: Graph structure helps, but does not automatically solve write authority, bad extraction, privacy boundaries or review workflows.
Model signature: Curation primary · app scope · Tool
Layer coverage
Where this tool fits.
This is not a completed review. It is a provisional profile from public positioning plus known failure-mode mapping. Hands-on benchmarks, source snapshots, and citation-bound claims are still required before stronger conclusions.
Production
Curation
Storage
Context Assembly
Governance
Review rule: a tool does not get credit for a layer unless it exposes inspectable behavior, not just a marketing claim.
Evidence notes
What the provisional profile has applied so far.
Graphiti is mapped to curation because temporal/entity modeling can represent evolving facts better than append-only memories.
Needs hands-on tests for deletion, conflict reconciliation, provenance visibility and graph drift.
Review packet
What a complete review must contain.
This page exposes the intended review structure. The current artifact is a profile, not a completed evidence-backed review.
Canonical source
Strengths
Applications where entity relationships and time matter more than flat semantic recall.
Limitations
Graph structure helps, but does not automatically solve write authority, bad extraction, privacy boundaries or review workflows.
Dimension assessment
Scope, volatility, authority, lifecycle, resource economics, interoperability, and evidence quality must each get a rationale and citations before final scoring.
Open questions
- What can be verified from docs, code, issues, benchmarks, and changelogs?
- Where does the tool fail under stale, contradictory, private, or high-cost knowledge?
- Which claims are vendor claims versus independently observed behavior?
Benchmark critique
No benchmark number is accepted as architectural evidence unless it says which layer it tests and what it misses: lifecycle, scope boundaries, authority, context cost, and governance.
Related systems
Related tools should be connected by evidence-backed edges: competes with, integrates with, implements concept, evaluated by, or has governance gap.
Update history
Provisional profile created. Stale-review detection, source snapshots, and changelog watching are required before this becomes a durable review.