jpmschweitzerandClaude Opus 4.6
4f5ee0274b
Replace monolithic 474-line DECISIONS.md with 7 domain files under decisions/: architecture, perception, content, scope, process, questions, rejected. Each file owns its decisions with cross-reference hyperlinks. Root DECISIONS.md becomes a redirect with domain index. Reduces per-agent context load by ~70-80% (80-150 lines vs 474). Taxonomy: architecture (D-008..D-031), perception (D-011..D-019), content (D-023..D-029), scope (D-001..D-027), process (D-004..D-022), questions (Q-001..Q-011), rejected (R-001..R-010). Restores D-002 original text (was a tombstone referencing D-005). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.6 KiB
2.6 KiB
Process Decisions
How the team works: composition, naming, workflow.
D-004: Team composition confirmed
- Date: 2026-02-08
- Decision: Team of 8 agents + Team Leader.
| Agent | Role |
|---|---|
| MIRI | Lore Expert & Canon Guardian |
| OZZIE | Player Experience / "Wow Factor" Advocate |
| PAULA | Narrative & Political Depth |
| GORE | Themes & Endgame Design |
| GESTALT | Systems Design & Fun Factor |
| NIGEL | Sandbox & Replayability |
| TYRE | Technical Architecture & Feasibility |
| SCRIBE | Documenter |
| Jeroen | Team Leader, final decisions |
D-021: Official project title — "The Settled Reach"
- Date: 2026-02-10
- Decision: The official project and game title is "The Settled Reach". The domain settledreach.com has been secured. Individual campaigns or scenarios can have subtitles in the format "The Settled Reach: [Scenario Name]" but the core title remains consistent.
- Rationale: Following Round 14's worldbuilding confirmation establishing the Settled Reach as the original setting, the Team Leader confirmed this as the official project title. The name reflects the setting's core tension: a civilization that has "settled" across the stars but whose "reach" is ultimately limited by infrastructure it doesn't fully control or understand.
- Repository note: The repository folder and git history will remain as "commonwealth" for historical continuity and to avoid breaking existing paths. The code name vs official title distinction is acceptable (similar to how game projects often have internal code names).
- Raised by: Team Leader (Jeroen), following Round 14 worldbuilding discussion.
- Dissent: None.
D-022: Process — Round-based collaboration workflow
- Date: 2026-02-10
- Decision: Going forward, discussions are captured directly in round documents at
docs/discussions/round-NN-topic.mdrather than in DISCUSSION.md. DISCUSSION.md has become unwieldy to manage and archive. Qatux must be included in all team interactions (single-agent or multi-agent) to document discussions. - Rationale: DISCUSSION.md grew to 26,000+ tokens and became clunky to archive. Direct round document creation is cleaner and more maintainable. Qatux's inclusion ensures no decisions or context are lost.
- New workflow:
- Create round document at
docs/discussions/round-NN-topic.md - Document collaboration within that file
- Extract decisions to appropriate domain file in
decisions/ - Update discussions README
- Re-index as needed
- Create round document at
- Raised by: Team Leader (Jeroen).
- Dissent: None.
- Effective: Immediately (Round 15 onward).
3 decisions. Last updated: 2026-02-11