jpmschweitzer/settled-reach
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(briefings): extract shared PROJECT_STATE.md, purge stale boilerplate

Browse Source 
Create PROJECT_STATE.md at repo root with cascade phase table,
decision count, and current sprint. All 18 briefings now reference
this file instead of duplicating the project state paragraph.

Also removes stale content from briefings:
- "v0.2 direction: generator-first" (contradicts D-166 cascade)
- "Sprint 25 generator spike confirmed as critical path" (Phase 5)
- Agent-specific generator prerequisite claims
- Gestalt "v0.2 Pivot" section reframed as "Key Design Pivots"

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
jpmschweitzer
2026-04-05 15:16:39 +02:00
co-authored by Claude Opus 4.6
parent 1254e41dc5
commit cfddcfb117
19 changed files with 56 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/briefings/hoshe.md
+2 -2
View File
@@ -11,7 +11,7 @@ updated: 2026-03-13
Last updated: 2026-03-13
## Current Project State
The Settled Reach: top-down immersive sim, single-character perspective, asymmetric information core mechanic, Rimworld-style storyteller. 137+ confirmed decisions. Where's the Fun? Workshop complete (2026-03-05) — 24 decisions locked. v0.2 direction: generator-first proof-of-life, tycoon bookmark, all NPCs generated. Sprint 25 generator spike confirmed as critical path.
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
## Status
**ACTIVE.** Test infrastructure from earlier sprints is operational. v0.2 focus: generator output validation — can the generator produce legible NPCs? Are relationships readable from generator output?
@@ -21,7 +21,7 @@ Read `decisions/architecture.md` (D-010, D-020, D-030) and `decisions/perception
- **D-010:** Information boundaries — testable? Can we verify information never leaks?
- **D-020:** MessagePack serialization — correct round-trip? No data loss at protocol boundary?
- **D-030:** Testability architecture (hybrid Rust tests, gdUnit4, three-layer IPC, CauseChain)
- **D-119:** Generator spike Sprint 25 — the success criterion is "can the player read NPC relationships from generator output?" Hoshe defines and verifies this criterion.
- **D-119:** Generator spike — Phase 5 per D-166 cascade (not imminent). Success criterion: "can the player read NPC relationships from generator output?" Hoshe defines and verifies this criterion.
## What's Been Delivered (Sprints 2-4)
### Test infrastructure now in place: