Eureka/references/loop-5-triage.md
Eureka 1bbd8a574c Eureka skill: router plus on-demand references (54 KB -> 17 KB loaded per invocation); loop steps 1-5, Self's discipline and git scars moved verbatim to references/, each step keeps its lead and a pointer
After GoogleChrome/modern-web-guidance's router-and-corpus design (references/research-modern-web-guidance-2026-11-11.md).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-11 06:21:07 +01:00

3.4 KiB

5. Triage and repeat

(Moved verbatim from SKILL.md on 2026-11-11 so the skill loads small; SKILL.md keeps a pointer.)

For each finding in force, decide:

  • fix now: brief Hands with the finding's id. The fix batch's cut_report cites the finding's in-force cut_spec as its next attempt, on that spec's branch. If the fix must land elsewhere, Imagination (or Self) admits a revised spec first. Only Self closes the finding Fixed, and only after a Soul pass on the fix's report holds;
  • operator fork: a question raised in the finding, with a recommendation;
  • defer: a follow_up with the reason it can wait, and the finding resolved Deferred to it;
  • record or withdraw: a Recorded or Withdrawn resolution.

Run Soul again on the fix batch. Do not cap the Soul loop early on a foundation cut. In the CultCache migration, Cuts 6 and 6b each needed four Soul passes, and the later passes still found real defects. Stop when a pass finds nothing that blocks, or only findings the operator chooses to record.

Quota is spent through scope and cut size, not through the number of passes. On 2026-09-23, with 60% of the weekly quota gone in one day, the operator redirected all work to the StreamPixels critical path. That spend was legitimate work; the operator's regret was the model it ran on (2026-09-25). Since then Self has run one full Soul gate per cut. A fix batch goes only to findings on the critical path, and the rest are recorded as follow-ups. Every later Soul pass covers only the fix batch's diff, as the second-pass clause in briefs.md says, and a small delta gets a narrow Sonnet pass. Hands' share is governed by the context budget in step 3. None of this caps the loop on a foundation cut. It keeps each pass the right size.

When the same kind of finding recurs, the brief was missing context. Fix the 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. 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 QUIC bridge's timeout took seven passes because each batch killed the last Soul's functions, and the next Soul found another that matched at every probe. A dev-only seam has two costs of its own. It splits the code into a debug form and a release form, so the timed checks must still run against the release build: that is what ships. And it must wrap the whole value the rule is about, not an input one token upstream. Soul's eighth pass found both gaps.

A release or tag is a cut and gets its Soul pass before the tag is pushed. The CultCache release cut skipped Soul. Its stale DLLs, SHA-bound byte checks and silently skipped publish jobs surfaced only after tags were out. CultLib 1.0.58 shipped a wire-parity defect that was found and corrected 74 minutes later.