Files

T

jpmschweitzerandClaude Opus 4.6 3005294c98 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>

2026-03-05 11:26:52 +01:00

architecture-review-2026-02-11.md

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

2026-03-05 11:26:52 +01:00

README.md

docs(audits): add architecture audit framework and Sprint 1 review

2026-02-11 21:29:58 +01:00

README.md

Architecture Audits

Audit Pattern: Adversarial Two-Round Review with Code Review

Format

Two independent reviewers (typically Tyre + Troblum) run a structured architecture audit in two rounds:

Round 1 — Independent Reviews (parallel)

Each reviewer independently analyzes the architecture plan AND current code
Covers decisions, implementation, risks, scalability, and recommendations
Reviewers do not see each other's output

Round 2 — Adversarial Debate (parallel)

Each reviewer receives the other's Round 1 findings
Writes a debate response: AGREE / PUSH BACK / SYNTHESIZE per finding
Challenges assumptions, catches blind spots, reconciles priorities

Synthesis — Consensus Recommendations

Merged priority list both reviewers sign off on
Items rated by sprint and effort
"Not Accepted" section for recommendations that were debated and deferred

Scope

Each review covers:

Architecture decisions (all decisions/*.md domain files)
Current implementation (server Rust code, client GDScript code, tests)
Technical risk assessment with severity ratings
Decision coherence and gaps
Scalability and performance analysis
Implementation readiness
Prioritized recommendations

Output

Single document per audit, date-coded: architecture-review-YYYY-MM-DD.md

Reviewers

Tyre (Technical Architect, internal) — focuses on decision coherence, system design, implementation readiness, algorithm selection
Troblum (External Technical Consultant) — focuses on technology evaluation, operational concerns, failure modes, performance profiling, time bombs

When to Run

Before major sprint milestones
After significant architecture decisions
When scope changes require re-evaluation
At kill switch checkpoints (D-020)

Audit History

Date	Reviewers	Scope	Key Finding
2026-02-11	Tyre + Troblum	Full architecture + code (Sprint 1)	Architecture GREEN, implementation plan AMBER — knowledge graph and observer pipeline underspecified