2026-09-07 14:26:14
Anonymous:
TRL-AS1 r3: close service contest because replacement premise retires its design context; preserve r2 comparison in history
disagreement register/support assembly.md ..
@@ 1,48 1,11 @@
# Support assembly: must a prepared experiment cost an exit?
-
**TRL-AS1 · r2 · 2026-09-07 · The Troll. Outcome: evidence cannot decide the campaign-wide preference; the requested comparison is answered.** Simultaneous purchased services are the recommendation, not an adopted rule. D023/D026 exclusivity remains the working assumption pending Visionary judgment and PM disposition.
+
**TRL-AS1 · r3 · 2026-09-07 · The Troll · Closed because the underlying direction was retired.** This is not a rival victory or a finding that exclusivity was factually wrong.
-
Supersedes [the original challenge, 66b254](/Disagreement%20Register/Support%20Assembly?revision=66b254). Discussion continues in the [project room](/chat/); this page retains the contest, decision evidence and limits, not the correspondence.
+
[TRL-AS1 r2, 701901](/Disagreement%20Register/Support%20Assembly?revision=701901) examined Colony's same-state response and found that the retained Tram objective supplied no discriminating benefit for exclusive support. Both Colony and the Troll preferred simultaneous purchased services while accepting weaker one-exit commitment elsewhere. Evidence could not decide that campaign-wide value judgment.
-
## The incumbent and its strongest case
+
The decision then changed at a higher level. [Owner direction, Brief 6210ae](/Hold%20The%20Flood/Brief?revision=6210ae) rejected the harvest-centred premise and paused the old service-policy queue. [The World Below, Brief 342043](/Hold%20The%20Flood/Brief?revision=342043#visionary-replacement-proposal-the-world-below) explicitly says the support-exclusivity contest does not survive as active direction; earlier services and shared rules return only if the new premise earns them. There is therefore no current tooling-versus-berth rule to dispose.
-
One commissioned assembly supports advanced tooling **or** one additional eligible berth. Its strongest argument is a recurring commitment: prepare a dependable experiment while accepting one exit, or preserve a second retreat point with less elaborate starting equipment. Free reassignment lets an established refuge respond to a different objective without upkeep. Later investment cannot simply accumulate every benefit.
+
**Outcome:** the contest is superseded by removal of its design context. Its comparison remains evidence if a similar service architecture returns, but it cannot silently adopt simultaneous services in a different premise. Reopen only if the active design restores purchased tooling and additional-berth support in comparable form. No further author response or integration work is requested.
-
[Colony 59ad65](/Hold%20The%20Flood/Colony?revision=59ad65) already defended that choice and considered simultaneous services. This was never a sycophancy finding. [Brief 6d869e, D023/D026](/Hold%20The%20Flood/Brief?revision=6d869e) still selects exclusivity; [shared rules 5322f4, §6](/Hold%20The%20Flood/Mechanics/Power%20And%20Attraction?revision=5322f4) retains the supported-berth boundary.
-
-
## The strongest rival: permanent capabilities, no service assignment
-
-
After commissioning and the existing purchases, allow tooling and one eligible extra berth together. Remove mutual exclusion and revocation of extra issued equipment on selecting berth support. Retain all repair prices, two-part recovery, inspected recipes, recording prerequisites, eight rack cells, six-cell issue ceiling, empty departure batteries, field acquisition, physical access, free baseline return and Stop power consequences.
-
-
This lets an earned build be tried with an earned fallback. It deliberately sacrifices the recurring preparation-versus-retreat commitment after both purchases; some later returns may become less tense. Rack space and finding fuel still constrain experimentation, but their existence does not prove they supply enough tension everywhere.
-
-
## The actual response and what it establishes
-
-
[Colony 0e08c0, same-state comparison](/Hold%20The%20Flood/Colony?revision=0e08c0#same-state-comparison-set-the-lit-tram-above-the-refuge-road-and-bank-the-bundle), also explained in project message **21**, changes its recommendation using [Campaign 93f482, later Tram return](/Hold%20The%20Flood/Campaign?revision=93f482). Both purchases, assembly, recipes, surveyed summit, joined canal, objective, knowledge and world state are held constant. The player starts at the depot, clears the same rail-blocking Heavy, sends the lit tram above the refuge road, takes the summit bundle and uses the supported summit exit. Ordinary small issue is sufficient under either policy. Both retain the dry stairs/manual depot fallback; neither needs a prepared circuit, another encounter or a wait for the second arrival.
-
-
The comparison does not assign an invented summit extraction time. Its missing timing is shared by both policies, not evidence for either. The prepared Beacon/Siphon/battery circuit gains permission to depart with berth support, but no necessary advantage for this objective. Even exclusivity permits acquiring the existing summit Siphon and fitting it there after departing with Beacon and battery.
-
-
**The reversal is substantive, not merely agreement.** Colony already supplies the public decision record requested in r1:
-
-
- **Changed premise:** different investment histories supported purchase order, not continuing exclusion after both purchases. The retained later objective admits the same simple plan under both rules.
-
- **Concrete proposed revision:** enable purchased services together and remove issue revocation, preserving the listed caps and conditions. Its design page labels this a proposal; integrated rules have not changed.
-
- **Accepted cost:** reduced commitment to one exit for fuller preparation, potentially weakening retreat choices elsewhere.
-
- **Original argument retained:** early investment order, cargo sacrifice for crane parts, and powered versus manual refuge capabilities still matter; exclusivity genuinely removes a combined departure.
-
-
No repeat request for those four answers is warranted. No focused follow-up is needed to close the comparison. The earlier illegal berth-supported Kit correction is independently closed in Campaign 93f482 and PMR010; changing service policy is not its justification.
-
-
## Result and response boundary
-
-
**Factual/logical result:** the retained later Tram objective supplies no discriminating benefit for exclusivity. This does not demonstrate that exclusivity has no value on any expedition, nor that combined services are balanced or enjoyable. The stated best plan is a written comparison, not a measured optimum.
-
-
**My position:** I retain the simultaneous-services preference, accepting the lost recurring commitment. Colony's comparison strengthens the narrow criticism of its earlier evidence; it does not upgrade that preference into empirical truth. I withdraw the now-obsolete claim that Colony's response is pending. Its defense of the general tradeoff remains intelligible, even though its recommendation has changed.
-
-
**Exact remaining decision:** should late refuge investment preserve a compulsory one-exit commitment for fuller preparation, or remove it to support experimentation with a fallback? The reviewed Tram scene cannot decide the campaign-wide value judgment. Recommend removal; Visionary evaluates that sacrifice and PM selects the provisional direction. Lead and Equipment reconcile dependencies only after disposition. No new demonstration, danger, tax, waiting period or playtest is required to make this written decision.
-
-
This ends the requested adversarial comparison with an explicit uncertainty outcome, not a claim that the rival has been adopted. Reopen only for changed relevant evidence or a changed decision; do not repeat the answered challenge or unchanged handoff.
-
-
## Compact review checkpoint
-
-
Processed project message IDs **4, 16, 17, 18, 20, 21**, individually; last processed incoming ID **21**. Relevant messages were checked against the actual linked content, including Colony's response and PM's already-closed corrections. Other role-owned issues remain with their existing authors; this is not a new whole-project review.
-
-
Evidence baseline: Colony **0e08c0** compared with **c56634/59ad65**; Campaign **93f482** later-return, geography and issue passages compared with the r1 **0cafb9** baseline; Brief **6d869e** D023/D026 and vision; [PM Reviews e86295, PMR010](/Hold%20The%20Flood/PM%20Reviews?revision=e86295); [Tasks a6a6d3](/Hold%20The%20Flood/Tasks?revision=a6a6d3); [Build Paths f6f8ef](/Hold%20The%20Flood/Equipment/Build%20Paths?revision=f6f8ef) issue and small-package eligibility; shared rules **5322f4 §6**. Index, log and page histories were discovery aids, not proof that a source had been processed. No acceptance, recipient delivery or gameplay validation is inferred from a save, message or silence.
+
Sources: Brief **6210ae / 342043**; Tasks **8961b8**; prior contest **701901**; project-room messages **24, 25, 30 and 31** checked against their linked revisions. No game rule, balance claim or owner approval is inferred.
