Publish Phase 3 memory ADRs (next free numbers after ADR-0047) covering HNSW expand, composite scoring v2, temporal conflict detection, memory tenant isolation, and retrieval-quality benchmark methodology. Do not reuse ADR-0040–0046.
Milestone 3.E.4 — ADR Consolidation and Index Update
Status: Planned
Goal: Track E — Exit Gate
Phase: 3 — Core Memory Substrate
Estimated effort: 1 day
Why This Milestone Exists
Per the repo's ADR workflow, Phase 3 needs new ADRs for the memory substrate. ADR-0040 through ADR-0046 are already published for Phase 2.5 (Anthropic adapter through embedder registry). Temporal validity foundation is ADR-0047. Assign the next free numbers at write time — do not reuse 0040–0046.
| Planned topic | Notes |
|---|---|
| Memory schema v2 expand (HNSW / multi-label) | Expands ADR-0047 foundation |
| Composite memory scoring v2 (category-conditional decay) | |
| Temporal-interval-aware conflict detection | Builds on ADR-0047 columns |
| Memory service tenant isolation (RLS + app-layer) | Phase 3 equivalent of ADR-0016 |
| Retrieval-quality benchmark methodology | Phase 3 sibling to ADR-0034 |
Each follows the exact template already in use: Status/Date/Authors header, Context, Decision, Consequences (positive/negative), References.
Orientation (indicative)
Named paths, package layouts, libraries, schemas, env vars, and commands anywhere on this page are rough sketches for orientation — inspiration and a baseline, not a required change list.
During implementation, expect to:
- open the live tree and follow existing patterns before inventing new ones
- research current constraints (latency, tenancy, deploy shape, libraries) more deeply than this page can
- advance the design beyond the sketch where measurement or code reality says so
- land work in different filenames, merged packages, deferred docs, or new surfaces when the situation calls for it
Prefer outcomes over matching any particular file tree or command sequence.
Areas that may be involved (situational — not a checklist):
- Evaluation / benchmarks
- Memory service / repositories
Success signals
Outcome-oriented signals that the milestone is in good shape. Exact filenames, package layouts, and commands may differ from any sketches above.
- Phase 3 memory ADRs written at next free numbers after ADR-0047 (not 0040–0046), following existing template
- Updated (exact path may differ)
-
index.mdx"through ADR-00xx" pointer updated -
pnpm exec fumadocs-mdxregeneration successful - Repo guards / CI checks still pass
Prerequisites
- All Track A–D milestones (ADRs document decisions made during implementation)
Last updated on