docs(knowledge): the judgment axis is knowledge, not a detector (B2)

Article rule 1 ("give Claude judgement instead of rules") gets its register
entry, and deliberately no detector. `BP-JUDG-001` carries `lensCheck: null`.

The cut between deterministic prefilter and prose judge was the open design
decision. It was settled by measurement, and the measurement declined both
halves:

- 409 real CLAUDE.md files (38488 lines, 8689 prose blocks): the caging class
  fires 7 times, and all 7 are false positives ("rendered prose-side",
  "naming is a flag on the class"). Verified along an independent grep path
  that bypasses block-splitting and sentence-splitting entirely, in both word
  orders: 5 lines and 1 line, none an instruction.
- The narrow variant (absolute + form noun + numeric cap) fired 8 times —
  one duplicated block seen seven times across plugin caches, precision 0 %.
  The pre-committed rule required 90 % over 20 distinct fires.
- Where the shape does occur — 45 lines across 4755 skill/agent/command files
  — it is the author's editorial policy (emoji, sentence length, slide
  titles). Nothing in the text separates that from a vendor's over-tight
  guardrail, and the article's reasoning does not transfer: the model is not
  the author of a user's config.

So no CA-OPT-002; finding-codes keeps OPT next-free = 2. The numbers live in
the entry's own `note`, so the next session does not re-derive the question.

Two premises the chunk falsified. The brief justified a separate axis by
saying these blocks sit inside `floor-exclusion`'s floor — but the article's
own canonical line carries no floor marker at all, so "inside the floor"
cannot define the axis (the corpus tendency is 76 %, which is a tendency, not
a mechanism). And the fasit's own form-noun vocabulary was wrong: `name` and
`format` alone drove 97 % of fires.

Not folded into `--subtract`: a third "loosen instead of delete" verdict in
the subtraction judge is the AS#5 mixing STATE forbids, and with the corrected
vocabulary there are 0 collisions to arbitrate anyway.

Guards, both seen red against their own defect first: the entry must exist,
be confirmed, date its source and name NO lensCheck; and every lensCheck in
the register must be backed by a real detector.

No behaviour changed — no new finding, no output change, nothing consumes the
entry yet — hence `docs`, not `feat`. Suite 1701 -> 1703/0; frozen v5.0.0 and
default-output baselines 0 changed files. Fasit:
docs/b2-judgment-lens-fasit.local.md

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017mCkx9wGywqNQzsXkBMzJ1

docs/v5.13-model-routing-effort-deadref-plan.md

@@ -46,12 +46,19 @@ scanner *input*, so the axes compose instead of competing.
   **Deviation from brief, verified 2026-08-03:** the article contains NO mechanism-choice or
   size-limit content → it was NOT added to BP-MECH-*/BP-SIZE-001 (that would be false
   provenance). If a future read finds real coverage, add it then.
-- **B2 — new lens axis (own chunk):** `BP-JUDG-001` + `CA-OPT-002` for instructions that are
-  local and specific but **over-specify and cage judgment** (article rule 1). NOT an extension
-  of `--subtract` — the floor (`floor-exclusion.mjs`) rightly protects these blocks from
-  deletion; this axis says *keep the content, loosen the phrasing*. Same precision gate as
-  `optimization-lens-agent` (cite rule + source, stay silent when unsure). Mixing the axes is
-  the ÅS#5 defect class.
+- **B2 — DONE, and the detector was DECLINED by measurement.** `BP-JUDG-001` ships as
+  register knowledge with `lensCheck: null`; **no `CA-OPT-002`** (OPT next-free stays 2).
+  Measured over **409 real CLAUDE.md files** (38 488 lines, 8 689 prose blocks): the caging
+  class fires **7 times, all 7 false positives**, confirmed along an independent grep path in
+  both word orders (5 lines / 1 line, none an instruction). Where the shape *does* occur — 45
+  lines across 4 755 skill/agent/command files — it is the author's **editorial policy** (emoji,
+  sentence length, slide titles), and nothing in the text separates that from a vendor's
+  over-tight guardrail: the article's reasoning does not transfer, because the model is not the
+  author of a user's config. Precision-first ⇒ silence. Two premises the chunk falsified: the
+  brief's «these blocks are inside the floor» (the article's own example carries **no** floor
+  marker; the corpus tendency is 76 %, which is not a mechanism), and the §4 form-noun
+  vocabulary (`name`/`format` alone were 97 % of fires). Full record:
+  `docs/b2-judgment-lens-fasit.local.md` §9.
 - **B3 — two-layer duplication/contradiction (CNF extension):** article rule 4 + `/doctor`'s
   measured Sjekk 2 catch (global CLAUDE.md model-policy ↔ agent frontmatter) prove the class
   exists and is catchable. Extend `conflict-detector` with cross-layer checks where the pair is
@@ -201,8 +208,11 @@ Check 3) and fails the binding `/doctor` positioning; and regenerating destroys
 - **C1–C5:** criteria as specified 2026-07-14 (C2 red-first nearest-match; C3 fixture
   missing-path fires / URL-glob-placeholder silent; C4 authored-agent matrix; C5 failure-modes
   section present).
-- **B2:** fixture with a precise-but-caging instruction → CA-OPT-002 with rule+source citation;
-  floor-protected block WITHOUT caging phrasing → silent (axis separation proven).
+- **B2 (superseded by the measurement above):** the criterion was written for a detector that
+  measurement declined. What was verified instead: `BP-JUDG-001` present, `confirmed`, primary
+  source dated `2026-07-24`, `lensCheck` **absent** — plus a guard that every `lensCheck` in the
+  register is backed by a real detector, so no later session can "complete" the entry by wiring
+  one. Both assertions seen RED against their own defect before landing.
 - **B3:** fixture with same instruction in CLAUDE.md + rule → CNF finding; single-layer only →
   silent ([[guard-can-be-green-on-its-own-defect]]: assert the blanket invariant).