clearotron 0.2.1 → 0.2.2

package/driver/runner.mjs

@@ -23,13 +23,13 @@ import "./engine/mcp/http-dispatcher.mjs";   // side effect: raise undici header
 import { readdirSync, renameSync, existsSync, mkdirSync, readFileSync, writeFileSync, appendFileSync, rmSync, statSync } from "node:fs";
 import { join, dirname, basename } from "node:path";
 import { driverDir, ensureDriverDir } from "../shared/driver-dir.mjs";   // — one definition of where `_driver/` is
-// The queue's filename vocabulary, in ONE place — 's rule, extended by to the prose-sidecar and
+// The queue's filename vocabulary, in ONE place — the rule, extended by to the prose-sidecar and
 // claim-sidecar names, because a harness check retyped four of them from memory and false-alarmed on the
 // other nine. Behaviour here is unchanged: the same object and the same three suffixes, sourced.
 import { isLiveQueueMarker, PROSE_PARTS, CLAIM_SIDECAR_SUFFIXES, TERMINAL_QUEUE_SUFFIXES } from "./queue-markers.mjs";
 import { matterLedgerPath } from "./usage-ledger.mjs";   // ONE ledger-path calculation, shared with the portal pre-check
-import { orderTimeRefusal } from "./run-requirements.mjs";   // tracker issue 216 — one authority for what a run needs, and when it is asked for
-import { unitEnvPath } from "../shared/env-local.mjs";   // tracker issue 216 — the file the units read, named by its one author
+import { orderTimeRefusal } from "./run-requirements.mjs";   // one authority for what a run needs, and when it is asked for
+import { unitEnvPath } from "../shared/env-local.mjs";   // the file the units read, named by its one author
 import { fileURLToPath } from "node:url";
 import { config, preflightDeploymentUrls } from "./driver.config.mjs";
 import { deriveSlug, todayISO, mintFreshCodename } from "./phase0.mjs";
