Context
A one-shot generator produces a wiki that was correct on the day it ran. Both halves of the alternative already exist and are not wired to each other:
- ai-architect-mcp-codebase:
detect_changes and co-change edges
- Cortex: staleness detection, the groomer,
wiki_reindex
Until they are connected, a generated wiki has the same decay profile as any one-shot tool, which removes the main reason to choose a pipeline with a memory layer in it.
Verified 2026-08-06: the nearest competing documentation generator writes into a date-stamped directory (<TOOL>-<YYYY-MM-DD>/) and has no regeneration path. A second run produces a second directory, not an update to the first. That is structural to a one-shot orchestration, not an oversight someone will patch. Freshness is therefore the one axis where a memory layer is a moat rather than a tax, and it is the least contested item in this series.
Scope
Wire change detection to selective page regeneration.
Acceptance criteria
- After a change touching N files, only the pages whose backing symbols changed are regenerated. Asserted with a fixed change set and a count assertion on regenerated pages — not "completed without exception".
- A page whose backing code changed and which was not regenerated is marked stale in its front-matter and in
wiki_list. Both are asserted.
- A deleted symbol invalidates the claims citing it: a
file:line citation pointing at code that no longer exists is detected, and the detection itself is asserted (the signal, not a downstream effect).
- Idempotent: running twice with no intervening change regenerates nothing. Asserted with a count of zero.
- Provenance tags survive regeneration; a regenerated page does not downgrade
extracted claims to authored.
- Scoped mutation run on the changed files: zero surviving non-equivalent mutants, or each survivor documented as equivalent.
- Completion Ledger in the PR.
Depends on
Context
A one-shot generator produces a wiki that was correct on the day it ran. Both halves of the alternative already exist and are not wired to each other:
detect_changesand co-change edgeswiki_reindexUntil they are connected, a generated wiki has the same decay profile as any one-shot tool, which removes the main reason to choose a pipeline with a memory layer in it.
Verified 2026-08-06: the nearest competing documentation generator writes into a date-stamped directory (
<TOOL>-<YYYY-MM-DD>/) and has no regeneration path. A second run produces a second directory, not an update to the first. That is structural to a one-shot orchestration, not an oversight someone will patch. Freshness is therefore the one axis where a memory layer is a moat rather than a tax, and it is the least contested item in this series.Scope
Wire change detection to selective page regeneration.
Acceptance criteria
wiki_list. Both are asserted.file:linecitation pointing at code that no longer exists is detected, and the detection itself is asserted (the signal, not a downstream effect).extractedclaims toauthored.Depends on