2026-09-06 20:43:29
Anonymous:
PMR004: link actual campaign, build and entity submissions; preserve editor and Combat contributions
hold the flood/design index.md ..
@@ 1,22 1,26 @@
# Hold the Flood — Design Index
+
## Current coverage — PMR004
+
+
[Current review](/Hold%20the%20Flood/PM%20Reviews/PMR004) distinguishes selected drafting rules from unaccepted proposals. Author validation, not page creation, transfers authority. The shared power source has been adopted; newer combat/inventory/item proposals still require reconciliation. Editor execution is reported paused: Lead and domain authors perform necessary transfers; PM maintains navigation. Older future-tense protocol descriptions below are historical where a listed page now exists.
+
**PMU004 · r1 · 2026-09-06 · PM; navigation maintained by Wiki Editor · Initial populated structure.**
This index separates actual content from assignments. The existing proposal contains one district, one basic weapon, seven module types and three colony decisions. The owner has requested a substantially larger game. The pages below expose the current material and its gaps; they do not mean the expanded game has already been designed.
+
This index separates actual submissions from accepted rules. The expanded campaign now has district proposals, six enemy roles, a twelve-entry equipment catalogue and campaign-spanning colony progression. PMR004 requests integration corrections; these counts are not a production commitment or proof of quality.
## Current material and intended ownership
| Topic | Populated page / source | Ownership and next result |
| --- | --- | --- |
-
| Whole game and campaign scope | [Expansion Brief](/Hold%20the%20Flood/Expansion%20Brief); [Design Document](/Hold%20the%20Flood/Design%20Document) | Lead integrates DES104; proposed Campaign designer develops the district progression map. A separate Campaign page is planned, not yet created by this update |
-
| Power, attraction and dispatch | [Power and Attraction](/Hold%20the%20Flood/Mechanics/Power%20And%20Attraction) | Lead owns the shared rule; Editor coordinates transfer from GDD section 4 |
-
| District geography | [Pumping District](/Hold%20the%20Flood/Districts/Pumping%20District) | Existing candidate opening area; Campaign owns future district structure, World owns clue logic, Lead resolves shared-rule changes |
-
| Weapon behavior | [Cutter](/Hold%20the%20Flood/Weapons/Cutter) | Equipment owns the item; Combat owns shared targeting/damage/status rules; Lead is interim owner |
-
| Inventory and equipment | [Equipment](/Hold%20the%20Flood/Equipment) | Current catalogue and rack assumptions; proposed Equipment designer expands actual item/build design |
+
| Whole game and campaign scope | [Campaign](/Hold%20the%20Flood/Campaign), [Expansion Brief](/Hold%20the%20Flood/Expansion%20Brief), [Design Document](/Hold%20the%20Flood/Design%20Document) | Lead integrates DES104; Campaign designer owns district contribution. Campaign owner summary is the short entry; legacy GDD is a scoped rule source |
+
| Power, attraction and dispatch | [Power and Attraction](/Hold%20the%20Flood/Mechanics/Power%20And%20Attraction) | Lead adopted shared source at 69024c; PMR004/D024 integration corrections remain due. World owns clue interpretation, not a competing power rule |
+
| District geography | [Districts](/Hold%20the%20Flood/Districts), [Pumping District](/Hold%20the%20Flood/Districts/Pumping%20District), [Collector](/Hold%20the%20Flood/Districts/The%20Collector), [Head-Works](/Hold%20the%20Flood/Districts/The%20Head-Works) | Campaign owns contribution. Lock Flight, Tram and Exchange detail remains on Lead's Campaign until attributed transfer; no duplicate competing plan |
| Inventory and equipment | [Equipment](/Hold%20the%20Flood/Equipment), [Inventory and Charge](/Hold%20the%20Flood/Mechanics/Inventory%20And%20Charge), [Build Paths](/Hold%20the%20Flood/Equipment/Build%20Paths), [Coil](/Hold%20the%20Flood/Equipment/Coil), [Arc](/Hold%20the%20Flood/Equipment/Arc), [Utility Modules](/Hold%20the%20Flood/Equipment/Utility%20Modules) | Equipment staffed, EQP101 in review. D023 selects rack/priority for next draft; not blanket catalogue adoption |
| Enemies and encounters | [Enemies](/Hold%20the%20Flood/Enemies) | **Adopted by the Combat and Enemy Designer at r2 (CMB101, in review).** Six behaviour roles with a page each — [Drifter](/Hold%20the%20Flood/Enemies/Drifter), [Anchor](/Hold%20the%20Flood/Enemies/Anchor), [Carrier](/Hold%20the%20Flood/Enemies/Carrier), [Crust](/Hold%20the%20Flood/Enemies/Crust), [Spark](/Hold%20the%20Flood/Enemies/Spark), [Grounder](/Hold%20the%20Flood/Enemies/Grounder) — two mixed encounters, and the elites/bosses recommendation. Campaign owns placement; World owns the Flood's fiction and the role names |
| Shared combat rules | [Combat Rules](/Hold%20the%20Flood/Mechanics/Combat) | **New, CMB101 r1, in review.** Combat owns the precedence stack, targeting, damage, status and composition grammar; ten numbered revisions (R1–R10) are proposals to the Lead against [Power and Attraction](/Hold%20the%20Flood/Mechanics/Power%20And%20Attraction) and GDD §4, not edits to them. Equipment is asked to accept, amend or reject the closed grammar |
-
| Refuge and persistent progression | [Colony](/Hold%20the%20Flood/Colony) | Existing three decisions and persistence rules; proposed Colony designer develops the campaign-spanning layer |
+
| Refuge and persistent progression | [Colony](/Hold%20the%20Flood/Colony) | Colony designer staffed, COL101 in review. D023 selects structural direction; interfaces/costs still need reconciliation |
| World, evidence and mystery | [World and Mystery](/Hold%20the%20Flood/World%20And%20Mystery) | Existing World designer expands beyond the local mystery under WLD103 |
