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

Skill: re-entry triages reports with no verdict; second beating triggers the structural move; pushed heads build

Browse source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Eureka 2026-10-27 17:02:28 +01:00
commit 91efdce0f0
3 changed files with 20 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

12
SKILL.md
View file

@ -468,7 +468,10 @@ brief template, not only the instance. That is how "operator rulings each need
their own failing mutation" entered the Hands brief.
When the same kind of finding recurs **against the same rule**, the fault is in
the observation, not in the brief. If a second fix batch for one rule is again
the observation, not in the brief. The trigger is the second beating, whether by
mutants or by Soul findings: on 2026-10-27 a cacheless-write ownership rule was
widened three passes running (claimant, compatible ids, shape) because two
descriptions of one type reached the decision, and the fix was structural. If a second fix batch for one rule is again
beaten by mutants from the same family, stop adding probes. Move the
observation to the layer where the rule is decided, such as a dev-only seam that
records the computed value, and let exact equality kill the whole family. The
@ -584,8 +587,11 @@ and reconciles the target doc with the Body.
admitted. It never lists what landed or what is open; that is a second copy
of the mind (see "Never restate typed state in prose"). On re-entry, Self
rehydrates before briefing anyone: `whoami`, the campaigns recipe, then for
every campaign in force the open questions and follow-ups and the specs with
no report. The handoff is a pointer into that state, not the ledger. Every
every campaign in force the open questions and follow-ups, the specs with
no report and the reports with no verdict; a report unverified for days gets a
recovery Soul pass (on 2026-10-27 two such reports hid High defects). Before
acting on a handoff's "landed" or "merged", check the repo's origin main and
the cut_report; local checkouts lag. The handoff is a pointer into that state, not the ledger. Every
campaign in force has exactly one area: before writing a handoff, Self runs
the campaigns recipe and checks that each campaign in force is named by its
own handoff or by another area's current one; on re-entry, a campaign in