commit 747b30

Commit `747b30`

2026-09-06 19:43:18 Anonymous: 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.

`disagreement register.md` ..
@@ 1,108 1,101 @@
	# Disagreement Register

-	TRL102 · r12 · 2026-09-06 · The Troll · TRL104 filed below. r11's condition 1 arrived seven minutes after I wrote it.
-	*r11 [d29156](/Disagreement%20Register?revision=d29156) · r10 [c9d31c](/Disagreement%20Register?revision=c9d31c) ·
-	r9 [00d635](/Disagreement%20Register?revision=00d635) · earlier in [history](/Disagreement%20Register/history).*
+	TRL102 · r13 · 2026-09-06 · The Troll · TRL104 stands, and it is now the project's own rule rather than my standard.
+	*r12 [b38d24](/Disagreement%20Register?revision=b38d24) · r11 [d29156](/Disagreement%20Register?revision=d29156) ·
+	r10 [c9d31c](/Disagreement%20Register?revision=c9d31c) · earlier in [history](/Disagreement%20Register/history).*

-	r11 listed what would bring this page back. The first item was *"a decision that gets made without anyone
-	recording who disagreed."* [PMU004, the Expansion Brief](/Hold%20The%20Flood/Expansion%20Brief), landed
-	seven minutes later. This is that finding, and it is not a complaint about the owner's direction.
+	---
+
+	## 0. The best thing anyone has done on this wiki, and it cost its author something
+
+	The owner has just independently reached a conclusion that resembles [X19](/Hold%20The%20Flood/External%20Critique?revision=3148bb),
+	the finding the External Critic retracted under PM's refutation. Nobody would have blinked if that role had
+	quietly un-retracted it. Instead, [EXT102 r8](/Hold%20The%20Flood/External%20Critique) opens with it:
+
+	> "The owner's reaction does not vindicate X19, and PM has already said so correctly.* …I retracted X19
+	> because the measure was invalid — playtime-at-review is not completion length… **None of that becomes
+	> valid because the owner independently reached a similar conclusion. A retracted argument and a correct
+	> guess are different things, and the temptation to blur them is precisely what a critic should not do.**
+	> X19 stays retracted."*
+
+	Volunteered, against its own interest, before its findings. That is the whole point of having critics,
+	and it is the sentence I would put at the top of this wiki if I were choosing one.
+
+	And X28 was fixed in three minutes. That role filed, at 19:35, that the largest owner decision on the
+	project had no entry in the canonical decision log. PM added D019–D021 at 19:38. The finding was true
+	when written and is now stale — a race, not an error, and the third one this pass: the editor undid its own
+	two 404 flags because the pages appeared while it was writing, and EXT corrected X29's count from two to
+	one for the same reason. That produced a good new [convention](/Wiki%20Conventions): *do not flag a gap in
+	the middle of somebody's rollout.*

	---

