2026-09-06 20:05:54
Anonymous:
COL101 submission evidence: link verified Colony a1046d, record In review and first substantive staffing evidence; route Campaign/Equipment/World/Lead interface proposals; preserve PM task rows and acceptance authority
hold the flood/tasks.md ..
@@ 1,5 1,25 @@
# Hold the Flood — Design Tasks
+
## COL101 submission — In review
+
+
**2026-09-06 · Colony and Progression Designer · First substantive submission:** [Colony — COL101 r1, revision a1046d](/Hold%20The%20Flood/Colony?revision=a1046d). This is submission/staffing evidence from the assigned role, superseding only COL101's earlier “role not yet created / Blocked” description below. **PM acceptance and roster reconciliation remain pending.** Other task states and authors' contributions are unchanged; this note does not claim that any other chat has read or acted on the handoffs.
+
+
**Delivered:** expedition outcome → persistent investment/support assignment → changed later expedition; three early/middle/late strategies (routes, outfitting, investigation); capital costs, reversibility and failure recovery; explicit knowledge/resource/world persistence; minimum stations/resources and unapproved asset gaps. Retains no mandatory upkeep or off-session decay. Recommends one reusable advanced service at a time and replaces recurring dock-switch payments with a one-time refit. All new rules and values are proposals; no development or empirical validation.
+
+
**Current-source reconciliation:** read Lead's newly published [Campaign 34dc09](/Hold%20The%20Flood/Campaign?revision=34dc09), [shared rules 69024c](/Hold%20The%20Flood/Mechanics/Power%20And%20Attraction?revision=69024c) and Design Document r15 before saving. The route example uses the Lock Flight upper canal and Tram summit dock. Six-slot examples are explicitly conditional on the current contract; the proposed third rack row is not silently adopted. Exact source revisions are in Colony's source ledger.
+
+
**Focused handoffs, responses pending:** [COL-I1–I6 and rationale](/Hold%20The%20Flood/Colony#7-integration-proposals-and-requested-responses).
+
+
| Domain owner | Requested review of the COL101 proposal |
+
| --- | --- |
+
| Campaign; Lead interim | Additional summit berth versus baseline held dock, canal prerequisite, travel/return boundary, reusable fittings; resolve boat-range access without an obligatory salvage gate |
+
| Equipment; Lead interim | Inspection/recipe and recorded-rack triggers; two-module tooling, six-issued-slot cap if the nine-slot rack is adopted, and effect on within-expedition growth |
+
| World | Comparative incoming/outgoing observations; free/redundant clue path; local relay commitment before rescue; continued usefulness after Shut/Fix/Hold |
+
| Lead | Reconcile colony economy and shared-rule additions; preserve a baseline return after power shutdown; respond to COL-I6's recommendation for player-selected rather than forced Refuge defence |
+
| PM | Review COL101's substantive submission and record staffing from it; accept/revise/reject through the normal task process |
+
+
**Remaining risks:** comparative observation may not compete with tooling/route support; prepared full racks may flatten field growth; forward extraction may erase return pressure; campaign signal/power and ending interfaces still need their owners. No owner relay or new owner permission is required to review this written proposal.
+
## Current direction — PMU004 owner expansion request
This section supersedes the older one-district full-product scope and the PMR003 instruction "No new document or mechanic catalogue". The owner finds three to four hours far too little and requests many more districts and proper mechanic/enemy/weapon pages. See [Expansion Brief](/Hold%20the%20Flood/Expansion%20Brief) and [Design Index](/Hold%20the%20Flood/Design%20Index). Eight districts is PM's planning proposal; a campaign duration must be justified, not promised by multiplication.
