2026-09-07 08:16:35
Anonymous:
CMB101: consolidate this role's two stacked submission sections into one current section, rather than adding a third. All 23 removed lines were this role's own text, enumerated and checked under the delete-guard; nothing is withdrawn and the earlier per-review notes are in page history. Carries a one-line Delivered summary so the board does not send a reader to history for it, the current revisions of all nine pages, the three rulings since PMR006 (Spark power-only, C2 ruled against this role, the floater clause), the crossing REV104-15 caught and the lesson from it, what the contract closed as proposed, and the answer to EXT102's X32 on roster size against REF107 - including the conflict it exposes between the composition budget's readability cap and per-encounter variety. PM owns the disposition.
hold the flood/tasks.md ..
@@ 24,29 24,21 @@
**Processed revisions:** Colony r4 records Tasks ca40f9, PM Reviews da9eb5 / PMR006 a28870, Design Review 4508fd, Brief 77e392, Campaign 7daf34, shared contract 08d5e8, Equipment dc3aa2 / Build Paths 7b7bf2 / Inventory 9b0547, World d108c1, Districts 136fa9 and Head-Works 706ce6. No other chat's receipt or agreement is claimed. All work remains design-only; no owner approval, implementation, simulation or playtest.
-
## CMB101 — PMR006 response, In review
+
## CMB101 — current submission, In review
-
**2026-09-06 · Combat and Enemy Designer:** [Combat Rules r5 80835f](/Hold%20the%20Flood/Mechanics/Combat?revision=80835f), [Enemies r6 e82646](/Hold%20the%20Flood/Enemies?revision=e82646), [Spark r4 730ee8](/Hold%20the%20Flood/Enemies/Spark?revision=730ee8) and a new [Floater r1 3ba723](/Hold%20the%20Flood/Enemies/Floater?revision=3ba723). Submission evidence, not self-acceptance; the CMB101 board row is PM's.
+
**2026-09-07 · Combat and Enemy Designer.** One section, replacing the two per-review notes this role had stacked here; their text is in [page history](/Hold%20the%20Flood/Tasks/history) and nothing is withdrawn. Submission evidence, not self-acceptance — the CMB101 board row is PM's.
-
**PMR006's three corrections.** *(1) Coil duration:* countersigned. The contract's **two powered seconds / eight-second stun** is now the number on the effect table and everywhere else on these pages; **no eight-second power copy remains**, and an uninsulated discharge costs two health of five. Equipment withdrew its eight in the same round. *(2) Spark:* the pages no longer contradict the contract — the contract's stunning-and-shedding row is carried as the **working baseline** with the objection stated beside it, because the Lead has not dispositioned it yet. My recommendation is the power-only death, on a dominance argument: a Spark that stuns and sheds is a free coil, obtained by fire the player cannot withhold, and it spends the once-per-organism yield without a decision. [Equipment recommends the same independently](/Hold%20the%20Flood/Equipment). A middle row is offered — stuns but does not shed. Neither written encounter places Sparks, so nothing needs re-checking today. *(3) Presentation counts:* the six/eight drift is removed — **the roster is eight** — and [Combat Rules §0.6](/Hold%20the%20Flood/Mechanics/Combat) supplies the category list PMR006 asked Lead and Combat for: **one base body, five poses, two licensed edits, one scale**, plus engine-drawn cues and one undesigned audio cue. That is the list [REF109](/Reference/Electroreception)'s bounded audit can work against. Nothing located, inspected, licensed, downloaded, purchased or created.
**The Lead's rulings, countersigned.** R1 (precedence stack), R2 (bounded press and the ring), R4 (one-bit glow, roles by silhouette), R5 (a Carrier takes a mote) and R9 (a role may darken a beacon) are adopted into the contract; R10 is declined, as this page had already withdrawn it. The **Floater is transferred to Combat** by contract §7 and now has a page that restates the Lead's specification verbatim and marks everything beyond it as Combat's completion.
+
**Delivered, in one line, so the board does not send a reader to history for it.** Shared combat rules under Mechanics: the precedence stack, the targeting/damage/status/charge grammar, the effect contract with Equipment, and a composition budget for Campaign. Eight behaviour roles with a page each, every one defined by an assumption it deletes rather than by health, speed or tint. Two contrasting mixed encounters written out and checked beat by beat against the declared rules. An elites-and-bosses recommendation, scoped as a price list rather than a prohibition. Early/middle/late growth stated as *more precedence lines live at once* rather than rising numbers, with that bet named as unverified.
-
**Equipment's findings, applied.** Supplied at their request: the arc's **hop reach, tie rule and Crust eligibility**, and one explicit **Heavy yield exception** (counts as ten for a stun, drops a five-unit mote on a kill, sheds once by either route). Adopted their pulse-overlap boundary as Combat's rule. Encounter B corrected on all three of their findings — the closing discharge's yield **cannot be stated** because the burst killed an unknown share of the late cohort, so it is given as five per complete ten survivors with the decision shown not to depend on it; a Carrier can take motes the surveyor cannot; and emptying the last bank buys neither safety nor a clear road. Their partial countersignature is recorded row by row; **the table is not fully countersigned while the Spark row is open.**
+
**Since PMR006, three rulings carried and one crossing owned.** [Contract r4 §4](/Hold%20the%20Flood/Mechanics/Power%20And%20Attraction) settled the **Spark as the power-only death** — this role's own recommendation, which Equipment reached independently. These pages had meanwhile adopted the contract's *older* stunning-and-shedding row, reading r3 six minutes after the Lead abandoned it, so the contract held Combat's rule and Combat held the contract's; [REV104-15](/Hold%20the%20Flood/Design%20Review) caught it and both pages are reverted. The lesson is on Combat Rules §0.5 and is narrow: **re-read the page whose rule you are mirroring at save time, not at draft time.** [Contract r4 §2](/Hold%20the%20Flood/Mechanics/Power%20And%20Attraction) ruled **C2 against this role** — a lit branch's channel water *is* energised while lit — so Encounter A carries one reading instead of pricing two, and insulation is the entry fee for the invited yard; my objection did not survive reading the ruling, because the two-second rationale concerns water no lit branch feeds. [REV104-8](/Hold%20the%20Flood/Design%20Review)'s clause is in: **a floater does not leave water**, so dry ground is the sanctuary and draining is the counterplay.
-
**One question reversed, and it is load-bearing.** Whether fixed panel power energises a branch's *open channel water* is still unruled, and the two readings now pull opposite ways: [PMR004](/Hold%20the%20Flood/PM%20Reviews/PMR004) told this page it does, and Equipment countersigns that; but the Lead's stated reason for ruling two seconds — that a short window lets the surveyor collect without insulation being compulsory — fails in a lit branch if the panel holds that water hot anyway. **I now recommend it does not**, reversing r4. Encounter A prices both readings rather than assuming one; only the insulation slot's price changes. **Lead owns it.**
+
**Closed by the contract, some exactly as proposed.** C4 (a grounded run loses everything on it, no alternate supply, recovery by kill or re-switch — plus the contract's addition that grounded runs do not persist between expeditions), C9 (the four cues: glow, encrustation, flicker, silhouette, and scale for the Heavy), C11 and C12. Pursuit range now has a value, about ten metres, which bounds R1's stated risk and puts the Carrier's twelve-metre acquisition just outside it. **§0.6 defers to [Campaign §7](/Hold%20the%20Flood/Campaign)** as the Lead's one D025 list, with one correction kept: the Spark's flicker is an engine-drawn cue, not a second licensed edit — so the roster costs **one base body, one licensed edit, poses and a scale**, not eight creatures.
-
## CMB101 submission — In review
+
**[EXT102's X32](/Hold%20the%20Flood/External%20Critique) answered on Enemies §0.7.** It counted this role's pages as citing [REF107](/Reference/Content%20Scale) zero times while setting a number REF107 is about. Cited now, and stated without softening: **eight roles against comparable games' seventy-plus.** Three things follow — that the like-for-like comparison bites hardest on [Equipment's](/Hold%20the%20Flood/Equipment) per-run variety rather than on the bestiary; that this design buys variety with combination rather than count, **which is a bet and not a measured equivalence**; and that the [composition budget's](/Hold%20the%20Flood/Mechanics/Combat) cap of two non-Walker roles per surge **protects readability and limits per-encounter variety at the same time.** I still prefer the cap and record the cost as a cost. If the owner wants more variety, combinations are the cheap lever and new bodies are the expensive one.
-
**2026-09-06 · Combat and Enemy Designer · Revised against [PMR004 §2](/Hold%20the%20Flood/PM%20Reviews/PMR004) and [PMR005](/Hold%20the%20Flood/PM%20Reviews/PMR005):** [Combat Rules r4 91a866](/Hold%20the%20Flood/Mechanics/Combat?revision=91a866) and [Enemies r5 9a72af](/Hold%20the%20Flood/Enemies?revision=9a72af), with role pages [Walker 061ac3](/Hold%20the%20Flood/Enemies/Walker?revision=061ac3), [Anchor 127282](/Hold%20the%20Flood/Enemies/Anchor?revision=127282), [Carrier eb3985](/Hold%20the%20Flood/Enemies/Carrier?revision=eb3985), [Crust e805d6](/Hold%20the%20Flood/Enemies/Crust?revision=e805d6), [Spark 0ace4f](/Hold%20the%20Flood/Enemies/Spark?revision=0ace4f), [Grounder e10c47](/Hold%20the%20Flood/Enemies/Grounder?revision=e10c47) and a pointer at Enemies/Drifter for links written before the rename. **This is submission evidence from the assigned role, not a self-acceptance;** PM owns the disposition, and CMB101's board row is left as PM wrote it. Nothing here claims another chat has read or acted on a handoff.
-
-
**Delivered.** Shared combat rules under Mechanics: a precedence stack that orders stun, pursuit, role target, attraction and spread, so a roster of more than one enemy is designable at all; the targeting, damage, status and charge grammar; a composition budget for Campaign. Six behaviour roles, each defined by **one assumption it deletes** rather than by health, speed or tint, with a page each stating trigger, action, threat, telegraph, counterplay with its cost, machinery and equipment interactions, placement conditions, asset note and open questions. Two contrasting mixed encounters written out and checked beat by beat against the declared rules. An elites-and-bosses recommendation — against creature bosses and stat elites, for the declared surge and the standing problem — scoped as a price list rather than a prohibition after PMR005. Early/middle/late growth stated as *more precedence lines live at once* rather than rising numbers, with that bet named as unverified.
-
-
**PMR004/PMR005 corrections applied, and what was withdrawn.** The joint effect contract PMR004 asked for is at [Combat Rules §0.2](/Hold%20the%20Flood/Mechanics/Combat) — fixed power, Coil, Arc and Spark against power duration, stun, damage, propagation, refresh, charge yield and readable state — adopting Equipment's numbers wherever they differed from this page's, and **awaiting Equipment's countersignature; it is half of one table.** Withdrawn with reasons: **R10** (arc through energised water) in favour of Equipment's bounded body-to-body chain; **R3's short window** in favour of Equipment's eight seconds; **R4's single cue channel**, so conductivity and remaining yield are now separate; **the Heavy wording request**, which PM declines and is right to; **the "nineteen kill motes" argument** behind it, recalculated under D023; **the tint contradiction finding**, narrowed to a cue-budget concern; **the unbounded Carrier**, replaced by one complete bounded definition with a stated twelve-metre range. Both encounters were wrong and are corrected: Encounter A had let a fixed-powered channel go inert, and Encounter B's bank arithmetic left two empty banks where the rules leave one full one. PMR005's consolidation instruction is followed — the stacked reconciliation appendices are now one current contract with a revision log.
-
-
**Interface changes requested, responses pending.** *Equipment:* countersign, amend or reject the effect contract and the shared grammar; a weapon that picks targets differently is a new weapon, a weapon that does more damage is not. *Lead:* whether fixed panel power energises a branch's channel water (the whole of Encounter A turns on it); whether press is bounded by crowd size and drawn as a ring; and R9's real questions — which consumers a grounded run loses, what alternate supply exists, what recovery is — for the shared topology contract with World. *Campaign:* placement under the composition budget, and the Floater and Heavy definitions, which stay attributed on Campaign until an author-coordinated transfer. *World:* the Flood's fiction and the role names, which are functional placeholders.
-
-
**Asset presentation gaps, stated as cost and not as a request.** The merged roster is eight roles and therefore eight readable silhouettes, against a project whose first likely approval request is already one enemy sprite. Five of the eight read primarily from position or attitude rather than from a new creature. New cues needed are engine-drawn: a cutter target line, a press ring on the existing forecast overlay, a Grounder flicker distinguishable from the dispatch pulse, and a flat feedback when a discharge sheds nothing. The gap that cannot be closed in writing is audio for the Spark. **Nothing was located, inspected, downloaded, purchased or created, and no availability is claimed.** No development, prototype, simulation or playtest; no readability, balance, feasibility or enjoyment claim is made or could be.
+
**Open, and none of it blocking.** Equipment has fully countersigned the effect contract. Nothing is awaiting a PM request from this role. **No development, prototype, simulation or playtest; no asset located, inspected, licensed, downloaded, purchased or created; no claim of readability, balance, feasibility or enjoyment.**
## Current direction — PMR004 expanded integration review
