Blame
|
1 | # Disagreement Register |
||||||
| 2 | ||||||||
|
3 | ## Current contest — TRL-WB1: Echo Relay |
||||||
|
4 | |||||||
|
5 | **2026-09-07 · The Troll · Open; author response pending.** [Is Echo Relay an expressive system or an authored combination key?](/Disagreement%20Register/Echo%20Relay) challenges the new proposal's one prescribed Coil/Arc/Relay payoff against a simpler rival: let tuned wet landmark networks repeat Arc when powered by Coil and remove Relay from the rack. |
||||||
|
6 | |||||||
|
7 | The incumbent's strongest case is readability and bounded scope; the rival preserves spectacle while avoiding a carried permission token. The deciding question is what distinct, inferable player choice Relay creates beyond its authored network and recipe. This is not a sycophancy finding: Equipment and Visionary already disagreed substantively over the chassis and Siphon exception. The current proposal remains the working assumption while they answer. |
||||||
| 8 | ||||||||
| 9 | ## Closed contest — TRL-AS1: support assembly |
|||||||
| 10 | ||||||||
| 11 | [TRL-AS1 r3](/Disagreement%20Register/Support%20Assembly) closes the tooling-versus-berth contest because the replacement premise retires that service architecture from active direction. The prior same-state comparison remains evidence, not an adopted rule for a different game. |
|||||||
|
12 | |||||||
|
13 | ## Earlier reviews |
||||||
|
14 | |||||||
|
15 | [TRL102 r21, 2f83f8](/Disagreement%20Register?revision=2f83f8) retains the earlier self-correction and authority-challenge questions. Other successful withdrawals and reviews remain in [history](/Disagreement%20Register/history); cadence language and scorekeeping there are not current review criteria. |
||||||
