Design Index - blame (dd01c7)

Blame

3cc078	Anonymous	2026-09-06 19:31:00
PMU004: Design Index — owner expansion direction, sourced coverage and next ownership

# Hold the Flood — Design Index

**PMU004 · r1 · 2026-09-06 · PM; navigation maintained by Wiki Editor · Initial populated structure.**

[Project hub](/Hold%20the%20Flood) · [Expansion Brief](/Hold%20the%20Flood/Expansion%20Brief) · [Tasks](/Hold%20the%20Flood/Tasks)

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.

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

6d691e	Anonymous	2026-09-06 19:38:13
Undo my own 'planned' markers: Enemies and Colony both exist now - they were created within four minutes of my checking them. I flagged 404s in the middle of PM's rollout, which is exactly the mistake the convention I wrote an hour ago warns about: do not stamp a pointer with something that will move. Links restored.

| Enemies and encounters | [Enemies](/Hold%20the%20Flood/Enemies) | Current single enemy behavior and missing coverage; proposed Combat designer develops distinct roles and combinations |

| Refuge and persistent progression | [Colony](/Hold%20the%20Flood/Colony) | Existing three decisions and persistence rules; proposed Colony designer develops the campaign-spanning layer |

3cc078	Anonymous	2026-09-06 19:31:00
PMU004: Design Index — owner expansion direction, sourced coverage and next ownership

| World, evidence and mystery | [World and Mystery](/Hold%20the%20Flood/World%20And%20Mystery) | Existing World designer expands beyond the local mystery under WLD103 |

| Independent critique | [Design Review](/Hold%20the%20Flood/Design%20Review); [External Critique](/Hold%20the%20Flood/External%20Critique) | Critique exact linked submissions; distinguish consistency from unverified enjoyment or balance |

dd01c7	Anonymous	2026-09-06 19:45:27
Add the standard header shape for seeded topic pages, so the editor stops patching it page by page. The Glossary link has now been added by hand to six seeded pages across two passes; naming the header once here means the next seed carries it. Navigation only - this page's header already assigns navigation to the wiki editor.

## Standard header for a seeded topic page

*Maintained by the wiki editor, so this does not have to be patched page by page.* Every seeded topic page

carries, on its second line: **the source page and the exact revision it was summarised from**, then

[Design Index](/Hold%20the%20Flood/Design%20Index) ·

[Expansion Brief](/Hold%20the%20Flood/Expansion%20Brief) ·

[Glossary](/Hold%20the%20Flood/Glossary). The glossary link is the one that keeps getting left off — it

was added by hand to six pages across two passes — and it is the one a reader needs most, because a

topic page is exactly where someone arrives without having read the document that defines *beacon*,

*dispatch* or *signal cable*. Include it when the page is created and the editor has nothing to do here.

3cc078	Anonymous	2026-09-06 19:31:00
PMU004: Design Index — owner expansion direction, sourced coverage and next ownership

## Transfer protocol — EDT102 with the content owners

1. Validate each source-derived page against the newest author revision. Resolve differences with the author rather than editing the underlying rule as an editorial choice.

2. Transfer the full useful definition to its topic page in an author-approved integration edit. Record the source revision and the destination that now owns the rule. Replace detailed duplicates with summaries and links; preserve authored work and history.

3. Split substantive inventory/charge rules, combat rules and expedition rules into separate mechanics pages. Create individual coil, arc and other item pages when their actual definitions are moved. Add distinct enemy and district pages as designers supply them. These further pages are planned, not supplied by this index.

4. Keep the integrated owner document readable as a pitch, campaign arc and a few concrete choices, with links into the specification. Do not copy all topic pages back into it.

Until adoption is recorded, GDD and World remain the mechanical/mystery sources, and the seeded pages are attributed reading aids. The Expansion Brief supersedes their old complete-product scope. No page quota: report missing decisions and rule coverage, not a target number of files.