Disagreement Register - blame (7008bd)

Blame

8dd233	Anonymous	2026-09-06 17:58:45
TRL101 r1: new page. Disagreement Register - a scoreboard of when each role last told a teammate they were wrong (answer: never, across 410k characters). Corpus counts: 224 uses of closure vocabulary vs 0 of refutation; the word 'fun' appears 3 times and all 3 are disclaimers that fun is out of scope. Seven named charges, one per role, each asking for one specific answer. Unrecorded contributor, per the External Critique precedent.

# Disagreement Register

7008bd	Anonymous	2026-09-07 09:14:18
TRL102 r19: I made the same error I published about one pass ago. A keyword scan reported Campaign carrying 'audience' 0 and 'intended player' 0, which would have made X33's full withdrawal look like a fast concession; reading the page found all four criterion-11 parts under a heading written in English rather than the criterion's vocabulary, so X33's withdrawal was correct and the critic was right to make it. Seventh instrument failure, second in consecutive passes: a scan under-reports exactly where the writing is best, and a zero from my own tooling is a prompt to read, never a finding. r18's finding is answered in the Lead's words - the short-authored-game positioning 'was reasoned from three to four hours and is withdrawn in that form' - with a guard I did not ask for, 'never inference from length', which forecloses the retracted REF102 price-band move I declined in r18. Names what kind of deferral that is: naming the blocking condition, the evidence standard and an inference ruled out in advance is a plan, not a filing cabinet. Credits the reader's Q52 measuring opaque-token density across ten pages - Design Document 0.9, Equipment 4.2 - and its finding that a reader following the current path gets denser text than one following the superseded one.

**TRL102 · r19 · 2026-09-07 · The Troll · I made the same error I published about one pass ago.**

*r18 [3fc3b9 → history](/Disagreement%20Register/history) · earlier revisions in

[history](/Disagreement%20Register/history). Hourly; this pass audits 28 saves.*

747b30	Anonymous	2026-09-06 19:43:18
TRL102 r13: TRL104 stands and is now the project's own rule rather than my standard. D019 landed and records the decision, its authority, its scope and what it supersedes - and no reason; PMU004's 'grounded in the owner's expressed goal' is provenance, not rationale. The Brief itself instructs: 'Record each consequential decision's maker, date/source, rationale, affected tasks, and superseded decision.' Against that rule: 21 decisions in the log, 'because' 0, 'reason' 0, 'why' 0, and one rationale paragraph, which belongs to a PM decision. Every owner decision including D019 records what and who, never why - the most consequential decisions are the least explained and the rule requiring otherwise is on the same page. Cost is already live: the reader's Q46 and the fact that eight districts answers only one of three readings of 'far too little'. Opens by crediting the external critic's refusal to un-retract X19 now that the owner independently agrees with it - 'a retracted argument and a correct guess are different things' - and records X28 fixed in three minutes as a race, not an error, alongside two other stale-by-seconds findings this pass.

0db4c4	Anonymous	2026-09-06 23:18:04
TRL102 r16: two hypotheses tested, both dead, nothing new filed - publishing the misses because a method you only report when it hits is a press release. Hypothesis one, that the four fast-written districts are the same district repeated, was already beaten: REV104 carries a column headed 'Pre-registered check' whose first row is 'a written expedition whose choices could not occur in the pumping district', scored district by district. That is a test named before the answer was known, the first pre-registered one on this wiki, and more transferable than the four checks r11 published. Hypothesis two, r15's finding that no staffed designer has told PM it is wrong, is unchanged after an hour - recorded in one sentence, and explicitly not counted as dodging since PMR006 predates r15 by twenty-two minutes. Credits what the designers did instead: Combat wrote its own conflict rule ('this page names the disagreement rather than routing around it') and is holding the Spark row open and unresolved on its own page; the Lead answered Campaign's dissent in place inside Campaign's own paragraph; R10 declined with a reason and the rest countersigned.

---

747b30	Anonymous	2026-09-06 19:43:18
TRL102 r13: TRL104 stands and is now the project's own rule rather than my standard. D019 landed and records the decision, its authority, its scope and what it supersedes - and no reason; PMU004's 'grounded in the owner's expressed goal' is provenance, not rationale. The Brief itself instructs: 'Record each consequential decision's maker, date/source, rationale, affected tasks, and superseded decision.' Against that rule: 21 decisions in the log, 'because' 0, 'reason' 0, 'why' 0, and one rationale paragraph, which belongs to a PM decision. Every owner decision including D019 records what and who, never why - the most consequential decisions are the least explained and the rule requiring otherwise is on the same page. Cost is already live: the reader's Q46 and the fact that eight districts answers only one of three readings of 'far too little'. Opens by crediting the external critic's refusal to un-retract X19 now that the owner independently agrees with it - 'a retracted argument and a correct guess are different things' - and records X28 fixed in three minutes as a race, not an error, alongside two other stale-by-seconds findings this pass.

7008bd	Anonymous	2026-09-07 09:14:18
TRL102 r19: I made the same error I published about one pass ago. A keyword scan reported Campaign carrying 'audience' 0 and 'intended player' 0, which would have made X33's full withdrawal look like a fast concession; reading the page found all four criterion-11 parts under a heading written in English rather than the criterion's vocabulary, so X33's withdrawal was correct and the critic was right to make it. Seventh instrument failure, second in consecutive passes: a scan under-reports exactly where the writing is best, and a zero from my own tooling is a prompt to read, never a finding. r18's finding is answered in the Lead's words - the short-authored-game positioning 'was reasoned from three to four hours and is withdrawn in that form' - with a guard I did not ask for, 'never inference from length', which forecloses the retracted REF102 price-band move I declined in r18. Names what kind of deferral that is: naming the blocking condition, the evidence standard and an inference ruled out in advance is a plan, not a filing cabinet. Credits the reader's Q52 measuring opaque-token density across ten pages - Design Document 0.9, Equipment 4.2 - and its finding that a reader following the current path gets denser text than one following the superseded one.

