clearotron 0.4.0 → 0.4.1-beta.1

package/driver/skills/clearance-search/worked-examples.md

@@ -33,7 +33,7 @@ Notice across all three:
 - **The proposed mark's own distinctiveness is assessed *per field*** — and it drives how narrowly any
   third-party right can block (descriptive term → narrow rights → weak block).
 - **Family-of-marks / branded-context is a real mitigant** ("consumers will perceive EMBERSTRIKE as
-  an extension of the Breaker range"; "strong Blockvale branding").
+  an extension of the Strike range"; "strong Blockvale branding").
 - **Use / revocability / enforcement appetite carry the analysis** — a registration with no use, in
   insolvency, or outside the owner's core market is a different risk from an active enforcer.
 - **Executive summary is synthesised prose:** name the primary risk(s), the overall rating, and the
@@ -236,30 +236,30 @@ cannot be excluded.
   sufficient differences to avoid confusion.
 
 *Common-law use*
-- **Manageable** — "Solstrikers" is a game "coming soon" on Steam from indie developer Crobatspr.
+- **Manageable** — "Solstrikers" is a game "coming soon" on Steam from an indie developer.
 
 **Emberstrike — Manageable Risk**
 
-- 3,060 live FLAME/FLAME-formative filings internationally in the searched classes (640 claim gaming
-  software/hardware/online gaming); analysis focuses on FLAME and FLAME BR___ marks covering gaming.
-- 8,575 live BR(E)AKER(S)/BR(E)AK(E)-formative filings (2,317 claim gaming); analysis focuses on
-  BR(E)AKER(S) and F__ BR(E)AKER(S) marks covering gaming.
+- 3,060 live EMBER/EMBER-formative filings internationally in the searched classes (640 claim gaming
+  software/hardware/online gaming); analysis focuses on EMBER and EMBER ST___ marks covering gaming.
+- 8,575 live STRIKE(S)/STRIK(E)-formative filings (2,317 claim gaming); analysis focuses on
+  STRIKE(S) and E__ STRIKE(S) marks covering gaming.
 
 *Filings*
-- **Manageable** — Numerous FLAME/FLAMES marks claim gaming goods/services; most significant is
-  an international FLAMES portfolio owned by gambling company Euro Games Technology (no apparent current
+- **Manageable** — Numerous EMBER/EMBERS marks claim gaming goods/services; most significant is
+  an international EMBERS portfolio owned by a gambling company (no apparent current
   use).
-- **Manageable** — Numerous BREAKER marks claim gaming goods/services; none appears to have
-  objected to the client's ongoing use of ___ BREAKER for controllers.
+- **Manageable** — Numerous STRIKE marks claim gaming goods/services; none appears to have
+  objected to the client's ongoing use of ___ STRIKE for controllers.
 
 *Common-law use*
 - **Manageable** — EmberstrikeGaming: streamer/YouTube channel (205 videos, 405 subscribers)
   with a merch store that does not sell hardware/accessories.
-- **Manageable** — Flamebreak: a 2016 Steam game (444 "very positive" reviews) by Nimbly Games;
+- **Manageable** — Emberstruck: a 2016 Steam game (444 "very positive" reviews) by an indie studio;
   no game published in ~10 years.
-- **Not a rated conflict (clear win)** — A "Emberstrike Set" appears in several Zelda games; not monetised or
+- **Not a rated conflict (clear win)** — A "Emberstrike Set" appears in several games of a long-running adventure series; not monetised or
   prominent.
-- **Not a rated conflict (clear win)** — Remedy's co-op shooter "Firebreak" (1,914 "mixed" reviews on Steam).
+- **Not a rated conflict (clear win)** — A studio's co-op shooter "Firestrike" (1,914 "mixed" reviews on Steam).
 
 ---
 
@@ -292,7 +292,7 @@ manageable.
 - **Moderate (register risk; no obvious market overlap)** — a Canadian provincial lottery corporation owns an official Canadian
   registration for CHART YOUR COURSE (all goods/services) used descriptively for self-service lotteries.
   Legal risk, but low practical objection risk — no enforcement history, no commercial overlap with a
-  console tagline. A Canadian application would undoubtedly be blocked; consent from OLC the only route.
+  console tagline. A Canadian application would undoubtedly be blocked; consent from that corporation the only route.
 - **Moderate (register risk; no obvious market overlap)** — A sports broadcaster owns a US registration covering publication of
   physical-fitness games and instruction-sharing websites, for an inactive youth-fitness program. No
   obvious current use. Statement-of-use deadline 27 July 2026 — if not filed (which seems possible),
@@ -301,7 +301,7 @@ manageable.
   via games consoles (among much else), used for a tennis participation campaign and descriptively.
   Revocable for unused goods/services; low confusion with a console tagline; scope likely reducible
   away from gaming services if challenged.
-- **Manageable** — Polish telecom P4 ("Play") owns a Polish registration covering computer game
+- **Manageable** — A Polish telecom owns a Polish registration covering computer game
   software and console game programs; no specific gaming interest; minor use on its careers site;
   low confusion; scope likely reducible away from gaming goods if challenged.
 - **Manageable** — A games-accessory maker holds invalid/lapsed CHART YOUR COURSE filings
@@ -313,11 +313,11 @@ manageable.
 - **Manageable** — "Chart Your Course" platform for sharing love of video games; limited social
   presence.
 - **Manageable** — "Chart Your Course" 2025 mental-health-in-gaming fundraiser (£7,000 raised).
-- **Manageable** — "Chart Your Course" announced as a major update for the game Peak (~127k
+- **Manageable** — "Chart Your Course" announced as a major update for a popular co-op game (~127k
   "overwhelmingly positive" Steam reviews).
 - **Manageable** — "Charting Your Course" arcade-game subscription service.
 - **Not a rated conflict (clear win)** — A third-party Nebula console-streaming app uses "Chart Your Course" descriptively.
-- **Not a rated conflict (clear win)** — PC gaming companion app Wand has minor descriptive use.
+- **Not a rated conflict (clear win)** — A PC gaming companion app has minor descriptive use.
 - **Not a rated conflict (clear win)** — A "Chart Your Course" card-game app and a "Chart My Course" fitness app.
 
 ---
@@ -336,18 +336,18 @@ side-glance at **Classes 35 and 39** (retail pizza store / pizza delivery) and *
 
 ### Executive summary (per mark)
 
-- **PRIZE CRATE — manageable.** Closest entries: UK registrations for PRIZE CRATE (food, not pizza) and LOOT
-  CHEST (cardboard pizza boxes); confusion unlikely in a Blockvale pizza context, practical objection
+- **PRIZE CRATE — manageable.** Closest entries: UK registrations for PRIZE CRATE (food, not pizza) and PRIZE
+  TRUNK (cardboard pizza boxes); confusion unlikely in a Blockvale pizza context, practical objection
   unlikely. Heavy gaming use/registration of PRIZE CRATE but none an immediate obstacle. Note the term's
   specific (often negative) gaming meaning — a PR consideration before use.
 - **CAVERN CRATES — manageable.** Closest is a US application CAVERN CRATE (Class 30, candy); confusion
   unlikely in the Blockvale pizza context, and no obvious use of CAVERN CRATE for candy. Some "Cavern
   Crate" use in a prize-crate context — minor negative-association risk.
-- **COUCH CO-OP MEAL — manageable.** "Couch co-op" = multiple players sharing one screen/console.
+- **LOCAL CO-OP MEAL — manageable.** "Local co-op" = multiple players sharing one screen/console.
   Numerous supermarket CO(-)OP registrations cover pizza and gaming goods, but given the descriptive
-  gaming meaning of "couch co-op" and strong Blockvale branding, confusion is unlikely.
-- **THE HERO'S CHEST: ADVENTURE ESSENTIALS — manageable.**
-- **THE SLICE AND DICE COMBO — moderate (low end).** An international "pizza and board game" venue trend uses
+  gaming meaning of "local co-op" and strong Blockvale branding, confusion is unlikely.
+- **THE RANGER'S SATCHEL: QUEST ESSENTIALS — manageable.**
+- **THE SLICE AND DICE PLATTER — moderate (low end).** An international "pizza and board game" venue trend uses
   "Slice and Dice"-type names (mostly unregistered, low reputation). The moderate rating attaches to an
   Irish registration SLICE N DICE (individual owner) claiming *both* pizza and electronic gaming goods;
   no use found but within the non-use grace period — plausibly a pizza/board-game venture. Given the
@@ -364,38 +364,38 @@ side-glance at **Classes 35 and 39** (retail pizza store / pizza delivery) and *
 - *Potential negative association / PR:* prize crates are tied to "compulsion loop" game design,
   criticised as gambling-style "dark patterns" and increasingly regulated; using "Prize Crate" for a
   gaming-pizza promo could be read as normalising a criticised practice. (Blockvale's natural-chest
-  loot is non-monetised, not a gambling-style system.)
-- *Filings* — **Manageable**: Pence Technology (UK) owns PRIZE CRATE (Stylised) over broad food/beverage
+  prizes are non-monetised, not a gambling-style system.)
+- *Filings* — **Manageable**: A UK technology company owns PRIZE CRATE (Stylised) over broad food/beverage
   (not pizza); no obvious use; not revocable yet, but low practical objection risk (company inactive).
-  Prize Crate Retail (UK) owns LOOT CHEST & device over "cardboard pizza boxes" + broad goods; in
-  voluntary insolvency, no recent operations, low practical risk. Loot Crate (geek subscription boxes)
-  owns an international LOOT CRATE portfolio (apparel/paper/toys/retail), not food — no overlap. Numerous
-  third-party LOOT( )BOX gaming filings — none can block given the term's non-distinctiveness in gaming.
-  Pepsi owns LOOT / DORITO'S LOOT / EAT. DRINK. GET LOOT. over Class 30 foods (not pizza) — noted only
+  Prize Crate Retail (UK) owns PRIZE TRUNK & device over "cardboard pizza boxes" + broad goods; in
+  voluntary insolvency, no recent operations, low practical risk. Prize Case (geek subscription boxes)
+  owns an international PRIZE CASE portfolio (apparel/paper/toys/retail), not food — no overlap. Numerous
+  third-party PRIZE( )CRATE gaming filings — none can block given the term's non-distinctiveness in gaming.
+  Crunchmore Foods owns PRIZE / CRUNCHMORE'S PRIZE / EAT. DRINK. GET PRIZE. over Class 30 foods (not pizza) — noted only
   as a large food player; no confusion.
 - *Common-law* — **Manageable**: a virtual unboxing platform "Prize Crate"; "PRIZECRATE Game Store" (card/
-  tabletop games); "Loot Drink" gamer energy-drink powder.
+  tabletop games); "Prize Drink" gamer energy-drink powder.
 
-**THE SLICE AND DICE COMBO — Moderate (low end)**
+**THE SLICE AND DICE PLATTER — Moderate (low end)**
 - *Distinctiveness/context:* "slice"/"dice" are not very distinctive for pizza (knife actions; "slice"
   = pizza), reflected in 370 live SLICE/DICE filings claiming pizza in Class 30 — so analysis focuses on
   marks with both words or another element bringing them closer; "slice and dice" *is* distinctive for
   non-dice computer games; "dice" is not distinctive for board games.
-- *Filings* — **Moderate (low end; settleable overlap, or paper-only if unused)**: Conor Jordan (individual) owns an
+- *Filings* — **Moderate (low end; settleable overlap, or paper-only if unused)**: An individual owns an
   Irish SLICE N DICE registration with a detailed gaming list (Class 28) *and* detailed pizza list
   (Class 30) — notable for that specificity. No use found; an international "board game + pizza" café
   trend uses identical "Slice and Dice" branding, plausibly the intent here. Despite the Blockvale
   context, given the identical mark and highly specific pizza+gaming intersection, **Irish counsel
-  advice is recommended** (ideally with an example of the proposed use). Also **Manageable**: Wymac
-  (Australian gaming-machine maker) SLICE N DICE (AU/US) — vulnerable to cancellation for unused goods,
-  and in-venue machines don't overlap; Seneca (US casino) SLICE-N-DICE for a casino restaurant;
-  Ravensburger DICE AND SLICE for a physical pizza-themed strategy game.
+  advice is recommended** (ideally with an example of the proposed use). Also **Manageable**: an
+  Australian gaming-machine maker's SLICE N DICE (AU/US) — vulnerable to cancellation for unused goods,
+  and in-venue machines don't overlap; a US casino's SLICE-N-DICE for a casino restaurant;
+  a board-game publisher's DICE AND SLICE for a physical pizza-themed strategy game.
 - *Common-law* — **Manageable**: "Slice & Dice" tactical dice roguelike (App Store / Google Play /
   Steam, 1m+ downloads, 2020) — no pizza theme, "dice" refers to the mechanic; confusion unlikely in
   the Blockvale pizza context. Numerous "Slice and Dice"-type pizzerias/bars, some offering tabletop
   gaming — none with reputation enough to confuse. "Slice and Dice" is also the name of a third-party Blockvale mod.
 
-*(Full CAVERN CRATES, COUCH CO-OP MEAL and THE HERO'S CHEST analyses follow the same chain — owner →
+*(Full CAVERN CRATES, LOCAL CO-OP MEAL and THE RANGER'S SATCHEL analyses follow the same chain — owner →
 coverage + distinctiveness → use/revocability → overlap → enforcement → net, in a Blockvale-branded
 promotional context.)*
 
@@ -443,7 +443,7 @@ The crowded-field framing drives the whole mark: a register sweep returned rough
 
 **Aqua Dawn — Manageable Risk**
 
-A register sweep returned roughly 1,900 live DAWN / DAWN-formative filings internationally, but only a small fraction touch beverages or supplements, and the single dominant DAWN right sits in an unrelated cleaning-products field. Analysis focuses on DAWN and DAYBR___ marks with any Class 5/30/32 claim, and on the coffee-hybrid space the product actually occupies.
+A register sweep returned roughly 1,900 live DAWN / DAWN-formative filings internationally, but only a small fraction touch beverages or supplements, and the single dominant DAWN right sits in an unrelated cleaning-products field. Analysis focuses on DAWN and SOLSTR___ marks with any Class 5/30/32 claim, and on the coffee-hybrid space the product actually occupies.
 
 *Filings*
 - **Manageable** — Procter & Gamble owns the well-known DAWN house mark, but its registrations sit in Class 3 (dishwashing/cleaning) with no beverage or supplement claim located. Famous mark, but a different field entirely; the dilution-style theory a famous-mark owner might raise is remote against a AQUA-led beverage extension, and there is no goods overlap. Noted because the name is prominent, not because it obstructs.

package/driver/skills/clearance-variants/SKILL.md

@@ -74,11 +74,11 @@ A single file inside the active run-dir: `studio/clearance-search/<slug>/<date>/
 ### Format
 
 ```markdown
-# Variant manifest — Dawn: Legends of Lumengarde (2026-05-11)
+# Variant manifest — Dusk: Tales of Lumengarde (2026-05-11)
 
 ## Request
 
-- **Marks:** Dawn: Legends of Lumengarde
+- **Marks:** Dusk: Tales of Lumengarde
 - **Classes:** 9, 28, 41, 42
 - **Jurisdiction:** worldwide
 - **Industry:** gaming
@@ -89,34 +89,34 @@ A single file inside the active run-dir: `studio/clearance-search/<slug>/<date>/
 
 ## Scope statement
 
-Preliminary clearance for "Dawn: Legends of Lumengarde" as a game title, Classes 9/28/41/42, worldwide. Industry-incumbent parallel sweeps apply for LUMENGARDE (lighting electronics).
+Preliminary clearance for "Dusk: Tales of Lumengarde" as a game title, Classes 9/28/41/42, worldwide. Industry-incumbent parallel sweeps apply for LUMENGARDE (lighting electronics).
 
 ---
 
-## Mark: Dawn: Legends of Lumengarde
+## Mark: Dusk: Tales of Lumengarde
 
 ### Archetype
 
-- **Primary:** Descriptive compound (3-word title; LUMENGARDE distinctive, DAWN + LEGENDS common saturated commons in gaming)
+- **Primary:** Descriptive compound (3-word title; LUMENGARDE distinctive, DUSK + TALES common saturated commons in gaming)
 - **Modifiers:** None
 - **Boundary note:** LUMENGARDE alone would be a coined-word; the compound title shape places it under descriptive-compound. Coined-word axes (phonetic, transliteration, leet) still apply to LUMENGARDE element-solo.
 
 ### Distinctiveness & registrability (advisory — the staff lawyer to assess)
 
-- **Dominant element:** LUMENGARDE (DAWN + LEGENDS are common/descriptive — stripped). Search + conflict-ranking centre here.
+- **Dominant element:** LUMENGARDE (DUSK + TALES are common/descriptive — stripped). Search + conflict-ranking centre here.
 - **Spectrum:** distinctive (LUMENGARDE coined; the compound is arbitrary for gaming). No obvious absolute-grounds problem.
 - **Flags:** none — not descriptive/generic/laudatory/geographic for the goods; not deceptive or offensive.
 
 ### Risk theory
 
-LUMENGARDE is the distinctive anchor — risk concentrates on coined-word axes around that element (phonetic variants, leet, foreign transliteration) plus the Lumengarde Electronics lighting incumbent. DAWN and LEGENDS are saturated commons; risk there is the single-distinctive-word DAWN-alone or LEGENDS-alone filing in gaming, not crowded-field volume. Compound-phrase exact hit is low-probability but high-impact if it surfaces.
+LUMENGARDE is the distinctive anchor — risk concentrates on coined-word axes around that element (phonetic variants, leet, foreign transliteration) plus the Lumengarde Electronics lighting incumbent. DUSK and TALES are saturated commons; risk there is the single-distinctive-word DUSK-alone or TALES-alone filing in gaming, not crowded-field volume. Compound-phrase exact hit is low-probability but high-impact if it surfaces.
 
 ### Elements
 
 | Element | Role | Saturation | Famous-mark | Notes |
 |---|---|---|---|---|
-| DAWN | common-word | high | no | Morning / new beginning; fantasy / adventure |
-| LEGENDS | common-word | very-high | no | Myth / tale; epic / fantasy |
+| DUSK | common-word | high | no | Evening / sunset; fantasy / adventure |
+| TALES | common-word | very-high | no | Story / myth; epic / fantasy |
 | LUMENGARDE | distinctive | low | no | Industry incumbent: **Lumengarde Electronics Co.** (lighting / LED / semiconductors, classes 9 + 11) — triggers parallel sweep |
 
 ### Variants
@@ -140,10 +140,10 @@ silently narrows what was searched, and the deferred row is the honest outcome.
 
 | Category | Value | Rationale | Verify? |
 |---|---|---|---|
-| exact-phrase | Dawn: Legends of Lumengarde | full mark | |
+| exact-phrase | Dusk: Tales of Lumengarde | full mark | |
 | exact-element | LUMENGARDE | distinctive anchor — primary register vector | |
-| exact-element | DAWN | common element — single-word coverage hunt | |
-| exact-element | LEGENDS | common element — single-word coverage hunt | |
+| exact-element | DUSK | common element — single-word coverage hunt | |
+| exact-element | TALES | common element — single-word coverage hunt | |
 | plural-root | LEGEND | tokeniser superset | |
 | phonetic | EVERLITE | homophone, distinctive element | |
 | phonetic | EVRLIGHT | vowel drop | |
@@ -179,7 +179,7 @@ silently narrows what was searched, and the deferred row is the honest outcome.
 ### Watchlists
 
 - **Aggressive enforcers:** Nordwave, Foxglade Interactive
-- **Major brand owners:** Sony, Aureon, Nintendo, HP, Activision, Take-Two, EA
+- **Major brand owners:** Veltrona, Aureon, Pinecrest, Brightwick, Halloway, Duomark, Skyvault
 - **Competitors:** Epic Games, Valve, Unity, Riot Games
 
 ### Famous-mark Perplexity calls needed
@@ -188,7 +188,7 @@ None for this mark.
 
 ### Diligence notes
 
-LUMENGARDE carries coined-word axes (phonetic + transliteration) despite the descriptive-compound primary archetype. Industry-incumbent alert triggers a parallel-class 11 sweep. DAWN and LEGENDS are saturated commons — still generated as single-word vectors; their saturation tells the downstream register search to **narrow** (class-scope the token and enumerate), it is never a reason to skip the vector here or to pre-judge the crowd clean.
+LUMENGARDE carries coined-word axes (phonetic + transliteration) despite the descriptive-compound primary archetype. Industry-incumbent alert triggers a parallel-class 11 sweep. DUSK and TALES are saturated commons — still generated as single-word vectors; their saturation tells the downstream register search to **narrow** (class-scope the token and enumerate), it is never a reason to skip the vector here or to pre-judge the crowd clean.
 
 ---
 
@@ -227,7 +227,7 @@ Pick one **primary** archetype. Pick zero or more **modifiers**. Write a one-lin
 **Worked examples:**
 
 - "LUMENGARDE" (single mark) → Coined word. No modifier. Risk: phonetic, transliteration, leet, coined-word collisions.
-- "Dawn: Legends of Lumengarde" → Descriptive compound (DAWN + LEGENDS commons, LUMENGARDE distinctive anchor). No modifier. Risk concentrates on LUMENGARDE element + compound-phrase hit.
+- "Dusk: Tales of Lumengarde" → Descriptive compound (DUSK + TALES commons, LUMENGARDE distinctive anchor). No modifier. Risk concentrates on LUMENGARDE element + compound-phrase hit.
 - "CHART YOUR COURSE" → Slogan. No modifier. Risk: family patterns (CHART * COURSE, * YOUR COURSE, CHART YOUR *), verb swaps, slang.
 - "Bloodguard Sabatons" → Descriptive compound + famous-element-masked (Sabatons = Swedish metal band). Risk: per-element famous-mark search on Sabatons; descriptive-compound axes on the rest.
 - "RAIZ8" → Acronym/initialism (leet form of RAISE). Risk: letter-collision; expansion-form search on RAISE.
@@ -330,7 +330,7 @@ The `phonetic` / `visual-substitution` / `numeric-substitution` / typographic ro
 
 For multi-word marks where the structure carries meaning (slogans, descriptive compounds), substitute each stem-formative back into the phrase template:
 
-- "RAISE YOUR PLAY" → "ELEVATING YOUR GAME", "RAISE THE PLAY", "RAISING YOUR PLAY", etc.
+- "RAISE YOUR PLAY" → "LIFTING YOUR PLAY", "RAISE THE PLAY", "RAISING YOUR PLAY", etc.
 - "CHART YOUR COURSE" → "CHARTING YOUR COURSE", "CHART MY COURSE", "CHART THE COURSE", "PLOT YOUR COURSE" (verb swap)
 
 Drop ungrammatical or semantically broken strings. Default: generate liberally; macro-count probes filter.

package/driver/skills/frame-diff/SKILL.md

@@ -54,10 +54,10 @@ A directive may carry a structured `remedy`:
 
 **A firing `variant` directive — severity `dominant-element` or `material` — MUST be dispatchable.** That means one of exactly two things:
 
-1. its `item` is *itself* a single mark-shaped search term (`TAKIS`, `AXIOS`, `CORAL MAGIC`), **or**
+1. its `item` is *itself* a single mark-shaped search term (`WAVA`, `ORBEXA`, `CORAL MAGIC`), **or**
 2. it carries `remedy.terms` naming the mark-shaped term(s) to search.
 
-A label-shaped `item` — more than 4 words, a parenthetical, an enumeration ("TAKIS (famous CPG snack, one-keystroke neighbour)", "Reverse-order WAVO composites (TROPICAL WAVO, ISLAND WAVO)") — is **never dispatched as a search term**: dispatched verbatim it is a nil search that comes back 0 and reads as a clean, which is worse than no search. So a firing `variant` directive whose item is a label **and which carries no remedy is a PARSE DEFECT** — the driver refuses the file and asks you to restate it, in this same turn, while restating is still free. Every term you put in `remedy.terms` is linted the same way: a remedy that is itself a label is refused exactly like the item was.
+A label-shaped `item` — more than 4 words, a parenthetical, an enumeration ("WAVA (famous CPG snack, one-keystroke neighbour)", "Reverse-order WAVO composites (TROPICAL WAVO, ISLAND WAVO)") — is **never dispatched as a search term**: dispatched verbatim it is a nil search that comes back 0 and reads as a clean, which is worse than no search. So a firing `variant` directive whose item is a label **and which carries no remedy is a PARSE DEFECT** — the driver refuses the file and asks you to restate it, in this same turn, while restating is still free. Every term you put in `remedy.terms` is linted the same way: a remedy that is itself a label is refused exactly like the item was.
 
 The refusal names **every** offending directive at once, and it arrives as the tool's answer to your call — in this turn, while restating is still free. Fix them **all** in one further call: the repair ladder counts attempts, not directives, so repairing only the first one loses the rest. A call replaces the stored diff, so send the whole thing again, not only the corrected directives.
 

package/driver/stage-context.mjs

@@ -123,6 +123,19 @@ export const TOOL_GROUP_EDGES = {
     { path: P.bandShapeMd, why: "band_shape serves band-shape.md (the readable shape, part-paged)" },
     { path: P.registerPositions, why: "the exact-identity projection the shape and the recall join read as one unit" },
     { path: join(P.runDir, "_records"), dir: true, why: "band_record serves the official registry records fetched into this run" },
+    // SEVENTH OCCURRENCE OF THIS TABLE'S OWN SUBJECT, and the arm written to prevent it could not see this
+    // one. `band_record` serves a body from `_records/` OR from this log, and at step 2 the real run served
+    // placement's reads from the log rather than from files. Undeclared, the sandbox copy held no bodies and
+    // every one of those reads failed — measured on five saved runs, where placement opened 31, 32, 2, 2 and
+    // 0 records: in the sandbox as shipped, all of them fail.
+    //
+    // WHY THE GENERIC ARM MISSED IT. That arm walked the servers for `driverDir(runDir, X)` and kept X only
+    // when it ended in `.json`; this file ends in `.jsonl`, so it was never in the population the arm
+    // checked. The filter stood in for telling a read from a write, since every file the servers write is
+    // `.jsonl` too. The walk now makes that distinction itself, at any extension (experiment-context.test.mjs,
+    // `driverFileUses`), so this file is held by the same rule as every other read.
+    { path: driverDir(P.runDir, "register-record-bodies.jsonl"),
+      why: "band_record serves a record body from this log when the run fetched it through the ledger rather than into _records/ (band-server.mjs recordLedgerPath); without it the sandbox's record reads all fail and the re-run sees less than the stage saw" },
   ],
   // ── conversion 11 — THE RECORD TOOL READS A DRIVER-WRITTEN SIDECAR, AND NOTHING DECLARED IT ───────
   //
@@ -200,13 +213,35 @@ const UNDECLARED = {
   // inline and names the `record_coverage` tool), the seat opens no coverage file, and the accumulator
   // the gate judges is declared on VALIDATOR_SIDECARS below. The brief's own read of that accumulator
   // is declared on DISPATCH_EXTRAS.
-  "register-digest": () => [],
+  // THE PROMPT NAMES A FILE THE SANDBOX DID NOT COPY, so a re-run of the digest differed from the real
+  // stage in one input the prompt names, invisibly: the stage passed. The digest's message ("MARK THE LIST")
+  // names the hit list and asks the model to mark lines on it, and `hit-list.mjs` reads those marks back.
+  // Absent from the copy, a marking the model sends lands nowhere and nothing refuses — measured on a bench
+  // plumbing run where the digest completed with owed 7 accounted 7 and the hit list was simply not there.
+  //
+  // DECLARED UNCONDITIONALLY, for the reason the digest's accounting stamp above is: `sandboxGaps` reports a
+  // gap only for something the CANONICAL run holds, so a run that never built a hit list contributes no gap,
+  // and one that built it and lost it in the copy refuses by name. Listing it costs nothing on the first and
+  // is the whole point on the second.
+  "register-digest": (P) => [
+    { path: P.registerHitList,
+      why: "the digest's own message names this file and asks the model to mark lines on it (hit-list.mjs reads the marks back); without it in the copy a marking lands nowhere and the stage passes having been given a different input than the real one" },
+  ],
   // The provider enforcement telemetry: the prompt names the path only when ctx.enforcerSignals is a
   // non-zero count (stages.mjs synthesis message). Undeclared on purpose — it is aim-attention only and
   // must never move a freshness stamp — but a sandbox without it hands a different prompt.
   synthesis: (P) => [
     { path: P.enforcerSignals, kind: "conditional",
       why: "named in the prompt only when ctx.enforcerSignals > 0; aim-attention telemetry, deliberately outside the freshness map" },
+    // The job's own scope. The prompt never names it, so nothing declared it, and the sandbox rebuilt the
+    // declination spec without it: no marks and no classes, so both of the tool's refusals were off in every
+    // synthesis arm while the canonical pass had them on.
+    { path: P.instructedScope, kind: "driver-side",
+      why: "prepareDeclinationSpec writes the declination spec's scope from it; without it the tool's refusals rest on nothing and accept what the canonical pass refused" },
+    // The Chinese-evidence flags, named in the prompt only when ctx.jxAim is set (stages.mjs synthesis
+    // message). Undeclared, an arm on a run that had them dispatched without the block.
+    { path: driverDir(P.runDir, "jx", "aim-attention.json"), kind: "conditional",
+      why: "named in the prompt only when ctx.jxAim > 0 — the zh lane's aim-attention flags; aim-attention only, deliberately outside the freshness map" },
   ],
 };
 

package/driver/stages-knockout.mjs

@@ -560,9 +560,10 @@ export const KO_STAGES = {
     // be composed by anything except the production call site, which is how a dispatch goes unexamined
     // — and the promise has to branch. A stage message that says "the lines are below" and then lists
     // none has handed the seat an absence dressed as a pass, which is the reading this whole rule
-    // exists to stop. The driver does not dispatch on an empty measurement; the branch is here because
-    // "it cannot happen" is not a property a message should depend on.
-    message: ({ K, evidenceLines = [], exclusionNote = "" }) => lines(
+    // exists to stop. A record the driver's read flags nowhere is handed its first-read lines instead,
+    // by the owner's ruling of 2026-10-10, so both branches have rows under them; a record with no such
+    // line is not dispatched at all.
+    message: ({ K, evidenceLines = [], firstReadLines = [], exclusionNote = "" }) => lines(
       // THE CLIENT'S QUESTION LEADS, in the owner's words (ruling 2026-09-24), ahead of the rewrite job.
       `Does the report answer the client's question: who could object, how strong they are, what the client should do? Are the marks a lawyer would list present, and is each position written from the record that matters? Answer that before any check on wording.`,
       reads(["skills/clearance-search/report-prose.md"]),
@@ -571,8 +572,8 @@ export const KO_STAGES = {
       `The rated record: ${K.findings}. Read it — the lines named below are quoted from it and you are rewriting them in place.`,
       evidenceLines.length
         ? `THE DRIVER MEASURED THESE LINES. Each row is the line, the ADDRESS that names it, and what a deterministic read found. THIS IS EVIDENCE, NOT A VERDICT: judge each in context and pass over any where the word is the subject rather than the profession's shorthand. ${exclusionNote}`
-        : `THE DRIVER'S READ FLAGGED NO LINE ON THIS RECORD, so there is no table below and nothing here is evidence of a fault. Read the record yourself against the rule above; if it is already plain, send one \`declined\` row saying so rather than inventing a rewrite to fill the call.`,
-      ...evidenceLines,
+        : `THE DRIVER'S READ FLAGGED NO LINE ON THIS RECORD, so nothing below is evidence of a fault. These are the lines a reader meets first, each with the ADDRESS that names it. Rewrite one only where it would answer the client's question more plainly; if every line already does, send one \`declined\` row at one of these addresses saying so, rather than inventing a rewrite to fill the call.`,
+      ...(evidenceLines.length ? evidenceLines : firstReadLines),
       // ── THE DICTATION NAMES THE FIELD, NOT AN EFFECT ────────────────────────────────
       //
       // "Make the report plainer" is read and not applied, and nothing refuses — it simply does not