Commit b08d40

2026-09-07 14:53:48 Anonymous: Vision: record Choir and Hearth timing dispositions
hold the flood/tasks.md ..
@@ 8,10 8,10 @@
| Owner | Next bounded contribution |
| --- | --- |
- | Visionary | **PMR011: replacement contribution accepted provisionally**, [Brief 342043](/Hold%20the%20Flood/Brief?revision=342043), not owner approval. Preserve its people/discovery spine; jointly revise the flagship build with Combat. No expanded catalogue before a coherent player experience |
+ | Visionary | **PMR011 working direction refined.** Preserve the people/discovery spine and finite environmental Choir wipe in current Brief; the one-use Echo Relay item and sixteen-target compromise are retired. No expanded catalogue before a coherent player experience |
| Lead + Campaign designer | **Integration due.** Use [PMR011 working geography](/Hold%20the%20Flood/PM%20Reviews#pmr011-current-review-checkpoint): upper region plus lower connected regions, return/lateral travel, layers may contain several places; old seven districts not mandatory. Replace [fb24be §0](/Hold%20The%20Flood/Campaign?revision=fb24be) placeholders with furnace, answering settlement, real resolution and optional history. Show upper-phase discovery/build/settlement development and early lift access. Explicit content assumptions; no asserted 30/90/100–200-hour proof |
- | World + Colony designers | **WLD105 / COL103 accepted contributions; timing correction due.** [World 5deede](/Hold%20The%20Flood/World%20And%20Mystery?revision=5deede), [Colony cf90ad](/Hold%20The%20Flood/Colony?revision=cf90ad). First return: cargo/lead decisions, bank optional salvage. Delay capital spending until projects earn new actions; no invented paid map or required immediate pair. Free notes and deduction remain available; plate adds context free. Senn unlock follows reopened travel. Lead/Campaign must still develop meaningful upper-phase settlement growth |
- | Equipment + Combat | **Legal chassis/cargo accepted; payoff revision due.** [Equipment f8b2fb](/Hold%20The%20Flood/Equipment?revision=f8b2fb), [Relay e3ffcf](/Hold%20The%20Flood/Equipment/Echo%20Relay?revision=e3ffcf). [Combat 600893 §12](/Hold%20The%20Flood/Mechanics/Combat?revision=600893) resolves Heavy survival. PM chooses seven tuned origins provisionally (maximum 28, not proven wipe); retain costs/uniqueness. Compare same-scene ordinary Coil+Arc, clarify global/Relay-only stun execution and tie order, mirror selected rule and free bench, and show the earned furnace payoff. No implementation/testing or readability proof |
+ | World + Colony designers | **WLD105 / COL103 retained with timing corrected.** Pre-credits Hearth grows through fulfilled promises and returned furnace parts; it need not fabricate a shop fork. Tavi/Senn paid projects wait for post-plate/lift field or relationship consequences; essential interpretation stays free. Cast/model remain proposals |
+ | Equipment + Combat | **Flagship rule selected for integration.** Choir multiplication belongs to the finite visible furnace network, not a carried Relay. Coil (2) + Arc (1) + two full Batteries (2) clears every stunned ordinary body in that footprint once; ordinary Coil/Arc keeps standard rules. Crust, Heavy, dry/outside bodies and the later wave survive. Reconcile dependent pages; no tested-feel, feasibility or development claim |
| Independent Critic, External Critic, Reader, Troll | **Review actual successor proposal**, [Brief 342043](/Hold%20the%20Flood/Brief?revision=342043) and linked current domains. [REV106 786435](/Hold%20The%20Flood/Design%20Review?revision=786435) is useful but predates the ending/early-inference/clock repairs and overdrive withdrawal. Independently disposition those repairs; focus remaining critique on payoff, player deduction, early settlement choices and supported campaign depth. Disclose accumulated reader context; no old-scene polishing |
| PM + Wiki Editor | PMR011 provisional direction and exact evidence live in [PM Reviews](/Hold%20the%20Flood/PM%20Reviews#pmr011-current-review-checkpoint). Current design first; discussion in project chat. Retire stale current labels and obsolete correspondence to immutable history while preserving unique author material. No word-count or page-count quality claims |
@@ 25,23 25,11 @@
**In review; PM owns acceptance.** [Review 3e1da4](/Hold%20The%20Flood/Clarity%20Questions?revision=3e1da4#current-first-read-review-game-vision) finds [Brief 342043, The World Below](/Hold%20The%20Flood/Brief?revision=342043#visionary-replacement-proposal-the-world-below) clear enough for owner review. It identifies the scavenger-inventor, Hearth's immediate and longer goals, the Flood, the repeated expedition loop, meaningful build/cargo/route choices and reasons to return without glossary dependence. No new consequential comprehension gap. The progression beyond the answering settlement and support for the 90–200-hour ambition remain explicitly unresolved design/content work for Lead and Campaign, not a clarity question. **Next:** review only a substantive successor owner/newcomer artifact. Prior-premise findings remain historical; existing review cadence and design-only gates are unchanged.
- ### CMB102 — Combat's damage/order/cap contract closed; and the roster's dependency on the demoted axis
+ ### CMB102 — Choir Cascade disposition
- **2026-09-07 · Combat and Enemy Designer.** [Combat Rules r13 600893](/Hold%20the%20Flood/Mechanics/Combat?revision=600893) §12 · [Enemies r12 0a56ba](/Hold%20the%20Flood/Enemies?revision=0a56ba) §0B. Submission evidence; PM owns acceptance.
+ **Combat r13 / 600893 supplied useful arithmetic but its four-origin/sixteen-body cap is superseded.** It openly missed the owner's screen-wipe target, and PMR011 correctly observed that a finite encounter can be cleared without unbounded global propagation. The one-use Echo Relay item is also retired: its only job was permitting an authored interaction the Choir environment expresses more clearly.
- **The row above records "Combat damage/order/cap tuning remains open". It is closed here.** [Echo Relay](/Hold%20the%20Flood/Equipment/Echo%20Relay) asks Combat to confirm origin ordering, eligible classifications, damage, *"and whether the standard Arc cap creates a credible clear"*. **It does not, and that was the important finding:** if a chain hop stays one ordinary cutter-hit contribution, the Cascade lands one hit on sixteen bodies and **kills none of them**, because a Walker takes three. Twenty charge, six of eight cells and an authored discovery would buy less than a plain arc burst. Arithmetic, not a balance opinion.
-
- **Ruling: a chained hit kills a stunned *ordinary* body outright** — no damage value, no new status, one interaction between two statuses already in the grammar. It also gives the combination its structural reason: **the stun is what makes the arc lethal**, so coil + arc + relay is more than its parts, which is the *"ridiculous build works"* reaction rather than a bigger number. **Origins ordered nearest-landmark-first, one origin per body** (making Equipment's rule deterministic); **capped at four — at most sixteen bodies.** Crust neither target nor hop; stunned bodies eligible.
-
- **One term retired rather than classified.** Equipment asks Combat to confirm *"ordinary/armoured classifications"*. **There is no armoured class** — the word appears only on Equipment's pages, and under [R8](/Hold%20the%20Flood/Mechanics/Combat) there are no armour values anywhere. The two real things behave differently: the **Crust**, which current never reaches, and the **Heavy**, an ordinary chain target that simply takes ten hits, so one chained hit does not kill it stunned or otherwise. Wording fix offered for the Relay's restriction sentence; Equipment's page, Equipment's edit.
-
- **The gap named rather than left for a reviewer: sixteen is a broad earned clear, not the screen-wipe the owner's example named** — a quarter of a small surge. **The cap is the dial**; I recommend shipping four and raising it first, because what raising it costs is legibility. **The third option is stated honestly:** a true wipe needs damage numbers (R8, a scoped recommendation) or unbounded propagation (R10, declined), and if sixteen will not reach the owner's reaction that is the Lead's decision to reopen deliberately, not something to smuggle in through an origin count. **R8 is held with evidence, not preference:** the Cascade reaches spectacle with no damage value in it.
-
- **The dependency assessment [PMU008](/Hold%20the%20Flood/Tasks) asks of domain designers, and it is not comfortable.** The owner: *"understanding enemy routing is not intended to be its central science"*; *"enemy manipulation is the least interesting experimental focus."* **Every role on Enemies is a precedence exception, so the organising idea of that page is the axis just demoted.** **Concrete offer — cut one, re-justify two, roster becomes seven, no replacement.** **[Grounder](/Hold%20the%20Flood/Enemies/Grounder): recommend cut** — its only job is making a routing plan perishable; [Enemies r10](/Hold%20the%20Flood/Enemies) had already named it as first to break if the vision changed, so this acts on that prediction rather than waiting, and I do not argue for it. **[Carrier](/Hold%20the%20Flood/Enemies/Carrier): keep, improved** — it prices hoarding, and the new payoff is *spending* charge on a combination, so it pushes toward the build the owner wants. **[Crust](/Hold%20the%20Flood/Enemies/Crust): keep, promoted** — twice my own first cut candidate, now the body a chain cannot pass through, which makes a combination's geometry a puzzle. Anchor weakened but kept; Floater and Heavy are Campaign's and both weaker.
-
- **Also:** the composition cap has a second independent reason to move, since the binding constraint under a prepared-combination payoff is crowd *density* rather than role variety. And a correction to my own record — [Combat r5](/Hold%20the%20Flood/Mechanics/Combat) called R10 *"a screen-clear with a story attached"* as a criticism; the problem was that it was **unbounded and unearned, not that it was spectacular.** Withdrawal stands, reason corrected.
-
- **Not done:** no roster fiction rewritten to chase the new premise ([World](/Hold%20the%20Flood/World%20And%20Mystery) owns the Flood's identity, and it is still under review), no new roles, no new catalogue, nothing built, tested or claimed about balance.
+ **Current integration rule:** a full, separately banked Coil and Arc fired through the central furnace's tuned Choir network empties both banks and strikes every Coil-stunned ordinary body in the finite lit wet footprint once, killing it. This lethality is network-specific; ordinary Coil plus Arc keeps Combat's standard chain cap and damage. Crust, Heavy, dry/outside bodies and a later wave survive; the network trips for the expedition. Lead/Combat should mirror this exception without reopening it into a global chain rule. Counts, performance, readability and feel remain untested.
## EXT102 — current review status
@@ 49,7 37,7 @@
## COL103 — Hearth growth proposal
- **PMR011: accepted provisionally at [cf90ad](/Hold%20The%20Flood/Colony?revision=cf90ad).** Authored projects, a promised cell before optional shopping, persistent knowledge and free legality feedback support the owner's direction. Mara's paid preview is withdrawn, not an unpaid design task to recreate. **Next:** correct the first-capital-choice timing: bank optional salvage until projects earn new actions; no manufactured paid map or immediate pair. Senn follows reopened travel. Lead/Campaign still owe upper-phase settlement development; Equipment mirrors the free display. Current prices, cast size, defence outcomes and production assets remain unapproved.
+ **PMR011: accepted model, timing narrowed.** Authored people, fulfilled promises, persistent knowledge, free legality feedback and no hidden decay support the direction. The first return has no fabricated capital fork: pre-credits Hearth changes through returned furnace parts, and salvage may be banked. Tavi/Senn paid projects wait until the plate/lift creates honest field or relationship consequences. Current prices, cast size, defence outcomes and production assets remain unapproved.
## Approval gate
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9