Files
settled-reach/docs/workshops/generator-architecture/miri-round5.md
T
jpmschweitzerandClaude Opus 4.6 9a5c9c4408 docs(docs): add frontmatter to generator-architecture workshop
Standardized YAML frontmatter on all 38 files with title, description,
type, workshop, agent, and round fields.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-13 23:40:37 +01:00

5.4 KiB

title, description, type, status, workshop, agent, round, created
title description type status workshop agent round created
Miri Round 5 — Final Review Final review and sign-off on workshop outcomes for worldbuilding domain workshop archived generator-architecture miri 5 2026-02-27

Generator Architecture Workshop — Round 5: Miri (Worldbuilder)

Topic: Final review of workshop-outcomes.md before D-record filing. Date: 2026-02-27 Scope: Sign-off + corrections only. No new proposals.


Sign-Off Summary

Most of the document is accurate. One factual error in D-READY-10 heritage root correlations. All other items I was asked to verify are correct.


Verified Correct

Ysabel Vorn litmus test (NPC Model section): Accurate. 4.5/5 stated correctly. 10 axes listed correctly and match my Round 4 document. Axis 11 (Network Footprint) raised correctly as a Q-record, not a confirmed decision. The "authored scenario NPCs" framing is right — this should never be procedurally generated.

D-READY-9 (Heritage Grammar Overlay): Authoring domain separation is correct.

  • Miri: organizational principles, boundary character, spacing, social grammar (HeritageGrammarOverlay Rust struct)
  • Araminta: visual expression — object sets, arrangement algorithms, lighting temperature (TOML modifier files)
  • Shared: ObjectTag vocabulary co-maintenance requirement

D-READY-12 (Trauma Events): Subtypes match my Round 3 specification (PhysicalDestruction, EconomicDisruption, PoliticalShock, ViolenceEvent, MigrationShock). Dual-track model (structural damage via StructuralChange; cultural response via NPC pattern weight shifts) is correct. Heritage-seeded decay rate variation is correct.

D-READY-13 (MobileChunk / Vessel): Correctly points to my Round 4 document for the canonical TransitSocialModifier and TransitVariant spec. BoundedLinear / BoundedMobile / InterSystem enum variants listed correctly.

OQ-R4-C synthesis (Q-NNN-f): The framing — "stored cultural baseline (DerivedDistrictAnalysis on skeleton) + on-demand computation for player-facing assessment" — is an acceptable synthesis. Clarification I want on record: if on-demand computation is added for player-facing use, it is subordinate to the Phase 1 DerivedDistrictAnalysis value. Game logic (Tactical triangle instantiation, guarantee audit) uses the Phase 1 value. Any on-demand computation is display-only. This should be explicit in the formal D-record.


Correction Required — D-READY-10

Current text: "Frost/Stone → physical_distance; Tide/Vine → social_permission; Dust/Salt → utilitarian_cover."

Error: Dust is misclassified. Dust should be social_permission, not utilitarian_cover.

Canonical source: My Round 3 document, Section 2.4:

"Frost → physical_distance (individual space is respected everywhere)" "Tide/Dust → social_permission (negotiated privacy within community framework)" "Iron → utilitarian_cover (labor function covers presence)"

Why this matters: Dust culture is characterized by maximum communal observation — survival-level social awareness, shared information as a community good. In a Dust community, the only privacy available is negotiated ("we agree not to see what you're doing"). There is no privacy via physical distance (everyone sees everything) and no privacy via utilitarian cover (in a Dust community, being in the barn is suspicious precisely because it's isolated from the collective). Dust belongs with Tide in social_permission.

Iron is missing entirely. Iron → utilitarian_cover is the clearest mapping: labor function covers presence ("what workers do after the shift" and "what happens in the union hall"). Iron should appear under utilitarian_cover.

Corrected heritage root correlations:

  • physical_distance: Frost, Stone
  • social_permission: Tide, Vine, Dust
  • utilitarian_cover: Iron, Salt

Note: Stone, Vine, and Salt were not mapped in my Round 3 document — these are plausible extensions I accept. The firm corrections are Dust (wrong type) and Iron (missing).

Corrected text for D-READY-10:

Heritage root correlation: Frost/Stone → physical_distance; Tide/Vine/Dust → social_permission; Iron/Salt → utilitarian_cover. Location within terrain is seeded independently.


One Omission (Not a Factual Error)

D-READY-12 is technically correct but loses a framing point that has gameplay implications. The design principle underlying trauma event response is:

Trauma intensifies culture, it does not transform it.

A stressed community becomes a more concentrated version of itself. Frost communities close harder. Tide communities grief more publicly. Iron communities organize more collectively. The heritage root character is amplified under stress, not replaced.

This matters for gameplay because players who have learned a heritage root's trust model can predict community behavior in the aftermath — and should be able to. It's not in the D-record language anywhere. Suggest adding a one-line note to the D-record: "Cultural response is heritage-root intensification, not transformation. Decay is toward the community's pre-trauma baseline, not toward a new equilibrium."


Status

One correction required (D-READY-10 heritage correlations). One clarification requested (OQ-R4-C on-demand computation is display-only). One framing note suggested for D-READY-12.

Everything else: confirmed accurate.

Author: Miri Date: 2026-02-27 Status: Round 5 complete.