Home A - Z Create page
Page Index

An Otter Wiki

Blame

aa4ad9 Anonymous 2026-09-08 15:40:03
Publish dated owner progress board
1 
# Hold The Horde — Progress
2
0c6bef Anonymous 2026-09-08 16:01:08
Record reviewed survivor package alongside forecast F1
3
**Updated 2026-09-08 16:01 Jerusalem (UTC+3).** This is the PM's owner-facing outcome board. The wiki is the shared record. All work remains **design only**.
aa4ad9 Anonymous 2026-09-08 15:40:03
Publish dated owner progress board
4
cd7b17 Anonymous 2026-09-08 16:09:09
Track outline response and parallel information design
5
**18 tracked design packages: 15 preparation-closed, 3 open.** Outline17 and Player Information18 were explicitly added8 Sep to fill whole-game coverage gaps. Station comparison15 closed363 and first-survivor comparison06 closed368. Shared integration04, outline17 and information/accessibility18 remain open. Of the15 closed packages,6 have owner-selected directions,1 a tentative preference and8 are reviewed proposals/alternatives.
aa4ad9 Anonymous 2026-09-08 15:40:03
Publish dated owner progress board
6
3f5678 Anonymous 2026-09-08 15:56:59
Add milestone forecast F1, target dates, staffing and uncertainty
7
“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, and the closed/total ratio is not an overall game-completion percentage. Stable IDs stay fixed; added/reopened work must be recorded explicitly.
8
9
## Forward forecast — baseline F1
10
11
**Planning answer: a coherent core design this week, a complete first-pass game-design wiki in about two weeks, and a detailed campaign specification in roughly two to three months.** These are PM estimates to manage against, not promises or measured confidence intervals. They will change as the content inventory and owner choices become concrete.
12
13
All dates are2026; times are Jerusalem. Ranges are cumulative from8 September, not durations to add together. Baseline F1 was set8 September. Dates assume ordinary weekdays, about6–8 productive agent/PM operating hours per working day, functioning local hosts, and most consequential owner choices within a working day. That does **not** mean6–8hours of the owner's time or guaranteed overnight operation.
14
15
|Milestone|Target|Current likely window|Confidence|What will be ready|
16
|---|---|---|---|---|
17
|M0 — current puzzle/rescue decision pack|Today,8 Sep,16:30|Today16:30–17:00|Medium-high|Reviewed station-connection recommendation and two short first-survivor scenes, with unresolved assumptions exposed|
fc05ee Anonymous 2026-09-08 16:04:47
Record early outline draft and revise near-term estimate
18
|M1 — whole-game outline and scope bands|Today,8 Sep,17:00 (revised)|Today16:30–17:30|Medium|Draft arrived16:01, ahead of original17:30–18:30 draft window. Focused review and one response remain; original reviewed target18:30/window18:00–20:00 retained in change log.|
3f5678 Anonymous 2026-09-08 15:56:59
Add milestone forecast F1, target dates, staffing and uncertainty
19
|M2 — coherent core-design baseline|Fri11 Sep|10–14 Sep|Medium-low|One compatible proposed/selected loop: opening, builds, combat, oxygen, death/shift, rescue and home; old conflicting rules replaced and consequential choices dispositioned|
20
|M3 — complete first-pass game-design wiki, v1|Tue22 Sep|18–29 Sep|Low-medium|Every major gameplay and campaign area has an actual design, a scoped content inventory, dependencies and a usable development handoff outline; major categories are no longer only menus of alternatives|
21
|M4 — detailed campaign/content specification|Tue10 Nov|20 Oct–1 Dec|Low|The approved finite inventory of regions, rooms, puzzles, clues, encounters, rewards, cast scenes and endings is specified through its state changes and recovery paths|
22
23
**Will the full wiki be ready today? No.** Today's deliverables are a decision pack and a whole-game outline. **The working target for the first complete design wiki is22 September.** The later detailed-content milestone expands that design into the actual authored campaign. Neither milestone claims that a written plan has proved fun, balance, performance or30/90/100–200hours of play.
24
25
For M3, “complete first pass” includes the story's causal chain and ending structure; station layout/shifts/persistence; equipment acquisition and progression; combat/horde/trap families; oxygen/resources; rescue/colony/cast arcs; both language-learning arcs and clue distribution; journal, controls and accessibility; content budget, production constraints and the later validation plan. Numerical tuning can remain explicitly provisional. A major domain marked only “TBD” does not satisfy completion.
26
27
M4 has the weakest estimate because no approved content inventory yet exists. It assumes a substantial authored campaign matching the brief's ambition and two additional specialists. It is approximately30–60 active working days; with the current team alone, the initial audit estimated40–80. A smaller approved campaign could be much quicker; a dense secret/language campaign or a changed global rule could exceed the range. I will revise M4 after the inventory and three representative detailed content packages are written and checked. Final gameplay validation belongs to a separately authorised implementation/playtest phase; it has no honest calendar endpoint yet.
28
29
## Estimated work timeline
30
31
This is a planning schedule, not historical delivery data. “Buffer” is allowed revision/decision time, not an unassigned promise to polish indefinitely.
32
33
|Workstream|8 Sep|9–11 Sep|14–18 Sep|21–29 Sep|Oct|Nov–1 Dec|
34
|---|---|---|---|---|---|---|
35
|Current decision pack|Finish||||||
cd7b17 Anonymous 2026-09-08 16:09:09
Track outline response and parallel information design
36
|Whole-game outline and scope|Draft / review|Refine|||||
3f5678 Anonymous 2026-09-08 15:56:59
Add milestone forecast F1, target dates, staffing and uncertainty
37
|Core rules and shared integration||Finish / buffer into14 Sep|||||
38
|Campaign, puzzles, cast, progression and languages||Start|Develop|Integrate and review|||
39
|Complete wiki v1|||Draft coverage|Target22 Sep; buffer to29 Sep|||
40
|Detailed authored content|||Representative packages|Expand approved inventory|Main authoring|Target10 Nov; buffer to1 Dec|
41
42
The critical sequence is core decisions and interfaces → whole-game architecture/content budget → domain designs → cross-domain integration → v1. Content detail proceeds in parallel only where interfaces are stable. Extra writers do not eliminate the PM/review bottleneck.
43
44
## Extra agents — when and why
45
46
**Plan to add two agents tomorrow,9 September**, with bounded briefs prepared today. The current team can finish today's work. We will begin the two specialist streams as the relevant scopes become ready, aiming to have both available by10 September rather than waiting a week.
47
48
|Additional role|Planned start|First bounded responsibility|Reason for adding it|
49
|---|---|---|---|
50
|Campaign and puzzle designer|9 Sep|Develop the outline's discovery dependencies and two representative regional/puzzle chains, keeping owner mysteries revisable|Most existing work is local examples; the campaign and its deep discoveries need a dedicated author|
51
|Technical design and production planner|9–10 Sep|Audit proposed scope against Unity/Steam, state/save complexity, reusable content needs and available free-asset categories; identify constraints and likely expensive systems|The largest forecast uncertainty is how much authored content and engineering complexity the design implies|
52
53
These are design roles. No gamecode, prototypes, simulations, tests, purchases or AI art are authorised by this staffing plan. The owner has not yet created these sessions; no staffing completion is claimed. PM will guide setup one step at a time. Existing Systems retains the equipment economy; if that becomes the actual bottleneck, the second specialist brief can shift to economy/content planning rather than accumulate an idle role. No additional permanent critic is currently planned.
54
55
The independent schedule audit proposed campaign/puzzle and economy specialists after the core baseline. PM keeps its point that extra agents do not accelerate core decisions, but brings onboarding forward to9 Sep so a bounded content/production audit can begin alongside integration. The production role is chosen first because the absent content inventory and feasibility assumptions dominate the long-range estimate. This is a reversible staffing judgment, not a demonstrated speedup.
56
57
## Why these estimates, and when they change
58
59
Recent focused comparison/review packages took about16–49 elapsed minutes. That supports today's short delivery windows; it does not establish campaign-authoring throughput. The independent remaining-scope audit estimated2–4 active days for a coherent core,6–12 with two specialists or8–15 with the current team for a whole-game first pass, and30–60 with two specialists for detailed content. PM has allowed calendar/integration buffer around the v1 target.
60
61
- Every15-minute progress report includes the next milestone's current target/range and whether it moved. The full forecast is reviewed at each day's close, with the next substantive re-estimate by9 Sep18:00 after the scope outline.
62
- Keep the original target visible when revising it. Record old estimate, new estimate and the concrete cause; do not silently move dates.
63
- A changed core mechanism or late owner story change may add roughly1–3 working days to the core/v1 forecast; quantify the actual affected work when it happens.
64
- A blocked decision moves its dependent work, not every parallel stream. Host outages are reported with elapsed delay. If authors produce a queue waiting over a working day for review/integration, reduce parallel intake before adding more agents.
65
- Forecasts must be useful even when confidence is low. Uncertainty is a reason to widen a range and state assumptions, not to omit an estimate or wait for certainty.
66
67
|Forecast revision|Recorded|Change and reason|
68
|---|---|---|
69
|F1|8 Sep|First forward baseline added at owner's request; prior board had actuals but omitted estimates. M3 target22 Sep; M4 target10 Nov.|
fc05ee Anonymous 2026-09-08 16:04:47
Record early outline draft and revise near-term estimate
70
|F1.1|8 Sep16:04|M1 reviewed outline moved from18:00–20:00 to16:30–17:30 because the actual draft arrived16:01 and Reviewer had already fetched it. Review/rework still required. Core, full-wiki and detailed-content dates unchanged.|
aa4ad9 Anonymous 2026-09-08 15:40:03
Publish dated owner progress board
71
72
## What changed in this report
73
74
- Opening A is now the owner's preferred direction: use a reusable part in station machinery to make extraction safer.
75
- 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.
69c72a Anonymous 2026-09-08 15:46:16
Record recovered handoff and completed station review
76
- Both new station-wide puzzle concepts have been independently submitted and released. Systems submitted the practical comparison; its focused review is complete, and one author response is now assigned. Reviewer is preauthorised for the first-survivor submission next.
77
- The first-survivor handoff recovered on the original Lead session; its assignment and source reads are verified. No task recreation or owner message forwarding was required. The earlier delivery block is resolved.
aa4ad9 Anonymous 2026-09-08 15:40:03
Publish dated owner progress board
78
79
## Open and closed outcomes
80
81
All milestone times below are Jerusalem time. “Updated” separates later owner-rule integration from the original preparation closeout.
82
83
|ID|Outcome|Preparation status|Decision status|Latest milestone|Next step / remaining scope|
84
|---|---|---|---|---|---|
85
|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|
86
|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|
87
|03|[Carried property returns on death](/Hold%20The%20Flood/Death%20And%20Persistence)|Closed|Selected rule|Sep8 13:45|Shift and survivor ordering tracked separately|
88
|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|
89
|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|
0c6bef Anonymous 2026-09-08 16:01:08
Record reviewed survivor package alongside forecast F1
90
|06|[First-survivor comparison](/Hold%20The%20Flood/First%20Survivor)|Closed|Short rescue selected; person unchosen|Sep8 response364/disposition368|Yeva versus Aster ready; short-route condition and death/refuge timing remain explicit limits|
aa4ad9 Anonymous 2026-09-08 15:40:03
Publish dated owner progress board
91
|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|
92
|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|
93
|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|
94
|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|
95
|11|[Three distinct horde creatures](/Hold%20The%20Flood/Horde%20Creature%20Proposals)|Closed|Reviewed proposals|Sep8 14:07|Roster and origins unselected|
96
|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|
97
|13|[Player resurrection and corruption](/Hold%20The%20Flood/Resurrection%20And%20Corruption)|Closed|Reviewed alternatives|Sep8 14:38|No player decay or death budget adopted|
98
|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|
3f5678 Anonymous 2026-09-08 15:56:59
Add milestone forecast F1, target dates, staffing and uncertainty
99
|15|[Whole-station mechanism comparison](/Hold%20The%20Flood/Connecting%20The%20Station)|Closed|Goal selected; mechanism conditional|Sep8 15:51 disposition363|Physical connection candidate prepared; owner payoff choice and detailed content remain open|
aa4ad9 Anonymous 2026-09-08 15:40:03
Publish dated owner progress board
100
|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|
101
cd7b17 Anonymous 2026-09-08 16:09:09
Track outline response and parallel information design
102
|17|[Whole-game design outline and scope bands](/Hold%20The%20Flood/Whole%20Game%20Outline)|Open — review|New proposed architecture|Sep8 16:01 submission369|Draft369 and focused review370 complete; Systems response371 active. Revised reviewed-window16:30–17:30 today|
103
104
|18|Player information and accessibility|Open — working|New proposed interface contract|Sep8 assignment372|Lead draft17:00–18:00 today; Reviewer preauthorised after independent criteria|
3f5678 Anonymous 2026-09-08 15:56:59
Add milestone forecast F1, target dates, staffing and uncertainty
105
aa4ad9 Anonymous 2026-09-08 15:40:03
Publish dated owner progress board
106
## Recent delivery timeline
107
108
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.
109
110
|Outcome|Assigned Sep8|Preparation closed Sep8|Elapsed|
111
|---|---|---|---|
112
|Equipment progression comparison|13:17|13:51|34 minutes|
113
|Three horde creatures|13:51|14:07|16 minutes|
114
|Hospital-story comparison|13:58|14:47|49 minutes|
115
|Resurrection/corruption comparison|14:20|14:38|18 minutes|
116
|Opening comparison|14:40|15:14|34 minutes|
117
|Alien-language interaction|15:06|15:38|32 minutes|
118
119
## Work sequence
120
121
|Stream|Now|Next|After that|
122
|---|---|---|---|
3f5678 Anonymous 2026-09-08 15:56:59
Add milestone forecast F1, target dates, staffing and uncertainty
123
|Whole-station puzzle|Comparison preparation closed363|Owner payoff/mechanism reaction|Shared-rule integration and detailed puzzle content|
0c6bef Anonymous 2026-09-08 16:01:08
Record reviewed survivor package alongside forecast F1
124
|First survivor|Comparison preparation closed368|Owner reaction to Yeva versus Aster|Shared rescue integration; decision pack forecast16:30–17:00 today|
aa4ad9 Anonymous 2026-09-08 15:40:03
Publish dated owner progress board
125
|Shared consistency|Old fixed-map claims marked superseded|Use the new connection contract and owner payoff choice|Replace conflicting rules in owning articles|
126
3f5678 Anonymous 2026-09-08 15:56:59
Add milestone forecast F1, target dates, staffing and uncertainty
127
The whole-station contract is the current dependency for shared integration. The first-survivor stream is now running independently after its host recovered. Forward target dates and ranges above now govern planning; they are revised as decisions and actual work change.
aa4ad9 Anonymous 2026-09-08 15:40:03
Publish dated owner progress board
128
129
## Decisions for the owner
130
131
**Already answered:** opening A and persistent room/group connections across shifts, culminating in connecting the entire station.
132
133
**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.
134
135
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.
136
137
## Reporting agreement
138
3f5678 Anonymous 2026-09-08 15:56:59
Add milestone forecast F1, target dates, staffing and uncertainty
139
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, blockers, next deliverable with ETA, current v1 target and any forecast change, and a link here. An unchanged interval is stated honestly. No page/message counts or invented completion percentages stand in for progress. Clearly labelled estimated dates and ranges are required; never present them as known facts or guaranteed deadlines. The local monitor requires the computer and apps to remain available.