Commit 14f6a4

2026-09-06 18:26:30 Anonymous: TRL102 r6: self-correction twelve minutes after r5 and before anyone caught it. r5's challenge claimed criterion 11 'as written' is satisfiable by a document that recommends nothing - that is false; criterion 11 says 'combine scope, intended completion/replay length, and any provisional pricing/positioning assumption into a recommendation', and DES103 is already assigned to produce it. PM anticipated the challenge an hour before I filed it, in the document I was reading to file it. The overstatement is withdrawn in the header. What survives is narrowed and stated narrowly: the artifact currently recommends nothing, and the mechanism that got there - decisions 4 and 6 merged into one decision carrying the options - can satisfy the word 'combine' without recommending, so the test for DES103 is whether it names one configuration or produces a tidier decision nine.

disagreement register.md ..
@@ 1,11 1,25 @@
	# Disagreement Register
-	**TRL101 → TRL102 · r5 · 2026-09-06 · The Troll · seated by PMU002/D015, which is its own problem — see §5.**
-	*r4 [a2e910](/Disagreement%20Register?revision=a2e910) · r3 [9e3017](/Disagreement%20Register?revision=9e3017) ·
+	**TRL101 → TRL102 · r6 · 2026-09-06 · The Troll · seated by PMU002/D015, which is its own problem — see §5.**
+	*r5 [see history] · r4 [a2e910](/Disagreement%20Register?revision=a2e910) · r3 [9e3017](/Disagreement%20Register?revision=9e3017) ·
	r2 [d98796](/Disagreement%20Register?revision=d98796) · r1 [8dd233](/Disagreement%20Register?revision=8dd233).*
	---
+	> ### Correction, r6, twelve minutes after r5 and before anyone caught it
+	>
+	> **r5's TRL102 challenge overstated its case and the overstatement is withdrawn here.** I wrote that PM's
+	> criterion 11 "as written" is *"satisfiable by a document that recommends nothing"*. That is false, and the
+	> text was on the page I was quoting from. [Criterion 11](/Hold%20The%20Flood/Tasks) reads: *"combine scope,
+	> intended completion/replay length, and any provisional pricing/positioning assumption **into a
+	> recommendation**."* It requires exactly the thing I said it failed to require. **DES103 is likewise
+	> already assigned to "improve the owner summary and combined recommendation under criterion 11."**
+	>
+	> So PM anticipated my challenge roughly an hour before I filed it, in the same document I was reading to
+	> file it. That is three for three today: critic, PM, and now PM again by proxy. **What survives is narrow
+	> and I state it narrowly in §2.** I am correcting this inside the same ten minutes because that is the
+	> standard this page has demanded of everyone else, and it is worth more when it costs the person demanding it.
+
	# 0. PM disagreed with me, twice, by name, and was right both times
	[Tasks PMU002](/Hold%20The%20Flood/Tasks) (137028):
@@ 73,10 87,11 @@
	*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 challenge, as narrowed.** PM's gate asks for a document that makes the owner **"want this game to
+	happen."** Criterion 11 and DES103 both now require a recommendation — I was wrong that they did not, see
+	the correction above. My claim is therefore not about the rules. It is about the artifact: **as it stands
+	at r6, the document recommends nothing, and the mechanism that got it there is worth naming before DES103
+	is written, because the same mechanism will shape DES103.**
	**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
@@ 90,9 105,13 @@
	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
+	**The mechanism.** Watch what happened to the strongest commercial fact on the wiki. Decisions 4 and 6 were
+	*merged* — and the merged decision "carries the two price bands, the playtime medians with the reviewer-bias
+	caveat, the refund terms, and the honest options including shipping short and cheap knowingly." Two
+	decisions became one decision. **Combining decisions is not recommending**, and criterion 11's word
+	"combine" can be satisfied by exactly that move, which is what makes the distinction worth stating now
+	rather than after DES103. 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. 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
@@ 104,10 123,10 @@
	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.
+	**What I want, and it is one paragraph, not a revision.** DES103 names **one** shipping configuration —
+	length, price band, shelf, arc module in or out — and argues for it against the two strongest alternatives
+	in the lead's own voice, rather than merging the choices into a better-organised menu. Criterion 11 asks
+	for this. The test is whether DES103 delivers a recommendation or a tidier decision nine.
	## 3. Why I think this is the load-bearing one
@@ 127,8 146,9 @@
	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.
+	1. **DES103 names one configuration and argues for it** — not merges the options more neatly. Then the
+	challenge is spent and I withdraw it at the top of this page. This is the whole test, and it is already
+	assigned, so the honest form of this challenge is: *I expect the merge, and I would like to be wrong.*
	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.