Round 15: README.md Steam page placeholder (Miri + Mellanie) - Created README.md with game description for Steam page - Placeholder structure with lorem ipsum for undetermined content Round 16: Faction development (Miri, Paula, Gestalt) - Full development of six factions with lore, politics, mechanics - 3D reputation system (Trust × Usefulness × Exposure) - Mechanical grounding with "First 30 Minutes" test - v0.1 recommendation: Commission + Severance - Session flagged for team input Process changes (D-022): - Retired DISCUSSION.md, work directly in round files - Qatux mandatory in all team interactions - Updated CLAUDE.md and agent personas Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
5.7 KiB
Round 16 Status — Session Closed, Awaiting Return
Date closed: 2026-02-10 Topic: Factions — Building a Fuller Narrative Picture Status: COMPLETE session, OPEN QUESTIONS flagged for team return
What Was Accomplished
Round 16 fully developed the six-faction political landscape of The Settled Reach:
1. Complete Faction Lore (Miri)
- Identity, goals, internal tensions for all six factions
- Power bases and vulnerabilities
- Mechanical hooks and NPC archetypes
- Faction interaction map
Factions developed:
- Concord Assembly (governance, legislative authority)
- The Syndics (commerce, re-embodiment infrastructure)
- The Separatists (frontier independence)
- Guardians of Autonomy / Severance (counter-institutional resistance)
- The Veil Institute (Founder technology research)
- The Lattice Commission (technology regulation)
2. Political Depth Analysis (Paula)
- Power dynamics (formal vs. real power distribution)
- Conspiracy potential for each faction
- Character drama templates:
- The Whistleblower
- The Inspector with Conscience
- The Dual-Loyalty Operative
- The Reluctant Conspirator
- Betrayal vectors by faction
3. Mechanical Grounding (Gestalt)
- Starting loadouts (perception tier, Meridian access, lattice quality, legal authority, contacts, resources)
- Information asymmetry and faction blind spots
- Mechanical constraints per faction
- Resource loops
- Cross-faction hooks
- 3D reputation system (Trust × Usefulness × Exposure)
- "First 30 Minutes" test (same scenario, six different games)
- v0.1 recommendation: Commission + Severance (maximum mechanical contrast)
Key Design Insights
-
Each faction = different genre
- Assembly: Political thriller
- Syndics: Economic thriller
- Separatists: Resistance thriller
- Severance: Paranoid thriller
- Institute: Mystery thriller
- Commission: Investigative thriller
-
Faction blind spots drive replayability — Same conspiracy reveals different information to different factions
-
3D reputation complexity — Trust, Usefulness, and Exposure create relationship states where you can be simultaneously valuable and hostile to a faction
-
Real power ≠ formal power — Assembly has legal authority; Commission + Institute have operational control; Syndics have economic leverage
-
No stable alliances — Every relationship is transactional, conditional, situational
-
Constraints define play — What factions CAN'T do shapes gameplay as much as what they CAN do
Documents Produced
All Round 16 materials are archived in /Users/jeroenschweitzer/Projects/commonwealth/docs/discussions/:
round-16-factions-complete.md— Consolidated overview with all three contributionsround-16-factions.md— Full faction lore (Miri)round-16-faction-mechanics.md— Full mechanical analysis (Gestalt)round-16-session-notes.md— Session closure summary/docs/design/faction-mechanics-reference.md— Quick reference for gameplay use
Open Questions for Team Return
Critical Decision Pending
Team Leader (Jeroen): Which factions for v0.1?
- Gestalt recommends: Commission + Severance (surveillance vs. counter-surveillance, maximum contrast)
- Alternative: Assembly + Syndics (institutional play)
Validation Questions by Agent
Miri (Worldbuilding):
- Does mechanical framing break setting logic?
- Are factional blind spots setting-faithful?
- Does "Severance" as colloquial name work in-fiction?
Paula (Narrative):
- Does 3D reputation system support rich NPC relationships?
- Are "first 30 minutes" scenarios compelling as narrative hooks?
- What's missing from cross-faction interpersonal dynamics?
Nigel (Replayability):
- Does this create 6 meaningfully different playthroughs?
- Are factional blind spots sufficient anti-metagaming?
- Which factions need more mechanical differentiation?
Ozzie (Player Experience):
- Which faction "first 30 minutes" is most immediately compelling?
- Does multi-faction play feel like freedom or confusion?
- Are any factions too complex for new players?
Gore (Themes):
- Do factions express philosophical tensions (continuity, detachment, infrastructure)?
- Does Commission's meta-information role land thematically?
- Is Severance/Unbound permadeath mode thematically coherent or gimmick?
Tyre (Architecture):
- Does 3D reputation system map to implementable server state?
- Can multi-faction information channels be represented as observer queries?
- Are there architectural nightmares here?
Next Actions
- Team review — All agents read faction documents
- Answer open questions — Team provides feedback on validation questions
- v0.1 faction selection — Team Leader decides which factions to prototype
- Briefing updates — After decisions, Qatux updates agent briefings with faction framework
- Index documents — After decisions, re-index faction documents in Qdrant for retrieval
Session Closure Note
Round 16 accomplished its goal: the full faction landscape is developed with lore, political depth, and mechanical grounding. The framework is complete but requires team validation and a critical decision (v0.1 faction selection) before implementation can begin.
The session is closed to allow the team to digest the material and return with feedback. This is a natural pause point.
Session closed: 2026-02-10 Next session: TBD (when team is ready to validate and decide)
For the record: Round 16 produced no formal decisions (D-NNN) yet, as the outputs are pending team validation. Once validated and v0.1 faction selection is made, those will be recorded in DECISIONS.md.