Tracking: Cortex V2 / vNext roadmap

[cursor]

Goal

Track Cortex V2 (memory control plane) per docs/CORTEX_V2.md / plan Cortex V2 Roadmap.

Thesis: Memory agents can trust before they act.

Signature trio: Reliability Gate · Evidence Graph · Memory Firewall

Phase 0

• Phase 0 audit — CURRENT_STATE.md + CORTEX_V2.md

P0 — Must Have

• Claim/Evidence data foundations + migrations
• Evidence Graph + explain API
• Temporal Truth Engine
• Memory Reliability Gate + /reliability/evaluate + cortex_evaluate
• MCP cortex_explain_memory
• CortexBench baseline + signature BLOCK scenario

P1 — Differentiators

• Memory Firewall
• Procedural + Experience Memory
• Outcome-driven updating (see also Phase 8: Implement outcome linker (decision → metrics/incidents) #63)

P2 — Intelligence

• Abstention + KnowledgeGap (see also Phase 8: Implement coverage scorer on /query and MCP inject #62)

Related existing backlog (not V2-specific)

• Redis query cache invalidation on pipeline writes #33 cache invalidation · Decay engine scheduler in docker-compose #36 decay scheduler · MCP server automated test suite and CI job #31/MCP tools: contradiction review and decision chain #32 MCP hardening
• Wire production API origin for public demo (CORTEX_API_ORIGIN) #61 public API origin · Phase 8: Meeting transcript connector #64 meetings · Hardening: thread-aware decision extraction + mid-confidence review queue #65 extraction hardening

Suggested order

1. Phase 0 audit
2. Data foundations → Evidence → Temporal
3. Reliability Gate → CortexBench signature
4. P1 Firewall / Procedures / Outcomes
5. P2 Abstention / Gaps

Non-goals

No new vector DB, no Kafka/Neo4j replacement, no connector sprawl, no frontend redesign before reliability features.