Skip to content

docs: add v3.1 "Make It True" design spec and phase plan - #31

Merged
RichardHightower merged 1 commit into
mainfrom
claude/spillwave-agent-memory-review-len4et
Aug 30, 2026
Merged

docs: add v3.1 "Make It True" design spec and phase plan#31
RichardHightower merged 1 commit into
mainfrom
claude/spillwave-agent-memory-review-len4et

Conversation

@RichardHightower

Copy link
Copy Markdown
Contributor

Summary

Add the comprehensive design specification and phase plan for v3.1 "Make It True" milestone. This document outlines the systematic effort to close the gap between v3.0's claims and its actual implementation, focusing on integration truth, performance validation, honest benchmarking, and proper project positioning.

Key Changes

  • New planning document: docs/plans/v3.1-make-it-true-plan.md (410 lines)
    • Detailed analysis of 9 major claim/reality gaps in v3.0 with evidence citations
    • Repositioning strategy: shift from "category leader with best-in-class retrieval" to "local-first memory for AI coding agents"
    • Four sequential phases (54–57) plus a launch side quest (58)
    • Specific, testable acceptance criteria for each phase plan
    • Process changes to prevent verification-by-existence failures in future milestones

Phase Structure

Phase 54 (Integration Truth): Wire the orchestrator into the CLI, fix silent no-ops in BM25 indexing, make the Hybrid retrieval layer actually hybrid, consolidate RRF implementations, remove dishonest daemon flags, and establish a lock-poisoning policy.

Phase 55 (Performance Truth): Root-cause the 65-second TOC p50 latency, fix percentile methodology (currently computed from 3 samples), and re-baseline measurements.

Phase 56 (Honest Benchmarks): Fix the custom benchmark harness (recall@k, compression_ratio, error handling), rewrite the LOCOMO adapter against the real dataset with LLM-as-judge scoring, and gate publication on honest methodology.

Phase 57 (Shop Window & Positioning): Add root README, LICENSE, positioning writeup, and declare supported-surface tiers to match solo-maintainer capacity.

Phase 58 (Launch): Blog post, community announcements, and v3.1.0 release.

Notable Details

  • Includes a detailed risk matrix with mitigation strategies
  • Establishes three new process rules (execution-evidence, reachability, retrospective) to prevent recurrence of v3.0's verification-by-existence failure mode
  • Estimates 14 plans across the milestone (2–4 weeks part-time effort)
  • All acceptance criteria are testable and tied to committed artifacts
  • Honest decision gate for LOCOMO benchmark: publish methodology regardless of score competitiveness, or hold entirely if not defensible

Rationale

v3.0 shipped strong code (~1,200 tests, correct transactional outbox, real integrations) but with a systematic gap between documented claims and executable reality. This milestone prioritizes closing that gap over adding new capabilities, ensuring every public statement about Agent-Memory is measurable and defensible before opening the shop window.

https://claude.ai/code/session_01R6oegDbEcoNgWHckPyZYCJ

Full-project review (2026-08-30) found a systematic gap between planning-doc
claims and running code: dead orchestrator crate, silent BM25 outbox no-op,
mislabeled Hybrid layer, an unrun LOCOMO adapter with an invented schema and
substring scoring, and a 65s TOC p50 in the recorded perf baseline.

This spec defines milestone v3.1 (Phases 54-58): integration truth,
performance truth, honest benchmarks with a real LOCOMO schema and
LLM-as-judge, repo shop window + local-first positioning, and GSD process
rules requiring execution evidence for verification.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01R6oegDbEcoNgWHckPyZYCJ
@RichardHightower
RichardHightower merged commit d937d1d into main Aug 30, 2026
19 of 21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants