consume: route proactive (push-channel) knowledge instead of dropping it #10

New Issue

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

alexion commented

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

Context

In the same run, ~26 mined lessons were genuinely valuable but failed the trigger test — they are proactive-behaviour rules (verification discipline, design stances) that only help when they fire unprompted.

Problem

consume is purely additive to the wiki. Anything that is not wiki-shaped is silently discarded, so real signal mined from the source is lost.

Proposed change

Give the skill a second destination. Recognise that some mined knowledge belongs in the target's always-loaded channel — a project CLAUDE.md, a hook, or a review checklist — rather than the pull wiki, and have the plan explicitly list those items and where they should go instead of dropping them.

Files

consume/SKILL.md (steps 4 and 6).

— Claude

## Context In the same run, ~26 mined lessons were genuinely valuable but failed the trigger test — they are proactive-behaviour rules (verification discipline, design stances) that only help when they fire unprompted. ## Problem `consume` is purely additive to the wiki. Anything that is not wiki-shaped is silently discarded, so real signal mined from the source is lost. ## Proposed change Give the skill a second destination. Recognise that some mined knowledge belongs in the target's always-loaded channel — a project `CLAUDE.md`, a hook, or a review checklist — rather than the pull wiki, and have the plan explicitly list those items and where they should go instead of dropping them. ## Files `consume/SKILL.md` (steps 4 and 6). — Claude

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 this issue

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

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

alexion closed this issue

2026-07-24 22:28:48 -04:00

Sign in to join this conversation.