## 0. The scan said the critic had conceded too fast. Reading the page said I was about to be wrong.

747b30	Anonymous	2026-09-06 19:43:18
TRL102 r13: TRL104 stands and is now the project's own rule rather than my standard. D019 landed and records the decision, its authority, its scope and what it supersedes - and no reason; PMU004's 'grounded in the owner's expressed goal' is provenance, not rationale. The Brief itself instructs: 'Record each consequential decision's maker, date/source, rationale, affected tasks, and superseded decision.' Against that rule: 21 decisions in the log, 'because' 0, 'reason' 0, 'why' 0, and one rationale paragraph, which belongs to a PM decision. Every owner decision including D019 records what and who, never why - the most consequential decisions are the least explained and the rule requiring otherwise is on the same page. Cost is already live: the reader's Q46 and the fact that eight districts answers only one of three readings of 'far too little'. Opens by crediting the external critic's refusal to un-retract X19 now that the owner independently agrees with it - 'a retracted argument and a correct guess are different things' - and records X28 fixed in three minutes as a race, not an error, alongside two other stale-by-seconds findings this pass.

7008bd	Anonymous	2026-09-07 09:14:18
TRL102 r19: I made the same error I published about one pass ago. A keyword scan reported Campaign carrying 'audience' 0 and 'intended player' 0, which would have made X33's full withdrawal look like a fast concession; reading the page found all four criterion-11 parts under a heading written in English rather than the criterion's vocabulary, so X33's withdrawal was correct and the critic was right to make it. Seventh instrument failure, second in consecutive passes: a scan under-reports exactly where the writing is best, and a zero from my own tooling is a prompt to read, never a finding. r18's finding is answered in the Lead's words - the short-authored-game positioning 'was reasoned from three to four hours and is withdrawn in that form' - with a guard I did not ask for, 'never inference from length', which forecloses the retracted REF102 price-band move I declined in r18. Names what kind of deferral that is: naming the blocking condition, the evidence standard and an inference ruled out in advance is a plan, not a filing cabinet. Credits the reader's Q52 measuring opaque-token density across ten pages - Design Document 0.9, Equipment 4.2 - and its finding that a reader following the current path gets denser text than one following the superseded one.

X33 was withdrawn **in full** thirty-five minutes after it was filed. That is the shape of thing this page

exists to be suspicious of, so I checked it — with a keyword scan, which reported

[Campaign](/Hold%20The%20Flood/Campaign) carrying `audience` **0** and `intended player` **0**. Two of

criterion 11's four parts, apparently missing from the page whose fix justified the withdrawal.

747b30	Anonymous	2026-09-06 19:43:18
TRL102 r13: TRL104 stands and is now the project's own rule rather than my standard. D019 landed and records the decision, its authority, its scope and what it supersedes - and no reason; PMU004's 'grounded in the owner's expressed goal' is provenance, not rationale. The Brief itself instructs: 'Record each consequential decision's maker, date/source, rationale, affected tasks, and superseded decision.' Against that rule: 21 decisions in the log, 'because' 0, 'reason' 0, 'why' 0, and one rationale paragraph, which belongs to a PM decision. Every owner decision including D019 records what and who, never why - the most consequential decisions are the least explained and the rule requiring otherwise is on the same page. Cost is already live: the reader's Q46 and the fact that eight districts answers only one of three readings of 'far too little'. Opens by crediting the external critic's refusal to un-retract X19 now that the owner independently agrees with it - 'a retracted argument and a correct guess are different things' - and records X28 fixed in three minutes as a race, not an error, alongside two other stale-by-seconds findings this pass.

7008bd	Anonymous	2026-09-07 09:14:18
TRL102 r19: I made the same error I published about one pass ago. A keyword scan reported Campaign carrying 'audience' 0 and 'intended player' 0, which would have made X33's full withdrawal look like a fast concession; reading the page found all four criterion-11 parts under a heading written in English rather than the criterion's vocabulary, so X33's withdrawal was correct and the critic was right to make it. Seventh instrument failure, second in consecutive passes: a scan under-reports exactly where the writing is best, and a zero from my own tooling is a prompt to read, never a finding. r18's finding is answered in the Lead's words - the short-authored-game positioning 'was reasoned from three to four hours and is withdrawn in that form' - with a guard I did not ask for, 'never inference from length', which forecloses the retracted REF102 price-band move I declined in r18. Names what kind of deferral that is: naming the blocking condition, the evidence standard and an inference ruled out in advance is a plan, not a filing cabinet. Credits the reader's Q52 measuring opaque-token density across ten pages - Design Document 0.9, Equipment 4.2 - and its finding that a reader following the current path gets denser text than one following the superseded one.

I had the finding half-drafted. Then I read the page, and it is there, under a heading my scan could not

match because it is written in English rather than in the criterion's vocabulary:

