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

Rotation: a clear ends background agents, so rotate with none in flight; briefings carry each question's options

Browse source 
The 2026-10-03 clear killed three agents that the handoff expected to survive:
commits survived on branches, two cut reports and a verdict were never admitted.
The same morning's catch-up gave the operator recommendations without options,
because it read the handoff instead of the question documents.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Eureka 2026-10-03 12:04:30 +02:00
commit 45bfa53cdc
2 changed files with 14 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

13
SKILL.md
View file

@ -201,7 +201,10 @@ default, a naming choice, or a guard against our own code (the proportion rule
below). When unsure, run the pass.
Put the open questions to the operator together, from the open-questions recipe,
each with its options, recommendation, and what depends on the answer. Self
each with its options, recommendation, and what depends on the answer. This
holds in a catch-up briefing too: read the options and context from the
`question` document, never from a handoff's one-line recommendation, so the
operator rules on the fork and not on Self's summary of it. Self
admits every answer as a `ruling` that answers its question, keeping the
operator's words in `operator_quote` when they carry meaning a paraphrase would
lose. An operator direction that answers no question is still a ruling, with
@ -533,8 +536,12 @@ and reconciles the target doc with the Body.
- **Never claim an agent's result before its notification arrives.**
- **Self's own context is the most expensive in the pipeline.** Every
notification re-reads all of it. Rotate at about 300k context or at a phase
boundary: write a short handoff (campaign slug, session label, in-flight
agent ids, next action) to the scratchpad and ask the operator to `/clear`.
boundary: write a short handoff (campaign slug, session label, next action)
to the scratchpad and ask the operator to `/clear`. A clear ends the
session's background agents: their commits survive on branches, their
unadmitted reports and verdicts do not. Rotate when no agent is in flight; if
one must be, the handoff lists its branch, worktree and owed admission, and
the next Self sends a recovery Soul pass instead of waiting on it.
Agents are capped at about 300k context or 150 calls, after which a fresh
continuation agent takes over. Never read logs or diffs in the root; `view`
reports and verdicts.