docs(docs): replace Commonwealth with Settled Reach across docs

Updated in-universe "Commonwealth" references to "the Settled Reach"
in decisions, architecture docs, design docs, workshop outputs,
README, and wiki. Kept all references to Hamilton's books as
inspiration/comparison in historical discussions and wiki-review
workshop rounds.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-03-05 11:26:52 +01:00
co-authored by Claude Opus 4.6
parent b492410e39
commit 3005294c98
20 changed files with 41 additions and 41 deletions
@@ -109,7 +109,7 @@ Reviewed all 40 confirmed decisions across 5 domain files. The decisions are **r
**Mild tension points (not contradictions):**
1. **D-003 vs current scope.** D-003 says "build a framework/engine, Commonwealth is the first campaign." But the NPC axes (D-024), contraband spec (D-037), and setting details (D-036) are deeply Commonwealth-specific. Fine for v0.1 — the "framework" claim should be understood as aspirational, not architectural.
1. **D-003 vs current scope.** D-003 says "build a framework/engine, the Settled Reach is the first campaign." But the NPC axes (D-024), contraband spec (D-037), and setting details (D-036) are deeply Settled Reach-specific. Fine for v0.1 — the "framework" claim should be understood as aspirational, not architectural.
2. **D-012 (chunk-based maps, future borderless) vs D-014 (bounded 150x150).** No contradiction, but chunk-based architecture is over-engineered for v0.1 scope (150x150 = ~25 chunks at 32x32). Investment justified by design principle.
3. **D-009 (multiplayer-ready) cost estimate ("15-20% slower").** Unverifiable at this stage. With subprocess/IPC, multiplayer readiness is essentially free because the architecture IS client-server.