settled-reach/docs/workshops/system-economic-specialization/scout-round2.md

Scout Round 2 — System Economic-Specialization Workshop

Independent Critical Review

Scout: Claude Code (fresh read, no prior workshop discussion)
Date: 2026-05-31

---

Mandate

Surface decision-changing findings only in three categories:

1. Materially simpler designs preserving quality
2. Internal contradictions with stated hard constraints
3. Missed options or external design precedent

This memo does not discuss execution, authoring burden, or taste disagreements.

---

Decision-Changing Findings

Finding 1: The Cultural Axis Scope Ambiguity is Real and Needs Resolution

Status: Paula's addendum reverses course on scope (good catch on quality grounds), but the reversal creates a new tension with the proposed implementation.

The problem:

• Paula argues the cultural axis breaks D-232 in Phase 4 if authoring is missing for systems that diverge from corridor baseline (~60-100 systems).
• All three participants agree the source is system_specialization.toml (same file as economic + faction).
• BUT the three still disagree on column placement: Burnelli proposes new system_economy.cultural_specialization column; Paula now leans toward the same TOML file but allows both system_economy and system_culture as home; Miri leaves it implicit.

Why this matters: If the cultural axis has active Phase 4 consumers (D-232 template draw), and it drives D-233-equivalent correctness in the same way economic specialization does, it should live on system_economy alongside the economic field for single-source-of-truth integrity. Splitting the authoring source (one TOML) from the write destination (two tables) creates a translation step that can drift.

Recommendation for synthesis: Clarify: if cultural axis is Phase 4-critical per Paula's quality argument, it earns a new column on system_economy and is not optional. The scope becomes "all systems where cultural diverges from corridor" (~60-100), authored in the same pass, stored in the same table as economic for coherence. This is cleaner than "optional field, maybe in this TOML, maybe lives elsewhere."

---

Finding 2: Vocabulary Granularity Mismatch May Cause D-233 Ambiguity

Status: Burnelli proposes 33 values; Miri proposes 16 values. Both converge on must-pin D-233 outputs, but the difference is not purely aesthetic.

The issue: Burnelli's vocabulary is richer in agricultural and extraction sub-types (e.g., terroir_spirits vs terroir_agriculture vs terroir_organics vs food_processing_hub). All four resolve to different combinations of BulkClass or ProductionUbiquity at the catalog level.

However, the D-233 mapping is backwards: the vocabulary value should drive the D-233 output deterministically, not the other way around. If two vocabulary values exist (terroir_spirits and terroir_agriculture), they must produce different D-233 outputs, or one is redundant.

The problem case: terroir_spirits and terroir_agriculture both should produce Perishable/BulkSolid × MonopolySource per the D-177 constraint. If they produce identical D-233 outputs, the distinction is purely cultural/narrative and doesn't belong on the economic axis — it belongs on the cultural axis.

Questions for the user:

1. Are Burnelli's 33 values designed such that every value produces a unique (BulkClass, ProductionUbiquity) pair?
2. If not, which values are purely cultural distinctions and should be relegated to the cultural axis?
3. Is there a principled rule for "granularity limit" — e.g., "add a value only if it produces a different D-233 coverage pattern"?