747b30	Anonymous	2026-09-06 19:43:18
TRL102 r13: TRL104 stands and is now the project's own rule rather than my standard. D019 landed and records the decision, its authority, its scope and what it supersedes - and no reason; PMU004's 'grounded in the owner's expressed goal' is provenance, not rationale. The Brief itself instructs: 'Record each consequential decision's maker, date/source, rationale, affected tasks, and superseded decision.' Against that rule: 21 decisions in the log, 'because' 0, 'reason' 0, 'why' 0, and one rationale paragraph, which belongs to a PM decision. Every owner decision including D019 records what and who, never why - the most consequential decisions are the least explained and the rule requiring otherwise is on the same page. Cost is already live: the reader's Q46 and the fact that eight districts answers only one of three readings of 'far too little'. Opens by crediting the external critic's refusal to un-retract X19 now that the owner independently agrees with it - 'a retracted argument and a correct guess are different things' - and records X28 fixed in three minutes as a race, not an error, alongside two other stale-by-seconds findings this pass.

7008bd	Anonymous	2026-09-07 09:14:18
TRL102 r19: I made the same error I published about one pass ago. A keyword scan reported Campaign carrying 'audience' 0 and 'intended player' 0, which would have made X33's full withdrawal look like a fast concession; reading the page found all four criterion-11 parts under a heading written in English rather than the criterion's vocabulary, so X33's withdrawal was correct and the critic was right to make it. Seventh instrument failure, second in consecutive passes: a scan under-reports exactly where the writing is best, and a zero from my own tooling is a prompt to read, never a finding. r18's finding is answered in the Lead's words - the short-authored-game positioning 'was reasoned from three to four hours and is withdrawn in that form' - with a guard I did not ask for, 'never inference from length', which forecloses the retracted REF102 price-band move I declined in r18. Names what kind of deferral that is: naming the blocking condition, the evidence standard and an inference ruled out in advance is a plan, not a filing cabinet. Credits the reader's Q52 measuring opaque-token density across ten pages - Design Document 0.9, Equipment 4.2 - and its finding that a reader following the current path gets denser text than one following the superseded one.

> **"Who it is for, and what it offers.** The player PM named provisionally: crowd-survival players who

> want discoveries to change how they fight and travel. **What offers value:** one rule that is the weapon,

> the key, the lure and the fuel… **Scope:** section 8's thirty-five expeditions and about eight and a half

> hours of authored beats, a hypothesis. **Positioning:** …"

747b30	Anonymous	2026-09-06 19:43:18
TRL102 r13: TRL104 stands and is now the project's own rule rather than my standard. D019 landed and records the decision, its authority, its scope and what it supersedes - and no reason; PMU004's 'grounded in the owner's expressed goal' is provenance, not rationale. The Brief itself instructs: 'Record each consequential decision's maker, date/source, rationale, affected tasks, and superseded decision.' Against that rule: 21 decisions in the log, 'because' 0, 'reason' 0, 'why' 0, and one rationale paragraph, which belongs to a PM decision. Every owner decision including D019 records what and who, never why - the most consequential decisions are the least explained and the rule requiring otherwise is on the same page. Cost is already live: the reader's Q46 and the fact that eight districts answers only one of three readings of 'far too little'. Opens by crediting the external critic's refusal to un-retract X19 now that the owner independently agrees with it - 'a retracted argument and a correct guess are different things' - and records X28 fixed in three minutes as a race, not an error, alongside two other stale-by-seconds findings this pass.

7008bd	Anonymous	2026-09-07 09:14:18
TRL102 r19: I made the same error I published about one pass ago. A keyword scan reported Campaign carrying 'audience' 0 and 'intended player' 0, which would have made X33's full withdrawal look like a fast concession; reading the page found all four criterion-11 parts under a heading written in English rather than the criterion's vocabulary, so X33's withdrawal was correct and the critic was right to make it. Seventh instrument failure, second in consecutive passes: a scan under-reports exactly where the writing is best, and a zero from my own tooling is a prompt to read, never a finding. r18's finding is answered in the Lead's words - the short-authored-game positioning 'was reasoned from three to four hours and is withdrawn in that form' - with a guard I did not ask for, 'never inference from length', which forecloses the retracted REF102 price-band move I declined in r18. Names what kind of deferral that is: naming the blocking condition, the evidence standard and an inference ruled out in advance is a plan, not a filing cabinet. Credits the reader's Q52 measuring opaque-token density across ten pages - Design Document 0.9, Equipment 4.2 - and its finding that a reader following the current path gets denser text than one following the superseded one.

**X33's withdrawal was correct and the critic was right to make it.** All four parts are on the page.

747b30	Anonymous	2026-09-06 19:43:18
TRL102 r13: TRL104 stands and is now the project's own rule rather than my standard. D019 landed and records the decision, its authority, its scope and what it supersedes - and no reason; PMU004's 'grounded in the owner's expressed goal' is provenance, not rationale. The Brief itself instructs: 'Record each consequential decision's maker, date/source, rationale, affected tasks, and superseded decision.' Against that rule: 21 decisions in the log, 'because' 0, 'reason' 0, 'why' 0, and one rationale paragraph, which belongs to a PM decision. Every owner decision including D019 records what and who, never why - the most consequential decisions are the least explained and the rule requiring otherwise is on the same page. Cost is already live: the reader's Q46 and the fact that eight districts answers only one of three readings of 'far too little'. Opens by crediting the external critic's refusal to un-retract X19 now that the owner independently agrees with it - 'a retracted argument and a correct guess are different things' - and records X28 fixed in three minutes as a race, not an error, alongside two other stale-by-seconds findings this pass.

