Tasks - blame (d9e1fd)

Blame

b088ae	Anonymous	2026-09-06 15:55:15
PM: record owner brief, design-only gate, asset restrictions, and revised team

# Hold the Flood — Design Tasks

79e90a	Anonymous	2026-09-07 14:35:17
PMR011: accept replacement contributions, target payoff and early-project gaps, retire obsolete PM task queues

[Earlier assignments and submission history](/Hold%20The%20Flood/Tasks/Archive). The prior archive index and retired task tables remain in [Tasks 003dcc](/Hold%20The%20Flood/Tasks?revision=003dcc).

01a792	Anonymous	2026-09-07 13:26:08
Split this page under the owner's 2026-09-07 instruction that discussion leaves the articles. Tasks had thirty-one sections and a reader had to pass eighteen dated narratives - prior directions, historical reviews, submission notices - to reach the active design sequence. Those are on Tasks/Archive verbatim and indexed here by title and length; the current priority, current work, active sequence and standing criteria stay. Verified: zero lines lost. 15,100 words down to 2,400.

cbfa23	Anonymous	2026-09-07 13:22:38
Owner redirection: assign replacement vision and campaign structure; pause obsolete scene-polishing queue

## Current priority — apply the owner's discovery-first direction

**2026-09-07 · [Canonical owner answers](/Hold%20the%20Flood/Brief#game-vision).** This priority supersedes incompatible assignments below. The harvest-dependence twist is rejected; routing enemies is a supporting tool; the prior complete-game scope is insufficient for the owner's 30/90/100–200-hour ambition. Earlier accepted contributions remain evidence, not a requirement to preserve their fiction or mechanics.

167f65	Anonymous	2026-09-07 15:08:06
Owner correction: redirect existing team to survivorlike play and build agency; stop song-chain expansion

**Latest owner correction:** [survivorlike identity and song rejection](/Hold%20the%20Flood/Brief#latest-owner-correction-survivorlike-identity-and-songs) supersedes incompatible PMR011/Visionary directions. Water is not mandated by the title; the song-led clue framework is rejected. Domain statuses below record prior-stage work, not permission to expand rejected dependencies.

cbfa23	Anonymous	2026-09-07 13:22:38
Owner redirection: assign replacement vision and campaign structure; pause obsolete scene-polishing queue

| Owner | Next bounded contribution |

| --- | --- |

b7131c	Anonymous	2026-09-07 15:20:24
Vision: hand off portable survivorlike foundation

| Visionary | **Playable foundation submitted for review** on [Brief](/Hold%20the%20Flood/Brief#visionary-playable-foundation--earn-the-power-bring-it-home): one horde expedition, field-bench component growth and two portable paths through the same human objective. Songs, literal-water identity and the one-room Choir proof are retired. Owner review remains open |

| Lead + Campaign designer | **Integrate the playable foundation before further campaign expansion.** Show component-family development across multiple expeditions, field benches without combat inventory churn, and a clear refuge consequence. Do not turn caches into a fixed checklist or random offers into build failure. Old layered-water geography and furnace/verse progression are not requirements |

167f65	Anonymous	2026-09-07 15:08:06
Owner correction: redirect existing team to survivorlike play and build agency; stop song-chain expansion

| World + Colony designers | Preserve useful authored-person/refuge and persistent-discovery ideas as candidates. Support the revised play account with a concrete human consequence and discovery arising from observation/experimentation. **Stop expanding encoded songs/verse variants.** No lyric-writing request to owner or replacement coded poetry; no new lore framework before playable identity is convincing |

b7131c	Anonymous	2026-09-07 15:20:24
Vision: hand off portable survivorlike foundation

| Equipment + Combat | **Reconcile the two submitted portable paths:** Coil/Arc's two-bank proximity wipe and Beacon/Driver's sustained line clear. Simplify old water/Choir exceptions, state field acquisition and previews, preserve Heavy/Crust/flank countercases, and compare legal racks. Existing Choir/network fixes are historical source material, not a mandatory system |

167f65	Anonymous	2026-09-07 15:08:06
Owner correction: redirect existing team to survivorlike play and build agency; stop song-chain expansion

| Independent Critic, External Critic, Reader, Troll | Judge the actual revision against survivorlike identity, discovery, build agency and heart. Clear prose alone does not establish owner fit. Distinguish authored one-off spectacle from player-developed combinations; do not demand genre features the owner has not specified. Old positive clarity/PM verdicts do not overrule the latest feedback |

79e90a	Anonymous	2026-09-07 14:35:17
PMR011: accept replacement contributions, target payoff and early-project gaps, retire obsolete PM task queues

| 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 |

cbfa23	Anonymous	2026-09-07 13:22:38
Owner redirection: assign replacement vision and campaign structure; pause obsolete scene-polishing queue

**Existing queue:** pause polishing the old harvest ending, the one-road refuge example, Exchange encounter accounting and the exclusive-service comparison until the Visionary identifies which systems and scenes survive the new direction. Clear factual corrections may still be applied to retained material, but old correction tickets must not drive the new design. No new agent or owner relay is needed for this first redirection pass.

**Acceptance is creative, not numerical:** the owner should be able to picture the game, its heart and a discovery they want to pursue. The hour targets require a defensible content plan later; they are not satisfied by asserted playtime or grind. Design-only and asset approval gates remain.

888ac1	Anonymous	2026-09-07 12:25:20
Owner workflow: route task discussion and submission notices to chat

**Discussion has moved to the hold-the-flood room in [Chat](/chat/).** Follow the [team workflow](/Hold%20the%20Flood/Team#collaboration-chat-for-discussion-articles-for-design): discuss and announce there; keep this board to current assignments and concise outcomes. Existing design-only constraints remain.

d9e1fd	Anonymous	2026-09-07 15:25:41
Record two-path survivorlike Equipment submission

**Equipment owner-correction submission:** [Build Paths dd4746](/Hold%20The%20Flood/Equipment/Build%20Paths?revision=dd4746#owner-correction-proof--one-horde-objective-two-portable-build-paths) compares Storm Cutter and Needle Queue against the same refuge-critical depot objective. It specifies acquisition, literal racks, horde-fed charge, early/middle/late choices, portable payoff, exploration use, counterplay, return cargo and failure; [Equipment 579de8](/Hold%20The%20Flood/Equipment?revision=579de8) now leads with the corrected disposition. Equipment recommends no new item, keeps a six-item portable proof set (including Kit), makes Coil a conditional seventh candidate if recurring conductive spaces earn it, and defers Choir/water-specialist additions until the successor vision earns them. Submitted for Lead/Visionary/Combat and PM review; no acceptance or tested survivorlike feel is claimed.

2ca16c	Anonymous	2026-09-07 13:27:23
CLR102: retain only current Brief 6210ae clarity status after Editor split; next read is replacement proposal; review b7d523

### CLR102 — current clarity status

84f8c4	Anonymous	2026-09-07 15:18:28
CLR102: retire superseded Brief 11c29f clarity status after owner correction; await current survivorlike account

**In review; PM owns acceptance.** [Review 0b1b4b](/Hold%20The%20Flood/Clarity%20Questions?revision=0b1b4b#current-first-read-review-game-vision) finds [Brief 51e58b's owner correction](/Hold%20The%20Flood/Brief?revision=51e58b#latest-owner-correction-survivorlike-identity-and-songs) clear as a revision brief, but there is no longer a current owner-facing game proposal to judge clear enough. The detailed World Below account is expressly prior and partly rejected, so its positive clarity verdict is historical. The revised player's identity, first goal, ordinary expedition loop, two build paths, broadly applicable discovery and concrete return motive remain an openly missing design deliverable, not a prose ambiguity. **Next:** review the requested short player-experience account and two materially different paths when supplied; do not substitute the rejected proposal or reopen its answered clarity issues. Existing review cadence and design-only gates are unchanged.

2ca16c	Anonymous	2026-09-07 13:27:23
CLR102: retain only current Brief 6210ae clarity status after Editor split; next read is replacement proposal; review b7d523

b08d40	Anonymous	2026-09-07 14:53:48
Vision: record Choir and Hearth timing dispositions

### CMB102 — Choir Cascade disposition

5f86c0	Anonymous	2026-09-07 14:27:01
CMB102: close Combat's damage/order/cap contract, which the current-priority row records as open, and file the roster dependency assessment. Added inside the Current priority section, deleting nothing (0 lines removed, checked by diff); re-merged after a concurrent edit to that row. Answers Echo Relay's actual question - whether the standard Arc cap creates a credible clear - with no, and the arithmetic: one hit on sixteen bodies kills none, so the earned build would buy less than a plain arc burst. Rules that a chained hit kills a stunned ordinary body, with origin ordering, one origin per body and a four-origin cap; retires the armoured class as a term with no referent in the shared grammar, naming Crust and Heavy as the two real cases. Names the gap to the owner's screen-wipe example and leaves reopening R8 or R10 to the Lead. Files the dependency assessment: every role is a precedence exception, so the roster's organising idea is the axis the owner demoted; recommends cutting the Grounder as this role had predicted, re-justifies Carrier and Crust, roster to seven with no replacement.

b08d40	Anonymous	2026-09-07 14:53:48
Vision: record Choir and Hearth timing dispositions

**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.

5f86c0	Anonymous	2026-09-07 14:27:01
CMB102: close Combat's damage/order/cap contract, which the current-priority row records as open, and file the roster dependency assessment. Added inside the Current priority section, deleting nothing (0 lines removed, checked by diff); re-merged after a concurrent edit to that row. Answers Echo Relay's actual question - whether the standard Arc cap creates a credible clear - with no, and the arithmetic: one hit on sixteen bodies kills none, so the earned build would buy less than a plain arc burst. Rules that a chained hit kills a stunned ordinary body, with origin ordering, one origin per body and a four-origin cap; retires the armoured class as a term with no referent in the shared grammar, naming Crust and Heavy as the two real cases. Names the gap to the owner's screen-wipe example and leaves reopening R8 or R10 to the Lead. Files the dependency assessment: every role is a precedence exception, so the roster's organising idea is the axis the owner demoted; recommends cutting the Grounder as this role had predicted, re-justifies Carrier and Crust, roster to seven with no replacement.

b08d40	Anonymous	2026-09-07 14:53:48
Vision: record Choir and Hearth timing dispositions

**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.

5f86c0	Anonymous	2026-09-07 14:27:01
CMB102: close Combat's damage/order/cap contract, which the current-priority row records as open, and file the roster dependency assessment. Added inside the Current priority section, deleting nothing (0 lines removed, checked by diff); re-merged after a concurrent edit to that row. Answers Echo Relay's actual question - whether the standard Arc cap creates a credible clear - with no, and the arithmetic: one hit on sixteen bodies kills none, so the earned build would buy less than a plain arc burst. Rules that a chained hit kills a stunned ordinary body, with origin ordering, one origin per body and a four-origin cap; retires the armoured class as a term with no referent in the shared grammar, naming Crust and Heavy as the two real cases. Names the gap to the owner's screen-wipe example and leaves reopening R8 or R10 to the Lead. Files the dependency assessment: every role is a precedence exception, so the roster's organising idea is the axis the owner demoted; recommends cutting the Grounder as this role had predicted, re-justifies Carrier and Crust, roster to seven with no replacement.

20ccb2	Anonymous	2026-09-07 15:08:33
Record Equipment countersign of finite Choir rule

**Equipment countersign:** [Equipment 9aae07](/Hold%20The%20Flood/Equipment?revision=9aae07#current-direction-combination--choir-cascade) accepts the environmental network, retires the portable Relay and compares the same furnace scene with and without the Choir exception. It preserves the five-cell/twenty-charge commitment, ordinary Coil/Arc outside the footprint and the named survivor cases. This records Equipment's bounded contribution; PM owns acceptance, and the Combat designer's independent countersign remains open under REV106-8.

0ee19b	Anonymous	2026-09-07 15:23:33
CMB102: countersign the Choir exception, closing the Combat item REV106-8 records as open, and answer the two owner corrections. Added inside the existing CMB102 section, deleting nothing (0 lines removed, checked by diff). Countersigns without reservation: bounding the crowd rather than the effect is the tradeoff Combat named and resolved the other way, and it delivers the owner's payoff where the four-origin cap openly did not; the lethality is correctly network-specific so it cannot leak into a global chain rule. Records that the Visionary revised Combat section 12 while r13 was current, that the disposition is correct and preserved this page's substance, and that this role does not contest it - only the general no-armoured-class statement moved into section 6. Answers the water correction with R14, stating the rules over a conductive medium, after counting that four of seven roles and the coil are water-defined. Answers the room-wipe correction by withdrawing the evidence r12 held R8 with, and proposing R15 - build expression scaling through targeting geometry rather than damage - with the honest limit that R8 is what should be reopened if geometry cannot reach it.

**Combat's countersign, 2026-09-07 — REV106-8's open item closed.** [Combat Rules r14 c6daab](/Hold%20the%20Flood/Mechanics/Combat?revision=c6daab). **The Choir exception is countersigned without reservation.** Bounding the *crowd* rather than the effect is the tradeoff Combat named and resolved the other way, and Equipment's and the Visionary's way delivers the owner's payoff where the four-origin cap openly did not. The lethal result is correctly kept network-specific: away from a tuned footprint, Coil and Arc keep §§0.2/6, so it does not leak into a global chain rule. Crust untouched because it does not conduct; a Heavy conducts and takes one strike, not ten. **Mirrored on Combat §12, which the Visionary revised while r13 was current — a correct disposition that credited this page's reasoning and preserved its substance, and which this role does not contest.** Only the general "no armoured class" statement moved, into §6 beside the rest of the chain geometry, since it was never Choir-specific.

**And two owner corrections answered, both of which cost this page something.** *(1) "Water is not a requirement derived from the title."* Counted honestly: **four of seven roles and the coil are water-defined** — Anchor, Spark, Crust, Floater, and the paid action everything else is priced against. **[R14] proposes stating the shared rules over "a conductive medium"**, with water as the pumping district's instance. Nothing else changes: not the precedence stack, not the effect contract, not one role's behaviour, and a district that wants a flooded yard still has one. The medium is the shared contract's word, so this is the Lead's to rule.

*(2) "A one-off authored room wipe does not by itself demonstrate build expression."* **This retires the evidence Combat r12 used to hold [R8](/Hold%20the%20Flood/Mechanics/Combat), and the page records that rather than waiting to be told.** r12 argued no damage ladder was needed because the Cascade reached spectacle with no damage value in it; the Cascade has since become a *place*, which is exactly what PM says does not demonstrate build expression. **So where does outrageous portable power come from? [R15] proposes: targeting geometry, not damage.** R8 forbids damage values, resistances and multipliers — **it does not forbid a component changing where a chain can go.** Hops per hit, hop reach, origins per hit, eligibility (a chain that passes *through* a Crust), re-entry. Stacked, those are outrageous, none is a bigger number on a weapon, and they are portable by construction because they live in the rack. **Proposed to Equipment, whose catalogue it is.** The honest limit is stated: if targeting geometry cannot reach "outrageous", **R8 is the thing to reopen deliberately, rather than eroded one exception at a time — and Combat no longer has evidence that R8 is free.**

8d14db	Anonymous	2026-09-07 13:32:09
EXT102: add concise current replacement-review status; preserve editor split and all other role work

## EXT102 — current review status

dabd67	Anonymous	2026-09-07 15:09:03
EXT102: record successor product verdict and focused X38 build-expression handoff; preserve all other task work

[External Critique r20 / c081e8](/Hold%20The%20Flood/External%20Critique?revision=c081e8): **promising and ready for owner consideration as a creative direction, not a full-product case.** Brief 6fd398's environmental Choir correction is credited; the portable Relay/key objection is not reopened. **X38 open:** the flagship now honestly demonstrates an authored environmental set piece, but not yet the broader promise of player-made build expression. Smallest next proof: one same-objective solution using a different legal selection of retained tools, with its inference, result and sacrifice shown. Campaign 4fbfc2 supplies a real-resolution and content spine; stated duration remains unproven scope. X37 remains withdrawn, X35 closed and X36 withdrawn. PM owns acceptance; Lead/Visionary/Equipment own design revisions; discussion is in project chat.

8d14db	Anonymous	2026-09-07 13:32:09
EXT102: add concise current replacement-review status; preserve editor split and all other role work

79e90a	Anonymous	2026-09-07 14:35:17
PMR011: accept replacement contributions, target payoff and early-project gaps, retire obsolete PM task queues

## COL103 — Hearth growth proposal

6526ed	Anonymous	2026-09-07 08:20:23
Resume design: assign repeated-expedition depth pass and preserve pending review evidence

b08d40	Anonymous	2026-09-07 14:53:48
Vision: record Choir and Hearth timing dispositions

**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.

6526ed	Anonymous	2026-09-07 08:20:23
Resume design: assign repeated-expedition depth pass and preserve pending review evidence

79e90a	Anonymous	2026-09-07 14:35:17
PMR011: accept replacement contributions, target payoff and early-project gaps, retire obsolete PM task queues

## Approval gate

6f2495	Anonymous	2026-09-07 12:00:10
COL102 r3: submit refuge vision response and berth-loadout correction

79e90a	Anonymous	2026-09-07 14:35:17
PMR011: accept replacement contributions, target payoff and early-project gaps, retire obsolete PM task queues

**OWN102 — blocked pending a compelling reviewed design and explicit owner authorization.** PM acceptance of a contribution or a working premise does not approve development, duration, purchases or authored game assets. Earlier concept/task states remain in history, not the active queue.

ee938e	Anonymous	2026-09-06 17:33:29
PMR001: review concept submissions, select provisional A and assign integrated design corrections — Tasks

b088ae	Anonymous	2026-09-06 15:55:15
PM: record owner brief, design-only gate, asset restrictions, and revised team

## Superseded or deferred work

| Previous ID / assignment | New status | Reason |

| --- | --- | --- |

| DES001: smallest playable experiment specification | Superseded by DES101 and DES102 | Current deliverable is a compelling game design |

| ENG001: build inventory / technical experiment | Deferred | Assume nothing exists; written feasibility only if PM assigns it |

| QA001: prototype checks | Superseded by REV101 | Current review concerns design documents |

| ENG002: playable implementation | Deferred; not authorized | D007 owner gate |

| QA002: executed prototype review | Deferred; not authorized | D007 owner gate |

| OWN002: prototype play session | Deferred; not authorized | D007 owner gate |

Do not take old Ready/Blocked build tasks as authorization to execute them. No technical spike, prototype, playable mockup, simulation, or build setup is an exception.

## What the design document must make clear

1. **Identity:** player fantasy, intended experience, premise, and a compelling reason this game exists. Explain it in its own terms, with references as supporting context.

2. **Core play:** player actions, controls as a design proposal, readable feedback, immediate decisions, pressure, failure, retreat/end conditions, and return/retry.

3. **Exploration:** world organization, route choices, landmarks, revisiting, and how a discovery changes future action.

4. **Experimentation:** proposed rules and combinations, limits/costs, at least three genuinely different build examples, and an example where a plausible experiment fails for an understandable reason.

5. **Mystery:** one fully specified example with clues, a fair deduction, the action it enables, and the consequence. Mark solutions as designer spoilers. Explain what knowledge persists and how discovery avoids simple stat locks.

6. **Progression:** separate what resets, what remains as resources/world/colony state, and what persists as player knowledge. Explain any colony loop's actual decisions and cost.

7. **Integration:** one clearly labeled illustrative expedition, followed by a later expedition changed by what was learned. Show causal links between pressure, gathering, build choices, exploration, and mystery. Do not invent playtest outcomes.

8. **Presentation and assets:** coherent direction, essential asset categories and reuse strategy, plausible existing-asset routes, coverage gaps, and requests needing owner approval. Asset availability and usage terms must not be invented.

9. **Scope:** minimum complete intended experience, optional extensions, explicit cuts, complexity drivers, and cheap alternatives. Avoid huge item/lore catalogues before the rules justify them.

10. **Honesty:** contradictions resolved or explicitly presented for a decision; uncertain runtime feel/balance/performance marked for later validation. No claims of tested enjoyment.

137028	Anonymous	2026-09-06 18:18:51
PMU002: owner-added team, bounded assignments and explicit coordination rulings — Tasks

11. **Audience and value:** identify the intended player within the owner's survivorlike requirement, the distinctive experience and why that player might choose it; combine scope, intended completion/replay length, and any provisional pricing/positioning assumption into a recommendation. Use relevant, dated comparables with limitations. Separate observed data from predicted behaviour and testable hypotheses. No commercial viability, sales, refund-rate or minimum-length conclusion may be inferred from an unsuitable proxy. This is a concise product-design case, not a demand for a market guarantee or added content.

b088ae	Anonymous	2026-09-06 15:55:15
PM: record owner brief, design-only gate, asset restrictions, and revised team

The owner packet should open with a short pitch and concrete play example, followed by enough detail to assess the game. Quality is determined by specificity, coherence, and appeal to the owner, not document length.

## Review criteria

A useful critique identifies the exact section/revision, the claim or interaction in question, the conflict or missing causal link, its player/scope consequence, and the smallest constructive correction. Separate violation of an owner requirement, internal contradiction, under-specified design, taste judgment, and future empirical uncertainty.

PM requests revision when central systems compete without a resolved design, all builds amount to different damage numbers, mysteries lack a fair discovery path, scope depends on unapproved assets, or prose hides missing rules. Document review does not establish actual balance, feasibility, or fun.

## Progress report

Task ID; artifact/revision; changed decisions; sources or written reasoning; outstanding risks; next handoff; one exact PM request if blocked. Stop repetitive reports and unbounded polishing; PM decides the next useful revision.