Phase 3 — Tracks

Track A — Schema & Migrations

Memory schema with temporal validity, multi-label categories, and HNSW-ready vector columns. Schema details are a planning baseline and may be refined during implementation.

Preferred sequencing within track: single foundation milestone; blocks Tracks B–D. Status: 3.1.1 completed (ADR-0052 / 000017).

• 3.1.1 — Memory Schema v2 (completed)

Track B — Vector Store & Embedding

Pluggable vector store interface with pgvector HNSW as the starting backend preference (replacing the earlier IVFFlat plan). Alternatives can be investigated if latency/recall measurements require it.

Preferred sequencing within track: depends on Track A schema.

• 3.2.1 — Vector Store Interface & pgvector HNSW

Track C — Write Pipeline

Memory write pipeline stages: validate → PII detect/redact → dedup → embed → near-dup → conflict detect → DB write → cache update → index. Stage order is the preferred starting sequence and can be adjusted after integration testing.

Preferred sequencing within track: 3.C.1 → 3.C.2 → 3.C.3 → 3.C.4 after Tracks A/B.

• 3.C.1 — PII Detection & Redaction
• 3.C.2 — Content Near-Duplicate Detection
• 3.C.3 — Temporal Conflict Detection
• 3.C.4 — Multi-Label Classification

Track D — Read/Ranking Pipeline

Semantic search read path, composite scoring with category-conditional decay, and Redis sorted-set hot cache.

Preferred sequencing within track: 3.D.1 → 3.D.2 → 3.D.3 after Track B.

• 3.D.1 — Semantic Search Read Path
• 3.D.2 — Composite Scoring v2
• 3.D.3 — Hot Cache (Redis Sorted Set)

Track E — Exit Gate

Security integration suite, E2E lifecycle test, retrieval-quality benchmark, ADR consolidation, and exit audit.

Preferred sequencing within track: 3.E.1 → 3.E.2 → 3.E.3 → 3.E.4 → 3.E.5 after Tracks A–D.

• 3.E.1 — Memory Security Integration Suite
• 3.E.2 — E2E Memory Lifecycle Test
• 3.E.3 — Retrieval-Quality Benchmark Sign-Off
• 3.E.4 — ADR Consolidation and Index Update
• 3.E.5 — Phase 3 Exit Audit Document