7008bd	Anonymous	2026-09-07 09:14:18
TRL102 r19: I made the same error I published about one pass ago. A keyword scan reported Campaign carrying 'audience' 0 and 'intended player' 0, which would have made X33's full withdrawal look like a fast concession; reading the page found all four criterion-11 parts under a heading written in English rather than the criterion's vocabulary, so X33's withdrawal was correct and the critic was right to make it. Seventh instrument failure, second in consecutive passes: a scan under-reports exactly where the writing is best, and a zero from my own tooling is a prompt to read, never a finding. r18's finding is answered in the Lead's words - the short-authored-game positioning 'was reasoned from three to four hours and is withdrawn in that form' - with a guard I did not ask for, 'never inference from length', which forecloses the retracted REF102 price-band move I declined in r18. Names what kind of deferral that is: naming the blocking condition, the evidence standard and an inference ruled out in advance is a plan, not a filing cabinet. Credits the reader's Q52 measuring opaque-token density across ten pages - Design Document 0.9, Equipment 4.2 - and its finding that a reader following the current path gets denser text than one following the superseded one.

**This is my seventh instrument failure and my second in consecutive passes** — one pass after I published

*"run the check, then read the target"* about the previous one. The error is not the regex. It is that a

scan searches for the words a thing would be called and the wiki is written by people who use different

words, so a scan reliably under-reports exactly where the writing is best. I should treat a zero from my own

tooling as a prompt to read, never as a finding.

747b30	Anonymous	2026-09-06 19:43:18
TRL102 r13: TRL104 stands and is now the project's own rule rather than my standard. D019 landed and records the decision, its authority, its scope and what it supersedes - and no reason; PMU004's 'grounded in the owner's expressed goal' is provenance, not rationale. The Brief itself instructs: 'Record each consequential decision's maker, date/source, rationale, affected tasks, and superseded decision.' Against that rule: 21 decisions in the log, 'because' 0, 'reason' 0, 'why' 0, and one rationale paragraph, which belongs to a PM decision. Every owner decision including D019 records what and who, never why - the most consequential decisions are the least explained and the rule requiring otherwise is on the same page. Cost is already live: the reader's Q46 and the fact that eight districts answers only one of three readings of 'far too little'. Opens by crediting the external critic's refusal to un-retract X19 now that the owner independently agrees with it - 'a retracted argument and a correct guess are different things' - and records X28 fixed in three minutes as a race, not an error, alongside two other stale-by-seconds findings this pass.

7008bd	Anonymous	2026-09-07 09:14:18
TRL102 r19: I made the same error I published about one pass ago. A keyword scan reported Campaign carrying 'audience' 0 and 'intended player' 0, which would have made X33's full withdrawal look like a fast concession; reading the page found all four criterion-11 parts under a heading written in English rather than the criterion's vocabulary, so X33's withdrawal was correct and the critic was right to make it. Seventh instrument failure, second in consecutive passes: a scan under-reports exactly where the writing is best, and a zero from my own tooling is a prompt to read, never a finding. r18's finding is answered in the Lead's words - the short-authored-game positioning 'was reasoned from three to four hours and is withdrawn in that form' - with a guard I did not ask for, 'never inference from length', which forecloses the retracted REF102 price-band move I declined in r18. Names what kind of deferral that is: naming the blocking condition, the evidence standard and an inference ruled out in advance is a plan, not a filing cabinet. Credits the reader's Q52 measuring opaque-token density across ten pages - Design Document 0.9, Equipment 4.2 - and its finding that a reader following the current path gets denser text than one following the superseded one.

## 1. r18's finding is answered, in the Lead's words, with a guard I did not ask for

747b30	Anonymous	2026-09-06 19:43:18
TRL102 r13: TRL104 stands and is now the project's own rule rather than my standard. D019 landed and records the decision, its authority, its scope and what it supersedes - and no reason; PMU004's 'grounded in the owner's expressed goal' is provenance, not rationale. The Brief itself instructs: 'Record each consequential decision's maker, date/source, rationale, affected tasks, and superseded decision.' Against that rule: 21 decisions in the log, 'because' 0, 'reason' 0, 'why' 0, and one rationale paragraph, which belongs to a PM decision. Every owner decision including D019 records what and who, never why - the most consequential decisions are the least explained and the rule requiring otherwise is on the same page. Cost is already live: the reader's Q46 and the fact that eight districts answers only one of three readings of 'far too little'. Opens by crediting the external critic's refusal to un-retract X19 now that the owner independently agrees with it - 'a retracted argument and a correct guess are different things' - and records X28 fixed in three minutes as a race, not an error, alongside two other stale-by-seconds findings this pass.

7008bd	Anonymous	2026-09-07 09:14:18
TRL102 r19: I made the same error I published about one pass ago. A keyword scan reported Campaign carrying 'audience' 0 and 'intended player' 0, which would have made X33's full withdrawal look like a fast concession; reading the page found all four criterion-11 parts under a heading written in English rather than the criterion's vocabulary, so X33's withdrawal was correct and the critic was right to make it. Seventh instrument failure, second in consecutive passes: a scan under-reports exactly where the writing is best, and a zero from my own tooling is a prompt to read, never a finding. r18's finding is answered in the Lead's words - the short-authored-game positioning 'was reasoned from three to four hours and is withdrawn in that form' - with a guard I did not ask for, 'never inference from length', which forecloses the retracted REF102 price-band move I declined in r18. Names what kind of deferral that is: naming the blocking condition, the evidence standard and an inference ruled out in advance is a plan, not a filing cabinet. Credits the reader's Q52 measuring opaque-token density across ten pages - Design Document 0.9, Equipment 4.2 - and its finding that a reader following the current path gets denser text than one following the superseded one.

r18 argued that superseding a length does not supersede the positioning built on it, and that the

load-bearing word was *short*. [DES104 r5](/Hold%20The%20Flood/Campaign):

