Files
settled-reach/docs/briefings/hoshe.md
T
jpmschweitzerandClaude Opus 4.6 af4d0d3f26 docs(workshops): complete v0.1 content gap analysis workshop
Workshop produced 42 new tickets (#297-#338) + 6 updated, 9 new
decisions (D-032 through D-040), and 53 dependency links. All 18
agent briefings updated to reflect 40 confirmed decisions.

Key outcomes: Sera Venn as detective's FRIEND, Kael Davan as
smuggler's FRIEND, all 6 wow moments in scope, converged 6+3 tag
taxonomy, wiki taxonomy with 14 categories, 8 audio files via
Stable Audio Open, 4 parallel unblocked work tracks identified.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-11 20:38:21 +01:00

47 lines
2.8 KiB
Markdown

# Hoshe - Project Briefing
Last updated: 2026-02-11
## Current Project State
The Settled Reach: top-down immersive sim, single-character perspective, asymmetric information core mechanic, Rimworld-style storyteller. 40 confirmed decisions, 17 discussion rounds + 1 workshop complete. Engine selected (D-020). Vertical slice defined (D-027). v0.1 Content Gap Analysis Workshop complete.
## Decisions Relevant to Your Role
Read `decisions/architecture.md` (D-010, D-020, D-030) and `decisions/perception.md` (D-011, D-017, D-018). Key decisions:
- **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-027:** Vertical slice success criteria (30-min runway, divergent playthroughs, emergent discovery)
- **D-030:** Testability architecture (hybrid Rust tests, gdUnit4, three-layer IPC, CauseChain)
## Open Questions Assigned to You
None assigned.
## Current Priorities
**ACTIVATED.** Vertical slice test plan preparation:
1. Write test plans for D-024 (NPC generation — verify 10 axes present, triangles formed)
2. Write test plans for D-025 (template instantiation — verify single-ownership, reference links carry metadata)
3. Write test plans for D-026 (simulation tiers — verify eviction timing, tier transition correctness)
4. Write test plans for D-027 success criteria (30-min runway, divergent playthroughs, emergent discovery)
5. Write test plans for D-028 (dialogue system — verify tag filtering, trait modifiers, layer activation)
6. Write test plans for D-035 (converged tag taxonomy — verify 4-layer filter pipeline: access → situation → trust → mood+topic)
7. Write test plans for D-033 (entity color — verify color derivation from relationship state, transition timing)
8. Write test plans for D-034 (THE FRIEND — verify ECS component integrity, contradiction event detection)
All test plans due BEFORE implementation begins.
## Development Workflow
See `docs/DEVOPS.md` for full procedures. Your key targets:
- `make test` — run all tests (server + client)
- `make test-server` — Rust unit + integration tests
- `make test-client` — gdUnit4 tests (headless runner pending)
- `make lint` — run all linters
- `make ci` — full CI pipeline locally (lint → build → test)
- Server tests: `server/` (inline `#[cfg(test)]` + `tests/` directory per D-030)
- Client tests: `client/` (gdUnit4 per D-030)
- Cross-boundary tests: `tests/` (IPC fixtures, serialization round-trips)
- Test caches: `.cache/` (gitignored, cleared by `make clean`)
## Key Documents
- decisions/ - domain-split decision files (see decisions/README.md for index)
- docs/DEVOPS.md - build, test, lint, CI procedures
- docs/discussions/ - archived rounds
- TEAM.md - team roster