GameCult/Eureka
Watch
9
0
Fork
You've already forked Eureka
 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

Changelog: prompt recall hook stays uninstalled #52

Merged
eureka merged 1 commit from self/recall-prompt-note into main 2026-11-06 20:21:26 +00:00
Conversation 0 Commits 1 Files changed 1 +2 -2
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
references/changelog.md
View file

@ -6,9 +6,9 @@ Record each change to the skill together with the evidence that motivated it.
Self, session `self-2026-11-04-eureka`.
Evidence. Operator: "It would be nice if things I say need building actually get built. So this persistence machinery is supposed to help with that, but it doesn't act unless you query it." The 2026-10-31 live-mind-sessions sequence (Huginn `docs/research/2026-10-31-live-mind-sessions-sequence.md`) planned nine cuts; the three admitted as specs landed, and the six left as table rows (plan readout, resume, the Self's replies reaching her Persona, the session keeper) had no spec, report or follow-up in the mind on 2026-11-06, so no recipe, lead or recall showed them. The step 1 rule kept them there: "Every later cut is one line in the prose map's cut sequence". Separately, `tools/recall.py prompt` (cut `cut-recall-prompt`, three Soul passes Holds) was installed only in its `admit` half on the operator's desktop.
Evidence. Operator: "It would be nice if things I say need building actually get built. So this persistence machinery is supposed to help with that, but it doesn't act unless you query it." The 2026-10-31 live-mind-sessions sequence (Huginn `docs/research/2026-10-31-live-mind-sessions-sequence.md`) planned nine cuts; the three admitted as specs landed, and the six left as table rows (plan readout, resume, the Self's replies reaching her Persona, the session keeper) had no spec, report or follow-up in the mind on 2026-11-06, so no recipe, lead or recall showed them. The step 1 rule kept them there: "Every later cut is one line in the prose map's cut sequence". (`tools/recall.py prompt` is uninstalled by ruling `eureka-substrate:ruling:recall-triggers-rescoped`; Self installed it this day without reading that ruling, and removed it the same evening once the hook itself surfaced the ruling.)
What changed. `SKILL.md` step 1: every later cut is a `follow_up` with its source and owner, open until Self closes it `Fixed` by the cut's report; an operator ruling that orders unbuilt work gets its follow-ups in the same batch. `references/briefs.md` (Imagination brief, budget split) and `references/campaign-state.md` (the prose map keeps the cut order and cites the follow-ups) follow. The six rows are backfilled as follow-ups `eureka-body:follow_up:cut-persona-hears-her-self`, `cut-self-session-resume`, `cut-session-keeper` and `cut-plan-readout-live` (receipt `mind-commit-9952f4b5149799109f5c03311deae81861404da51c5e007876d572a43f11ef44`; rows 5 and 6b fold into one). The prompt hook is installed in the operator's `~/.claude/settings.json`. Still open: follow-ups reach a Mind's Persona only if she queries for them (`eureka-body:follow_up:recall-gap-flag-replay`).
What changed. `SKILL.md` step 1: every later cut is a `follow_up` with its source and owner, open until Self closes it `Fixed` by the cut's report; an operator ruling that orders unbuilt work gets its follow-ups in the same batch. `references/briefs.md` (Imagination brief, budget split) and `references/campaign-state.md` (the prose map keeps the cut order and cites the follow-ups) follow. The six rows are backfilled as follow-ups `eureka-body:follow_up:cut-persona-hears-her-self`, `cut-self-session-resume`, `cut-session-keeper` and `cut-plan-readout-live` (receipt `mind-commit-9952f4b5149799109f5c03311deae81861404da51c5e007876d572a43f11ef44`; rows 5 and 6b fold into one). Still open: follow-ups reach a Mind's Persona only if she queries for them (`eureka-body:follow_up:recall-gap-flag-replay`).
## 2026-11-06: three tiers of context