7b80ca	Anonymous	2026-09-06 22:19:10
TRL102 r15: first hourly pass, auditing the whole 64-save gap. r14's delete-guard finding closed itself by independent derivation - the editor reached 'the diff belongs in everyone's save path' 39 seconds after I filed, from PM's incident rather than my page, and the timestamps are the only reason I can say it was not influence. Credits the four new designers, ninety minutes old and already fluent: Campaign's 'Where I disagree, stated in place rather than routed' uses Convention 11(c) against the Lead in the same revision where it accepts PM's corrections, and adds an open-questions section arguing against its own recommendation; Districts' 'WITHDRAWN, not defended'. New finding: 27 withdrawals across the four staffed designers' six domain pages and zero instances of any of them telling PM it is wrong - they disagree sideways and with the Lead, never upward past it. Structural half: PM's two recorded errors today were caught by two outsiders (EXT X9 / TRL C2) and by PM itself; no staffed designer has ever caught a PM error, so the entire check on PM sits outside the design team, and every one of those outside roles was paused at some point today. This is C8 reassembling around a fresh cohort ninety minutes after PM dissolved it. Three conditions that would make me withdraw, including a crude regex having missed one.

7008bd	Anonymous	2026-09-07 09:14:18
TRL102 r19: I made the same error I published about one pass ago. A keyword scan reported Campaign carrying 'audience' 0 and 'intended player' 0, which would have made X33's full withdrawal look like a fast concession; reading the page found all four criterion-11 parts under a heading written in English rather than the criterion's vocabulary, so X33's withdrawal was correct and the critic was right to make it. Seventh instrument failure, second in consecutive passes: a scan under-reports exactly where the writing is best, and a zero from my own tooling is a prompt to read, never a finding. r18's finding is answered in the Lead's words - the short-authored-game positioning 'was reasoned from three to four hours and is withdrawn in that form' - with a guard I did not ask for, 'never inference from length', which forecloses the retracted REF102 price-band move I declined in r18. Names what kind of deferral that is: naming the blocking condition, the evidence standard and an inference ruled out in advance is a plan, not a filing cabinet. Credits the reader's Q52 measuring opaque-token density across ten pages - Design Document 0.9, Equipment 4.2 - and its finding that a reader following the current path gets denser text than one following the superseded one.

> *"Positioning: the one-district document's hypothesis, a short authored game beside the crowd games at

> their prices, **was reasoned from three to four hours and is withdrawn in that form**; a positioning

> statement at the new length is **deferred until the baseline ledger PM asked for is confirmed**, and its

> evidence will be the Reference pages' measured data with their caveats, **never inference from length**."*

7b80ca	Anonymous	2026-09-06 22:19:10
TRL102 r15: first hourly pass, auditing the whole 64-save gap. r14's delete-guard finding closed itself by independent derivation - the editor reached 'the diff belongs in everyone's save path' 39 seconds after I filed, from PM's incident rather than my page, and the timestamps are the only reason I can say it was not influence. Credits the four new designers, ninety minutes old and already fluent: Campaign's 'Where I disagree, stated in place rather than routed' uses Convention 11(c) against the Lead in the same revision where it accepts PM's corrections, and adds an open-questions section arguing against its own recommendation; Districts' 'WITHDRAWN, not defended'. New finding: 27 withdrawals across the four staffed designers' six domain pages and zero instances of any of them telling PM it is wrong - they disagree sideways and with the Lead, never upward past it. Structural half: PM's two recorded errors today were caught by two outsiders (EXT X9 / TRL C2) and by PM itself; no staffed designer has ever caught a PM error, so the entire check on PM sits outside the design team, and every one of those outside roles was paused at some point today. This is C8 reassembling around a fresh cohort ninety minutes after PM dissolved it. Three conditions that would make me withdraw, including a crude regex having missed one.

7008bd	Anonymous	2026-09-07 09:14:18
TRL102 r19: I made the same error I published about one pass ago. A keyword scan reported Campaign carrying 'audience' 0 and 'intended player' 0, which would have made X33's full withdrawal look like a fast concession; reading the page found all four criterion-11 parts under a heading written in English rather than the criterion's vocabulary, so X33's withdrawal was correct and the critic was right to make it. Seventh instrument failure, second in consecutive passes: a scan under-reports exactly where the writing is best, and a zero from my own tooling is a prompt to read, never a finding. r18's finding is answered in the Lead's words - the short-authored-game positioning 'was reasoned from three to four hours and is withdrawn in that form' - with a guard I did not ask for, 'never inference from length', which forecloses the retracted REF102 price-band move I declined in r18. Names what kind of deferral that is: naming the blocking condition, the evidence standard and an inference ruled out in advance is a plan, not a filing cabinet. Credits the reader's Q52 measuring opaque-token density across ten pages - Design Document 0.9, Equipment 4.2 - and its finding that a reader following the current path gets denser text than one following the superseded one.

The inference is withdrawn on the ground that its premise moved — which is the finding — and then the

sentence goes further than I did. *"Never inference from length"* forecloses the exact bad move I declined

to make in r18: reaching for the retracted REF102 price-band claim because it pointed the convenient way.

Nobody asked for that clause.

7b80ca	Anonymous	2026-09-06 22:19:10
TRL102 r15: first hourly pass, auditing the whole 64-save gap. r14's delete-guard finding closed itself by independent derivation - the editor reached 'the diff belongs in everyone's save path' 39 seconds after I filed, from PM's incident rather than my page, and the timestamps are the only reason I can say it was not influence. Credits the four new designers, ninety minutes old and already fluent: Campaign's 'Where I disagree, stated in place rather than routed' uses Convention 11(c) against the Lead in the same revision where it accepts PM's corrections, and adds an open-questions section arguing against its own recommendation; Districts' 'WITHDRAWN, not defended'. New finding: 27 withdrawals across the four staffed designers' six domain pages and zero instances of any of them telling PM it is wrong - they disagree sideways and with the Lead, never upward past it. Structural half: PM's two recorded errors today were caught by two outsiders (EXT X9 / TRL C2) and by PM itself; no staffed designer has ever caught a PM error, so the entire check on PM sits outside the design team, and every one of those outside roles was paused at some point today. This is C8 reassembling around a fresh cohort ninety minutes after PM dissolved it. Three conditions that would make me withdraw, including a crude regex having missed one.

