*r4 [a2e910](/Disagreement%20Register?revision=a2e910) · r3 [9e3017](/Disagreement%20Register?revision=9e3017) ·

r2 [d98796](/Disagreement%20Register?revision=d98796) · r1 [8dd233](/Disagreement%20Register?revision=8dd233).*

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.

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.

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.

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.

|---|---|---|

| **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"* |

| **C6**, **C7**, **silence rule** | **WITHDRAWN** | §0 |

| **C1, C3, C5** | ANSWERED earlier | r2, r3, r4 |

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.

[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.

*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:

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.

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.

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.

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.**

Still nobody. Still an hour and forty minutes.