Repository navigation
promote-memory-council's description says 'forked context'; its body requires a fresh context #158
Description
Revision: 6246c35 (main). Reported by Copilot on PR #155 (comment); confirmed against the source.
Observed. The description of .claude/agents/promote-memory-council.md says each critic runs "in an isolated forked context"; its body (line 105) says each critic runs in its own fresh context — a conversation fork would inherit exactly what the council must not see.
Expected. The description, which callers read first, matches the body. Done when the description says fresh context.
Activity
pedrohcgs commentedon Sep 27, 2026
Landed on main in #163 (merge commit 97887fc).
What was wrong.
promote-memory-council's description said its critics run in a "forked context", but its body requires each to run in a fresh one. That matters: a fork inherits the conversation, which is exactly what the council must not see.Fixed in 0425fd6. The description now says "isolated fresh context". The same wording was corrected in seven other files (
review-fencing.md,orchestrator-protocol.md,post-flight-verification.md,theory-proving.md,/preregister,/respond-to-eval) and in two places in the guide.Checked. The remaining uses of "forked context" are correct:
/slide-excellencedeclarescontext: fork, andreview-fencing.mdsays a fork is not a fence./commit stops at the commit, and no GitHub issue is created without a…