consume: add a trigger-ability acceptance test to note selection #9

New Issue

alexion · 2026-07-24T21:38:03-04:00

alexion commented

2026-07-24 21:38:03 -04:00

Context

A /consume run over a NixOS dotfiles project produced a 94-note plan on the first pass, and it took three full re-derivations of the selection bar to land on ~68. The only acceptance test the skill states — a note must "generalize past the target" (SKILL.md step 4) — is necessary but not sufficient.

Problem

"Generalizes" admits a large class of notes that are true and transferable but that a reader would never retrieve: general engineering-judgment principles such as "test at the highest seam" or "verify the mechanism, not the outcome". The wiki is a pull medium, so a note only earns its place if something would send a reader to look it up.

Proposed change

Add a second, decisive acceptance test to step 4: trigger-ability — there must be a recognizable symptom, error, or task that would send a future agent searching for exactly this note. State the two premises behind it:

The wiki is retrieval-on-demand (pull), so knowledge whose only value is firing unprompted does not belong here however well it generalizes.
The consumer is an amnesiac agent, so "the reader will internalize it" is never a reason to cut — trigger-ability, not memorability, is the axis.

Files

consume/SKILL.md, step 4.

— Claude

## Context A `/consume` run over a NixOS dotfiles project produced a 94-note plan on the first pass, and it took three full re-derivations of the selection bar to land on ~68. The only acceptance test the skill states — a note must "generalize past the target" (SKILL.md step 4) — is necessary but not sufficient. ## Problem "Generalizes" admits a large class of notes that are true and transferable but that a reader would never *retrieve*: general engineering-judgment principles such as "test at the highest seam" or "verify the mechanism, not the outcome". The wiki is a pull medium, so a note only earns its place if something would send a reader to look it up. ## Proposed change Add a second, decisive acceptance test to step 4: **trigger-ability** — there must be a recognizable symptom, error, or task that would send a future agent searching for exactly this note. State the two premises behind it: - The wiki is retrieval-on-demand (pull), so knowledge whose only value is firing *unprompted* does not belong here however well it generalizes. - The consumer is an amnesiac agent, so "the reader will internalize it" is never a reason to cut — trigger-ability, not memorability, is the axis. ## Files `consume/SKILL.md`, step 4. — Claude

alexion referenced this issue

2026-07-24 21:40:13 -04:00

consume: name the general-lesson + specific-residue split #12

alexion referenced this issue

2026-07-24 21:40:13 -04:00

consume: plan report should justify each note's inclusion, not only trace provenance #13

alexion referenced this issue from a commit

2026-07-24 22:22:46 -04:00

feat: route consume knowledge to two channels (#9-#14)

alexion referenced a pull request that will close this issue

2026-07-24 22:23:32 -04:00

feat: route consume knowledge to two channels (#9-#14) #15