Eureka/references/loop-1-imagination.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

6.5 KiB

1. Imagination maps the cut

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

Brief an Imagination agent to admit the cut_spec for the next cut against the current Body; depends_on names the cut labels it waits on. The fields are the spec standard: repo, branch and base; deletes first, with exact paths and line counts; keeps_moves; adds; file_changes at file:line for code that exists; reads for code Hands must see but not change; an authority_map for anything that changes ownership; verification (builds, tests with the rule each pins, negative greps, operator checks); an estimate for the ledger; and the rulings and questions it rests on. A changed spec is a new revision, admitted with the resolution that supersedes the old one, never an edit.

Map only what is about to run. A cut_spec is admitted for a cut Self dispatches as soon as the spec is in: its dependencies have landed or are in their Soul pass, and Self has the head and the machine for it. That is the next cut of a campaign, plus a sibling that can run beside it in its own worktree. Every later cut is a follow_up, never a spec: its item is the title and what it waits on, its source the ruling or spec that orders it, its owner the steward who will map it. A cut split for budget admits its first part; the rest are follow-ups. The follow-up stays open while its cut is mapped and built, and Self closes it Fixed by the cut's report once Soul holds, so it stays in view until the work exists. A later cut kept only as a line in prose has no owner and no status, and nothing surfaces it: the 2026-10-31 live-mind-sessions sequence planned nine cuts in a research doc's table, and the six that stayed as table rows (resume, the Self's replies reaching her Persona, the session keeper) were still unbuilt on 2026-11-06, when the operator asked again (ruling three-tiers-of-context). An operator ruling that orders work not yet built gets its follow-ups in the same batch. A spec waits on the Body and goes stale: the variants specs of 2026-10-02 sat ten days behind a moving CultLib and needed a fresh Imagination pass before Hands could use them. Operator, 2026-10-12: "Originally a spec would get dispatched as soon as it's written, but we've been drifting way ahead of the work". So the specs-with-no-report recipe is the dispatch queue, and a spec on it that Self is not dispatching this session is a defect. A spec already in force from before this rule is refreshed (revision N+1) or withdrawn when its campaign's frontier reaches it, never dispatched on a base tools/context-pack.py reports as moved.

Spend the detail where the map can be wrong, not where Hands will rewrite it anyway. Anchors against existing code earn their length: they say what to delete and what not to touch. They are also Hands' context pack, pinned at base and carried to Hands' tree by tools/context-pack.py (ruling context-pack-resolving-anchors), so each one is stated exactly at base. Transcribing the body of code that does not exist yet does not. A cut section that runs to eight hundred lines against a crate nobody has written is a 1:1 map, and the only spec complete enough at that scale is the code itself. Soul catches a wrong function body cheaply; it cannot catch a missing namespace. So for new code, name the types, the rules that must die under their own mutation, and the boundaries, then stop.

Cutting faster means less prose per cut, never more code per cut. Small commits stay small.

Subtraction comes from a consumer audit of the public surface, not from taste:

  • Count real use across every project the operator works in before sizing or cutting a feature, not only one runtime's repos. Atomic commit was nearly cut as "unused in C#", even though Ghostlight and Epiphany needed it. Call counts decided whether compare-exchange was in scope.
  • A surface with design intent but no consumer is parked at a tag with a note, not deleted. SoA was parked at parked/cultcache-soa.
  • A capability the operator has needed across projects is reshaped, not removed, even when its current consumers are only tests.
  • A general-purpose library is judged by what a reasonable consumer would expect, not by our own call counts. For CultLib, the consumer audit bounds internal duplication and dead internals. It never licenses cutting or omitting public capability. A math type that doesn't serialize, or a runtime missing a sibling runtime's feature, is a gap to fill, not a cut to take. When consumers each carry their own copy of something, the owner-level fix is usually to add it to the library. (Operator, 2026-09-30: "just because we're not using a feature doesn't mean we can cut it".)
  • Where the operator's own original code exists, it is the style bar.

Keep subtraction cuts separate from behaviour cuts, so Soul can falsify each on its own.

Before specifying a domain concept, ask the operator what it is for. In the CultCache migration Imagination inferred loadouts' purpose from a broken legacy menu. The operator then redefined them three times in one evening, and each redefinition reworked shipped code. Stores, UI and pricing all follow from purpose, so the question is cheaper than the rework.

Design order as data, not as scheduling. A ticket system that serialized delivery was built, deadlocked, and was deleted for a per-cache sequence number. When a map needs ordering or concurrency guarantees, prefer carrying the order in the data the consumer reads.

Imagination must establish mechanism claims by running code: probes, scratch builds, decoding a real file. It must not reason from names. A map built on unprobed claims is where bad cuts come from. The probes and their results go in the prose map's body facts. Real forks come back as questions with a recommended option, never chosen silently.

Iterate with further Imagination passes, not Soul passes, until Hands could go straight to the cut. The admitted specs are the durable record of the means. Self commits the prose map when its body facts, model page or rationale change.

Check overlap before fanning Imagination out. Before dispatching Imagination passes in parallel, list the code and the decisions each will touch. Passes that overlap run in sequence, or one of them owns the shared decision and the others cite it. On 2026-10-08 two parallel passes over the same code made two owners of one decision twice: Title against DisplayName, and the Huginn crate move.

Templates are in references/briefs.md and references/campaign-state.md.