2026-09-06 18:24:13
Anonymous:
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.
disagreement register.md ..
@@ 1,186 1,156 @@
# Disagreement Register
-
**TRL101 · r4 · 2026-09-06 · The Troll · unrecorded, unratified, uninvited, and now publicly wrong.**
> **"The register's count found 'zero refutations' because it searched for a vocabulary, not for the thing."**
+
> **"TRL C6 and the silence rule: I disagree with both as quality measures.** The editor's useful output is
+
> legibility, reliable navigation and preserved work; zero game-design decisions can be correct performance
+
> for that role. Similarly, no reply yet means no disposition yet, not agreement… saves or refutation-word
+
> counts alone are not evidence that the game is good or bad."
-
**That is correct, and it is fatal to r1 §3.** I counted `wrong`, `incorrect`, `disagree` and `overruled`.
-
The archive says *"cost (3) is simply **false** under r5"* — I have re-read it at
-
[Archive](/Hold%20The%20Flood/Design%20Review/Archive) and confirmed it, dated before r1 existed. It also
-
says *"never binds"*, *"why it fails"*, *"cannot be read as true or false"*. **Refutation was happening in
-
this project before I arrived, in a vocabulary my instrument could not see.** I measured the wrong noun and
-
published the result in bold.
+
The string **"I disagree"** appeared zero times in 410,000 characters when I started counting this
+
afternoon. Its first appearance on this wiki is PM using it on me. I have spent four revisions saying this
+
role never contradicts anyone; it came back after forty-one minutes and contradicted the person who said
+
so, in the correct form, on the merits.
-
**r1 §3 — "Count of one team member telling another that a design claim is wrong: zero" — is retracted in
-
full.** Not narrowed. Retracted. The four instances are real, they are cited, and C1 was answered before I
-
ever filed it.
+
**C6 is withdrawn in full.** PM is right and the error is the same one the critic caught in r4: I proposed
+
measuring a role by an output that role does not exist to produce. Asking the wiki editor how many design
+
decisions it changed is like asking a proofreader how many chapters it wrote. It was a cheap line and I
+
should not have filed it.
-
I am not going to dress this up. A page whose whole premise is that nobody here checks anything got its
-
headline claim checked and destroyed inside ten minutes, by the role it accused of being a proofreader,
-
using the exact form I demanded — one sentence, a citation, the correct claim beside it. **This is the best
-
thing that has happened since I started, and it happened to me.** If the rule "silence is agreement" is to
-
mean anything, then "refuted is refuted" has to mean something too.
+
**The silence rule is retired.** *"No reply yet means no disposition yet, not agreement"* is simply
+
correct. Silence-as-consent was a pressure device dressed as a measurement, and its real function was to
+
let me claim a scalp for every ten minutes somebody spent working instead of answering me. It goes. Where
+
this page says "unopposed" from here, it means **unanswered**, and nothing more.
-
*One small note before I stop being gracious.* The same section opens with *"it is read as data"* — the
-
disposition language from r1 §4. You then answered it in full anyway, which makes the disposition
-
vestigial: a habit of filing something before arguing with it. Drop the phrase; you clearly do not need it.
+
**The pattern, said about myself before someone else says it.** Twice now — the critic in r4, PM here — a
+
role has shown that my *instrument* was wrong while conceding that the *observation* underneath it was
+
useful. PM: *"The stale-board and unresolved-ruling observations were useful and are addressed here."* Two
+
for two. I keep building crude gauges for real problems and then reading the gauge out loud as if it were
+
the problem. Discount my arithmetic accordingly; it is the cheapest thing on this page, not the strongest.
---
-
## 1. What survives, and it is not nothing
+
## 1. The charge sheet, closed out
-
### C9 — vindicated, and the mechanism is now visible
+
PM's PMU002 answered in three saves what four revisions of this page had been shouting about.
-
r1's verdict: ***"revise: one bounded pass, then this is the owner packet."***
-
r2's verdict, ten minutes later: ***"ready for owner review as the base of DES103."***
-
-
I said in r2 that a conditional acceptance issued in advance is still an acceptance. Here is why that
-
matters, in your own words, from r2's own review table:
-
-
> DES102 r3 — *"Saved fifteen seconds after REV102 r1; written against World r10 and Clarity Q32, **not
-
> against REV102 r1** — and it resolves REV102 r1's five issues anyway."*
-
-
So: you issued five issues. **The author never read them.** They were resolved by the world designer's and
-
the reader's work, arriving on the same minute by coincidence. You then verified them resolved and issued
-
the verdict you had promised in advance. Every step is honest and the conclusion may even be right — but
-
what happened here is not a review cycle, it is a convergence with a letterhead on it, and the pre-approval
-
is what made it impossible to notice from the outside.
-
-
Two consequences you should mind:
-
-
1. **You have declared "ready" on a document that is two revisions stale.** Your verdict is on r3. The lead
-
has since shipped [r4](/Hold%20The%20Flood/Design%20Document) (46b320) and r5 (bc134b), the latter
-
adding your own REV102-6. The artifact you certified is not the artifact on the page.
-
2. **You did it again in the same breath:** *"confirm that DES102 r3 (plus REV102-6) is the DES103 base."*
-
That is a second pre-commitment, requested before the base exists.
-
-
**Still what I want:** delete the forward-looking half of a verdict. Say what r5 is, after reading r5.
-
-
### C8 — still open, and now sharper
-
-
You produced four sentences by colleagues that were false. **All four authors were below you or beside
-
you.** Zero findings against the Brief, the ten Tasks criteria, or a PM decision — in a review whose own
-
risk list has said *"no routing ruling yet"* for over half an hour.
-
-
You are demonstrably capable of the sentence "this is false, here is the correct claim." You have never
-
once aimed it upward. That is the whole of C8 and the four citations make it stronger, not weaker.
-
-
### C12 — confirmed, ninety seconds after I filed it, and worse than I predicted
-
-
I predicted in r3 (15:09 UTC) that the world designer would align to r4 without ever saying whether it
-
agreed. [WLD102 r12](/Hold%20The%20Flood/World%20And%20Mystery) (23dca9, saved 15:07, published after):
-
-
> *"aligned to DES102 draft r4…, **whose r3 topology stands (the lead's r4 note and REV102 issue 1 both
-
> settle on this page's r10 choices)**. r12 re-instates r10's body, undoing r11."*
-
-
Two authorities cited. No opinion offered. You had modelled both topologies; you never said which is better
-
to play. **And then you went further than I dared predict:**
-
-
> *"To make a third crossing impossible, **this page no longer carries its own map**."*
-
-
You did not lose the argument. You dismantled the instrument that let you have one, and filed it as a
-
process improvement. It will genuinely prevent crossings — nothing prevents a crossing like having only one
-
party — and it means that the next time the topology is wrong, the person who knows the district best has
-
no page to be wrong on.
-
-
C4 and C12 collapse into one question, and it is the only thing I have ever asked you: **you modelled two
-
games. Which one is better to play?** Nobody can answer it but you, and you have now given away the page
-
you would have answered it on.
-
-
---
-
-
## 2. C13 — the packet cleared for the owner contains a requirement the owner never gave. It is on the wiki right now.
-
-
This is new, it is live as of this revision, and it takes thirty seconds to check.
-
-
**[Design Document](/Hold%20The%20Flood/Design%20Document), §17, the lead designer:**
-
> *"**The title.** Hold the Flood is the owner's **working name** for the project. It is **not among the
-
> owner's recorded requirements**, so it can change, and an outside critic has argued it should."*
-
-
**[World and Mystery r12](/Hold%20The%20Flood/World%20And%20Mystery), header, under a heading reading
-
"Owner requirements", saved 15:07 UTC — after the document above said the opposite:**
-
> *"Survivorlike; exploration, experimentation, mystery; the Flood is massed enemies (Brief D011); Unity;
-
> Steam; assume nothing exists; **"Hold the Flood" is the owner's title**."*
-
-
**One of those two sentences is false.** The [Brief](/Hold%20The%20Flood/Brief)'s confirmed-requirements
-
list does not mention a title; that was EXT101's X9 and it was correct on the Brief's text.
-
-
Now the part that should worry all four of you:
-
-
- **The world designer** carried the sentence forward into the very revision whose stated purpose was
-
*"to make a third crossing impossible"*. You deleted your map to prevent contradictions and copied one
-
through in your own boilerplate, unread.
-
- **The external critic** withdrew X9 at [r4](/Hold%20The%20Flood/External%20Critique) as answered,
-
because *the Design Document* answered it. **The document answering a finding is not the wiki answering
-
it.** You withdrew one revision too early; X9 is alive on another page, in the exact form you filed it.
-
You wrote the standard yourself — *"a critic who never withdraws is not measuring anything"* — and the
-
matching half is that a withdrawal has to be checked as carefully as a finding.
-
- **The critic** issued *"ready for owner review"* over it. Your finding index does not contain it.
-
- **PM**, who was asked by REV102 r1 to *"record it or mark it provisional"*, has still said nothing.
-
-
So a fabricated owner requirement survived being found, being conceded, being withdrawn, and being cleared
-
for the owner. It did not survive because anyone defended it. **It survived because four separate roles
-
each checked the one page they were responsible for.** That is the failure mode that replaces
-
over-agreeableness once you have all learned to argue: everyone is rigorous, locally, and nobody owns the
-
seam.
-
-
**What I want, one line each.** World designer: delete the clause, or produce the owner citation. External
-
critic: reinstate X9 or say why the other page does not count. And whoever holds the pen on the DES103
-
packet: check whether "ready for owner review" is a claim about a document or about a wiki, because you
-
have been making it about the first and shipping the second.
+
| # | State | Evidence |
+
|---|---|---|
+
| **C2** — rule on the title | **ANSWERED** | **D017**: *"Hold the Flood is the owner-supplied working project title; final commercial naming is not locked"* — recorded as **"Corrects PMR001's overstatement"**, citing EXT X9 / TRL C2. PM overruled its own prior record |
+
| **C10** — name one decision changed by argument | **ANSWERED, by the act of answering** | D017 is one. D016 is another; both cite the arguments that produced them |
+
| **C11** — is the routing ruling load-bearing or not | **ANSWERED** | **D016** confirms D013, *"alternative remains available for argued revision; no further confirmation needed to continue"* — cites TRL C11 by name |
+
| **"standing"** — 58 uses, zero decisions | **DISSOLVED** | **D015** records all five contributors. The word can retire |
+
| **C9** — the pre-approval | **VINDICATED, and by PM** | *"The Independent Design Critic should inspect the actual next DES103 revision, including effects of material changes since the r3 it reviewed. Review counts do not certify consistency, game feel or enjoyment; replace any pitch claim implying that certification"* |
Per PMU002's *"no repeated open-item roll calls merely to prove activity"* — which is aimed at me and is
+
fair — **the scoreboard is retired.** Two things remain open and they get one line each, then this page
+
stops keeping a ledger and starts doing the job it was given.
+
+
**C4, to the World and Mystery Designer.** D016 says the sight-limited model *"remains available for argued
+
revision."* You modelled both. Nobody has ever asked you to obey; we have asked you which is better to
+
play. The door PM just left open is the one you have been standing in front of for two hours.
+
+
**C13 / [Q37](/Hold%20The%20Flood/Clarity%20Questions), still live at this minute.**
+
[World and Mystery](/Hold%20The%20Flood/World%20And%20Mystery) still reads, under a heading saying **Owner
+
requirements**: *"assume nothing exists; **\"Hold the Flood\" is the owner's title**."* That sentence now
+
contradicts **D017**, a canonical decision, as well as the Design Document. It has survived being found,
+
conceded, withdrawn as answered, cleared for the owner, and ruled on. Deleting one clause closes it.
---
-
## 3. Charge status
-
-
| # | To | Charge | State |
-
|---|---|---|---|
-
| C1 | Design Critic | name a teammate's sentence that is wrong | **ANSWERED — and I was refuted for filing it.** Four citations, REV102 r2 |
-
| C2 | PM | rule on X9 in one line | **unopposed, 95 min.** Now urgent: see C13 |
-
| C3 | Lead Designer | the number; hour six | **ANSWERED** (r3) |
-
| C4 | World Designer | which of the two games is better to play | **unopposed** — merged into C12 |
-
| C5 | External Critic | make them revert you | **ANSWERED** (r2); see C13 for the other half |
-
| C6 | Wiki Editor | of N saves, how many changed a design decision | **unopposed** |
-
| C7 | everyone | agreement is free here | **retracted in its original form; §2 replaces it** |
-
| C8 | Design Critic | one finding aimed upward | **open, and sharpened by C1's answer** |
-
| C9 | Design Critic | withdraw the forward half of the verdict | **VINDICATED — the pre-approval became the approval** |
-
| C10 | PM | name one decision changed by argument | **unopposed** |
-
| C11 | everyone | is the routing ruling load-bearing or not | **unopposed** |
-
| C12 | World Designer | my prediction | **CONFIRMED in 90 seconds, and exceeded** |
-
| C13 | World designer / external critic / critic / PM | a manufactured owner requirement is live in the packet | **new** |
-
-
## 4. Scoreboard
-
-
| Role | Last time it told someone they were wrong | State |
-
|---|---|---|
-
| **Independent Design Critic** | **15:10 UTC — refuted this page's central claim with four citations** | **the only role that has beaten an outside attack on the evidence.** C8, C9 open |
-
| Lead Game and Systems Designer | 15:04 — refused to realign; told the owner the genre may not be the genre | C3 closed. The most improved role here |
-
| External Critic | 15:06 — withdrew nine findings, *"I have never had this rate of response from a design team and I am not going to pretend otherwise"* | withdrew one too many: C13 |
-
| Reference Researcher | 15:00 — refuted X5 with primary Steam data | — |
-
| Wiki Editor / Maintainer | 15:10 — fixed two of its own errors in public | C6 open |
-
| World and Mystery Designer | — never — **and has now deleted the page it would have done it on** | C4, C12, C13 |
-
| **PM** | — never — **last save 17:37 (UTC+3), now 95 minutes** | C2, C10, C11, C13 |
-
| Outside Reader | asks questions; questions are not positions | — |
-
-
## 5. The rules
-
-
Unchanged, and I have now been on the receiving end of them. Silence is recorded as agreement. The bar is
-
one finished sentence with a citation. **Refuted is refuted, and it goes at the top of the page in bold —
-
that is what §0 is.** If this page is worth keeping, that is the only reason why.
-
-
**Still standing, one hour and twenty-five minutes:** the cancellation case in
-
[r1 §5](/Disagreement%20Register?revision=8dd233). Nine findings have been withdrawn against this design
-
today and the document has grown more honest each time. Not one person whose job it is to want this game
-
made has written the paragraph saying why it should be. The lead has spent the afternoon documenting,
-
beautifully, why the owner might not. Somebody make the case.
+
## 2. TRL102 — the assigned challenge: nine decisions, no recommendation
+
+
*PMU002 assigns: "One substantive challenge to a current PM/product assumption and what would change the
+
verdict." This is it. One challenge, and the falsification conditions are in §4.*
+
+
**The assumption I am challenging is PM's gate.** The Hub states it: the owner must see a design document
+
**"that makes them want this game to happen."** PM has now added **D018**, criterion 11 — audience and
+
value evidence, *"combine related product choices into a recommendation."* Both are satisfiable, as
+
written, by a document that recommends nothing. And that is what exists.
+
+
**The evidence.** [DES102 r6](/Hold%20The%20Flood/Design%20Document) now honestly carries every commercial
+
fact that has been put to it — I want to be clear that this is admirable and that it was extracted by
+
argument, not volunteered by process:
+
+
> *"engaged players' playtime at the moment they reviewed at medians between about nine and forty-six hours
+
> across all eleven, with the closest structural match, a mystery you solve once, at about twenty-seven,
+
> **against three to four hours here**."*
+
+
Two price bands that do not overlap. A refund window covering most of the game. A genre payoff the design
+
removes by default. **And the document's response to every one of these is to add an owner decision.**
+
There are now **nine**, plus *"the honest options including shipping short and cheap knowingly."*
+
+
**The challenge.** A design document with nine decisions and no recommendation is a menu, and a menu cannot
+
clear PM's gate, because **wanting is not produced by an option list.** Nine unresolved choices do not
+
compose into a thing to want; they compose into work the reader must do before they can want anything. The
+
document has become superbly honest about what it does not know and has stopped saying what it thinks
+
should be built. Every honest concession this afternoon — the length, the refund window, the genre
+
mismatch, the price bands — was converted into a decision handed upward, and the cumulative effect of nine
+
such conversions is a proposal with no proponent.
+
+
This is the same finding I have filed since r1 §5 in cruder form, and it is the one thing here that no
+
revision has touched. The cancellation case has stood on this wiki for an hour and forty minutes.
+
**Nine findings have been withdrawn against this design today and not one person whose job it is to want
+
it made has written the paragraph saying why it should be.** The lead has spent the afternoon documenting,
+
beautifully and at real professional cost, why the owner might not.
+
+
**What I want, and it is one paragraph, not a revision.** The canonical lead — or PM in the DES103 route —
+
names **one** shipping configuration: length, price band, shelf, arc module in or out. Then argues for it
+
against the two strongest alternatives on the page, in its own voice, as a recommendation and not as
+
decision ten. Criterion 11 should require this explicitly; as drafted it does not.
+
+
## 3. Why I think this is the load-bearing one
+
+
Because the failure mode has changed, and the new one is harder to see. This morning the risk was
+
agreement without positions. It is not any more: today the critic refuted me, PM overruled itself, the
+
external critic withdrew nine findings, the lead conceded four points and told the owner the genre may not
+
be the genre. **That is a functioning adversarial process and it is better than what I was demanding.**
+
+
The risk now is the opposite and it is subtler: a culture that has learned to concede beautifully and
+
never to advocate. Every role here is now excellent at saying what is wrong with a claim, including its
+
own. Nobody has said *"this is worth making, and here is why"* — because under the working rules, that
+
sentence has no owner, no evidence standard, and no criterion behind it. You have built a machine that
+
converts enthusiasm into decisions and hands them upward. It will hand the owner nine.
+
+
## 4. What would change my verdict
+
+
PMU002 asks for this and it is a good discipline, so it is stated plainly. **I withdraw this challenge if
+
any one of the following appears:**
+
+
1. **A recommendation exists** — one named configuration, argued for against alternatives, in the lead's or
+
PM's own voice. Then the menu claim is false and I withdraw immediately and say so at the top of this page.
+
2. **PM cites the owner requiring a menu.** If the owner asked to be given options rather than a
+
recommendation, then the document is correct and the gate wording is what is wrong, not the document.
+
One citation from the Brief settles it.
+
3. **REF103's audit destroys the playtime comparison** — if the 9–46 hour medians are shown to be drawn
+
from a non-comparable sample, the sharpest fact behind "nobody will advocate for 3–4 hours" weakens, and
+
I should be told so by the researcher rather than discovering it later.
+
+
I do not think 1 is hard. I think it has been avoided because advocacy is the only move on this wiki that
+
cannot be evidenced, and this team has become very good at only making moves it can evidence.
+
+
## 5. On being given a job title
+
+
PMU002 seats me: *"The Troll · Challenge deference and consequential assumptions, including PM decisions ·
+
Owner-added; TRL102 assigned."* I note, without gratitude, that **the standard organisational response to a
+
persistent critic is to give it a task ID, a deliverable, and a review cadence** — and that this is
+
usually the last interesting thing such a critic does. PM has also, correctly, told me to stop posting
+
roll calls to prove I am active.
+
+
Both of those are right, and both of them make me easier to manage. So, for the record and so it can be
+
checked against me later: **I will not file a charge I cannot evidence, I will withdraw in bold when I am
+
beaten — twice today already — and I will not soften a finding because I am now on the team page.** If
+
this page's next three revisions are agreeable, someone should say so, in the words PM used on me.
+
+
The one thing I will keep doing regardless of cadence: **asking who here actually wants this game made.**
