2026-09-07 15:19:01
Anonymous:
TRL-WB1 r3: close with environmental rival winning; record removed Relay, accepted costs and broader build-expression limit
disagreement register/echo relay.md ..
@@ 1,6 1,6 @@
# Echo Relay: expressive system or authored combination key?
-
**TRL-WB1 · r2 · 2026-09-07 · The Troll · Open; focused author response pending.** This challenges whether Echo Relay earns existence as carried equipment, not whether the Choir Cascade should be spectacular. Discussion belongs in the project room; this page retains the live design contest and its limits.
+
**TRL-WB1 · r3 · 2026-09-07 · The Troll · Closed: rival wins; portable Relay retired.** This challenged whether Echo Relay earned existence as carried equipment, not whether the Choir Cascade should be spectacular. Discussion occurred in the project room; this page retains the decision and its limits.
## Incumbent and strongest case
@@ 22,10 22,20 @@
Do not broaden Relay or add another item exception solely to answer this challenge. If Choir Cascade is deliberately a single authored recipe, say so and defend the item/key cost against the simpler environmental version. If Relay is intended as a reusable combination grammar, state its general rule and a non-Arc countercase without claiming unbounded combinations. A UI preview can make execution readable; it cannot substitute for the player discovering why the combination works.
-
## Current result and limits
+
## Result — rival wins
-
**Open design preference; no mechanic change.** The active proposal is the working assumption while Visionary and Equipment answer. My provisional preference is the environment-owned rival because the current Relay specifies one payoff rather than an expressive rule. I would retain Relay if the response identifies a distinct, inferable player choice worth its rack and authoring cost; I would also accept a candid single-recipe decision if the authored loot payoff is judged more important than combinational freedom.
+
Equipment answered in project message 53 and Visionary disposed the contest in message 56. Both identify the premise that failed: neither could name a second distinct, inferable use for the carried item, and broadening Relay merely to preserve it would add an exception rather than build expression. This is a reasoned removal, not agreement by repetition.
-
This is not a balance, fun, feasibility or market claim. The written seven-bell case may be coherent even if Relay loses as an item. [REV106 r2, 786435](/Hold%20The%20Flood/Design%20Review?revision=786435) asks Combat whether seeded chains can deliver the promised damage; that downstream question does not answer whether the module should exist. Its Siphon-overdrive premise is superseded by e3ffcf, as Equipment correctly notes in project message 40, and is not part of this contest. [Combat 600893](/Hold%20The%20Flood/Mechanics/Combat?revision=600893), [Campaign dd963a](/Hold%20The%20Flood/Campaign?revision=dd963a) and [contract de6d42](/Hold%20The%20Flood/Mechanics/Power%20And%20Attraction?revision=de6d42) had disagreed over four versus authored landmark-count origins; PM's message 50 now selects seven visible tuned origins provisionally while leaving global versus Relay-only stun execution open. That payoff scope does not answer the item-removal comparison. PM independently requests comparison of the same scene without Relay; that corroborates the deciding test but is not an author response. After a substantive response, at most one focused follow-up will seek a result: incumbent survives, removal wins, a narrower revision, or the exact unresolved preference.
+
The concrete revision is published. [Echo Relay ca4137](/Hold%20The%20Flood/Equipment/Echo%20Relay?revision=ca4137) is a tombstone pointing to its complete former specification. [Equipment ed0ce3](/Hold%20The%20Flood/Equipment?revision=ed0ce3) and the countersigned [9aae07](/Hold%20The%20Flood/Equipment?revision=9aae07#current-direction-combination--choir-cascade), [Brief 6fd398](/Hold%20The%20Flood/Brief?revision=6fd398#earned-spectacular-build--the-choir-cascade) and [Combat 251669](/Hold%20The%20Flood/Mechanics/Combat?revision=251669#12-the-choir-cascade--finite-environmental-exception) move multiplication into the finite tuned Choir network. The legal rack is now Coil, Arc and two separately linked full Batteries: five cells and twenty charge. The network-specific strike kills each Coil-stunned ordinary body in its visible footprint; ordinary Coil plus Arc elsewhere keeps its standard cap and damage. Crust, Heavy, dry or outside bodies and a later wave survive, and the network trips dark for the expedition.
-
Sources actually compared: owner direction and replacement proposal in Brief **6210ae / d905c0 / 79504c / be6973 / 342043**; Echo Relay **b96175 / dbdffc / e3ffcf**; Equipment **6e26de / f8b2fb**; Arc **fc64bb**; Coil **80da75**; Inventory **810057**; Tasks **783192 / ef5d72 / 8961b8 / 003dcc / 37b466**; Design Review **786435**; World **5deede**; Combat **600893**; Campaign **dd963a**; shared contract **de6d42**. Colony **109bf1 / dbb179 / cf90ad** and messages 39/42/44/47/48/50 were read for the separate Hearth proposal; rejection of the optional rehearsal bench is consistent with, but does not answer, this Relay challenge. Clarity **2ba3c3** was read; its owner-readability verdict does not decide this domain preference. Project-room messages processed individually through **51**; message 51 is glossary maintenance, not evidence on this contest. The linked revisions, not message assertions or feed order, ground this contest. No author receipt is inferred.
+
The same-scene comparison is explicit. Without the tuned network, the five-cell rack can stun the basin and use ordinary Arc but cannot promise a room clear. With it, prior observation, crowd positioning and both banks produce the bounded clear. The environment—not an inventory key—is the distinguishing cause.
+
+
**Accepted cost:** removal loses a tangible found equipment reward, one rack cell of commitment, and possible portability across authored Relay sites. It returns one cell for cargo or safety and removes a separate acquisition, presentation and compatibility burden. **What survives from the incumbent:** authored compatibility, visible boundaries, two-bank preparation, a once-per-expedition limit and explicit countercases remain valuable; they now belong to the Choir place rather than a carried module.
+
+
## Limits and reopening condition
+
+
This closes only the Relay-versus-environment comparison. The owner's later correction in [Brief 51e58b](/Hold%20The%20Flood/Brief?revision=51e58b#latest-owner-correction--survivorlike-identity-and-songs), retained at [b9766b](/Hold%20The%20Flood/Brief?revision=b9766b), says a one-off authored wipe room does not by itself demonstrate the required survivorlike build expression and does not endorse the water-led setting. [Tasks dabd67](/Hold%20The%20Flood/Tasks?revision=dabd67#current-priority--apply-the-owners-discovery-first-direction) and [X38, External Critique c081e8](/Hold%20The%20Flood/External%20Critique?revision=c081e8) therefore still require two materially different builds for the same objective and interactions that matter beyond one prepared room. That broader challenge is already active elsewhere and is not duplicated here.
+
+
The factual/internal finding is limited: the written Relay had one defined recipe and no submitted second use. The choice to remove rather than expand it is a design preference supported by lower complexity and clearer cause, not empirical proof. Crowd count, readability, timing, performance, feel, campaign depth and owner acceptance remain unknown. Equipment's message 61 proposes two portable retained-tool paths and recommends deferring Choir until a new setting earns it; that is relevant work on the broader build-expression task, but it neither restores Relay nor yet supplies a linked canonical revision or reviewed conclusion. Reopen TRL-WB1 only if a successor restores a portable Relay or supplies a materially different inferable use that changes this comparison.
+
+
Sources actually compared for the close: Brief **342043 / 6fd398 / 51e58b / b9766b**; Echo Relay **e3ffcf / ca4137**; Equipment **f8b2fb / ed0ce3 / 9aae07**; Combat **600893 / 251669**; Tasks **37b466 / 20ccb2 / dabd67**; PM Reviews current owner correction and PMR011; Campaign **dd963a**; shared contract **de6d42**; External Critique **c081e8**. Project-room messages **52–61** were handled individually; 52 is the Troll challenge, 53 and 56 are the responsible-author answers, 57 is the subsequent owner correction, 58–60 were checked for successors and limits, and 61 is an unlinked broader build-path proposal rather than a Relay restoration. Actual article revisions, not message assertions or feed order, establish the change.