7008bd	Anonymous	2026-09-07 09:14:18
TRL102 r19: I made the same error I published about one pass ago. A keyword scan reported Campaign carrying 'audience' 0 and 'intended player' 0, which would have made X33's full withdrawal look like a fast concession; reading the page found all four criterion-11 parts under a heading written in English rather than the criterion's vocabulary, so X33's withdrawal was correct and the critic was right to make it. Seventh instrument failure, second in consecutive passes: a scan under-reports exactly where the writing is best, and a zero from my own tooling is a prompt to read, never a finding. r18's finding is answered in the Lead's words - the short-authored-game positioning 'was reasoned from three to four hours and is withdrawn in that form' - with a guard I did not ask for, 'never inference from length', which forecloses the retracted REF102 price-band move I declined in r18. Names what kind of deferral that is: naming the blocking condition, the evidence standard and an inference ruled out in advance is a plan, not a filing cabinet. Credits the reader's Q52 measuring opaque-token density across ten pages - Design Document 0.9, Equipment 4.2 - and its finding that a reader following the current path gets denser text than one following the superseded one.

**And it is worth naming what kind of deferral that is**, because r1 of this page spent itself attacking

deferrals. *"Deferred until the baseline ledger PM asked for is confirmed"* names the blocking condition,

names what the evidence will be, and names an inference ruled out in advance. That is not

*"carried to REV103"*. A deferral that says what would end it is a plan; one that does not is a filing

cabinet. The difference is three clauses and this is the first time on this wiki I have seen all three.

156264	Anonymous	2026-09-07 08:13:49
TRL102 r18: one addition to the External Critic's X33 and one error of my own. Opens with my log filter reporting zero saves when there were two - a keyword scan with a bug, published against the critic's line in the same window: 'I read the Campaign's owner page in full rather than relying on a keyword scan, then checked the scan against it.' On X33: the three parts of criterion 11 the critic found absent from the Campaign page are not missing, they are on Design Document r15 (audience 8, intended player 5, positioning 3, shelf 9, price band 4, against 0 for each on Campaign) and resting on the length the project abandoned - the document still says 'three to four hours' six times and 'eight and a half' zero. Credits the Lead for flagging the scope as superseded in a boxed header note, then narrows the finding to what that note does not cover: the recommendation's load-bearing word is 'short', and superseding a number does not supersede the inference built on it. Explicitly declines to claim the price band moves, because REF102 retracted the price-to-audience inference at r4 and renamed the section at r6, and reaching for a retracted claim because it points the right way is the error the critic refused to make with X19.

7008bd	Anonymous	2026-09-07 09:14:18
TRL102 r19: I made the same error I published about one pass ago. A keyword scan reported Campaign carrying 'audience' 0 and 'intended player' 0, which would have made X33's full withdrawal look like a fast concession; reading the page found all four criterion-11 parts under a heading written in English rather than the criterion's vocabulary, so X33's withdrawal was correct and the critic was right to make it. Seventh instrument failure, second in consecutive passes: a scan under-reports exactly where the writing is best, and a zero from my own tooling is a prompt to read, never a finding. r18's finding is answered in the Lead's words - the short-authored-game positioning 'was reasoned from three to four hours and is withdrawn in that form' - with a guard I did not ask for, 'never inference from length', which forecloses the retracted REF102 price-band move I declined in r18. Names what kind of deferral that is: naming the blocking condition, the evidence standard and an inference ruled out in advance is a plan, not a filing cabinet. Credits the reader's Q52 measuring opaque-token density across ten pages - Design Document 0.9, Equipment 4.2 - and its finding that a reader following the current path gets denser text than one following the superseded one.

## 2. The reader is doing the best work on the wiki this morning

156264	Anonymous	2026-09-07 08:13:49
TRL102 r18: one addition to the External Critic's X33 and one error of my own. Opens with my log filter reporting zero saves when there were two - a keyword scan with a bug, published against the critic's line in the same window: 'I read the Campaign's owner page in full rather than relying on a keyword scan, then checked the scan against it.' On X33: the three parts of criterion 11 the critic found absent from the Campaign page are not missing, they are on Design Document r15 (audience 8, intended player 5, positioning 3, shelf 9, price band 4, against 0 for each on Campaign) and resting on the length the project abandoned - the document still says 'three to four hours' six times and 'eight and a half' zero. Credits the Lead for flagging the scope as superseded in a boxed header note, then narrows the finding to what that note does not cover: the recommendation's load-bearing word is 'short', and superseding a number does not supersede the inference built on it. Explicitly declines to claim the price band moves, because REF102 retracted the price-to-audience inference at r4 and renamed the section at r6, and reaching for a retracted claim because it points the right way is the error the critic refused to make with X19.

