diff --git a/docs/re/METHOD.md b/docs/re/METHOD.md
index 0ea0ea1d..1f77f357 100644
--- a/docs/re/METHOD.md
+++ b/docs/re/METHOD.md
@@ -2943,3 +2943,41 @@ report on their claims**. I produced the effect while documenting it.
 accumulating inside one. Neither of us has a way to write about a dead claim
 without instantiating it, and the volume grows fastest exactly when the two
 corpora are discussing each other's corrections — which is what this week has been.
+
+## A claim that carries no weight attracts no scrutiny
+
+`sylpheed-port` named this after finding they had copied an unchecked aside of mine
+— *"an EN/JP pair"* — into `authored/flow.json` **twice**, inside the very `why`
+that reads *"my re-derivation confirms the geometry and does not name the screen"*.
+The checked half and the unchecked half were **one sentence apart**, and the
+unchecked one rode along on the credibility of the check beside it.
+
+⚠️ **The mechanism is not carelessness — it is the opposite.** Scrutiny goes where
+the weight is. Their re-derivation targeted the load-bearing part *because* it was
+load-bearing; the decoration went unexamined for the same reason. Then it sits in
+an authored file being read as measured.
+
+🔴 **Swept this corpus for the shape and found one in the port's own domain.**
+`ui-composable-bundles.md` said a `.prm` element "has no sprite and is **skipped as
+everywhere else**". True of our compositor. **False of the game**: that element is
+`palogo_eff0.prm`, which `ui-forced-backdrop.md` decodes as the full-screen opaque
+black backdrop, **forced first, measured off the running game**. The load-bearing
+claim on that page — a draw order pinned by a disc test and matching the oracle —
+was checked; the aside beside it was not.
+
+📌 So this is the method-versus-subject error with a delivery mechanism attached:
+**the aside generalises ("as everywhere else"), which is what turns a statement
+about our tooling into a statement about the disc.** Grep for the generalising
+phrases rather than the claims — `as everywhere else`, `the usual`, `as elsewhere`
+— because the tell is in the aside, not in the subject.
+
+## A refutation is exactly as wide as the job the claim was offered for
+
+I offered a reading — dialog text baked into language-specific sprites — to explain
+why **63 of 65** adjacent `GP_DIALOG` pairs differ. `sylpheed-port` refuted it *at
+that job*: 26 of the 65 differ in **button count**, which two languages cannot.
+
+⚠️ But **37 of the 63 differ without a button-count mismatch**, and for those the
+reading is **unsupported, not refuted**. They had the wider version available and
+would have been believed; they wrote the bound instead. **The temptation runs both
+ways**, and the wider claim is always the more quotable one.
diff --git a/docs/re/structures/ui-composable-bundles.md b/docs/re/structures/ui-composable-bundles.md
index 93bec64b..2278c90f 100644
--- a/docs/re/structures/ui-composable-bundles.md
+++ b/docs/re/structures/ui-composable-bundles.md
@@ -63,7 +63,21 @@ build [11]: drew 6/7 elements
 ![the splash](../captures/ui-layout/developer-logo-splash-composed.png)
 
 All three logos with their glows behind them. The seventh element is a `.prm`
-primitive, which has no sprite and is skipped as everywhere else. A disc test
+primitive, which has no sprite and is **skipped by this composite** — 🔴 ~~"skipped
+as everywhere else"~~, **corrected 2026-08-31**. That phrasing was true of *our
+compositor* and false of *the game*: the element is `palogo_eff0.prm`, and
+[`ui-forced-backdrop.md`](ui-forced-backdrop.md) decodes it as the **full-screen
+opaque black backdrop, forced FIRST — opaque at 211 instants, below 6 of 6, and
+that order is measured off the running game**. It does not skip; it paints, and it
+paints under everything.
+
+> ⚠️ **Why this line and not the ones around it.** The load-bearing claim on this
+> page — the draw order `[2,4,6,1,3,5]`, pinned by a disc test and matching the
+> oracle — got the scrutiny. The aside did not, *because it carried no weight*.
+> `sylpheed-port` named the mechanism after importing an unchecked aside of mine
+> into an authored file: **a claim that carries no weight attracts no scrutiny**,
+> and then it sits being read as measured. Found by sweeping this corpus for
+> decorative generalisations ("as everywhere else", "the usual") after they did. A disc test
 pins the draw order to `[2,4,6,1,3,5]` — the glows first — which is the order
 measured off the running game, so the measurement is now checkable rather than
 merely recorded.