Recommendation: Reconcile before synthesis. A 33-value vocabulary is justifiable if each value is economically distinct (different D-233 outputs). A smaller unified vocabulary (Burnelli + Miri + Paula's intuitions merged) might be cleaner if it collapses duplicate D-233 outputs into single economic values + cultural axis overrides.

---

Finding 3: Groombridge's MonopolySource Gamble Carries Unexamined Risk

Status: Burnelli's OQ-1: is Groombridge monopolistic (MonopolySource) or just concentrated (Specialist)?

Why this matters more than it appears: The D-233 MonopolySource rule per Miri's vocab description is "the mine IS the settlement, everything else is support." This is a settlement layout constraint, not just a coverage fraction. If Groombridge is MonopolySource, the settlement form concentrates all civic, residential, and support infrastructure around the financial district — the clearing house IS the gravity well for the entire settlement.

If Groombridge is Specialist, there's a financial district, but the settlement has other districts (shipyards, repair, residential, admin) that are NOT in orbital decay around the clearing house. The built form changes fundamentally.

The GTTR signal is ambiguous:

• "Where the money lives" suggests dominance (MonopolySource read)
• "Four centuries" and "architecture understated in the way that communicates expense" suggest enduring presence but not absolute economic lock (Specialist read)
• Groombridge has financial_services commodity in the catalog at common default; MonopolySource requires explicit override justification

Red flag: Burnelli states his MonopolySource preference but says "Miri should confirm." Miri's Round 2 proposed financial_hub (Specialist) without acknowledging Burnelli's OQ-1. This is not a resolved disagreement — it's been sidestepped.

Recommendation: User needs to make an explicit call here before synthesis. The decision changes Groombridge's entire spatial form. Guidance needed: is Groombridge "THE financial node of the Reach" (MonopolySource) or "THE major financial hub" (Specialist)? The lore text supports either reading; the D-233 implications demand one answer.

---

Finding 4: Missing Prior-Art Anchor — Fallback Heuristic Design

Status: All three participants propose heuristics for unautored systems, but none cite how other procedural/sim games handle the fallback problem.

Context: Dwarf Fortress uses value-weighted random selection for regional identities, biasing but not locking on commodity availability. RimWorld's faction generation is lightweight (not economically sophisticated). EVE Online's null-sec regions are hand-authored (not procedural). X4 uses procedural faction presence + trade routes but not authored per-station cultural identity.

The gap: The Settled Reach's fallback heuristic for unautored economic specialization is deterministic (role + planet_class + corp HQ → vocabulary lookup). This is more rigid than Dwarf Fortress's weighted draw but more explainable than RimWorld's lightweight approach. It's reasonable, but there's no external validation that this rigidity won't produce boring or repetitive regional characters in the ~200+ unautored systems.

The real question: Is a deterministic fallback the right tradeoff, or should the heuristic include weighted randomness (with a pinned seed per system) to produce variety while remaining deterministic? The current design is safe but may under-deliver on "world feels alive."

Recommendation (low priority): Document the fallback heuristic's philosophy explicitly (determinism for reproducibility vs. monotony risk) and note this as a post-launch tuning opportunity.

---

What Converged Well

• All three participants lock the three-field schema (economic, cultural, faction) ✓
• Keid, Cygni B, Dài Lộ, and Zenzele resolved via GTTR textual authority ✓
• Vocabulary is curated-value abstraction, not raw commodity FK ✓
• Scale encodes in vocabulary values, not separate column ✓
• D-172 currency-zone compliance checks in CI ✓

---

What Remains Open

1. Cultural axis: column placement (system_economy vs. system_culture; materially affects pipeline coherence)
2. Vocabulary granularity reconciliation (33 vs. 16; need principled rule for distinctness)
3. Groombridge: MonopolySource vs. Specialist (impacts settlement form, not yet resolved despite OQ-1 flag)
4. Fallback heuristic philosophy (determinism vs. weighted variety — document the tradeoff)

---

No Decision-Changing Findings on

• Fork resolutions (all user-checkpointed and sound)
• CI guardrails (Burnelli's spec is thorough)
• Must-pin authoring scope (~60-100 systems is reasonable)
• Faction vocabulary (Paula's 8 values are clean)

---

Summary: 1–2 Synthesis Conversations Needed

Critical: Groombridge's MonopolySource call + cultural axis column placement (materially changes schema/pipeline coherence).

Important: Vocabulary granularity rule (prevents Future redundancy/bloat).

Documentation: Fallback heuristic philosophy (not blocking, but good to surface).

Three items. Nothing blocks the synthesis checkpoint from proceeding; all are solvable in ~15–20 minutes of discussion once the user is aware of the open frame.

---

Scout sign-off. All participants have done strong work on lore integration and logical consistency. The remaining questions are clean architectural/design calls, not smoke signals for deeper confusion.