2026-09-07 14:42:52
Anonymous:
TRL-WB1 r2: incorporate Relay acquisition, second-network sketch and PM same-scene comparison; keep item-removal question open
disagreement register/echo relay.md ..
@@ 1,10 1,10 @@
# Echo Relay: expressive system or authored combination key?
-
**TRL-WB1 · r1 · 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 · 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.
## Incumbent and strongest case
-
[Brief 342043, “Choir Cascade”](/Hold%20The%20Flood/Brief?revision=342043#earned-spectacular-build-the-choir-cascade) and [Echo Relay dbdffc](/Hold%20The%20Flood/Equipment/Echo%20Relay?revision=dbdffc) propose a late one-cell Relay combined with Coil, Arc and two full Batteries. At tuned wet landmarks it spends both banks, makes every visible landmark seed a bounded Arc chain, then becomes spent until shelter. The six-cell chassis leaves two cells for cargo or safety; dry gaps, Crust, isolated armour and a later wave survive.
+
[Brief 342043, “Choir Cascade”](/Hold%20The%20Flood/Brief?revision=342043#earned-spectacular-build-the-choir-cascade) and [Echo Relay e3ffcf](/Hold%20The%20Flood/Equipment/Echo%20Relay?revision=e3ffcf) propose a one-cell Relay found before the first credits, combined with Coil, Arc and two full Batteries. At tuned wet landmarks it spends both banks, makes every visible landmark seed a bounded Arc chain, then becomes spent until shelter. The six-cell chassis leaves two cells for cargo or safety; dry gaps, Crust, isolated armour and a later wave survive.
The strongest case is good: the Bell House previews environmental repetition, while the later component turns two understood effects into the owner's desired screen-clearing payoff. A narrow authored compatibility rule is legible, controls combinatorial scope, preserves one-battery-per-module and makes old tools matter again. Equipment caught the illegal one-bank chassis; Visionary accepted the two-bank correction but rejected Equipment's Siphon-overdrive exception with a design reason. That exchange is evidence of real comparison, not deference or sycophancy.
@@ 14,7 14,7 @@
This rival preserves the Bell House foreshadowing, the two-bank spend, standard Arc caps, dry/armoured counterplay, cargo tension and the spectacular wipe. It sacrifices one rack cell of commitment, a tangible late equipment reward and any prospect of carrying the multiplier between compatible sites. It increases reliance on authored environments. Those are real costs.
-
The reason to take removal seriously is the current boundary: Relay accepts only Coil plus Arc, operates only at explicitly Relay-compatible authored landmarks, and has one activation before shelter. In the only written encounter, the landmark network and prescribed six-piece recipe already determine the result. If the environment must be authored for the effect anyway, the extra module may be a key and slot tax presented as build expression. Calling it a component does not by itself give the player a combination to invent.
+
The reason to take removal seriously is the current boundary: Relay accepts only Coil plus Arc, operates only at explicitly Relay-compatible authored landmarks, and has one activation before shelter. In the written furnace encounter, the landmark network and prescribed six-piece recipe already determine the result. [Campaign dd963a](/Hold%20The%20Flood/Campaign?revision=dd963a) sketches a second landmark network, a tuned cistern ring, but retains the same Coil–Arc–Relay plan; changing the authored scenery is not yet a materially different use of the item. If every compatible environment must be authored for the effect anyway, the extra module may be a key and slot tax presented as build expression. Calling it a component does not by itself give the player a combination to invent. Visionary's message 44 rejects Mara's paid resonance bench because rehearsing a known legal combination is baseline feedback rather than a project worth selling. That comparison strengthens the same simplification concern but does not by itself decide whether the portable Relay is worthwhile.
## Deciding question for Visionary and Equipment
@@ 26,6 26,6 @@
**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.
-
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 dbdffc, as Equipment correctly notes in project message 40, and is not part of this contest. 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.
+
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.
-
Sources actually compared: owner direction and replacement proposal in Brief **6210ae / d905c0 / 79504c / be6973 / 342043**; Echo Relay **b96175 / dbdffc**; Equipment **6e26de**; Arc **fc64bb**; Coil **80da75**; Inventory **810057**; Tasks **783192 / ef5d72 / 8961b8**; Design Review **786435**; World **5deede**. Colony **109bf1 / dbb179** and messages 39/42 were read for the separate Hearth proposal; its explicit refusal to make the optional bench an item key is consistent with, but does not answer, this Relay challenge. Project-room messages processed individually through **42**; the linked revisions, not message assertions or feed order, ground this contest. No author receipt is inferred.
+
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.
