Batch 1
Run run-full-improvement-pass-on-note.md once per note, one note at a time, in the order listed. Read the workshop README for operating constraints before starting.
Status: complete.
Notes
| # | Path | Status |
|---|---|---|
| 1 | kb/notes/llm-recompute-cost-inverts-the-store-vs-recompute-default.md |
complete — keep (reframe); follow-up complete |
| 2 | kb/notes/superseded-choices-are-retained-superseded-beliefs-are-not.md |
complete — keep (reframe); follow-up complete |
| 3 | kb/notes/areas-exist-because-useful-operations-require-reading-notes-together.md |
complete — keep |
| 4 | kb/notes/documentation-generates-the-system-rather-than-describing-it.md |
complete — keep (reframe); follow-up complete |
Order is binding. The seven notes are topologically sorted across both batches so every note runs after the notes it cites, and a reframe therefore lands before anything citing it is passed. Within batch 1 the live edge is 4 citing 1.
Per-note context
1. llm-recompute-cost-inverts — the oldest note here and the least
examined against its new neighbours. Cited by three others across both batches,
which is why it runs first. Received a scope paragraph on 2026-08-23 naming the
volume condition under which its materialization default flips back, plus a
contrasts edge to addressability-grain. That addition propagates a caveat
its sibling frontloading-spares-execution-context already carried; it is not a
correction, and the note's own instances sit far on the safe side of the
condition.
2. superseded-choices-are-retained — scoped against
artifact-classification, which assigns the maintenance operation; this note
claims only what happens to displaced content. Watch that the distinction
survives a pass, since it is narrow. Cited by
artifacts-must-preserve-named-choice-scope in batch 2.
3. areas-exist-because-useful-operations-require-reading-notes-together —
the note here most likely to come back delete or rehome rather than keep,
and the one whose disposition has consequences outside this cluster.
The earlier choice-scoping sweep flagged choice-dependent propositions after its
opening: a ~40-note split threshold presented as generally determined, a
single-area membership default, and assertions about the areas: field, Topics
footers, and areas.md. That machinery is retired —
ADR 004 replaced areas
with tags — so parts of the note describe a system that no longer exists.
Two things temper that. Its description already reads "while fixed sizes, membership rules, tags, and index layouts remain implementation choices", so a binding repair has been partly applied since the sweep; check the body against that before assuming the sweep's findings still stand. And the opening mechanism — orientation and comparative reading need bounded, sufficiently related note sets — survives the removal test independently of the retired machinery, which makes retire-versus-repair a real question rather than a formality.
Consequences of a non-keep disposition.
artifacts-must-preserve-named-choice-scope in batch 2
cites this note evidenced-by as the worked hard case for its removal test; a
delete would take that evidence with it. Two citers outside the cluster,
execution-shaping-determines-directory-placement and
two-context-boundaries-govern-collection-operations, would also need
reconciling. Record these in the packet's Open items rather than acting on them
in the pass.
4. documentation-generates-the-system — written in the originating
conversation but committed by a concurrent session, which is why a
commit-trailer filter misses it. Its central move is a reconciliation with
commitment-not-derivation-creates-new-ground-truth rather than a flat
inversion: the pair is bidirectionally irrecoverable, so artifact-level "source
of truth" is malformed. Grounds on note 1 above and is extended by
addressability-grain in batch 2.