Commit aa4ad9
2026-09-08 15:40:03 Anonymous: Publish dated owner progress board| /dev/null .. hold the flood/progress.md | |
| @@ 0,0 1,72 @@ | |
| + | # Hold The Horde — Progress |
| + | |
| + | **Updated 2026-09-08 15:40 Jerusalem (UTC+3).** This is the PM's owner-facing outcome board. The wiki is the shared record. All work remains **design only**. |
| + | |
| + | **16 tracked design packages: 13 preparation-closed, 3 open.** Open: 1 working, 1 blocked on an agent host, 1 waiting on a design dependency. Of the13 closed packages,6 have owner-selected directions,1 has a tentative owner preference and6 are reviewed proposals/alternatives. |
| + | |
| + | “Closed” means the bounded written design/review outcome is complete. It does not mean a feature is implemented, every detail approved or fun validated. This board covers the current design batch; it is not a complete campaign or production backlog, and13/16 is not an overall game-completion percentage. Stable IDs stay fixed; added/reopened work must be recorded explicitly. |
| + | |
| + | ## What changed in this report |
| + | |
| + | - Opening A is now the owner's preferred direction: use a reusable part in station machinery to make extraction safer. |
| + | - The alien-language interaction finished its focused review and correction. It supports learning a useful interaction protocol while keeping the speaker and exact meaning uncertain. |
| + | - Both new station-wide puzzle concepts have been independently submitted and released. Systems is writing their practical comparison; Reviewer can review the actual submission without another PM handoff. |
| + | - The first-survivor comparison is assigned, but its automatic handoff was not sent because the original Lead session is absent from a fresh local listing. Owner availability question pending. Other work continues. |
| + | |
| + | ## Open and closed outcomes |
| + | |
| + | All milestone times below are Jerusalem time. “Updated” separates later owner-rule integration from the original preparation closeout. |
| + | |
| + | |ID|Outcome|Preparation status|Decision status|Latest milestone|Next step / remaining scope| |
| + | |---|---|---|---|---|---| |
| + | |01|[Reusable equipment combinations](/Hold%20The%20Flood/Build%20Rules)|Closed|Selected direction|Sep7 22:19; updated Sep8 13:45|Catalogue and numerical rules remain proposed| |
| + | |02|[Oxygen visibility and journal pause](/Hold%20The%20Flood/Oxygen%20and%20Observation)|Closed|Selected direction|Sep7 20:55; updated Sep8 13:45|Exact oxygen amounts remain open| |
| + | |03|[Carried property returns on death](/Hold%20The%20Flood/Death%20And%20Persistence)|Closed|Selected rule|Sep8 13:45|Shift and survivor ordering tracked separately| |
| + | |04|[Shifts, persistent work and historical records](/Hold%20The%20Flood/Shifting%20Station%20Options)|Open — dependent|Binding direction selected|Sep8 14:49 direction recorded|Integrate final station contract after15; older fixed-map clauses are superseded| |
| + | |05|[Ordinary combat and horde encounters](/Hold%20The%20Flood/Combat%20Rules)|Closed|Selected direction|Sep8 10:51; updated13:45|Automatic ordinary fire, manual specials; balance remains open| |
| + | |06|First short human rescue|Open — blocked|Short rescue selected; scene unchosen|Sep8 15:34 assigned|Lead session unavailable for handoff; two encounter/homecoming options requested| |
| + | |07|[Practical discovery and optional help](/Hold%20The%20Flood/Clues%20and%20Help)|Closed|Selected direction|Sep8 11:23; updated13:45|Current routes cannot be inferred from historical records| |
| + | |08|[Cooperation and useful work aboard](/Hold%20The%20Flood/Home%20Projects)|Closed|Tentative preference|Sep8 12:00; updated13:45|Equipment loans tentative; full colony/cast still open| |
| + | |09|[Two-language expedition and journal use](/Hold%20The%20Flood/Language%20Expedition)|Closed|Reviewed proposal|Sep8 13:45|Detailed language system unselected;16 is a distinct evidence scene| |
| + | |10|[How equipment is acquired and improves](/Hold%20The%20Flood/Progression%20Options)|Closed|Reviewed alternatives|Sep8 13:51|Find working components versus observe/fabricate; owner choice later| |
| + | |11|[Three distinct horde creatures](/Hold%20The%20Flood/Horde%20Creature%20Proposals)|Closed|Reviewed proposals|Sep8 14:07|Roster and origins unselected| |
| + | |12|[Hospital story and its causal alternatives](/Hold%20The%20Flood/Hospital%20Story%20Directions)|Closed|Reviewed alternatives|Sep8 14:47|Owner hospital/godhood draft leads; exact story/ending remain revisable| |
| + | |13|[Player resurrection and corruption](/Hold%20The%20Flood/Resurrection%20And%20Corruption)|Closed|Reviewed alternatives|Sep8 14:38|No player decay or death budget adopted| |
| + | |14|[Opening expedition: reusable machinery](/Hold%20The%20Flood/First%20Expedition%20Options)|Closed|Option A selected|Prepared Sep8 15:14; selected15:30|Preferred direction recorded; exact starting items/rooms remain proposed| |
| + | |15|[Deep puzzle connecting the entire station](/Hold%20The%20Flood/Connecting%20The%20Station)|Open — working|Goal selected; mechanism proposed|Sep8 15:35 work verified|Systems comparison349 → focused Reviewer review → one response/disposition| |
| + | |16|[Testable alien-language interaction](/Hold%20The%20Flood/Alien%20Utterance%20Discovery)|Closed|Reviewed proposal|Sep8 15:38|Protocol discovery prepared; does not prove request semantics or a god| |
| + | |
| + | ## Recent delivery timeline |
| + | |
| + | These are observed calendar spans from assignment to preparation closeout, including handoffs and review. They are historical measurements, not estimates of labour or promised future turnaround. |
| + | |
| + | |Outcome|Assigned Sep8|Preparation closed Sep8|Elapsed| |
| + | |---|---|---|---| |
| + | |Equipment progression comparison|13:17|13:51|34 minutes| |
| + | |Three horde creatures|13:51|14:07|16 minutes| |
| + | |Hospital-story comparison|13:58|14:47|49 minutes| |
| + | |Resurrection/corruption comparison|14:20|14:38|18 minutes| |
| + | |Opening comparison|14:40|15:14|34 minutes| |
| + | |Alien-language interaction|15:06|15:38|32 minutes| |
| + | |
| + | ## Work sequence |
| + | |
| + | |Stream|Now|Next|After that| |
| + | |---|---|---|---| |
| + | |Whole-station puzzle|Systems writes comparison|Reviewer checks submitted revision|One response if needed; PM disposition and owner-facing proposal| |
| + | |First survivor|Lead handoff blocked on host|Two concrete short encounter/rescue/homecoming options|PM review and owner reaction| |
| + | |Shared consistency|Old fixed-map claims marked superseded|Use the new connection contract and owner payoff choice|Replace conflicting rules in owning articles| |
| + | |
| + | The whole-station contract is the current dependency for shared integration. The first-survivor stream can run independently when its host is available. No completion deadline is promised before the current comparison is examined. |
| + | |
| + | ## Decisions for the owner |
| + | |
| + | **Already answered:** opening A and persistent room/group connections across shifts, culminating in connecting the entire station. |
| + | |
| + | **Open creative question:** should completing the entire connection puzzle finally stabilise the layout, or should rooms keep moving while every established connection survives? PM recommends stabilisation as a reward for mastery. This is a proposed late payoff, not an answer inferred from the opening choice; the team can continue its comparison while it is pending. |
| + | |
| + | The next new creative choice will be the first-survivor scenes. Progression, creature, story and corruption alternatives are prepared for later reactions; the owner is not expected to review the whole wiki at once. |
| + | |
| + | ## Reporting agreement |
| + | |
| + | PM sends a compact report every15 minutes while useful work is active, plus meaningful completion, disagreement, blocker or decision updates. Each report gives the timestamp, changes since the previous report, numeric open/closed preparation counts, real worker activity, blocker and next deliverable, and a link here. An unchanged interval is stated honestly. No page/message counts, invented completion percentages or ungrounded Gantt deadlines stand in for progress. The local monitor requires the computer and apps to remain available. |