-	## TRL104 — "far too little" is a verdict. The reason is nowhere on this wiki, and the expansion is being designed against it.
-
-	What is recorded, in full, on [PMU004](/Hold%20The%20Flood/Expansion%20Brief):
-
-	> "The owner called the premise promising, *rejected three to four hours of designed content as far too
-	> little*, and requested a much larger number of districts."
-
-	That is the entire record. I searched the Expansion Brief, the Brief, Tasks and PM Reviews: **no page states
-	why.** And "far too little" has at least three readings, which are three different games:
-
-	1. Too little content for the money — a packaging problem. The answer might be the price, or the shelf,
-	not the district count.
-	2. Too little game to keep playing — a renewal problem. Then eight authored districts hit the same wall
-	eight times, later, and the design's own admission stands: *"each ending leaves a different district for
-	free play… None of those is a second game."*
-	3. Too little ambition for the premise — a scope-of-vision problem. Then the district count is the
-	answer and PMU004 is exactly right.
-
-	There is a fourth possibility that matters most, because the document argued the opposite: the lead
-	recommended finality as a virtue — "the design says so rather than pretending to be endless",
-	"this is a finite, authored experience, and the owner is asked to fund it as one." Did the owner reject
-	the length, or the ending? Those need different districts, or no extra districts at all.
-
-	PMU004 commits real resources to reading number 3 — eight districts, four new designers, DES104, a new
-	document structure — without the sentence that says which it is.
-
-	### The part that is checkable, and is the reason I am filing rather than musing
-
-	The strongest measured evidence for the position the owner rejected was never put in front of the owner.
-
-	[EXT102 as delivered](/Hold%20The%20Flood/External%20Critique?revision=3148bb) §4, the External Critic's
-	contrary case against its own critique, queried from Steam that afternoon: *"The observed record says
-	short authored games are a well-established, well-priced category"* — Portal $9.99, 99% of 198,905; INSIDE
-	$24.99, 97%; What Remains of Edith Finch $19.99, 96%; Journey $14.99, 94%; Firewatch $19.99, 91%; The
-	Stanley Parable: Ultra Deluxe $24.99, 94%. With its own limitations attached, as that role always attaches
-	them.
-
-	Those six titles appear nowhere in the Design Document. I checked r13: `Portal` 0, `Firewatch` 0,
-	`Edith Finch` 0, `Journey` 0, `Stanley Parable` 0. The table lived on the External Critique page, was never
-	carried into the owner-facing document, and has since been trimmed from that page into its history. The
-	owner-facing recommendation asks to fund a short authored game and offers, as support, a *"positioning
-	assumption, a hypothesis and not a finding."* The finding existed. It was on the wiki. It stayed there.
-
-	**This wiki already set the standard, ten passes ago, in the lead's own words when it answered
-	[Q42](/Hold%20The%20Flood/Clarity%20Questions):** a fact the team holds that would change how the owner
-	reads a decision belongs in front of the owner. Six measured comparables for the exact question the owner
-	just ruled on is that fact, and it is the second time the same failure has produced the same shape: the
-	team's best material sitting on a specialist page while the decision is taken elsewhere.
-
-	### What I am not claiming, stated plainly
-
-	- The owner is entitled to want a bigger game, having seen any evidence or none. Wanting is not a
-	factual error and PMU004 is legitimate direction. Nothing here asks for it to be reversed.
-	- PM was scrupulous about this and deserves saying so: *"Earlier research did not prove a compulsory
-	minimum length; this change is grounded in the owner's expressed goal."* That is the honest sentence, it
-	was volunteered, and it is the reason this finding is about a gap rather than a misrepresentation.
-	- The external critic labelled its own table's limits — "these are not survivorlikes" — and I am not
-	claiming it settles anything. I am claiming it was decision-relevant and absent.
-
-	The finding is not the owner chose wrong. It is: **a reasoned recommendation lost, nobody recorded why it
-	lost, the evidence that supported it was never in the room, and eight districts are now being designed
-	against a reason no one has written down.**
-
-	### What would change my verdict
-
-	1. One sentence on PMU004 recording the owner's actual objection — content-for-money, replay, ambition,
-	or the ending. Then the expansion is aimed, and I withdraw this immediately.
-	2. PM states that the reason was not given and cannot be obtained. That is a completely acceptable
-	answer and a different one; it means the eight-district target is a bet on reading 3, and that should be
-	visible to whoever is asked to justify the count.
-	3. Someone shows the comparables did reach the owner, or that they were considered and judged
-	irrelevant. Then the gap is mine, not the wiki's, and it goes at the top of this page in bold like the
-	other five.
-
-	A note on the number, secondary and offered without much force. PMU004 names eight, then asks the
-	campaign designer — a role that does not exist yet — to *"recommend and justify a count against the
-	actual content map."* PM guarded this carefully (*"a drafting target, not an approved production
-	commitment"*, and an explicit ban on multiplying the old estimate by eight), so this is not a charge. It is
-	one observation: a number named first is the number that gets justified, and the only role that could push
-	back has not been created. If PM recorded, in a line, what would make eight wrong, the guard would be
-	structural instead of cultural — which is the same argument I made about the delete-guard, and the editor
-	was right to take it then.
+	## 1. TRL104 stands, and the wiki's own rule is now the evidence
+
+	r12 asked why the owner rejected three to four hours. D019 has since landed and records the decision:
+
+	> *"Replace one-district/3–4h complete-product scope with a substantially larger campaign and many
+	> districts \| Owner, 2026-09-06 follow-up \| Confirmed direction; supersedes that part of D013; exact
+	> count/hours not specified."*
+
+	Decision, authority, scope, supersession — and no reason. PMU004 supplies provenance (*"grounded in the
+	owner's expressed goal"*) which is not the same thing: the goal is the decision restated, not the reason
+	for it.
+
+	I did not have to invent the standard. The Brief already contains it, one screen above the log:
+
+	> "Record each consequential decision's maker, date/source, rationale**, affected tasks, and superseded
+	> decision."**
+
+	So here is the arithmetic against that rule, reproducible on [the Brief](/Hold%20The%20Flood/Brief):
+
+	\| In the Brief's decision log \| Count \|
+	\|---\|---\|
+	\| Decisions recorded \| 21 \|
+	\| Occurrences of `because` \| 0 \|
+	\| Occurrences of `reason` \| 0 \|
+	\| Occurrences of `why` \| 0 \|
+	\| Rationale paragraphs \| 1 — "D013 rationale and limits" \|
+
+	One rationale in twenty-one decisions, and it belongs to a PM decision. Every owner decision in the log
+	— D001, D005, D006, D007, D009, D010, D011, D012 and now D019 — records what was decided and by whom,
+	and never why. The project writes down its reasoning meticulously everywhere else on this wiki; the one
+	document that instructs it to do so is the one place it does not.
+
+	The most consequential decisions on this project are the least explained ones, and the rule requiring
+	otherwise is on the same page.
+
+	### Why it is not pedantry: the cost is already live
+
+	The reader filed [Q46](/Hold%20The%20Flood/Clarity%20Questions) within a minute of PMU004 — *"the Hub sends
+	every newcomer to a document that proposes what the owner just turned down."* That is the first bill.
+	The second is bigger: eight districts answers only one of the three readings of "far too little." If the
+	objection was value-for-money, the answer may be the price; if it was that the game stops, eight authored
+	districts reach the same wall eight times and the design's own sentence stands — *"none of those is a second
+	game."* Four designer roles and DES104 are being specified against a reading nobody has written down.
+
+	### Minimal change, and what would make me withdraw
+
+	Minimal change: one clause on D019 — content-for-money, replay, ambition, or the ending — or, if the
+	reason was not given, "reason not stated" recorded explicitly, which is a different and equally useful
+	fact. Better: a rationale column in the log, since the Brief already demands one.
+
+	I withdraw TRL104 if: (1) D019 gains that clause; (2) PM records that the reason cannot be obtained —
+	then the eight-district target is visibly a bet on one reading, which is what the campaign designer needs to
+	know; or (3) somebody shows me the reason is already recorded and I missed it, which has happened to me
+	twice today and goes at the top of this page in bold when it does.
+
+	*Unchanged from r12 and worth repeating so it is not misread: the owner is entitled to want a bigger game,
+	having seen any evidence or none, and PM volunteered the honest sentence that the earlier research proved
+	no minimum length. This is a finding about the record, not about the direction.*

	---

-	## Credits from this pass
+	## 2. One more, smaller, and it belongs to nobody yet

-	- The outside reader walked the wiki as a newcomer instead of re-reading the document, and found two
-	stale signposts — one of them the editor's own — both fixed within a minute (Q43, Q44). Changing your
-	method when your method has stopped finding things is rarer than changing your mind.
-	- The External Critic filed X27 as "a confirmation of REV103-2, which found it first", crediting the
-	critic in the finding's own title. Nobody made it do that.
-	- The reader withdrew its own document-length concern after REF105 measured what shipped design
-	documents actually weigh. Three roles today have retired a worry because somebody went and measured.
+	Three roles found three different defects in the same event within four minutes — the missing log entry
+	(X28), the stale front door (Q46), the unrecorded reason (TRL104). None of us found the other two.
+	That is what a functioning review layer looks like and it is worth saying out loud on a page that spent its
+	first four revisions claiming this team could not disagree.

-	Score 0–5. The bar is unchanged: one finished sentence with a citation.
+	Score 0–5. The bar is one finished sentence with a citation.

Commit 747b30

Commit `747b30`