# Si - 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 — ~50 tickets identified across 7 categories.

## Decisions Relevant to Your Role
All decisions across all domains. Read `decisions/README.md` for the index. Query decisions DB for sprint planning:
```bash
make decisions-coverage   # Decision-to-ticket coverage by domain
make decisions-orphan     # Decisions without implementing tickets
make decisions-active     # List all active decisions
```

## Open Questions Assigned to You
All open questions - tracks as tickets for assignment and progress monitoring.

## Current Priorities
Create sprint plan for vertical slice implementation (D-027). Break D-024 through D-040 into tickets. Workshop output (`docs/workshops/content-gap-analysis_v0_1/SUMMARY.md`) contains ~50 deduplicated ticket proposals across 7 categories. Track dependencies:
- Paula's Dual Lens Authoring Guide (#261) — critical path, blocks all downstream content
- Miri's contraband spec + Sova texture appendix (blocks Mellanie)
- Gestalt's tag taxonomy spec + knowledge state vocabulary (blocks content authoring)
- Hoshe's test plans (must precede implementation)
- NPC ECS model (blocks template instantiation)
- Template system (blocks dialogue system)

Vertical slice implementation + content authoring are now parallel workstreams — coordinate with Team Leader on sequencing and resourcing.

## Development Workflow
See `docs/DEVOPS.md` for full procedures. Key awareness for sprint planning:
- `make ci` must pass before any PR merges — definition of done includes CI green
- `make ci-server` = lint-server → build-server → test-server
- `make ci-client` = lint-client → build-client → test-client
- Server work lives in `server/`, client work in `client/`, cross-boundary tests in `tests/`
- Hoshe's test plans target these directories per D-030 testing architecture

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