@@ -136,7 +136,7 @@ function matterSignature(job, { product = null } = {}) {
   const base = `${forwarder}|${mark}|${classes}|${customer}|${ref}`;
   // Product dimension. ONE product adds nothing to the string, and it has to be one or every legacy
   // ledger row would stop colliding with its own re-send: the pre-spine signature had no suffix at all,
-  // and the level that ran then was `prelim`. That level's SUCCESSOR is the Global preliminary search —
+  // and the level that ran then was `clearotron`. That level's SUCCESSOR is the Global preliminary search —
   // the clearance a request with nothing named resolves to — so it is the one that stays silent, and
   // `sigLevel`'s default reads a suffixless row as it. The key name stays `level:` for the same reason:
   // it is a string already written into every ledger on disk.
@@ -342,7 +342,7 @@ async function intakeNotify(agentId, base, job, v) {
   const what = v?.classify === "clarify"
     ? `needs clarification before it can run: ${v.errors.join("; ")}`
     : `was rejected at intake: ${(v?.errors ?? ["unparseable job file"]).join("; ")}`;
-  const text = `⚠️ Prelim request "${mark}" ${what}. Nothing has been searched or delivered. ` +
+  const text = `⚠️ Clearotron request "${mark}" ${what}. Nothing has been searched or delivered. ` +
     `Job parked as ${base}.failed in the ${agentId} queue.`;
   const p = writeOutboxPacket(`intake-${base}.failed`, {
     kind: "intake-rejected", classify: v?.classify ?? "reject", base, agent: agentId,
@@ -381,7 +381,7 @@ function cleanupClaimSidecars(procPath) {
  * Returns true when this call moved the marker, false when it was already gone. Any other error still
  * throws: a permissions failure or a full disk is not a sibling.
  */
-export function retireMarker(procPath, destPath, what = "") {   // exported for 's honesty test
+export function retireMarker(procPath, destPath, what = "") {   // exported for the honesty test
   try { renameSync(procPath, destPath); return true; }
   catch (e) {
     if (e?.code !== "ENOENT") throw e;
@@ -389,7 +389,7 @@ export function retireMarker(procPath, destPath, what = "") {   // exported for
     // <dest> is on disk. On this branch the rename did NOT happen, so <dest> was never created by this
     // call, and the parenthetical named the outcome the caller intended rather than the one an operator
     // would find. It is the single line an operator reads to discover where a job went, and it was
-    // pointing at a file that is not there. The reproduction (, PR) ends with the queue dir
+    // pointing at a file that is not there. The reproduction (PR) ends with the queue dir
     // holding `job-race.processing` and `job-race.processing.pid` and NO `.json` at all, under a log
     // line that said the orphan had been returned to the queue.
     note(`[runner] ${basename(procPath)} was already retired by another runner — this call did NOT create ${basename(destPath)} (it wanted: ${what || "retire the marker"}); the marker is in whatever state that runner left it`);
@@ -433,13 +433,13 @@ export function retireMarker(procPath, destPath, what = "") {   // exported for
  * marker; the argument holds only because no `<base>.json` exists while we hold the lock (both enqueue
  * doors refuse an id whose `.json` or `.processing` is already present, and this call is the one about
  * to create it). The residual — a fresh enqueue of the SAME id landing between the two renames — is the
- * window 's claim lock and `takeoverClaim` already carry, unchanged here. At a call site where a
+ * window the claim lock and `takeoverClaim` already carry, unchanged here. At a call site where a
  * `<base>.json` CAN coexist with the marker, that argument does not transfer.
  *
  * Returns true when this call moved the marker to `destPath`. False means the claim was not ours to
  * retire — and that nothing on disk was touched.
  */
-export function retireClaimAndSweep(procPath, destPath, what = "", { token = claimToken() } = {}) {   // exported for 's race test
+export function retireClaimAndSweep(procPath, destPath, what = "", { token = claimToken() } = {}) {   // exported for the race test
   const lockPath = `${procPath}.claimed-${token}`;
   try { renameSync(procPath, lockPath); }
   catch (e) {
@@ -482,7 +482,7 @@ export function retireClaimAndSweep(procPath, destPath, what = "", { token = cla
  *     RE-ASSEMBLED from. It is the one deletion that outlives every marker state: the winner's job — a
  *     resume, or a hand-back to `.json` — then cannot be assembled at all.
  *   - `<base>.done.result` / `<base>.failed.result` asserts a terminal that is not on disk. That is
- *     's defect exactly (a line naming the outcome the caller WANTED, not the one an operator would
+ *     That defect exactly (a line naming the outcome the caller WANTED, not the one an operator would
  *     find), one call below the fix for it.
  *   - `dropMatter` marks the matter ledger row `failed`, and `findDuplicateMatter` skips failed rows —
  *     so it re-opens the dedup gate for a matter the winner may be mid-resume, and the ~$40 duplicate
@@ -578,7 +578,7 @@ async function failAtIntake(procPath, qdir, base, agentId, job, v, reasons) {
 // outcome string for the .reason file.
 async function duplicateNotify(agentId, base, job, prior = null, sig = null) {
   const mark = job?.markName ?? job?.name ?? job?.marks?.[0]?.name ?? base;
-  // ── tracker issue 136 — A REFUSAL DELIVERED AS SILENCE IS INDISTINGUISHABLE FROM A LOST JOB ────────
+  // ── A REFUSAL DELIVERED AS SILENCE IS INDISTINGUISHABLE FROM A LOST JOB ────────
   //
   // The observable outcome of a dedup park was an empty queue and no run, which is exactly what an
   // enqueue that vanished looks like — and the two want completely different next actions. That got
@@ -598,7 +598,7 @@ async function duplicateNotify(agentId, base, job, prior = null, sig = null) {
   const which = prior?.msgId
     ? ` The run already under way was submitted as ${prior.msgId}${when ? ` at ${when}` : ""} — that is the one that will deliver.`
     : " The earlier run will deliver.";
-  const text = `⚠️ Prelim request "${mark}" matches a matter already in progress or just delivered, so it was `
+  const text = `⚠️ Clearotron request "${mark}" matches a matter already in progress or just delivered, so it was `
     + `NOT run — a second search would spend twice for one answer.${which}`
     + ` If you genuinely need a fresh run of the same matter, re-submit it with dupOverride (\`--dup-override\` on the`
     + ` command line) and it will go through.`;
@@ -631,7 +631,7 @@ async function parkDuplicate(procPath, qdir, base, agentId, job, prior, sig) {
   const conv = String(job.conversationId ?? "").trim();
   const matchedBy = prior.conversationId && prior.conversationId === conv ? "thread (conversationId)" : "matter signature";
   const reason = [
-    `duplicate prelim — not run (a second search for the same matter)`,
+    `duplicate clearotron — not run (a second search for the same matter)`,
     `matched by: ${matchedBy}`,
     `matter: ${sig}`,
     `conversationId: ${conv || "-"}`,
@@ -666,7 +666,7 @@ function preRunFailNotify(agentId, base, job, reason) {
   // terminalReasonFields `reason`, so this cut is a no-op today — which is exactly why it survived: a
   // latent second cap, unmarked, waiting for the next caller to pass a raw reason. It collapses and
   // trims identically, so this is the same string with the cut made visible when there is one.
-  const text = `❌ Prelim request "${mark}" FAILED before the run could start: ${terminalReasonFields(reason).reason} — ` +
+  const text = `❌ Clearotron request "${mark}" FAILED before the run could start: ${terminalReasonFields(reason).reason} — ` +
     `nothing has been searched or delivered. Job parked as ${base}.failed in the ${agentId} queue.`;
   // `intake-${base}.` PREFIX, not a third scheme: scripts/e2e.mjs's outboxPackets matches by runId
   // first and by that prefix second, so a name outside it is a notice the harness reports as
@@ -716,7 +716,7 @@ async function backstopFailureNotice({ res, job, agentId, base, codename, studio
       shortReason, reasonVerbatim: reason.slice(0, 1000), whatsappTo: AGENT_WHATSAPP[agentId] ?? null,
     });
     // same per-send invariant as the pipeline's failure path: a fresh notice supersedes an older .sent
-    // and its per-channel receipts (B4 — stale receipts would make prelim-deliver skip this notice)
+    // and its per-channel receipts (B4 — stale receipts would make clearotron-deliver skip this notice)
     try { rmSync(join(owned.dir, ".sent"), { force: true }); } catch { /* none */ }
     try { rmSync(driverDir(owned.dir, "send-receipts.json"), { force: true }); } catch { /* none */ }
     ensureDriverDir(owned.dir);
@@ -740,7 +740,7 @@ async function backstopFailureNotice({ res, job, agentId, base, codename, studio
 // one-at-a-time so the dedup check+record stays race-free even while prior jobs' pipelines run concurrently
 // (Phase-4). Returns the prepared {procPath, base, job} to execute, or null when the job was terminally
 // parked/failed-at-intake, or the claim was lost.
-// ── tracker issue 216 — THE ORDER-TIME REFUSAL, AND WHY IT IS HERE ──────────────────────────────────
+// ── THE ORDER-TIME REFUSAL, AND WHY IT IS HERE ──────────────────────────────────
 //
 // A hosted install now STARTS with no register configured (owner ruling 2026-09-06: "someone can install
 // and select key later so it should still start"). The protection that used to live in
@@ -849,7 +849,7 @@ async function claimAndPrep(jsonFile, qdir, agentId) {
     await failAtIntake(procPath, qdir, base, agentId, job, v, v.errors);
     return null;
   }
-  // ── tracker issue 216 — IS THIS BOX CONFIGURED TO SEARCH AT ALL? See the header above claimAndPrep.
+  // ── IS THIS BOX CONFIGURED TO SEARCH AT ALL? See the header above claimAndPrep.
   {
     const refusal = orderTimeRefusal(process.env, await runTables(), { envFile: unitEnvPath() });
     if (refusal) {
@@ -860,11 +860,11 @@ async function claimAndPrep(jsonFile, qdir, agentId) {
     }
   }
   // Search-depth spine — resolve WHICH product shape this job selects (job selector → project/customer
-  // default → house prelim), then gate on what this deployment can actually run. A selection that cannot
+  // default → house clearotron), then gate on what this deployment can actually run. A selection that cannot
   // run here CLARIFIES loudly (parked + requester notified) — it must never silently run as a different-
   // priced product, and never silently drop. Fail-open discipline (review 2026-07-17): infra trouble may
   // NO FAIL-OPEN LEFT ON THIS PATH, and its removal is the point. It used to fall back to the literal
-  // level `prelim` when resolution errored and the job "provably" wanted a plain clearance — but `prelim`
+  // level `clearotron` when resolution errored and the job "provably" wanted a plain clearance — but `clearotron`
   // named THREE products depending on where it pointed, so the fallback was a guess wearing a level key:
   // an account whose defaults hold one country would have run a Full country search, case law and all,
   // off a config read that failed. Under the offering the product is a function of the scope, and a scope
@@ -1027,7 +1027,7 @@ async function claimAndPrep(jsonFile, qdir, agentId) {
 // result the whole time and the marker threw it away.
 //
 // WHAT THIS DOES NOT DO: invent a cause. Neither branch classifies anything; each states which park
-// fired and what its clock means. 's damage was a record that could not be contradicted from the
+// fired and what its clock means. That damage was a record that could not be contradicted from the
 // artifacts, so the fix is not a better guess — it is saying less, and saying which.
 export function parkCause(res = {}) {
   const RESOLVED_BY = "a live retry — the stored time is a hint about when to look, not the authority on "
@@ -1182,8 +1182,8 @@ async function runPrepared({ procPath, base, job }, qdir, agentId, resumeMeta =
       //
       // The pipeline already made this distinction where it writes its own sentinel — "only the recovery
       // sentinel carried a discriminator … the 2026-07-28 postmortem misread: a recovery park diagnosed
-      // as a rate-limit park". The queue-side marker never got it. Same shape as 's terminal fields
-      // reaching two writers and not four, and 's stamp reaching the audit path and not the rebuild.
+      // as a rate-limit park". The queue-side marker never got it. Same shape as the terminal fields
+      // reaching two writers and not four, and the stamp reaching the audit path and not the rebuild.
       ...parkCause(res),
     });
     note(`[runner] ${base} → POSTPONED (${parkCause(res).parkKind}; retries at the earlier of ${res.resetsAt ?? "its due time"} and its next probe — no hand-edit needed if it clears early)`);

package/driver/scope-rules.mjs

@@ -113,7 +113,7 @@ export function checkClearanceScopeRules({ job = null, profile = null, resolved
   // request resolves to no territory" would be a claim about a scope nobody saw. But when the request —
   // or the saved search it names — DOES name territories, the profile is irrelevant to the count and the
   // rules still bite. Skipping them there is how a roster-blind deployment (profile_key_unknown → the
-  // fail-open to prelim) would admit a three-country deep dive at the wall itself (review 2026-07-27).
+  // fail-open to clearotron) would admit a three-country deep dive at the wall itself (review 2026-07-27).
   if (!profileReadable && !scope.length) return { errors, warnings };
   // Quoted AS WRITTEN, worldwide tokens dropped (a mode is not a place — territory-tiers.mjs answers
   // which entries those are, so this module and the door cannot disagree about the spelling of

package/driver/search-policy.mjs

@@ -351,7 +351,7 @@ export function reportIdentityFor(levelOrPolicy) {
 
 /** The product's coverage note for the report masthead (charter ruling 1, 2026-07-30: what was bought
  *  must be VISIBLY clear on the page — a reader must never confuse "the same section" in two different
- *  searches). One plain sentence, NAME-LED per the ruling (match 's registry-name pills: the
+ *  searches). One plain sentence, NAME-LED per the ruling (match the registry-name pills: the
  *  product's name leads, never a rung on our ladder), stating what THIS search covers and the material
  *  thing it does not. The name comes from the registry join (reportIdentityFor — today's name for what
  *  ran, exactly the  doctrine); the coverage clauses come from the run's own frozen COMPONENTS
@@ -678,7 +678,7 @@ export function productAvailability(policy, { built = BUILT, registerCanCount =
  */
 export const UNAVAILABLE_NOTE = {
   unbuilt: "Not part of the current release.",
-  // `demo` IS DELETED FROM THIS MAP (, owner ruling 2026-08-31 14:47), and
+  // `demo` IS DELETED FROM THIS MAP (owner ruling 2026-08-31 14:47), and
   // deleting it is what makes the reversal structural rather than a filter somebody can undo by
   // accident. Every client-facing surface renders a product's refusal as `UNAVAILABLE_NOTE[cause]`;
   // while a sentence sat here for a demo, the greyed control was one `return "demo"` away from coming
@@ -692,7 +692,7 @@ export const UNAVAILABLE_NOTE = {
   // a baked-in provider name, no CLEAROTRON_* string in scope here, and it says the one thing a reader can
   // act on — this is a coverage limit, so a newer version will not fix it.
   //
-  // `register-not-worldwide` IS DELETED FROM THIS MAP (, owner ruling
+  // `register-not-worldwide` IS DELETED FROM THIS MAP (owner ruling
   // 2026-08-31), and deleting it is what makes the ruling structural rather than a filter somebody can
   // reverse by accident. Every client-facing surface renders a product's refusal as
   // `UNAVAILABLE_NOTE[cause]`; while a sentence sat here for that cause, the ruling held only as long as

package/driver/skeptic-search.mjs

@@ -1,7 +1,7 @@
 // SPDX-License-Identifier: AGPL-3.0-only
 // Copyright 2026 Cordillera Sàrl. Additional terms under section 7 of the AGPL-3.0 apply — see ADDITIONAL-TERMS.md
 // skeptic-search.mjs — the skeptic's SANCTIONED READ SURFACE: literal substring search over the run's
-// own artifact tree. 's ratification hold, unlock path 1.
+// own artifact tree. That ratification hold, unlock path 1.
 //
 // ── WHAT THIS REPLACES, measured and nothing more ───────────────────────────────────────────────────
 //

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

@@ -5,7 +5,7 @@ description: The frame-STARVED independent re-derivation for the v3 preliminary
 
 ## Purpose
 
-Every other stage in a prelim run reasons *inside* a frame that was set early (at `matter-frame` / `prelim-variants`): the variants to chase, the field that counts as on-field, the sources worth searching. Verification then runs *on* that frame — nothing tests the frame itself. When the frame is mis-scoped, the whole run inherits the miss and the skeptic, reasoning from the same frame, certifies it.
+Every other stage in a clearotron run reasons *inside* a frame that was set early (at `matter-frame` / `prelim-variants`): the variants to chase, the field that counts as on-field, the sources worth searching. Verification then runs *on* that frame — nothing tests the frame itself. When the frame is mis-scoped, the whole run inherits the miss and the skeptic, reasoning from the same frame, certifies it.
 
 You are the antidote. You are **deliberately starved of the frame**: you receive only the raw instruction, exactly as the requester wrote it, and you re-derive the threat model **cold**. Because you never see the run's conclusions, you cannot anchor to them. Your output is later **diffed** against what the run actually scoped — the gaps in that diff are the omissions the frame missed.
 

package/driver/skills/case-law-citation/SKILL.md

@@ -17,7 +17,7 @@ cannot reach any other stage's context, because no stage shares one — and it i
 arranges or can lose. Nothing here spawns a session; sequencing, fan-in and retries are the driver's.
 
 The identical skill is also valid **inline** in ad-hoc chat when a conflict / confusability / enforcer
-question arises outside a prelim run.
+question arises outside a clearotron run.
 
 **Reads** — from the dispatch message (plain markdown, not JSON), for each finding to ground:
 - the proposed mark and the conflicting mark / owner / entity,
@@ -46,7 +46,7 @@ Boards-of-Appeal decisions — no free API today). EUIPO *register* lookups are
 
 Called by `prelim-search` after synthesis flags the risk-relevant findings (Step 4.5). Also triggers in
 chat when the user raises a trademark conflict, likelihood-of-confusion, or enforcement-history question.
-Gated and optional: if this skill is absent, prelim skips Step 4.5 and delivers normally.
+Gated and optional: if this skill is absent, clearotron skips Step 4.5 and delivers normally.
 
 ## Model
 

package/driver/skills/knockout-assess/SKILL.md

@@ -162,9 +162,14 @@ your job. These two fields are how what you concluded reaches the reader instead
 every id against that store and refuses one it does not hold — so the report can state a filing's
 source as a fact rather than as a word you typed about your own sourcing.
 
-- **`registerReads`** — on the MARK. Rows of `{recordId, read}` for a filing you weighed that did **not**
-  become a `findings[]` record. `read` is what you concluded about *that* filing: whether it bears on the
-  rating, and why. It prints on that filing's card.
+- **`registerReads`** — on the MARK. Rows of `{recordId, read, band?}` for a filing you weighed that did
+  **not** become a `findings[]` record. `read` is what you concluded about *that* filing: whether it bears
+  on the rating, and why. It prints on that filing's card. `band` is **optional** and is how you rate that
+  filing on its own — in the framework's band words, the same vocabulary as the mark's rating. Send it
+  whenever you formed a view on the filing itself: a registered right is often the one hard legal fact on
+  the page, and with no band its card is the only one carrying no rating while softer uses around it carry
+  one, which reads as though the registration mattered least. Omit it and the read still prints, claiming
+  no rating.
 - **`weighedFilings`** — on a FINDING. The `recordId`s whose evidence your reasoning for that conflict
   actually used. The report derives the finding's source labelling from this, so list one only if you
   reasoned from it.
@@ -205,7 +210,8 @@ line, which describes the card and claims nothing about the rating. So:
                "classesDriving": [8], "bullets": ["..."], "purpleNotes": ["..."],
                "registerEstimate": "...", "parodyNote": null, "crowdedField": false,
                "registerReads": [ { "recordId": "<verbatim from the filings you were given>",
-                                    "read": "<what you concluded about THAT filing>" } ],
+                                    "read": "<what you concluded about THAT filing>",
+                                    "band": "<OPTIONAL — your rating of THAT filing, in the ladder's words>" } ],
                "basis": "<ONE sentence: why this band, for this name, in these classes>",
                "factors": ["<2-4 load-bearing observations, one line each>"],
                "counterFactors": ["<1-3: what holds it at this band rather than the next>"],

package/driver/skills/prelim-search/SKILL.md

@@ -26,7 +26,7 @@ description: Orchestrator for preliminary trademark search requests with registe
 
 ## Spawned session
 
-This file is the **driver's compute orchestration spec** — it lives in `driver/skills/` (co-located with the driver) and is read by the pipeline stages, NOT by the integrator agent. The integrator's prelim role is only **intake** (recognise the request, resolve the client, submit the job — `../../docs/INTAKE.md`) and **delivery** (courier the outbox packets — `../../docs/DELIVERY.md`); everything between is the driver's.
+This file is the **driver's compute orchestration spec** — it lives in `driver/skills/` (co-located with the driver) and is read by the pipeline stages, NOT by the integrator agent. The integrator's clearotron role is only **intake** (recognise the request, resolve the client, submit the job — `../../docs/INTAKE.md`) and **delivery** (courier the outbox packets — `../../docs/DELIVERY.md`); everything between is the driver's.
 
 This workflow is run by the **deterministic driver** (`driver/`): an intake path (the `enqueue` CLI or the ops-MCP `start_run` tool) enqueues a job and the driver invokes each stage as a standalone compute turn (the `anthropic-agent` engine — a headless `claude -p` process off the gateway; sequencing, fan-in, gating, retries all in code). The judgment content + companion files below are what the stages read; the driver passes each stage its run-dir paths + the job context (email message id, forwarder, instructions, mark names).
 
@@ -58,7 +58,7 @@ reads only their compact findings files. This is the workflow's primary cost con
 
 ## Trigger
 
-The requesting or reviewing lawyer forwards an email containing a **Trademark Search Request Form** to the intake mailbox. The forwarded email is typically structured as a request form ("Worldwide preliminary trademark search — TMP<n>", "Please run this through a preliminary search", or similar). When the request is recognisable as a prelim search ask, this skill invokes.
+The requesting or reviewing lawyer forwards an email containing a **Trademark Search Request Form** to the intake mailbox. The forwarded email is typically structured as a request form ("Worldwide preliminary trademark search — TMP<n>", "Please run this through a preliminary search", or similar). When the request is recognisable as a clearotron search ask, this skill invokes.
 
 ## Register sources — the vendor is the source of truth; EUIPO is a free EU cross-check
 

package/driver/skills/prelim-search/template-formatting.md

@@ -1,4 +1,4 @@
-# Prelim Template — HTML Formatting Spec
+# Clearotron Template — HTML Formatting Spec
 
 > **THIS FILE IS HALF LIVE, AND THE HALVES HAVE DIFFERENT READERS. Check which half you are in before
 > you trust a line.**

package/driver/skills/prelim-search/templates/email/generic.md

@@ -20,7 +20,7 @@ The email body has these blocks, in this order:
 
 > "Hi [first name from request],
 >
-> Prelim for [mark name] complete — findings below; full audit Excel attached."
+> Clearotron for [mark name] complete — findings below; full audit Excel attached."
 
 (For internal test runs, use "Hi [forwarder first name]" and add a one-line context note: "v[N] test run — replied to you only, not forwarded to [client].")
 

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

@@ -5,7 +5,7 @@
   synthesis-rules.md.
 -->
 
-# Prelim synthesis — gold-standard worked examples
+# Clearotron synthesis — gold-standard worked examples
 
 ## Contents
 

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

@@ -1,6 +1,6 @@
 ---
 name: prelim-variants
-description: Shared strategy + variant generation for the v3 preliminary trademark search workflow. **Invoked exclusively by the `prelim-search` orchestrator** as the first stage of any v3 prelim run — do not call directly. Classifies the proposed mark into one of six analytical archetypes, derives a risk theory from that classification, then generates the variant set whose axes are shaped by the archetype. Emits a markdown variant manifest consumed by both common-law (`prelim-common-law`) and register (`prelim-register`) execution skills.
+description: Shared strategy + variant generation for the v3 preliminary trademark search workflow. **Invoked exclusively by the `prelim-search` orchestrator** as the first stage of any v3 clearotron run — do not call directly. Classifies the proposed mark into one of six analytical archetypes, derives a risk theory from that classification, then generates the variant set whose axes are shaped by the archetype. Emits a markdown variant manifest consumed by both common-law (`prelim-common-law`) and register (`prelim-register`) execution skills.
 ---
 
 ## Contents
@@ -27,7 +27,7 @@ Companion files:
 
 ## Trigger
 
-Called by `prelim-search` at the start of any prelim run. Not invoked directly.
+Called by `prelim-search` at the start of any clearotron run. Not invoked directly.
 
 ## Model
 

package/driver/stage-context.mjs

@@ -92,7 +92,7 @@ const DECLARED_KIND = {
     // — the placement form is CONTEXT, and deliberately NOT a freshness input. The driver writes it
     // before dispatch and rewrites it after every judgement (the union runs on each one), so it is always
     // newer than the md the seat just wrote — and adding it to stageInputs would make the largest stage in
-    // the run read stale on every resume and re-dispatch itself. 's ruling exactly: the fix is a
+    // the run read stale on every resume and re-dispatch itself. That ruling exactly: the fix is a
     // second view, not a wider freshness list.
     placementForm: ["driver-side",
       "written by the driver before dispatch and re-unioned on every judgement; the prompt names the path because the seat writes its selections there"],

package/driver/stages-knockout.mjs

@@ -5,7 +5,7 @@
 // kept in its OWN table: the knockout lane is a different product shape (a 5–15 mark triage batch), and
 // its stages must never leak into the clearance STAGE_ORDER. New-named stages get [] MCP tool groups
 // automatically (gather-config prefix map — the matter-frame precedent), so frame/assess run lean.
-import { existsSync } from "node:fs";
+import { existsSync, readFileSync } from "node:fs";
 import { join } from "node:path";
 import { driverDir } from "../shared/driver-dir.mjs";   //
 import { validators as koValidators } from "./verify-knockout.mjs";
@@ -19,6 +19,30 @@ export { kebab };   // one definition (search-policy) — re-exported for the la
 const lines = (...xs) => xs.filter(Boolean).join("\n");
 const reads = (skillReads) => `First, read and follow exactly: ${skillReads.join(", ")}.`;
 
+/**
+ * One line per owner the driver looked up, for the assess dispatch (tracker issue 276).
+ *
+ * BOTH OUTCOMES ARE NAMED, and that is the point. A row whose search answered gets its payload path; a
+ * row whose search did NOT answer says so in the dispatch itself. Listing only the answered ones would
+ * leave the seat unable to tell "nobody searched this owner" from "the search found nothing", and those
+ * two license completely different reads — the second is a fact about the owner's visibility, the first
+ * is a gap the seat would fill by inferring from the name, which is the defect this whole issue is about.
+ *
+ * Returns [] when the lane did not run or the store is unreadable, so the dispatch simply omits the block
+ * rather than naming a path that is not there.
+ */
+export function ownerCheckLines(K) {
+  let doc = null;
+  try { doc = existsSync(K.ownerChecks) ? JSON.parse(readFileSync(K.ownerChecks, "utf8")) : null; } catch { doc = null; }
+  const checks = Array.isArray(doc?.checks) ? doc.checks : [];
+  return checks.map((c) => {
+    const who = `${c.owner} (proprietor of a filing for ${c.mark})`;
+    return c.ok && c.payloadFile
+      ? `- ${who}: ${join(K.runDir, "research", c.payloadFile)}`
+      : `- ${who}: THE SEARCH RETURNED NOTHING. Say so in the read; do not infer the trade from the name.`;
+  });
+}
+
 // ── Paths (knockout-own; beside the standard _driver sidecars) ───────────────────────────────────────
 export function koPaths(runDir) {
   return {
@@ -39,10 +63,15 @@ export function koPaths(runDir) {
     // rows were left exactly as they were rather than gaining a matching marker: their shape is pinned
     // byte-for-byte by register-count.test.mjs, and a discriminator only one side needs is enough.
     registerRecords: driverDir(runDir, "register-records.json"),
+    // The scoped owner lookups this run owes its promoted filings, and their receipts (tracker issue
+    // 276). Both under `_driver/` because both are the DRIVER's own measurement of a call it made — the
+    // rule stated fourteen lines above. The seat reads the payloads under research/, never these.
+    ownerChecks: driverDir(runDir, "owner-checks.json"),
+    ownerCheckLedger: driverDir(runDir, "owner-check.jsonl"),
     researchDir: join(runDir, "research"),
     research: (markKebab) => join(runDir, "research", `${markKebab}.md`),
     sweepLedger: driverDir(runDir, "knockout-sweep.jsonl"),
-    // 's SHAPE, APPLIED: the WORK MOVES OUT OF THE GUARDED TREE — the hook is never weakened.
+    // That SHAPE, APPLIED: the WORK MOVES OUT OF THE GUARDED TREE — the hook is never weakened.
     //
     // This chunk is a MODEL OUTPUT, and it sat under `_driver/` in flat contradiction of the rule stated
     // fourteen lines above: those files "are the driver's own measurements, NEVER a model's output". So
@@ -289,6 +318,28 @@ export const KO_STAGES = {
       existsSync(K.registerRecords)
         ? `THE REGISTER FILINGS THIS RUN ALREADY FETCHED — ${K.registerRecords}. Real records, retrieved before you started: owner, jurisdiction, status, classes, dates. Read them and WEIGH them for the marks you are rating. A registration on this list is evidence about the name it names — treat its owner, its scope and its vulnerability the way the firm-wide reasoning tells you to (revocability above the lowest band; an enforcer's portfolio profile; a crowd as a mitigant under its gating precondition). What you may NOT do is describe the lane that fetched them — see the coverage rule below.`
         : "",
+      // ── WHAT THE OWNER ACTUALLY SELLS, ALREADY SEARCHED (tracker issue 276) ────────────────────────
+      //
+      // The defect this closes is not that the seat lacked an instruction — it is that the seat had no
+      // way to know. It was handed an owner's NAME and its class numbers and nothing else, so a read
+      // about what that owner sells could only ever be an inference from the string. The driver now runs
+      // the scoped query before this stage and hands the answer over.
+      //
+      // ORDERED, NOT OFFERED. Naming a payload the seat may read is what produces "read and not applied,
+      // no refusal" — a rule that names a downstream effect rather than the field the seat writes. This
+      // names the field: the read on that filing's registerReads row.
+      //
+      // AND THE NEGATIVE CASE IS ORDERED TOO, because it is the one that produced the original defect:
+      // where the lookup did not answer, the honest sentence is that it did not, NOT a fresh inference
+      // from the owner's name dressed as a finding.
+      ownerCheckLines(K).length
+        ? [
+          `WHAT THESE OWNERS ACTUALLY SELL — the driver ran ONE scoped web search per promoted filing's proprietor BEFORE this stage, so you are not guessing from the company name. Payloads:`,
+          ...ownerCheckLines(K),
+          `USE THEM. When you write a registerReads row for one of these filings, your "read" must state what the owner actually sells ACCORDING TO THAT PAYLOAD, not what the company's name suggests and not what its class numbers imply. An owner's name is not evidence of its trade. A company name that reads as a line of business is a guess that happens to land sometimes, and the run where it lands is indistinguishable from the run where it does not — which is the reasoning this rule exists to stop.`,
+          `WHERE A PAYLOAD SAYS THE SEARCH FOUND NOTHING, say that plainly in the read — "a search for the proprietor's trade returned nothing" — and reason from the register record alone. Do NOT substitute an inference from the owner's name for the answer the search did not give. The report prints the source line itself, from the driver's own record of the call, so you never type a URL and never need to.`,
+        ].join("\n")
+        : "",
       // ── THE READ REACHES THE PAGE ────────────────────────────────────────────
       //
       // Until now nothing this seat concluded about an INDIVIDUAL filing could reach a reader. A filing
@@ -301,7 +352,7 @@ export const KO_STAGES = {
       // a finding with no register evidence. Omitting either field is always safe: the card keeps its
       // neutral line, which describes the card and is true.
       existsSync(K.registerRecords)
-        ? `WHEN YOU WEIGH ONE OF THOSE FILINGS, SAY SO BY ITS OWN ID — copy "recordId" verbatim from the file above. "registerReads" on the MARK: rows of {recordId, read} for a filing you weighed that did NOT become a findings[] record; "read" is what you concluded about THAT filing — whether it bears on the rating and why — and it prints on that filing's card in the reader's own report. "weighedFilings" on a FINDING: the recordIds whose evidence your reasoning for that conflict actually used, because the report derives that finding's source labelling from it. Both are optional and both are joined against the filings you were given, so an id we do not hold is refused by name. A filing you did not weigh simply gets no row: do not invent a read to fill one, and never write "not weighed" as a read.`
+        ? `WHEN YOU WEIGH ONE OF THOSE FILINGS, SAY SO BY ITS OWN ID — copy "recordId" verbatim from the file above. "registerReads" on the MARK: rows of {recordId, read, band?} for a filing you weighed that did NOT become a findings[] record; "read" is what you concluded about THAT filing — whether it bears on the rating and why — and it prints on that filing's card in the reader's own report. "band" is OPTIONAL and is your rating of THAT filing on its own, in the framework's band words: send it whenever you formed a view on the filing itself, because a registered right left unbanded is the only card on the page with no rating while softer uses beside it carry one, which reads as though the registration mattered least. Omit it and your read still prints, claiming no rating. "weighedFilings" on a FINDING: the recordIds whose evidence your reasoning for that conflict actually used, because the report derives that finding's source labelling from it. Both are optional and both are joined against the filings you were given, so an id we do not hold is refused by name. A filing you did not weigh simply gets no row: do not invent a read to fill one, and never write "not weighed" as a read.`
         : "",
       `A DEGRADED mark's row must carry degraded:true and the purple "Manual verification recommended"`,
       `note; a mark WITH a payload must never claim degraded (the validator joins both against the disk).`,
@@ -414,7 +465,7 @@ export const KO_STAGES = {
       `IT IS THE SHORTER DIGEST ABOVE THE PER-MARK ASSESSMENTS, not a rival to them. A reader opens this`,
       `to decide which name to read about; the mark's own page is where the full read lives. Keep it`,
       `tighter than any one mark's assessment.`,
-      // ── THE RETURN IS A CALL, NOT A FILE (, item B) ────────────────────────────
+      // ── THE RETURN IS A CALL, NOT A FILE (item B) ────────────────────────────
       //
       // THE DISPATCH NAMES NO PATH, and on this stage that is not merely the house pattern. This seat
       // spent 2026-08 writing its chunk through a Bash redirect because the Write tool was already