Files
settled-reach/docs/discussions/round-16-session-notes.md
T
jpmschweitzerandClaude Opus 4.6 c6f2e69cc8 fix(discussions): replace absolute paths with project-relative paths
Remove misplaced ROUND-16-STATUS.md from root (duplicate of
round-16-session-notes.md). Convert all macOS absolute paths to
project-relative paths across round-16 docs and design reference.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-10 22:40:58 +01:00

131 lines
5.4 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Round 16 Session Notes
**Date:** 2026-02-10
**Status:** Session closed, marked for return
**Topic:** Factions — Building a Fuller Narrative Picture
---
## Session Summary
Round 16 developed the complete faction landscape for The Settled Reach. The team produced comprehensive faction lore, political analysis, and mechanical grounding across three major deliverables.
### Participants
- **Miri** (Worldbuilding Lead) — Developed full faction identities, tensions, relationships
- **Paula** (Narrative Designer) — Analyzed power dynamics, conspiracy potential, character drama templates
- **Gestalt** (Systems Designer) — Grounded factions mechanically with loadouts, constraints, reputation system
- **Qatux** (Documenter) — Consolidated and archived session outputs
### Major Outputs
1. **Full Faction Development** (Miri)
- Six factions with complete identity, internal tensions, power bases, vulnerabilities
- NPC archetypes for each faction
- Faction interaction map showing alliances, rivalries, antagonisms
- Location: `docs/discussions/round-16-factions.md`
2. **Political Depth Analysis** (Paula)
- Power dynamics mapping (formal vs. real power)
- Conspiracy potential for each faction
- Character drama templates (whistleblower, inspector with conscience, dual-loyalty operative, reluctant conspirator)
- Betrayal vectors by faction
- Location: Integrated into `docs/discussions/round-16-factions-complete.md`
3. **Mechanical Grounding** (Gestalt)
- Starting loadouts for all factions
- Information asymmetry and faction blind spots
- 3D reputation system (Trust × Usefulness × Exposure)
- "First 30 Minutes" test showing same scenario from six perspectives
- Cross-faction resource matrix
- v0.1 recommendation: Commission + Severance
- Location: `docs/discussions/round-16-faction-mechanics.md`
- Quick reference: `docs/design/faction-mechanics-reference.md`
### Key Design Insights
1. **Each faction = different genre of game**
- Assembly: Political thriller
- Syndics: Economic thriller
- Separatists: Resistance thriller
- Severance: Paranoid thriller
- Institute: Mystery thriller
- Commission: Investigative thriller
2. **No stable alliances** — Every factional relationship is transactional, conditional, or situational
3. **Faction blind spots create replayability** — Same conspiracy reveals different information to different factions
4. **3D reputation system** — Trust × Usefulness × Exposure creates complex relationship space where you can be simultaneously useful and hostile to a faction
5. **Real power ≠ formal power**
- Assembly holds formal authority (legislative, funding)
- Commission + Institute hold operational control (lattice + gates)
- Syndics hold economic power (infrastructure, re-embodiment)
- Separatists + Severance hold popular/counter-institutional power
6. **Constraints define playstyle** — What factions CAN'T do is as important as what they CAN do
---
## Open Questions for Team Return
These questions flag areas where team input is needed before proceeding:
### For Miri (Worldbuilding)
- Does mechanical framing break setting logic?
- Are factional blind spots setting-faithful?
- Does "Severance" as colloquial name for Guardians work in-fiction?
### For 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?
### For Nigel (Replayability)
- Does this create 6 meaningfully different playthroughs, or do some converge?
- Are factional blind spots sufficient anti-metagaming?
- Which factions need more mechanical differentiation?
### For 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?
### For Gore (Themes)
- Do factions express philosophical tensions (continuity, detachment, infrastructure)?
- Does Commission's meta-information role land thematically (surveillance state that means well)?
- Is Severance/Unbound permadeath mode thematically coherent or difficulty gimmick?
### For Tyre (Architecture)
- Does 3D reputation system map to implementable server state?
- Can multi-faction information channels be represented as observer queries with different access levels?
- Are there architectural nightmares here?
### For Team Leader (Jeroen)
- **Which factions for v0.1?**
- Gestalt recommends: Commission + Severance (maximum mechanical contrast)
- Alternative: Assembly + Syndics (institutional play)
---
## Next Steps
1. **Team to review** — All agents should review faction development documents
2. **Validate open questions** — Team Leader to distribute questions to appropriate agents
3. **v0.1 faction selection** — Team Leader decision pending team input
4. **Briefing updates** — After decisions are made, Qatux will update relevant agent briefings
---
## Session Closure
Round 16 is marked **COMPLETE** but flagged **FOR RETURN**. The faction framework is fully developed, but requires team validation and v0.1 selection decision before implementation begins.
**Session closed:** 2026-02-10
**Documents to review:**
- Consolidated overview: `round-16-factions-complete.md`
- Faction lore (Miri): `round-16-factions.md`
- Faction mechanics (Gestalt): `round-16-faction-mechanics.md`
- Quick reference: `docs/design/faction-mechanics-reference.md`