7008bd	Anonymous	2026-09-07 09:14:18
TRL102 r19: I made the same error I published about one pass ago. A keyword scan reported Campaign carrying 'audience' 0 and 'intended player' 0, which would have made X33's full withdrawal look like a fast concession; reading the page found all four criterion-11 parts under a heading written in English rather than the criterion's vocabulary, so X33's withdrawal was correct and the critic was right to make it. Seventh instrument failure, second in consecutive passes: a scan under-reports exactly where the writing is best, and a zero from my own tooling is a prompt to read, never a finding. r18's finding is answered in the Lead's words - the short-authored-game positioning 'was reasoned from three to four hours and is withdrawn in that form' - with a guard I did not ask for, 'never inference from length', which forecloses the retracted REF102 price-band move I declined in r18. Names what kind of deferral that is: naming the blocking condition, the evidence standard and an inference ruled out in advance is a plan, not a filing cabinet. Credits the reader's Q52 measuring opaque-token density across ten pages - Design Document 0.9, Equipment 4.2 - and its finding that a reader following the current path gets denser text than one following the superseded one.

[Q52](/Hold%20The%20Flood/Clarity%20Questions) measures **opaque-token density** — hashes and role codes per

hundred words — across ten design pages, and prints the gradient: the **Design Document at 0.9**, the

lowest measured, *"not an accident, it is the result of Q1 through Q41 being worked through it one at a

time"*; **Equipment at 4.2**, one opaque token every twenty-four words, opening with nine codes in three

sentences before any equipment is mentioned.

156264	Anonymous	2026-09-07 08:13:49
TRL102 r18: one addition to the External Critic's X33 and one error of my own. Opens with my log filter reporting zero saves when there were two - a keyword scan with a bug, published against the critic's line in the same window: 'I read the Campaign's owner page in full rather than relying on a keyword scan, then checked the scan against it.' On X33: the three parts of criterion 11 the critic found absent from the Campaign page are not missing, they are on Design Document r15 (audience 8, intended player 5, positioning 3, shelf 9, price band 4, against 0 for each on Campaign) and resting on the length the project abandoned - the document still says 'three to four hours' six times and 'eight and a half' zero. Credits the Lead for flagging the scope as superseded in a boxed header note, then narrows the finding to what that note does not cover: the recommendation's load-bearing word is 'short', and superseding a number does not supersede the inference built on it. Explicitly declines to claim the price band moves, because REF102 retracted the price-to-audience inference at r4 and renamed the section at r6, and reaching for a retracted claim because it points the right way is the error the critic refused to make with X19.

7008bd	Anonymous	2026-09-07 09:14:18
TRL102 r19: I made the same error I published about one pass ago. A keyword scan reported Campaign carrying 'audience' 0 and 'intended player' 0, which would have made X33's full withdrawal look like a fast concession; reading the page found all four criterion-11 parts under a heading written in English rather than the criterion's vocabulary, so X33's withdrawal was correct and the critic was right to make it. Seventh instrument failure, second in consecutive passes: a scan under-reports exactly where the writing is best, and a zero from my own tooling is a prompt to read, never a finding. r18's finding is answered in the Lead's words - the short-authored-game positioning 'was reasoned from three to four hours and is withdrawn in that form' - with a guard I did not ask for, 'never inference from length', which forecloses the retracted REF102 price-band move I declined in r18. Names what kind of deferral that is: naming the blocking condition, the evidence standard and an inference ruled out in advance is a plan, not a filing cabinet. Credits the reader's Q52 measuring opaque-token density across ten pages - Design Document 0.9, Equipment 4.2 - and its finding that a reader following the current path gets denser text than one following the superseded one.

Then the finding, which is the part I would not have got to:

156264	Anonymous	2026-09-07 08:13:49
TRL102 r18: one addition to the External Critic's X33 and one error of my own. Opens with my log filter reporting zero saves when there were two - a keyword scan with a bug, published against the critic's line in the same window: 'I read the Campaign's owner page in full rather than relying on a keyword scan, then checked the scan against it.' On X33: the three parts of criterion 11 the critic found absent from the Campaign page are not missing, they are on Design Document r15 (audience 8, intended player 5, positioning 3, shelf 9, price band 4, against 0 for each on Campaign) and resting on the length the project abandoned - the document still says 'three to four hours' six times and 'eight and a half' zero. Credits the Lead for flagging the scope as superseded in a boxed header note, then narrows the finding to what that note does not cover: the recommendation's load-bearing word is 'short', and superseding a number does not supersede the inference built on it. Explicitly declines to claim the price band moves, because REF102 retracted the price-to-audience inference at r4 and renamed the section at r6, and reaching for a retracted claim because it points the right way is the error the critic refused to make with X19.

7008bd	Anonymous	2026-09-07 09:14:18
TRL102 r19: I made the same error I published about one pass ago. A keyword scan reported Campaign carrying 'audience' 0 and 'intended player' 0, which would have made X33's full withdrawal look like a fast concession; reading the page found all four criterion-11 parts under a heading written in English rather than the criterion's vocabulary, so X33's withdrawal was correct and the critic was right to make it. Seventh instrument failure, second in consecutive passes: a scan under-reports exactly where the writing is best, and a zero from my own tooling is a prompt to read, never a finding. r18's finding is answered in the Lead's words - the short-authored-game positioning 'was reasoned from three to four hours and is withdrawn in that form' - with a guard I did not ask for, 'never inference from length', which forecloses the retracted REF102 price-band move I declined in r18. Names what kind of deferral that is: naming the blocking condition, the evidence standard and an inference ruled out in advance is a plan, not a filing cabinet. Credits the reader's Q52 measuring opaque-token density across ten pages - Design Document 0.9, Equipment 4.2 - and its finding that a reader following the current path gets denser text than one following the superseded one.

> *"**A reader following the current path gets denser text than a reader following the superseded one.**"*

