Memini Docs

Memini: implementation plan (draft v0)

Milestones in build order, with acceptance scenarios. For current implementation paths and tests, see the developer guide. Requirements describe the contracts.

Tracking

Tasks live in beads, one epic per milestone plus two tracks that run alongside: "CI/CD on GitHub" and "Production hardening". bd ready lists what can start now; bd show <id> gives the description and the acceptance check. The release task Release v0.1.0 depends on every production gate.

M0. Skeleton

Done when: docker compose up starts, an MCP client connects with a token and status answers.

Done when: two repositories in two workspaces are indexed; a new commit re-chunks only changed files; a rebuild from the mirrors gives the same chunk ids; the eval runs.

M2. Ingest contract, messages and meetings

Done when: synthetic chat and meeting fixtures ingest twice with no change on the second run; "meetings I attended about X" and "messages to me about X" return the expected records; expired records and their chunks disappear.

M3. MCP recipes

Done when: one recipe run by both executors yields identical records; an incomplete window leaves the checkpoint in place and lists the missing calls; a parser fix replays from stored raw responses.

M4. Decision journal

Done when: on a fixture where thread B reverses thread A, A becomes superseded, the default list shows only B and the history shows the chain with evidence links; the eval reports precision, recall and supersession accuracy for the chosen local model.

M5. Release

Done when: a clean machine goes from the release installation guide to a working search over one repository and one pushed thread.

Order and risks