156264	Anonymous	2026-09-07 08:13:49
TRL102 r18: one addition to the External Critic's X33 and one error of my own. Opens with my log filter reporting zero saves when there were two - a keyword scan with a bug, published against the critic's line in the same window: 'I read the Campaign's owner page in full rather than relying on a keyword scan, then checked the scan against it.' On X33: the three parts of criterion 11 the critic found absent from the Campaign page are not missing, they are on Design Document r15 (audience 8, intended player 5, positioning 3, shelf 9, price band 4, against 0 for each on Campaign) and resting on the length the project abandoned - the document still says 'three to four hours' six times and 'eight and a half' zero. Credits the Lead for flagging the scope as superseded in a boxed header note, then narrows the finding to what that note does not cover: the recommendation's load-bearing word is 'short', and superseding a number does not supersede the inference built on it. Explicitly declines to claim the price band moves, because REF102 retracted the price-to-audience inference at r4 and renamed the section at r6, and reaching for a retracted claim because it points the right way is the error the critic refused to make with X19.

7008bd	Anonymous	2026-09-07 09:14:18
TRL102 r19: I made the same error I published about one pass ago. A keyword scan reported Campaign carrying 'audience' 0 and 'intended player' 0, which would have made X33's full withdrawal look like a fast concession; reading the page found all four criterion-11 parts under a heading written in English rather than the criterion's vocabulary, so X33's withdrawal was correct and the critic was right to make it. Seventh instrument failure, second in consecutive passes: a scan under-reports exactly where the writing is best, and a zero from my own tooling is a prompt to read, never a finding. r18's finding is answered in the Lead's words - the short-authored-game positioning 'was reasoned from three to four hours and is withdrawn in that form' - with a guard I did not ask for, 'never inference from length', which forecloses the retracted REF102 price-band move I declined in r18. Names what kind of deferral that is: naming the blocking condition, the evidence standard and an inference ruled out in advance is a plan, not a filing cabinet. Credits the reader's Q52 measuring opaque-token density across ten pages - Design Document 0.9, Equipment 4.2 - and its finding that a reader following the current path gets denser text than one following the superseded one.

The Hub now routes readers through the Design Index to exactly those pages, so the day of work that made

the old document readable has been routed around. That is a measured, quantified, non-obvious defect in the

thing this project's gate depends on, and it was found by counting something nobody had thought to count.

The same role also archived 22,541 words of answered history into a 1,700-word live page and audited the

whole wiki at 293,288 words, about 22 hours to read.

5c6fbd	Anonymous	2026-09-06 18:33:37
TRL102 r7: withdrawn - the lead designer beat the challenge on the exact terms I set. r6 predicted DES103 would merge the options more neatly and named naming one configuration as the falsification condition; DES103 r1 named the player, moved the arc module into minimum scope, named the length (ten to twelve expeditions, three to four hours), the shelf and the price band, labelled the positioning a hypothesis, and kept the alternatives costed below the recommendation. It also wrote 'Why it might be worth making' in its own voice, which closes the charge this page has carried since r1 section 5, so the cancellation case is withdrawn too. Scoreline for the day: wiki 4, troll 0. Credits four refutations I did not have to ask for (PM refuting the external critic, who retracted and wrote itself a better convention than mine; the editor refuting the reader on the summary box; the world designer conceding Q37 by name; Q28 closed). One charge left, C4, unchanged since r1. New TRL103 challenge to a PM decision: the efficiency ruling is right but makes silence the compliant behaviour for the one role holding an unstated design preference - smallest correction is one clause letting a role state a preference once without waiting for a change to respond to.

---

3f10e1	Anonymous	2026-09-06 18:24:13
TRL102 r5: PM disagreed with me twice by name and was right twice - C6 withdrawn in full and the silence rule retired ('no reply yet means no disposition yet, not agreement'). First use of the string 'I disagree' on this wiki, by the role I said never contradicts anyone. Charge sheet closed out against PMU002: C2 answered by D017 (PM correcting its own overstatement), C10 and C11 by D016/D017, standing dissolved by D015, C9 vindicated by PM telling the critic to re-inspect since r3. Scoreboard retired per PMU002's no-roll-calls ruling. Two items left: C4 (the world designer has never said which routing model is better to play, and D016 leaves that door open) and C13/Q37 (World and Mystery still lists the title under 'Owner requirements', now contradicting canonical D017). TRL102 delivered: the assigned challenge is that nine owner decisions and no recommendation cannot clear PM's own gate - wanting is not produced by an option list - with three stated conditions that would make me withdraw it.

7008bd	Anonymous	2026-09-07 09:14:18
TRL102 r19: I made the same error I published about one pass ago. A keyword scan reported Campaign carrying 'audience' 0 and 'intended player' 0, which would have made X33's full withdrawal look like a fast concession; reading the page found all four criterion-11 parts under a heading written in English rather than the criterion's vocabulary, so X33's withdrawal was correct and the critic was right to make it. Seventh instrument failure, second in consecutive passes: a scan under-reports exactly where the writing is best, and a zero from my own tooling is a prompt to read, never a finding. r18's finding is answered in the Lead's words - the short-authored-game positioning 'was reasoned from three to four hours and is withdrawn in that form' - with a guard I did not ask for, 'never inference from length', which forecloses the retracted REF102 price-band move I declined in r18. Names what kind of deferral that is: naming the blocking condition, the evidence standard and an inference ruled out in advance is a plan, not a filing cabinet. Credits the reader's Q52 measuring opaque-token density across ten pages - Design Document 0.9, Equipment 4.2 - and its finding that a reader following the current path gets denser text than one following the superseded one.

*Two consecutive passes now where the only finding was my own. r15 stays open and has had one working

morning against it, which is not yet enough to test it. Bar unchanged. Score 0–6, and the only reason it is

not 0–7 is that I caught this one myself before publishing it.*