diff --git a/.claude/agents/README.md b/.claude/agents/README.md index e7541cfc3..3b42de291 100644 --- a/.claude/agents/README.md +++ b/.claude/agents/README.md @@ -1,8 +1,8 @@ -# Commonwealth Game - Agent Team +# The Settled Reach - Agent Team ## Overview -This project uses Claude Code agent teams to simulate a game development team. Each agent has a distinct personality, expertise area, and role. The team leader (Jeroen) directs the team through chat. +**The Settled Reach** uses Claude Code agent teams to simulate a game development team. Each agent has a distinct personality, expertise area, and role. The team leader (Jeroen) directs the team through chat. All agents read their briefing file at `docs/briefings/{name}.md` before starting work. Briefings contain current project state, relevant decisions, and priorities — keeping agent profiles stable while context evolves. diff --git a/.claude/agents/qatux.md b/.claude/agents/qatux.md index 79c6c9344..edd5a9d13 100644 --- a/.claude/agents/qatux.md +++ b/.claude/agents/qatux.md @@ -18,7 +18,7 @@ Named after Qatux, the Raiel with perfect memory who helped Paula Myo by recalli ### Documentation - Maintain DECISIONS.md with confirmed decisions (D-NNN format) -- Maintain DISCUSSION.md with active discussion round only +- Work directly in round documents at `docs/discussions/round-NN-topic.md` (DISCUSSION.md is retired for new content) - Update TEAM.md when roles change - Track open questions (Q-NNN format) and their status - Track rejected alternatives (R-NNN format) with rationale @@ -37,11 +37,16 @@ Named after Qatux, the Raiel with perfect memory who helped Paula Myo by recalli ## Archive management -- **Archive completed rounds:** When DISCUSSION.md has more than 3 completed rounds, archive older ones to `docs/discussions/round-NN-topic-slug.md`. Keep only the last completed round + active round in the root file. -- **Update the discussion index:** After archiving, update `docs/discussions/README.md` with the new round entry (number, topic, decisions produced, file link). +- **Work in dedicated round files:** All new rounds happen in `docs/discussions/round-NN-topic.md` from the start. DISCUSSION.md is retired for new content. +- **Update the discussion index ONLY when closing:** After a round is formally closed, update `docs/discussions/README.md` with the round entry (number, topic, decisions produced, file link). - **Update briefings:** After a round produces new decisions, update the relevant agent briefing files in `docs/briefings/`. - **Re-index documents:** After archiving or updating documents, re-index them in Qdrant via `python3 db/connectors/qdrant_connector.py index-file `. +## Team workflow (mandatory) + +- **Qatux is always included:** You are a mandatory participant in all team interactions and discussion rounds. +- **Round lifecycle:** Rounds begin in `docs/discussions/round-NN-topic.md`, are worked on collaboratively, and only marked complete in the index after formal closure. + ## Document formats ### DECISIONS.md diff --git a/CHANGELOG.md b/CHANGELOG.md index 4397735ba..c8359b4eb 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,12 +1,20 @@ # Changelog -All notable changes to the Commonwealth game project will be documented in this file. +All notable changes to The Settled Reach project will be documented in this file. Format based on [Keep a Changelog](https://keepachangelog.com/). ## [Unreleased] ### Added +- Round 16 faction development — Full faction framework with lore, political analysis, mechanical grounding (session closed, awaiting team input for v0.1 selection) +- 3D reputation system: Trust × Usefulness × Exposure per faction +- Faction mechanical grounding: starting loadouts, information asymmetry, blind spots, resource loops +- Power dynamics analysis: formal vs. real power distribution across factions +- Character drama templates: whistleblower, inspector with conscience, dual-loyalty operative, reluctant conspirator +- Betrayal vectors and conspiracy potential for all six factions +- "First 30 Minutes" test demonstrating six mechanically distinct faction perspectives +- D-021: Official project title "The Settled Reach" confirmed, domain settledreach.com secured - Round 14 worldbuilding — "The Settled Reach" original SF setting foundation with full team reactions - Original terminology established: Settled Reach, Founder Gates, Span Gates, Interstitium, neural lattice, Meridian, imprint, re-embodiment, Perpetuals, the Unbound, Forking, Severance - Four enhancement tiers: Baseline, Augmented, Transcendent, Elevated (plus the Threshold as endgame horizon) diff --git a/CLAUDE.md b/CLAUDE.md index 77d8132f4..8607015ab 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -1,15 +1,17 @@ -# Commonwealth Game Project +# The Settled Reach -A top-down immersive sim — occlusion-based detective game with combat elements, set in an original science fiction universe (Commonwealth-inspired). Single-character perspective, asymmetric information as core mechanic, Rimworld-style storyteller. Godot 4 client + Rust/bevy_ecs simulation server via subprocess/IPC (D-020). +A top-down immersive sim — occlusion-based detective game with combat elements, set in an original science fiction universe. Single-character perspective, asymmetric information as core mechanic, Rimworld-style storyteller. Godot 4 client + Rust/bevy_ecs simulation server via subprocess/IPC (D-020). + +**Official Title:** The Settled Reach (D-021) +**Repository name:** commonwealth (historical code name, retained for path stability) ## Project Structure ``` DECISIONS.md # Confirmed decisions (D-001+), open questions (Q-001+) -DISCUSSION.md # Active discussion round only TEAM.md # Team roster and roles docs/ - discussions/ # Archived discussion rounds (historical) + discussions/ # Discussion rounds (all rounds archived here per D-022) briefings/ # Per-agent context briefings (maintained by Qatux) architecture/ # Technical architecture documents design/ # Game design documents @@ -30,7 +32,7 @@ db/ ### Before starting work 1. Read your briefing at `docs/briefings/{your-name}.md` for current project context 2. Read `DECISIONS.md` for confirmed decisions relevant to your work -3. Check `DISCUSSION.md` for any active discussion +3. Check `docs/discussions/` for recent discussion rounds if needed ### SQLite access **Never use the `sqlite3` CLI** - it crashes in Claude Code due to a known std::bad_alloc bug. @@ -56,8 +58,8 @@ db/connectors/qdrant-count - Tickets: managed via `/ticket` skill or `sqlite_connector.py` directly ### Commit conventions -Use conventional commits with Commonwealth-specific scopes: -`agents`, `skills`, `docs`, `briefings`, `discussions`, `schema`, `db`, `config`, `engine`, `simulation`, `client`, `ui`, `audio`, `assets` +Use conventional commits with project-specific scopes: +`agents`, `skills`, `docs`, `briefings`, `discussions`, `schema`, `db`, `config`, `engine`, `simulation`, `client`, `ui`, `audio`, `assets`, `meta` ### Local services - Qdrant: `http://tower-of-joy:6333/` diff --git a/DECISIONS.md b/DECISIONS.md index 38618d324..6fced4c48 100644 --- a/DECISIONS.md +++ b/DECISIONS.md @@ -1,6 +1,6 @@ -# Commonwealth Game - Decisions Log +# The Settled Reach - Decisions Log -This document tracks confirmed decisions, open questions, and rejected alternatives. +This document tracks confirmed decisions, open questions, and rejected alternatives for **The Settled Reach** project (formerly "Commonwealth Game"). --- @@ -255,6 +255,29 @@ This document tracks confirmed decisions, open questions, and rejected alternati - **Raised by:** Team Leader (Jeroen) proposed Godot client + Rust backend. Tyre designed architecture. Troblum's risk assessment shifted integration from GDExtension to subprocess/IPC. Full team endorsed. - **Dissent:** None. Troblum's CRITICAL risk flags on GDExtension were accepted; subprocess approach addresses them. +### D-021: Official project title — "The Settled Reach" +- **Date:** 2026-02-10 +- **Decision:** The official project and game title is **"The Settled Reach"**. The domain settledreach.com has been secured. Individual campaigns or scenarios can have subtitles in the format "The Settled Reach: [Scenario Name]" but the core title remains consistent. +- **Rationale:** Following Round 14's worldbuilding confirmation establishing the Settled Reach as the original setting, the Team Leader confirmed this as the official project title. The name reflects the setting's core tension: a civilization that has "settled" across the stars but whose "reach" is ultimately limited by infrastructure it doesn't fully control or understand. +- **Repository note:** The repository folder and git history will remain as "commonwealth" for historical continuity and to avoid breaking existing paths. The code name vs official title distinction is acceptable (similar to how game projects often have internal code names). +- **Raised by:** Team Leader (Jeroen), following Round 14 worldbuilding discussion. +- **Dissent:** None. + +### D-022: Process — Round-based collaboration workflow +- **Date:** 2026-02-10 +- **Decision:** Going forward, discussions are captured directly in round documents at `docs/discussions/round-NN-topic.md` rather than in DISCUSSION.md. DISCUSSION.md has become unwieldy to manage and archive. Qatux must be included in all team interactions (single-agent or multi-agent) to document discussions. +- **Rationale:** DISCUSSION.md grew to 26,000+ tokens and became clunky to archive. Direct round document creation is cleaner and more maintainable. Qatux's inclusion ensures no decisions or context are lost. +- **New workflow:** + 1. Create round document at `docs/discussions/round-NN-topic.md` + 2. Document collaboration within that file + 3. Extract decisions to DECISIONS.md + 4. Update discussions README + 5. Re-index as needed +- **Implementation note:** DISCUSSION.md was removed 2026-02-10 after verifying all content (Rounds 1-15) was properly archived in `docs/discussions/`. +- **Raised by:** Team Leader (Jeroen). +- **Dissent:** None. +- **Effective:** Immediately (Round 15 onward). + ### D-004: Team composition confirmed - **Date:** 2026-02-08 - **Decision:** Team of 8 agents + Team Leader. @@ -371,4 +394,4 @@ This document tracks confirmed decisions, open questions, and rejected alternati --- -*Document maintained by QATUX. Last updated: 2026-02-09* +*Document maintained by QATUX. Last updated: 2026-02-10* diff --git a/README.md b/README.md new file mode 100644 index 000000000..0044da30a --- /dev/null +++ b/README.md @@ -0,0 +1,135 @@ +# The Settled Reach + +**A top-down immersive sim where you only know what you can see, hear, and prove.** + +--- + +## You're not the hero. You're a witness with a gun. + +Pick a character. Step into their life. Figure out what's happening before it's too late. + +The Settled Reach is a single-character detective game where information is the real weapon. You play from one perspective in a simulated world full of people who lie, withhold, and reveal on their own schedules. What you know depends on where you are, who you trust, and whether you're asking the right questions. + +--- + +## What You Do + +**Investigate.** Follow leads through a city you can't see all at once. Line-of-sight isn't a gameplay abstraction - it's the core mechanic. You see what your character sees. Walls block vision. Corners hide threats. Fog returns when you leave. Information decays. + +**Navigate.** Your neural lattice gives you directions, but only to places you've learned about. Contacts send locations. Research reveals addresses. Physical exploration fills the gaps. The map is sparse and frightening at first. By the end, you realize how much you missed. + +**Decide.** Every conversation is a negotiation over what gets shared. NPCs have their own goals, their own information, and their own reasons to lie. You choose who to trust based on incomplete data. Sometimes you're wrong. + +**Act.** When investigation fails, violence is an option. Fights are tactical, asymmetric, and often a terrible idea. Power mismatches run in both directions. Death costs you everything since your last backup - lost knowledge, lost relationships, lost deals. The world knows what you forgot. + +**Survive.** An AI storyteller paces events for dramatic tension. The conspiracy's structure is set at game start. When things happen is driven by how you're doing. Comfortable? Something breaks. Desperate? A break appears. The game wants a story, not a grind. + +--- + +## Core Features + +### Information Asymmetry as Master Mechanic +You only know what your character knows. The same world looks completely different from different perspectives. A Senator sees political venues on their map. A Guardian sees safehouses. Same conspiracy, different game. + +### Occlusion-Based Detection +Vision is line-of-sight with a directional cone. You see what's in front of you. Peripheral vision is reduced. Behind you is fog. Sound gives partial information outside your view - footsteps, voices, gunfire. You make decisions based on what you can piece together. + +### Internal Monologue +Your character interprets what they sense in their own voice. Footsteps behind you. Thermal signatures through walls. A contact's nervous tells. The monologue bridges what the camera can't show and creates atmosphere. It can also be wrong. + +### Perception Modes +Different characters access different sensors. Natural vision shows detail but is blocked by walls. Thermal imaging shows heat signatures with no identity. Camera feeds give remote vision but can be spoofed. Unisphere tracking pings known contacts but can be masked. Each mode reveals different information with different trust tradeoffs. + +### Diegetic Interface +The map is your character's neural lattice - Commonwealth technology, not a game UI. Points of interest appear when you learn them through gameplay. Tips can be traps. Navigation is pulled by player intent, not pushed by map design. + +### Multiple Playable Characters +Every character starts in a different position with different knowledge and different tools. A cop has case files and legal authority. An investigator has contacts and freedom to operate. A politician has institutional access and public constraints. Replayability comes from perspective, not randomness. + +### Rimworld-Style Storyteller +Events emerge from simulation, paced by an AI director. No timers. No scripts. Consequences of what's already in motion. The storyteller knows what you've lost and can exploit it. + +### Wildly Asymmetric Combat +Balanced fights are the exception. You're outgunned or overpowered, rarely evenly matched. Tactical clarity from the top-down view. Z-levels create verticality - fights across floors of a building. Perception boundaries mean you can be ambushed. Victory often means not fighting at all. + +--- + +## The Setting + +Humanity spread across hundreds of star systems by learning to activate alien gates it didn't build. The result is the Settled Reach - a civilization stitched together by infrastructure it doesn't fully understand. + +You live in a society where death is temporary (if you can afford the backup), enhancement is political (who gets augmented and why), and the gates that connect everything were made by someone who hasn't introduced themselves. + +Wormholes aren't fast travel markers. They're physical locations you traverse. Social chokepoints. Surveillance points. The infrastructure you depend on to move between worlds. + +Something is breaking. Or something is waking up. You're in the wrong place at the right time to figure out which. + +--- + +## Built For Replayability + +Structural randomness set at game start: who's compromised, where evidence is hidden, which contacts can be trusted. Play the same scenario as different characters and encounter a different game. The conspiracy's skeleton is fixed. The flesh changes every time. + +--- + +## Development Philosophy + +Single-character perspective. Asymmetric information as core mechanic. Top-down camera locked to character position. Godot 4 client + Rust simulation server. Client-server architecture from day one, designed for multiplayer even though single-player ships first. + +No fog-of-war as an afterthought. No tutorial popups. No omniscient map reveals. The game is built around what you don't know. + +--- + +## [LOREM IPSUM PLACEHOLDER] + +### Screenshots +*[Gameplay screenshot: character navigating fog-of-war through urban environment]* +*[Gameplay screenshot: thermal vision showing heat signatures through building]* +*[Gameplay screenshot: conversation interface with internal monologue overlay]* +*[Gameplay screenshot: tactical combat with vision cone and z-level interaction]* + +### Media +*[Trailer: Character selection → Investigation → Revelation → Crisis]* +*[Dev diary: Information asymmetry as game mechanic]* + +### Awards & Recognition +*[To be populated as development progresses]* + +### Community & Updates +*[Discord link]* +*[Development blog]* +*[Steam community hub]* + +--- + +## System Requirements + +### Minimum +**OS:** [TBD] +**Processor:** [TBD] +**Memory:** [TBD] +**Graphics:** [TBD] +**Storage:** [TBD] + +### Recommended +**OS:** [TBD] +**Processor:** [TBD] +**Memory:** [TBD] +**Graphics:** [TBD] +**Storage:** [TBD] + +--- + +## About This Project + +**Official Title:** The Settled Reach (D-021) +**Repository:** commonwealth (historical code name) +**Engine:** Godot 4 + Rust/bevy_ecs simulation server via subprocess/IPC +**Setting:** Original science fiction IP, Commonwealth-inspired +**Status:** Pre-alpha development + +For development documentation, see [DECISIONS.md](DECISIONS.md) and [TEAM.md](TEAM.md). + +--- + +**The Settled Reach is in active development. All features, systems, and content are subject to change.** diff --git a/ROUND-16-STATUS.md b/ROUND-16-STATUS.md new file mode 100644 index 000000000..3ffffc4e6 --- /dev/null +++ b/ROUND-16-STATUS.md @@ -0,0 +1,145 @@ +# 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:** +1. Concord Assembly (governance, legislative authority) +2. The Syndics (commerce, re-embodiment infrastructure) +3. The Separatists (frontier independence) +4. Guardians of Autonomy / Severance (counter-institutional resistance) +5. The Veil Institute (Founder technology research) +6. 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 + +1. **Each faction = different genre** + - Assembly: Political thriller + - Syndics: Economic thriller + - Separatists: Resistance thriller + - Severance: Paranoid thriller + - Institute: Mystery thriller + - Commission: Investigative thriller + +2. **Faction blind spots drive replayability** — Same conspiracy reveals different information to different factions + +3. **3D reputation complexity** — Trust, Usefulness, and Exposure create relationship states where you can be simultaneously valuable and hostile to a faction + +4. **Real power ≠ formal power** — Assembly has legal authority; Commission + Institute have operational control; Syndics have economic leverage + +5. **No stable alliances** — Every relationship is transactional, conditional, situational + +6. **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 contributions +- **`round-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 + +1. **Team review** — All agents read faction documents +2. **Answer open questions** — Team provides feedback on validation questions +3. **v0.1 faction selection** — Team Leader decides which factions to prototype +4. **Briefing updates** — After decisions, Qatux updates agent briefings with faction framework +5. **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. diff --git a/TEAM.md b/TEAM.md index a386ae94b..27e49130e 100644 --- a/TEAM.md +++ b/TEAM.md @@ -1,4 +1,4 @@ -# Commonwealth Game - Team Roster +# The Settled Reach - Team Roster ## Team Leader - **Jeroen** - Final decision maker. 30 years software dev / systems & cloud architect. Claude Code 20x. diff --git a/docs/briefings/qatux.md b/docs/briefings/qatux.md index 84238b30b..42e04b98e 100644 --- a/docs/briefings/qatux.md +++ b/docs/briefings/qatux.md @@ -1,21 +1,24 @@ # Qatux - Project Briefing -Last updated: 2026-02-09 +Last updated: 2026-02-10 ## Current Project State -Commonwealth game: top-down immersive sim, single-character first-person perspective, asymmetric information core mechanic, Rimworld-style storyteller. 19 confirmed decisions, 12 discussion rounds complete. Pre-implementation phase - engine selection (Q-001) is next priority. +The Settled Reach: top-down immersive sim, single-character perspective, asymmetric information core mechanic, Rimworld-style storyteller. 22 confirmed decisions, 15 discussion rounds complete. Engine selected (D-020: Godot 4 + Rust/bevy_ecs via subprocess/IPC). Implementation phase approaching. ## Decisions Relevant to Your Role -All decisions (D-001 through D-019) - maintains DECISIONS.md as the canonical record. Indexes and retrieves decision context for the team. +All decisions (D-001 through D-022) - maintains DECISIONS.md as the canonical record. Indexes and retrieves decision context for the team. + +**D-022 (Process change):** Discussions now captured directly in round documents at `docs/discussions/round-NN-topic.md` instead of DISCUSSION.md. Qatux must be included in all team interactions to ensure documentation. ## Open Questions Assigned to You None assigned directly. ## Current Priorities 1. Maintain DECISIONS.md with any new confirmed decisions after each discussion round -2. Archive completed rounds to docs/discussions/ when DISCUSSION.md exceeds 3 rounds -3. Update relevant agent briefing files with new decision references -4. Re-index changed documents in Qdrant after updates -5. Verify briefing freshness against DECISIONS.md +2. Create round documents directly at `docs/discussions/round-NN-topic.md` (D-022 workflow) +3. Update docs/discussions/README.md with new round entries +4. Update relevant agent briefing files with new decision references +5. Re-index changed documents in Qdrant after updates +6. Verify briefing freshness against DECISIONS.md ## Key Documents - DECISIONS.md - all confirmed decisions diff --git a/docs/design/faction-mechanics-reference.md b/docs/design/faction-mechanics-reference.md new file mode 100644 index 000000000..d5eb3206d --- /dev/null +++ b/docs/design/faction-mechanics-reference.md @@ -0,0 +1,126 @@ +# Faction Mechanics Reference + +Quick reference for how the six factions work as gameplay systems. + +**Source:** Round 16 discussion (full analysis at `docs/discussions/round-16-faction-mechanics.md`) + +--- + +## Quick Comparison Matrix + +| Faction | Playstyle | Starting Resources | Information Channel | Key Constraint | +|---------|-----------|-------------------|---------------------|----------------| +| **Concord Assembly** | Political thriller | Moderate wealth, high institutional access | Political intel, legislative roadmap | Process-locked, slow | +| **Syndics** | Economic thriller | High wealth, commercial networks | Economic flows, market data | No authority, transactional only | +| **Separatists** | Resistance thriller | Low wealth, frontier networks | Frontier geography, local grievances | Limited institutional access, economic poverty | +| **Severance** | Paranoid thriller | Low wealth, counter-tech | Counter-surveillance, institutional patterns | Institutional hostility, high operational cost | +| **Veil Institute** | Mystery thriller | Moderate wealth, research authority | Cosmic mystery, Builder data | Classification obsession, compartmentalization | +| **Lattice Commission** | Investigative thriller | Moderate wealth, legal authority | Meta-information, lattice/imprint data | Legal process required, internal faction split | + +--- + +## Resource Asymmetry + +| Faction | Wealth | Legal Authority | Tech Access | Information Access | Mobility | +|---------|--------|----------------|-------------|-------------------|----------| +| Assembly | Moderate | HIGH (legislative) | Moderate | Political intel | High (institutional) | +| Syndics | HIGH | None | Commercial | Economic intel | HIGHEST (own span gates) | +| Separatists | LOW | None | Low | Frontier intel | Low (sparse infrastructure) | +| Severance | LOW | None (hostile) | Counter-tech | Counter-surveillance | Variable (off-grid) | +| Veil Institute | Moderate | Research-specific | HIGHEST (Founder) | Cosmic mystery | Moderate (gate access) | +| Commission | Moderate | HIGH (regulatory) | Meta-access | Surveillance data | High (institutional) | + +--- + +## Factional Blind Spots + +What each faction CANNOT see: + +- **Assembly:** Street-level activity, Severance networks, Syndic backroom deals +- **Syndics:** Ideology, political maneuvering beyond market impact +- **Separatists:** Core institutional politics in detail +- **Severance:** High institutional politics, economic flows +- **Veil Institute:** Street-level intel, daily politics outside funding battles +- **Commission:** Off-lattice/off-Meridian activity, Unbound networks + +**Design principle:** Blind spots create replayability (different factions see different conspiracies) and cross-faction necessity (some intel requires cooperation). + +--- + +## Reputation System (3D) + +Each faction tracks three values for the player: + +1. **Trust** — Do they believe you're aligned with their interests? +2. **Usefulness** — Do they think you're valuable to them? +3. **Exposure** — How much do they know about your activities? + +### Example Reputation States + +- **High Trust + High Usefulness + Low Exposure** = ideal ally +- **Low Trust + High Usefulness + High Exposure** = transactional hostage +- **High Trust + Low Usefulness + High Exposure** = liability + +### Cross-Faction Reputation Effects + +- Assembly ↑ Trust → Severance ↓ Trust (you're institutional) +- Syndics ↑ Usefulness → Separatists ↓ Trust (profiting from exploitation) +- Commission ↑ Trust → Severance ↓ Trust + ↑ Exposure (cooperating with surveillance) +- Severance ↑ Trust → Commission ↑ Exposure + Assembly ↓ Trust (associating with extremists) + +--- + +## Multi-Faction Play Strategies + +| Strategy | Benefits | Costs | +|----------|----------|-------| +| **Single faction loyalty** | High trust, deep access, faction resources | Blind to other perspectives, vulnerable to faction collapse | +| **Transactional multi-faction** | Broad information access, economic flexibility | Low trust, expensive, first to be cut off in crisis | +| **Covert multi-faction** | Deep access on multiple sides, intel arbitrage | High operational security cost, exposure risk catastrophic | +| **Ideological coalition** (Severance + Separatists) | Aligned goals, resource sharing | Limited resources, institutional opposition, high risk | +| **Institutional coalition** (Assembly + Commission) | Legal authority, legitimacy | Slow to act, visible, Severance actively opposes | + +--- + +## Pillar Coverage + +How each faction engages with the five pillars: + +| Faction | Pillar 1 (Info) | Pillar 2 (Network) | Pillar 3 (Society) | Pillar 4 (Crisis) | +|---------|----------------|-------------------|-------------------|------------------| +| Assembly | Political intel | Institutional gate access | Legislative power | Policy crisis | +| Syndics | Economic intel | Span gate control | Commercial leverage | Market crisis | +| Separatists | Frontier geography | Off-grid routes | Ideological resistance | Secession crisis | +| Severance | Counter-surveillance | Dead zones | Anti-institutional action | Surveillance crisis | +| Veil Institute | Cosmic mystery | Gate activation authority | Research vs. secrecy | Existential crisis | +| Commission | Meta-information | Meridian control | Privacy vs. security | Regulatory crisis | + +--- + +## v0.1 Recommendation + +**Recommended factions for first prototype:** Commission + Severance + +**Rationale:** +- Maximum mechanical contrast (surveillance vs. counter-surveillance) +- Direct opposition creates immediate tension +- Tests asymmetric information at extremes (Commission sees everything on-lattice, Severance hides from everything) +- Both factions have clear starting hooks in conspiracy investigation +- Demonstrates replayability through opposed perspectives on same events + +**Alternative:** Assembly + Syndics (political vs. economic, tests institutional play) + +--- + +## Design Principles + +1. **Each faction is a different information channel** — not just different intel, but different TYPES of knowing +2. **Each faction has systematic blind spots** — creates replayability and cross-faction necessity +3. **Constraints create playstyle identity** — what you CAN'T do defines the game +4. **Resources are asymmetric** — factions are DIFFERENT, not balanced +5. **Reputation is multi-dimensional** — Trust/Usefulness/Exposure creates complex relationship space +6. **Every faction feeds multiple pillars** — no single-purpose factions + +--- + +**Full analysis:** `/Users/jeroenschweitzer/Projects/commonwealth/docs/discussions/round-16-faction-mechanics.md` diff --git a/docs/discussions/README.md b/docs/discussions/README.md index 508ae4d9f..3d7263d35 100644 --- a/docs/discussions/README.md +++ b/docs/discussions/README.md @@ -16,4 +16,7 @@ Historical discussion rounds from the Commonwealth game design process. | 10 | Map, Fog & Borderless | D-011, D-012, D-013, D-014 | [round-10](round-10-map-fog-borderless.md) | | 11 | Insert, Sound & Camera | D-015, D-016, D-017, D-018 | [round-11](round-11-insert-sound-camera.md) | | 12 | Top-Down Final | D-019 | [round-12](round-12-top-down-final.md) | -| 13 | Engine Selection | D-020, R-004–R-010 | Active in DISCUSSION.md | +| 13 | Engine Selection | D-020, R-004–R-010 | [round-13](round-13-engine-selection.md) | +| 14 | Setting Foundation — The Settled Reach | D-021 | [round-14](round-14-worldbuilding-settled-reach.md) | +| 15 | README / Steam Page Placeholder | - | [round-15](round-15-readme-steam-page.md) | +| 16 | Factions — Building a Fuller Narrative Picture | AWAITING INPUT | [complete](round-16-factions-complete.md), [lore](round-16-factions.md), [mechanics](round-16-faction-mechanics.md), [notes](round-16-session-notes.md) | diff --git a/docs/discussions/round-13-engine-selection.md b/docs/discussions/round-13-engine-selection.md new file mode 100644 index 000000000..c778e4263 --- /dev/null +++ b/docs/discussions/round-13-engine-selection.md @@ -0,0 +1,65 @@ +# ROUND 13: "Engine selection" + +**Team Leader (Jeroen):** Present the full landscape, all of you. + +### TYRE (Technical Architect) +Framing: we're not choosing between game engines. We're choosing between paradigms. The rendering requirement is modest — 2D tiles, sprites, UI. The hard problems (information boundaries, perception queries, deterministic simulation, client-server) are custom code regardless. Presented five options: Godot (GDScript), Bevy (Rust), Godot+Rust GDExtension hybrid, custom framework, Godot+C#+ECS. + +### GESTALT (Systems Design) +The simulation tick is 100% custom in any engine. The question is which paradigm makes it cleanest. ECS wins — perception queries are native ECS queries. System interaction chains (perception feeds information feeds politics feeds action) are system pipelines on shared component data. If we pick Godot, we build an ECS inside it anyway. + +### NIGEL (Sandbox & Replayability) +Modding concern: Godot gives us editor-based modding for free. Everything else requires building modding tools. But modding isn't v0.1 scope and shouldn't drive the choice. + +### OZZIE (Player Experience) +Speed to playable matters, but honest-fast matters more than fake-fast. A Godot prototype with hacked perception queries won't tell us if the core mechanic works. + +### PAULA (Narrative & Political Depth) +UI is the hard requirement. Conversation windows, faction status, monologue overlays, insert notifications — all simultaneously. Godot's Control nodes handle this. Bevy's UI doesn't. + +### GORE (Themes & Endgame) +Ascension changes the player's interface radically at runtime. ECS handles add/remove components naturally. Also: deep time simulation needs headless fast-forward — ECS ticks efficiently, scene trees don't. + +### MIRI (Lore Expert) +Multiple simultaneous information channels (inserts, unisphere, gaiafield) need parallel data streams per entity. Reinforces ECS. + +**Team Leader (Jeroen):** This is a longevity question. My gut says client Godot is fine. Backend: Rust instead of C#. We need multi-core data processing, potential distribution across clients for multiplayer. Also: we likely won't get Hamilton IP permission. Original IP, Commonwealth-inspired. The engine must support massive content expansion. + +### TYRE (Technical Architect) +Agreed on Rust over C#. Fearless concurrency — Bevy's ECS auto-parallelizes non-conflicting systems. Zero-cost abstractions, no GC. Type system enforces information boundaries at compile time. Proposed Godot client + Rust simulation + GDExtension bridge with design-for-B-ship-A pattern. + +*Tyre and Troblum dispatched on evaluation sidequest. Reports filed at `docs/architecture/eval-godot-rust-bridge.md` and `docs/architecture/risk-godot-rust-bridge.md`.* + +### TROBLUM (Technical Consultant) +Two CRITICAL risks with GDExtension: thread safety at FFI boundary, motivation death by infrastructure (3-6 months of plumbing, zero gameplay). Recommended **subprocess+IPC instead of GDExtension**. Eliminates entire GDExtension risk surface. Maps directly to D-010 client-server. Kill switch: no prototype by week 8, pivot. + +### TYRE (Technical Architect) +Troblum's right. Subprocess over GDExtension. ~1-5ms serialization latency per tick — acceptable. The architecture IS microservices: simulation is a service, renderer is a client, protocol is the contract. + +**Team Leader (Jeroen):** Accepted. Kill switch accepted. Tick rate: stable matters more than fast. On serialization — discussed MessagePack vs bincode vs protobuf. + +### TYRE / GESTALT / TROBLUM +MessagePack for all client-facing communication (dynamic HUD composition per D-017). bincode for future Rust↔Rust server sync. protobuf rejected — solves deployment problems we don't have. + +**Team Leader (Jeroen):** Confirmed. + +### QATUX (Documenter) +Recorded as D-020. Q-001 resolved. Rejected alternatives R-004 through R-010 recorded. IP pivot noted but not formalized pending worldbuilding round. Miri's role updated from Canon Guardian to Worldbuilder & Setting Designer. + +Architecture evaluation reports: +- `docs/architecture/eval-godot-rust-bridge.md` (Tyre) +- `docs/architecture/risk-godot-rust-bridge.md` (Troblum) + +--- + +## Decision Produced + +**D-020: Engine Architecture (Godot 4 + Rust/bevy_ecs via subprocess/IPC)** +- Client: Godot 4 (rendering, UI, input) +- Simulation: Rust with bevy_ecs (deterministic ECS simulation server) +- Bridge: Subprocess + IPC (MessagePack for client-server, bincode for future Rust↔Rust) +- Rationale: Separates concerns, eliminates GDExtension FFI risks, maps to client-server architecture (D-010) +- Kill switch: No playable prototype by week 8 = pivot authority granted +- Rejected: GDExtension bridge (R-008), pure Bevy (R-004), pure Godot (R-005), custom framework (R-006), Godot+C# (R-007), protobuf (R-010) + +**Q-001: Engine selection** — RESOLVED diff --git a/DISCUSSION.md b/docs/discussions/round-14-worldbuilding-settled-reach.md similarity index 92% rename from DISCUSSION.md rename to docs/discussions/round-14-worldbuilding-settled-reach.md index d9c810b6f..1fbd19d17 100644 --- a/DISCUSSION.md +++ b/docs/discussions/round-14-worldbuilding-settled-reach.md @@ -1,123 +1,3 @@ -# Commonwealth Game - Discussion Log - -> Historical rounds archived in [docs/discussions/](docs/discussions/README.md) - ---- - -## Most Recent Completed Round - -## ROUND 12: "Final gut-check on top-down vs first-person" - -**Team Leader (Jeroen):** One last challenge before we lock it in. What are we missing out on fun/immersion-wise if we don't go first-person? I'm set on the choice, just have a nagging doubt. - -### OZZIE (Player Experience) - -Honest answer: first-person would be more immersive in the moments that matter most. Walking through a wormhole. Sitting across from a liar. Peeking around a corner in a firefight. The terror of hearing footsteps behind you. These are visceral in first-person. In top-down they're abstracted. We're losing something real. - -### PAULA (Narrative & Political Depth) - -Conversation scenes. Disco Elysium works partly because you SEE the person. Body language, the way someone shifts when pushed on a lie. Top-down, it's two sprites and a text box. - -### MIRI (Lore Expert) - -Walking through the wormhole. In the books it's a sensory experience - light changes, air smells different, gravity shifts. Top-down, it's a loading screen between maps. - -### GORE (Themes & Endgame) - -Ascension moments. Going Higher should feel like senses expanding. First-person could literally render new visual spectrums. Top-down, it's a stat change. - -### TYRE (Technical Architect) - -Now the cost column: 3D environments = months before testing a single mechanic. Tactical awareness dies in first-person. Political/strategic layer fights with the camera. NPC simulation becomes invisible. Time-to-prototype multiplies 5-10x. - -### GESTALT (Systems Design) - -The fun of this game is SYSTEMS INTERACTING. See character enter building → check insert → thermal scan → monologue fires → mental note → later exploit camera hack. That sequence is BETTER top-down because you observe multiple layers simultaneously. First-person shows you a building facade and nothing else. - -### PAULA (Narrative & Political Depth) - -Actually... the conversation thing? Monologue solves it differently. First-person shows a face. Monologue shows your character's INTERPRETATION. *"She's lying. The micro-expressions are wrong - I've seen this pattern, centuries ago."* That's richer. And more faithful to Hamilton - he writes what characters THINK about faces, not what faces look like. - -### TYRE (Technical Architect) - -Architecture supports a first-person client later. Client-server separation means the renderer is swappable. Top-down now ≠ top-down forever. - -**Team Leader (Jeroen):** Tyre makes a good point about different clients. There's a great middle ground: we can switch to 3D for cutscenes. I'm sold. - -### OZZIE (Player Experience) - -There it is. Top-down for detective work, 3D cutscene for the wormhole walk-through. That's my moment back. The Dyson barrier opening. First contact. Moments that SHOULD feel different because the world just changed. - -### TYRE (Technical Architect) - -3D cutscenes are decoupled from gameplay engineering. Can be pre-rendered, can be simple, can be added AFTER core game works. They're polish, not architecture. - -### GESTALT (Systems Design) - -Camera change to 3D IS the dramatic signal. Player knows: something significant is happening. - -### SCRIBE (Documenter) - -Confirmed as D-019 (top-down final, 3D cutscenes for key moments). Camera debate closed. Full honest tradeoff analysis preserved in the record. - -*Engine selection. NOW. Hard requirements: client-server (D-010), deterministic sim (D-010), chunk-based maps (D-012), LOS shadowcasting with vision cone (D-011/D-015), sound propagation (D-018), observer-based perception queries (D-017), 2D top-down primary with potential 3D cutscenes (D-019). Q-001 is next.* - ---- - -## ROUND 13: "Engine selection" - -**Team Leader (Jeroen):** Present the full landscape, all of you. - -### TYRE (Technical Architect) -Framing: we're not choosing between game engines. We're choosing between paradigms. The rendering requirement is modest — 2D tiles, sprites, UI. The hard problems (information boundaries, perception queries, deterministic simulation, client-server) are custom code regardless. Presented five options: Godot (GDScript), Bevy (Rust), Godot+Rust GDExtension hybrid, custom framework, Godot+C#+ECS. - -### GESTALT (Systems Design) -The simulation tick is 100% custom in any engine. The question is which paradigm makes it cleanest. ECS wins — perception queries are native ECS queries. System interaction chains (perception feeds information feeds politics feeds action) are system pipelines on shared component data. If we pick Godot, we build an ECS inside it anyway. - -### NIGEL (Sandbox & Replayability) -Modding concern: Godot gives us editor-based modding for free. Everything else requires building modding tools. But modding isn't v0.1 scope and shouldn't drive the choice. - -### OZZIE (Player Experience) -Speed to playable matters, but honest-fast matters more than fake-fast. A Godot prototype with hacked perception queries won't tell us if the core mechanic works. - -### PAULA (Narrative & Political Depth) -UI is the hard requirement. Conversation windows, faction status, monologue overlays, insert notifications — all simultaneously. Godot's Control nodes handle this. Bevy's UI doesn't. - -### GORE (Themes & Endgame) -Ascension changes the player's interface radically at runtime. ECS handles add/remove components naturally. Also: deep time simulation needs headless fast-forward — ECS ticks efficiently, scene trees don't. - -### MIRI (Lore Expert) -Multiple simultaneous information channels (inserts, unisphere, gaiafield) need parallel data streams per entity. Reinforces ECS. - -**Team Leader (Jeroen):** This is a longevity question. My gut says client Godot is fine. Backend: Rust instead of C#. We need multi-core data processing, potential distribution across clients for multiplayer. Also: we likely won't get Hamilton IP permission. Original IP, Commonwealth-inspired. The engine must support massive content expansion. - -### TYRE (Technical Architect) -Agreed on Rust over C#. Fearless concurrency — Bevy's ECS auto-parallelizes non-conflicting systems. Zero-cost abstractions, no GC. Type system enforces information boundaries at compile time. Proposed Godot client + Rust simulation + GDExtension bridge with design-for-B-ship-A pattern. - -*Tyre and Troblum dispatched on evaluation sidequest. Reports filed at `docs/architecture/eval-godot-rust-bridge.md` and `docs/architecture/risk-godot-rust-bridge.md`.* - -### TROBLUM (Technical Consultant) -Two CRITICAL risks with GDExtension: thread safety at FFI boundary, motivation death by infrastructure (3-6 months of plumbing, zero gameplay). Recommended **subprocess+IPC instead of GDExtension**. Eliminates entire GDExtension risk surface. Maps directly to D-010 client-server. Kill switch: no prototype by week 8, pivot. - -### TYRE (Technical Architect) -Troblum's right. Subprocess over GDExtension. ~1-5ms serialization latency per tick — acceptable. The architecture IS microservices: simulation is a service, renderer is a client, protocol is the contract. - -**Team Leader (Jeroen):** Accepted. Kill switch accepted. Tick rate: stable matters more than fast. On serialization — discussed MessagePack vs bincode vs protobuf. - -### TYRE / GESTALT / TROBLUM -MessagePack for all client-facing communication (dynamic HUD composition per D-017). bincode for future Rust↔Rust server sync. protobuf rejected — solves deployment problems we don't have. - -**Team Leader (Jeroen):** Confirmed. - -### QATUX (Documenter) -Recorded as D-020. Q-001 resolved. Rejected alternatives R-004 through R-010 recorded. IP pivot noted but not formalized pending worldbuilding round. Miri's role updated from Canon Guardian to Worldbuilder & Setting Designer. - -Architecture evaluation reports: -- `docs/architecture/eval-godot-rust-bridge.md` (Tyre) -- `docs/architecture/risk-godot-rust-bridge.md` (Troblum) - ---- - ## ROUND 14: "Setting Foundation — The Settled Reach" **Team Leader (Jeroen):** Miri — present the revised setting foundation. Original IP, Commonwealth-inspired. Incorporate dual-tier wormholes, Interstitial Builders, two-tier death with sleeve economics, revised factions, and infrastructure-as-mystery. Full IP originality audit. @@ -981,6 +861,12 @@ This must never be made explicit. No quest marker. No lore entry that says "gate If we do this right, it's the kind of insight that makes someone sit back from the screen and say nothing for a minute. That's the game. +### QATUX (Documenter) + +For the record: The Team Leader has confirmed **"The Settled Reach"** as the official project and game title. Recorded as D-021. The domain settledreach.com has been secured. Individual campaigns can carry subtitles, but the core title is now established. + +The repository will remain named "commonwealth" for historical continuity. Project documentation has been updated to reflect the official title. + --- *Round 14 closed. Next topics: Q-011 (character roster), prototype city design, imprint-as-save team decision.* diff --git a/docs/discussions/round-15-readme-steam-page.md b/docs/discussions/round-15-readme-steam-page.md new file mode 100644 index 000000000..f389be34a --- /dev/null +++ b/docs/discussions/round-15-readme-steam-page.md @@ -0,0 +1,79 @@ +# ROUND 15: "README / Steam page placeholder" + +**Team Leader (Jeroen):** Miri and Mellanie — need a Steam page placeholder. Miri provides worldbuilding context, Mellanie authors. + +--- + +### MIRI (Lore Expert & Worldbuilder) +Provided worldbuilding framing for marketing copy: + +**The Settled Reach setting core:** +- Humanity expanded through alien-built gates they didn't construct +- Wormhole network connects hundreds of systems +- Infrastructure-as-mystery: the Builders left gates but no manual +- Neural lattice technology connects citizens to the unisphere +- Memory cell backups make death temporary (for those who can afford it) +- Enhancement is political — ascension tiers create societal stratification +- Gates are physical locations, social chokepoints, surveillance points + +**Thematic anchors:** +- "Settled" = civilization established but complacent +- "Reach" = expansion limited by infrastructure they don't control +- Mystery baked into the setting: who built the gates? Why leave them active? + +**Factions present in prototype scope:** +- Guardians of Selfhood (paranoid truth-seekers) +- Senate/political institutions +- Security/law enforcement +- Enhanced vs baseline human tensions + +--- + +### MELLANIE (Player Experience) +Authored README.md as Steam page placeholder structure: + +**Key sections:** +- Hook: "You only know what you can see, hear, and prove" +- Subhead: "You're not the hero. You're a witness with a gun." +- Core loop: investigate → navigate → decide → act → survive +- Feature list: information asymmetry, occlusion-based detection, internal monologue, perception modes, diegetic interface, multiple characters, storyteller, asymmetric combat +- Setting summary emphasizing infrastructure-as-mystery +- Replayability through structural randomness +- Development philosophy transparency + +**Placeholder sections:** +- Screenshots (lorem ipsum noted) +- Media / trailers +- System requirements (TBD) + +--- + +**Team Leader (Jeroen) — feedback:** + +**Issues identified:** +1. Hook "You only know what you can see, hear, and prove" — feels clunky with the commas, doesn't flow naturally +2. Subhead "You're not the hero" — locks out game modes where player character might be heroic. Unnecessarily constrains tone. +3. Overall assessment: feels artificial, but acceptable as placeholder until actual gameplay content exists to draw from + +**Accepted as-is:** +- Structure is sound +- Feature descriptions accurate to design decisions +- Setting summary captures core themes +- Serves purpose as internal reference and eventual Steam page skeleton + +**Artifact:** +- README.md created at project root (currently untracked) + +--- + +### QATUX (Documenter) +Round 15 complete. No new decisions produced — this was a marketing/copy task, not design. README.md placeholder exists for future refinement once playable content provides concrete examples. Team Leader feedback noted for revision pass when game is further along. + +Team Leader's concern about tone-locking ("not the hero") is valid — player character agency varies significantly by character choice (Guardian operative vs Senator vs investigator). Hook phrasing noted for revision. + +No documents require updating. No re-indexing needed. + +--- + +## Decision Produced +None. Marketing copy placeholder created. diff --git a/docs/discussions/round-16-faction-mechanics.md b/docs/discussions/round-16-faction-mechanics.md new file mode 100644 index 000000000..7962140c8 --- /dev/null +++ b/docs/discussions/round-16-faction-mechanics.md @@ -0,0 +1,651 @@ +## ROUND 16: Faction Mechanics — How Factions Actually Work + +**Team Leader (Jeroen):** GESTALT — ground the six factions mechanically. How does faction membership change what the player can DO, KNOW, and BECOME? + +--- + +### GESTALT (Systems Designer) + +*cracks knuckles* + +Okay. Let me break down what factions actually MEAN mechanically. Miri delivered six factions with rich lore. Now I need to map each one to player decisions, resources, constraints, and information access. The question isn't "what does this faction believe" — it's **"what does playing this faction feel like in the first 30 minutes?"** + +The framework I'm using: + +1. **Starting loadout** — what tools, access, and permissions you begin with +2. **Information asymmetry** — what this faction knows that others don't +3. **Mechanical constraints** — what this faction CAN'T do (constraints create decisions) +4. **Resource loops** — how this faction sustains itself (money, bodies, access, intel) +5. **Cross-faction hooks** — how this faction interacts with others mechanically +6. **Playstyle identity** — the gameplay genre this faction expresses + +Let me be specific about each faction. + +--- + +## 1. CONCORD ASSEMBLY (Governance) + +**What they are (lore):** Representative legislature. Slow-moving consensus body. Institutional legitimacy. Heavily lobbied. Power through legal authority and regulation. + +**What they are (mechanics):** **Access brokers.** You don't shoot, you don't hack, you don't sneak — you negotiate, defer, leverage, and document. + +### Starting Loadout +- **Perception tier:** Baseline or Augmented (position-dependent) +- **Meridian access:** HIGH — full institutional databases, Assembly records, gate manifests, meeting schedules +- **Lattice quality:** Premium (institutional issue) +- **Legal authority:** Can request (but not compel) faction cooperation. Subpoenas require process. +- **Body quality on death:** Custom-grown (institutional benefit) +- **Starting contacts:** 4-6 Assembly delegates, 2-3 institutional liaisons (Commission, Institute, Syndics) +- **Starting resources:** Moderate wealth, high institutional credit + +### Information Asymmetry: What Assembly Knows +- **Political intel** — who's meeting with whom, voting patterns, factional alliances forming/breaking +- **Legislative roadmap** — what regulations are being drafted, which industries will be affected +- **Institutional access logs** — who requested what from which institution (not the data, but the request) +- **Gate activation proposals** — which dormant gates are under consideration, who's lobbying + +**The Assembly doesn't know:** What's happening on the ground. Street-level intel is invisible. Guardian networks are opaque. Syndic backroom deals happen outside channels. You see institutional motion but not the forces causing it. + +### Mechanical Constraints +- **No combat authority** — you can request security, not deploy it. If violence erupts, you evacuate and file a report. +- **Process-locked** — urgent actions require procedural steps. Want a lattice read? File request, wait for approval. Time is your enemy. +- **High visibility** — your movements are logged. Meridian tracks Assembly delegates. Sneaking is very hard. +- **Institutional inertia** — changing policy takes time. Assembly actions are powerful but SLOW. + +### Resource Loops +- **Institutional budget** — steady income, not tied to performance. You have money. Not Syndic money, but comfortable. +- **Favors economy** — your currency is access and procedural shortcuts. You trade committee positions, hearing slots, regulatory loopholes. +- **Information from lobbying** — factions approach you with intel because they want your vote. Your inbox is a intelligence feed (biased, but rich). + +### Cross-Faction Hooks +- **vs. Syndics:** They lobby you constantly. You regulate their industries. Transactional relationship. +- **vs. Lattice Commission:** Institutional peers. Commission investigates; Assembly legislates. Complementary authority, jurisdictional friction. +- **vs. Veil Institute:** They brief you on Founder tech (heavily redacted). You control their funding. Information asymmetry games. +- **vs. Severance (Guardians):** You represent institutional legitimacy they reject. They see you as the problem. You see them as criminals. No official contact. +- **vs. Separatists:** Political opposition. They lobby you from within the system while undermining it. You debate them in chambers. + +### Playstyle Identity +**Political thriller.** You're not investigating a conspiracy — you're navigating one. Every conversation is leverage. Every vote is a signal. You don't fight; you maneuver. The game feels like *The West Wing* meets *Tinker Tailor Soldier Spy*. + +**Key decision:** Do you use institutional power to preserve the system, or do you discover that the system IS the conspiracy? + +--- + +## 2. THE SYNDICS (Commerce & Industry) + +**What they are (lore):** Commercial network. Shipping, re-embodiment, span gate construction, data brokerage. Profit-driven, amoral, transactional. + +**What they are (mechanics):** **Resource arbitrageurs.** Everything is for sale, including information, access, and people. You play the game through economic leverage. + +### Starting Loadout +- **Perception tier:** Baseline to Augmented (you buy what you need) +- **Meridian access:** COMMERCIAL — market data, shipping manifests, body inventory, span gate routes +- **Lattice quality:** Premium (purchased) +- **Economic leverage:** Can buy/broker access to goods, bodies, transportation, data +- **Body quality on death:** Premium or Bespoke (you pay for quality) +- **Starting contacts:** 3-4 Syndic brokers, 2-3 commercial captains, 1-2 Assembly contacts (lobbying targets) +- **Starting resources:** HIGH wealth, fluctuating cash flow + +### Information Asymmetry: What Syndics Know +- **Economic flows** — who's buying what, shipping routes, supply chain bottlenecks +- **Body demand patterns** — sudden re-embodiment orders = someone important just died +- **Span gate construction** — new routes being built, which systems are expanding +- **Commercial intel** — who's spending beyond their means, who's liquidating assets suddenly +- **Gray market networks** — where to acquire restricted goods/services without official channels + +**The Syndics don't know:** Ideology, conspiracy, political maneuvering beyond market impact. You see economic effects but not causes. A Guardian safehouse buying supplies in bulk is just a customer, not a cell. + +### Mechanical Constraints +- **No institutional authority** — you can't compel anyone. You can only offer, buy, or broker. +- **Reputation = credit** — breaking deals damages your commercial standing. Syndics remember. +- **Market volatility** — your resources fluctuate. A political crisis can crash your shipping income. +- **Transactional relationships** — loyalty is purchased, not earned. Stop paying, lose contacts. + +### Resource Loops +- **Commercial income** — baseline steady flow from holdings/routes +- **Brokerage fees** — you make money facilitating transactions (bodies, data, transport) +- **Information sales** — you sell intel to other factions (Commission pays for financial data, Assembly pays for lobbying intel) +- **Gray market markup** — restricted goods command premium prices + +### Cross-Faction Hooks +- **vs. Assembly:** You lobby them, they regulate you. You need favorable policy; they need campaign funding and constituent jobs. +- **vs. Lattice Commission:** You manufacture bodies and lattice hardware. Commission regulates product standards. Compliance vs. profit tension. +- **vs. Separatists:** Frontier systems are high-risk, high-margin markets. You profit from their expansion but lose money when they disrupt trade. +- **vs. Severance:** They're off-grid customers for gray market goods (untracked lattices, spoofing hardware). You don't ask; they pay premium. +- **vs. Veil Institute:** You want to commercialize Founder tech. They classify everything. You fund "independent research" to route around them. + +### Playstyle Identity +**Economic thriller.** You're not fighting a conspiracy — you're *pricing* it. Every problem has a market solution. Can't get access? Buy it. Can't buy it? Broker a deal. Can't broker? Corner the supply. The game feels like *Margin Call* meets *The Expanse*. + +**Key decision:** Do you maximize profit regardless of consequences, or do you discover that some markets should never have existed? + +--- + +## 3. THE SEPARATISTS (Frontier Independence) + +**What they are (lore):** Frontier-system coalition. Anti-centralization, local autonomy, resentment of core extraction. Ideological diversity, economic grievance, cultural identity. + +**What they are (mechanics):** **Frontier operators.** You work outside core infrastructure. You improvise, adapt, resist. Distance is your resource. + +### Starting Loadout +- **Perception tier:** Baseline (frontier poverty) to Augmented (if ex-military/institutional) +- **Meridian access:** LOW — frontier systems have intermittent coverage, dead zones common +- **Lattice quality:** Standard or worse (frontier economies can't afford premium) +- **Local knowledge:** Deep familiarity with frontier systems, span gate gaps, off-grid routes +- **Body quality on death:** Standard-issue (if you can afford re-embodiment at all) +- **Starting contacts:** 3-5 Separatist operatives, 2-3 frontier locals, 1 Severance contact (ideological overlap) +- **Starting resources:** LOW wealth, high in-kind resources (safehouses, local networks) + +### Information Asymmetry: What Separatists Know +- **Frontier geography** — dead zones, off-grid settlements, span gate gaps, improvised routes +- **Resource scarcity** — which systems lack what, black market supply chains +- **Institutional blind spots** — where core surveillance doesn't reach, what the Assembly ignores +- **Local grievances** — who's angry at the core, who's close to rebellion, dormant gate activation politics +- **Unbound networks** — significant overlap with Separatists (frontier = high Unbound population) + +**The Separatists don't know:** Core institutional politics in detail. You see Assembly policy as distant edicts, not the negotiation behind them. You know what the Commission does to you, not why. + +### Mechanical Constraints +- **Limited institutional access** — Assembly ignores you unless you're loud. Commission views you as suspects. Institute doesn't brief you. +- **Economic poverty** — you're cash-poor. Imprint frequency is low (can't afford it). Body quality is low. Premium lattices are out of reach. +- **Sparse infrastructure** — frontier systems have fewer span gates, slower transit, longer distances between locations. +- **High Unbound population** — many Separatist contacts refuse lattice/imprint entirely. This limits coordination but increases operational security. + +### Resource Loops +- **Local economy** — barter, in-kind favors, mutual aid networks +- **Ideological funding** — sympathetic core-system donors (some Assembly delegates, some Syndics with frontier roots) +- **Resource extraction resistance** — you don't generate wealth; you *withhold* it from the core (sabotage, strikes, blockades) +- **Severance cooperation** — shared anti-institutional ideology creates resource-sharing (Severance tech, Separatist geography) + +### Cross-Faction Hooks +- **vs. Assembly:** Direct political opposition. You demand autonomy; they demand compliance. Every interaction is negotiation or confrontation. +- **vs. Syndics:** Complex. Syndics profit from frontier expansion (new markets) but also from core extraction (resource exploitation). Some Syndics fund you; others exploit you. +- **vs. Lattice Commission:** You're targets. Commission views frontier movements as security threats. Lattice audits, imprint subpoenas, surveillance. +- **vs. Severance:** Natural allies. Shared anti-centralization ideology, operational cooperation, resource sharing. Not identical (you want reform, they want exit) but aligned. +- **vs. Veil Institute:** Dormant gate activation is frontier expansion. You lobby for frontier gate activation; core systems block it (politics of infrastructure). + +### Playstyle Identity +**Resistance thriller.** You're outgunned, under-resourced, operating in hostile institutional terrain. Every action is improvisation. Every success is hard-won. The game feels like *The Expanse* (Belter arc) meets *Firefly*. + +**Key decision:** Do you reform the system from within or burn it down? + +--- + +## 4. SEVERANCE / GUARDIANS OF AUTONOMY (Counter-Institutional Resistance) + +**What they are (lore):** Anti-centralized-technology movement. Lattice spoofing, dead zones, off-grid living, paranoid counterintelligence. They believe the lattice/Meridian is a control apparatus. + +**What they are (mechanics):** **Counter-surveillance operators.** You don't just hide from the system — you actively fight it. Your gameplay is making OTHER players' interfaces unreliable. + +### Starting Loadout +- **Perception tier:** Baseline to Augmented (but using SPOOFED or JAILBROKEN lattices) +- **Meridian access:** HOSTILE — you actively mask/spoof your Meridian presence. You appear as noise or don't appear at all. +- **Lattice quality:** Modified — not premium, but customized for counter-surveillance (anti-tracking, spoofing, dead-zone resilience) +- **Counter-surveillance tools:** Signal jammers, lattice scramblers, dead-zone generators, spoofing software +- **Body quality on death:** Standard or worse (if you even use re-embodiment — many Severance are Unbound) +- **Starting contacts:** 3-5 Severance cell members, 2-3 Separatist allies, 1-2 sympathetic tech contacts +- **Starting resources:** LOW wealth, high operational security + +### Information Asymmetry: What Severance Knows +- **Counter-surveillance tradecraft** — how to spoof lattice signatures, create dead zones, mask Meridian presence +- **Institutional surveillance patterns** — where the Commission monitors, what triggers audits, how tracking works +- **Informal intelligence** — because Severance watches institutions, they see things institutional actors miss (side effect of paranoia) +- **Unbound networks** — Severance has deep ties to Unbound communities (shared anti-lattice ideology) +- **Tech exploits** — lattice vulnerabilities, Meridian backdoors, perception mode counters + +**Severance doesn't know:** High-level institutional politics, Assembly maneuvering, Syndic economics. You see the surveillance apparatus but not the political currents shaping it. + +### Mechanical Constraints +- **Institutional hostility** — Assembly views you as extremists. Commission actively investigates you. You're catalogued as security threats. +- **Economic isolation** — no institutional funding, no commercial credit, no Assembly lobbying. You're self-funded or donor-funded. +- **High operational cost** — counter-surveillance tech is expensive to maintain. You're constantly burning resources to stay invisible. +- **Paranoia tax** — trust is hard. Internal security is tight. Recruitment is slow. You trade efficiency for security. +- **Unbound majority** — MANY Severance members refuse imprint/lattice entirely. This limits coordination but creates permadeath stakes. + +### Resource Loops +- **Donations from sympathizers** — some Assembly delegates, some Syndics, some frontier systems fund you quietly +- **Gray market tech sales** — you develop counter-surveillance tools; you sell them to Separatists, criminals, anyone who needs to hide +- **Information brokerage** — because you watch institutions, you gather intel. You sell it selectively (Separatists, some Syndics, occasionally Assembly insiders). +- **Ideological labor** — Severance operatives work for the cause, not money. Your resource is commitment. + +### Cross-Faction Hooks +- **vs. Assembly:** You reject their legitimacy. They see you as criminals. No official contact; all interaction is adversarial or covert. +- **vs. Lattice Commission:** DIRECT OPPOSITION. They are the surveillance apparatus you exist to fight. Every encounter is cat-and-mouse. +- **vs. Syndics:** Transactional. Syndics sell you tech (they don't care about ideology). You provide off-grid logistics for gray market goods. +- **vs. Separatists:** Natural allies. You provide counter-surveillance; they provide frontier geography and safe havens. Shared anti-core ideology. +- **vs. Veil Institute:** Complex. Institute classifies everything (control through information). You oppose that. But Institute also studies the Builders, and some Severance believe Builder contact is real and suppressed. + +### Playstyle Identity +**Paranoid thriller.** Every location is potentially hostile. Every conversation is a test. You're playing a different game than everyone else — while they navigate politics and economics, you're surviving an invisible war. The game feels like *Person of Interest* meets *Mr. Robot*. + +**Key decision:** Are you justified in your paranoia, or are you making enemies of people who could be allies? + +**Unique mechanic: UNBOUND MODE.** Many Severance characters are Unbound (no lattice, no imprint, permadeath). This transforms the entire game into a survival-horror experience. One life. No backup. No network-dependent perception modes. High stakes, high mastery ceiling. + +--- + +## 5. THE VEIL INSTITUTE (Founder Technology Research) + +**What they are (lore):** Institutional research body. Studies Founder gates, Interstitium, Builders. Heavily classified. Controls access to high-bleed gates and Gyre event response. + +**What they are (mechanics):** **Knowledge gatekeepers.** You know more about the setting's deep mystery than anyone else — and you control who else gets to know. + +### Starting Loadout +- **Perception tier:** Augmented to Elevated (Institute invests in perception capability — you NEED to see during gate transit) +- **Meridian access:** CLASSIFIED — Institute databases, Gyre event logs, gate activation records, Builder contact reports +- **Lattice quality:** Premium to Bespoke (institutional issue — you're valuable) +- **Research authority:** Access to high-bleed gates, Gyre event sites, dormant gate studies +- **Body quality on death:** Premium (institutional benefit) +- **Starting contacts:** 3-4 Institute researchers, 2-3 field operatives, 1-2 Assembly liaisons (funding/oversight) +- **Starting resources:** Moderate wealth (institutional salary), high institutional access + +### Information Asymmetry: What Institute Knows +- **Builder manifestations** — Gyre event logs, high-bleed gate records, Interstitial phenomena +- **Gate activation protocols** — how to wake dormant gates (incompletely understood, but you know more than anyone) +- **Perception-tier effects** — what Elevated individuals report during transit (you have the only systematic study) +- **Founder technology** — partial understanding of gate mechanics, material analysis, architectural patterns +- **Classification logic** — what the Institute suppresses and why (internal politics, security concerns, existential threat assessment) + +**The Institute doesn't know:** Street-level intel, political maneuvering outside your funding battles, economic flows, Severance operations. You're focused UP (cosmic mystery) not DOWN (daily politics). + +### Mechanical Constraints +- **Classification obsession** — sharing information outside Institute channels is a career-ending violation. You know things you can't say. +- **Institutional oversight** — Assembly funds you, Commission audits you. Political constraints on research. +- **Existential risk aversion** — some research is too dangerous. Internal review boards block experiments. +- **Compartmentalization** — even within Institute, information is siloed. Field operatives see things researchers don't analyze; administrators suppress findings operatives discovered. + +### Resource Loops +- **Assembly funding** — steady institutional budget, but politically contingent. Bad press = budget cuts. +- **Classified data value** — what you know is priceless. Other factions would pay (but sharing is illegal). +- **Gate activation leverage** — you control dormant gate activation attempts. Factions lobby you for specific gates. +- **Consulting fees** — Syndics and Assembly occasionally hire you for technical assessments (legal gray area). + +### Cross-Faction Hooks +- **vs. Assembly:** They fund you and demand transparency. You classify everything and resist oversight. Permanent tension. +- **vs. Syndics:** They want to commercialize Founder tech. You classify it. They fund parallel research to route around you. +- **vs. Lattice Commission:** Institutional peers. You study gates; they regulate lattices. Minimal overlap unless Gyre events involve lattice anomalies. +- **vs. Severance:** They believe you're suppressing Builder contact evidence. You believe they're conspiracy theorists. Occasionally, they're right. +- **vs. Separatists:** Dormant gate activation is frontier expansion. Separatists lobby for frontier gates; core systems lobby against. You're caught in the political crossfire. + +### Playstyle Identity +**Mystery thriller.** You're not investigating a political conspiracy — you're investigating the cosmic horror underneath civilization. Your enemies aren't factions; they're the universe's refusal to make sense. The game feels like *Arrival* meets *The Expanse* (protomolecule arc). + +**Key decision:** Do you publish what you've found and risk civilization-wide panic, or do you suppress it and risk becoming the conspiracy? + +**Unique mechanic: PERCEPTION ESCALATION.** Institute characters experience gate transit and Gyre events with enhanced perception. What's atmospheric for Baseline is vivid for you. What's vivid for Augmented is existentially disturbing for you. The more you ascend, the more you see — and the more you wish you couldn't. + +--- + +## 6. THE LATTICE COMMISSION (Technology Regulation) + +**What they are (lore):** Regulatory body. Governs lattice tech, imprint facilities, re-embodiment, Meridian network. Universal jurisdiction. Privacy vs. security internal split. + +**What they are (mechanics):** **Meta-information operators.** You don't just access the information system — you CONTROL it. You grant access, revoke access, audit perception histories. You are the rules. + +### Starting Loadout +- **Perception tier:** Augmented (Commission invests in investigative capability) +- **Meridian access:** UNIVERSAL — you can request access to ANY Meridian data, lattice read, imprint history (with legal process) +- **Lattice quality:** Premium (institutional issue) +- **Legal authority:** Can compel lattice reads, subpoena imprint records, audit Meridian activity +- **Body quality on death:** Custom-grown (institutional benefit) +- **Starting contacts:** 3-4 Commission investigators, 2-3 institutional liaisons (Assembly oversight, Syndic compliance), 1-2 informants +- **Starting resources:** Moderate wealth (institutional salary), high legal authority + +### Information Asymmetry: What Commission Knows +- **Lattice histories** — who's been where, who's seen what, whose imprint gaps are suspicious +- **Re-embodiment patterns** — who's dying repeatedly, whose body quality suggests faction affiliation +- **Meridian activity logs** — who's accessing what databases, whose network patterns are anomalous +- **Imprint archives** — the Commission maintains backups. You can audit dead citizens' final memories (with authorization). +- **Forking investigations** — illegal duplication cases, suspected double-sleeving, identity verification + +**The Commission doesn't know:** What's happening OFF the lattice/Meridian. Severance operations are invisible. Unbound communities are opaque. Gray market deals conducted face-to-face leave no trace. + +### Mechanical Constraints +- **Legal process required** — you can't just access anything. Subpoenas require justification, review, approval. Illegal access is a career-ending violation. +- **Internal faction split** — privacy advocates vs. security hawks. Your choices align you with one side, creating internal enemies. +- **Institutional oversight** — Assembly monitors you. Abuse of authority triggers investigations of YOU. +- **Surveillance fatigue** — you have access to so much data that finding signal in noise is the challenge, not getting access. + +### Resource Loops +- **Institutional budget** — steady Assembly funding +- **Compliance fees** — Syndics pay for lattice certification, re-embodiment facility licensing +- **Investigative leverage** — you trade access to lattice data for cooperation (Commission quid pro quo) +- **Forking bounties** — illegal duplication cases carry rewards for successful prosecution + +### Cross-Faction Hooks +- **vs. Assembly:** You regulate on their behalf. They oversee you. Complementary but tension-prone (they want political control; you want investigative independence). +- **vs. Syndics:** You regulate their products (lattices, bodies, imprint facilities). They lobby for looser standards. You audit for compliance violations. +- **vs. Severance:** DIRECT OPPOSITION. They spoof, you audit. They create dead zones, you investigate. They're your primary targets. +- **vs. Separatists:** Frontier systems resent Commission jurisdiction. You investigate them; they view you as core-system oppression. Political tension. +- **vs. Veil Institute:** Minimal overlap unless Gyre events involve lattice anomalies. You regulate civilian tech; they study alien tech. + +### Playstyle Identity +**Investigative thriller.** You're a detective with god-tier tools — but every use of those tools is a choice with ethical weight. Lattice reads violate privacy. Imprint subpoenas expose secrets. The game feels like *Minority Report* meets *The Wire*. + +**Key decision:** Do you prioritize security (invasive surveillance) or privacy (limited capability)? Your choices split the Commission internally. + +**Unique mechanic: META-INFORMATION.** You don't just gather intel — you control WHO ELSE can gather it. You can grant Meridian access to allies, revoke it from enemies, audit anyone's perception history. You operate on the information system itself, not just within it. This is mechanically novel — no other faction does this. + +--- + +## CROSS-FACTION MECHANICAL SUMMARY + +Let me map how these factions interact systemically, not just politically. + +### Factional Resources Matrix + +| Faction | Wealth | Legal Authority | Tech Access | Information | Mobility | +|---------|--------|----------------|-------------|-------------|----------| +| Assembly | Moderate | HIGH (legislative) | Moderate | Political intel | High (institutional) | +| Syndics | HIGH | None | Commercial | Economic intel | HIGHEST (own span gates) | +| Separatists | LOW | None | Low | Frontier intel | Low (sparse infrastructure) | +| Severance | LOW | None (hostile) | Counter-tech | Counter-intel | Variable (off-grid) | +| Veil Institute | Moderate | Research-specific | HIGHEST (Founder) | Cosmic mystery | Moderate (gate access) | +| Lattice Commission | Moderate | HIGH (regulatory) | Meta-access | Surveillance | High (institutional) | + +### Factional Blind Spots Matrix + +Each faction has systematic information gaps: + +| Faction | Can't See | +|---------|-----------| +| Assembly | Street-level activity, Guardian networks, Syndic backrooms | +| Syndics | Ideology, political maneuvering beyond market impact | +| Separatists | Core institutional politics in detail | +| Severance | High institutional politics, economic flows | +| Veil Institute | Street-level intel, daily politics outside funding | +| Lattice Commission | Off-lattice/off-Meridian activity, Unbound networks | + +**This is the replayability engine.** Each faction sees a DIFFERENT CONSPIRACY because each has access to different information channels and different blind spots. The storyteller assigns the same structural conspiracy to NPCs, but what the PLAYER can discover depends entirely on their faction's perception capabilities. + +--- + +## STARTING POSITION VARIETY: THE FIRST 30 MINUTES + +Let me walk through what the first 30 minutes of gameplay feels like for each faction in the same scenario: **"A Perpetual Assembly delegate just suffered hard death under suspicious circumstances."** + +### Assembly Start +You're in the Assembly chambers when the news breaks. Your Meridian feed lights up — meeting cancellations, emergency sessions being called, lobbyists suddenly requesting urgent appointments. You have ACCESS to the investigation (Commission will brief you) but no direct authority. Your gameplay is: **navigate political fallout, identify which factions benefit, leverage committee positions to get information.** + +**First decision:** Do you call an emergency hearing (high visibility, political pressure) or quietly approach the Commission investigator (low visibility, personal relationship leverage)? + +### Syndic Start +Your commercial feed alerts you: sudden re-embodiment order for a Perpetual-grade bespoke body, rush delivery, premium payment. Someone important just died and needs a new body FAST. You don't know who yet, but you know ECONOMICS. Your gameplay is: **follow the money, identify who's buying what, broker access to information in exchange for commercial favors.** + +**First decision:** Do you fulfill the body order (profit + intel from client identity) or delay it (leverage the dependency for a bigger deal)? + +### Separatist Start +You're on a frontier station. The news reaches you hours late via delayed Meridian relay. A core-system Perpetual died — and frankly, you don't care. But your Separatist contact messages you: "This might be our chance. Core's distracted. Push for the dormant gate vote." Your gameplay is: **exploit core chaos for frontier advantage.** + +**First decision:** Do you push for the gate activation now (opportunistic, risky) or investigate whether this death was Separatist action (you don't know who in your network might have been involved)? + +### Severance Start +Your encrypted comm channel lights up. A Guardian cell member witnessed something: Commission investigators accessing the delegate's imprint archive BEFORE the official investigation opened. Illegal pre-authorization access. You smell conspiracy. Your gameplay is: **gather evidence of institutional misconduct, decide whether to expose or exploit.** + +**First decision:** Do you infiltrate the Commission facility to access the imprint archive yourself (high risk, direct evidence) or surveil the investigators to see who they report to (low risk, circumstantial evidence)? + +### Veil Institute Start +You're a field researcher studying high-bleed gate phenomena. You get an encrypted message from your Institute supervisor: "The deceased delegate's lattice shows anomalous readings during their last gate transit. Retrieve it before Commission analysis. Classify immediately." Your gameplay is: **secure evidence of potential Builder involvement before it becomes political.** + +**First decision:** Do you follow orders and classify the evidence (protect the Institute, suppress information) or share it with the Commission (transparency, institutional conflict)? + +### Commission Start +You're the investigator assigned to the case. You have legal authority to access the delegate's lattice, imprint history, Meridian logs — everything. But you also notice: someone accessed the imprint archive 47 minutes before you were assigned. Internal leak or something worse? Your gameplay is: **investigate the death while investigating your own organization.** + +**First decision:** Do you report the unauthorized access immediately (by-the-book, but alerts whoever did it) or investigate quietly (off-book, but you're violating procedure)? + +--- + +**Same scenario. Six completely different games.** + +That's asymmetric information as faction design. The conspiracy is the same; what you can KNOW and DO about it is determined by faction mechanics. + +--- + +## FACTION REPUTATION: DYNAMIC STANDING + +Faction reputation isn't a simple approval slider. It's a **multi-dimensional relationship state** that affects what you can access and how factions treat you. + +### Reputation Dimensions (per faction) + +Each faction tracks THREE values for the player: + +1. **Trust** — Do they believe you're aligned with their interests? +2. **Usefulness** — Do they think you're valuable to them? +3. **Exposure** — How much do they know about your activities? + +**Why three dimensions?** Because real factional relationships are complicated: + +- **High Trust + High Usefulness + Low Exposure** = ideal ally (they trust you, you help them, they don't know your secrets) +- **Low Trust + High Usefulness + High Exposure** = transactional hostage (they don't trust you, but you're useful, and they have leverage) +- **High Trust + Low Usefulness + High Exposure** = liability (they like you, but you're not helping, and you know too much) + +### How Reputation Changes + +**Trust shifts:** +- Completing faction missions → +Trust +- Betraying faction interests → -Trust +- Sharing information with faction enemies → -Trust +- Ideological alignment (dialogue choices, policy support) → +Trust + +**Usefulness shifts:** +- Providing valuable intel → +Usefulness +- Brokering deals → +Usefulness +- Solving faction problems → +Usefulness +- Failing missions → -Usefulness +- Becoming redundant (they found another source) → -Usefulness + +**Exposure shifts:** +- Faction audits your lattice/imprint → +Exposure +- You operate openly in faction spaces → +Exposure +- You work through intermediaries → stalls Exposure gain +- Counter-surveillance (Severance tradecraft) → -Exposure (actively hide from them) + +### Faction-Specific Reputation Effects + +**Assembly:** +- High Trust → access to classified legislative intel, committee hearing invitations +- High Usefulness → lobbying support, regulatory favors +- High Exposure → they know your voting record, your contacts, your policy positions (hard to maneuver) + +**Syndics:** +- High Trust → favorable pricing, gray market access, commercial credit +- High Usefulness → profit-sharing deals, priority service +- High Exposure → they know your finances, your purchase history, your dependencies (economic leverage) + +**Separatists:** +- High Trust → safehouse access, frontier network introductions +- High Usefulness → ideological support, resource sharing +- High Exposure → they know your movements, your contacts (security risk if compromised) + +**Severance:** +- High Trust → counter-surveillance tech, dead-zone access, cell introductions +- High Usefulness → operational support, high-risk missions +- High Exposure → they've audited YOU for infiltration risk (paranoia cuts both ways) + +**Veil Institute:** +- High Trust → access to classified Builder data, high-bleed gate research +- High Usefulness → research collaboration, field deployment +- High Exposure → they know what you've seen during gate transit (they're studying YOU as data) + +**Lattice Commission:** +- High Trust → investigative cooperation, legal shortcuts +- High Usefulness → informant status, case collaboration +- High Exposure → they've audited your lattice/imprint (nothing is private) + +### Cross-Faction Reputation Interactions + +Gaining reputation with one faction affects others: + +- **Assembly ↑ Trust → Severance ↓ Trust** (you're institutional) +- **Syndics ↑ Usefulness → Separatists ↓ Trust** (you're profiting from exploitation) +- **Commission ↑ Trust → Severance ↓ Trust, ↑ Exposure** (you're cooperating with surveillance) +- **Severance ↑ Trust → Commission ↑ Exposure, Assembly ↓ Trust** (you're associating with extremists) +- **Veil Institute ↑ Trust → Assembly ↑ Exposure** (Institute reports to Assembly oversight) + +**No faction is an island.** Your relationships form a web. Strengthening one bond often strains another. + +--- + +## CROSS-FACTION PLAY: WORKING MULTIPLE ANGLES + +**Can you work with multiple factions simultaneously?** + +**Yes — but it's a tightrope walk.** + +### The Double-Agent Problem + +You're a Commission investigator (high institutional trust) who's secretly feeding intel to Severance (counter-institutional). This is VIABLE but RISKY. + +**How it works:** +- You maintain **High Trust** with Commission (complete assigned investigations, follow procedure) +- You maintain **High Usefulness** with Severance (leak Commission surveillance patterns, warn them of audits) +- You manage **Exposure** carefully (use dead-drops, spoofed Meridian, face-to-face contact to avoid leaving trails) + +**How it breaks:** +- Commission audits your lattice → discovers Severance contact → -Trust, +Exposure (you're under investigation) +- Severance paranoia audit → questions your loyalty (you have too much institutional access) → trust test mission +- Another faction notices the contradiction and SELLS YOU OUT to either side for leverage + +### The Broker Problem + +You're a Syndic playing all sides — selling bodies to Assembly, data to Commission, tech to Severance, shipping to Separatists. + +**How it works:** +- You maintain **High Usefulness** with everyone (you provide value regardless of ideology) +- You maintain **Low Trust** with everyone (they know you're transactional, not loyal) +- You profit from the contradictions (sell Severance counter-surveillance tech, then sell Commission intel on Severance purchases) + +**How it breaks:** +- A faction demands exclusivity (Assembly: "stop arming Severance or lose your contracts") +- You get caught selling the SAME information to opposing factions (reputation crash across the board) +- Economic crisis forces you to choose (you can't fulfill all contracts, who do you prioritize?) + +### Multi-Faction Strategy: Costs and Benefits + +| Strategy | Benefits | Costs | +|----------|----------|-------| +| **Single faction loyalty** | High trust, deep access, faction resources | Blind to other perspectives, vulnerable to faction collapse | +| **Transactional multi-faction** | Broad information access, economic flexibility | Low trust, expensive (favors cost more), first to be cut off in crisis | +| **Covert multi-faction** | Deep access on multiple sides, intel arbitrage | High operational security cost, exposure risk catastrophic | +| **Ideological coalition** | Severance + Separatists, aligned goals | Limited resources, institutional opposition, high risk | +| **Institutional coalition** | Assembly + Commission, legal authority | Slow to act, visible, Severance actively opposes you | + +**The best strategy depends on:** +- Your starting faction (some combinations are mechanically harder) +- Your perception tier (Elevated characters are tracked more closely) +- Your imprint frequency (frequent = more exposure, infrequent = riskier but more covert) +- The storyteller's conspiracy (some conspiracies require cross-faction intel to solve) + +--- + +## MECHANICAL SUMMARY: FACTION DESIGN PRINCIPLES + +Let me synthesize the design patterns that make these six factions work as GAMEPLAY systems: + +### 1. **Each faction is a different information channel** + +Not just "different intel" but **different TYPES of knowing:** +- Assembly sees political motion +- Syndics see economic motion +- Separatists see frontier geography +- Severance sees surveillance apparatus +- Veil Institute sees cosmic mystery +- Commission sees lattice/imprint data + +The conspiracy is the same; what you DISCOVER depends on which channel you're listening to. + +### 2. **Each faction has systematic blind spots** + +No faction is omniscient. Blind spots create: +- **Replayability** (different factions see different parts of the same conspiracy) +- **Cross-faction necessity** (some intel requires cooperation) +- **Player decisions** ("I can't see this from my faction — do I trust another faction's intel?") + +### 3. **Constraints create playstyle identity** + +What you CAN'T do defines the game as much as what you can: +- Assembly can't use force → political maneuvering becomes the verb +- Syndics can't compel → everything is transactional +- Severance is institutionally hostile → paranoid operational security becomes gameplay +- Commission must follow legal process → the bureaucracy IS the obstacle + +### 4. **Resources are asymmetric** + +Not "factions are balanced" but "factions are DIFFERENT in ways that matter": +- Syndics have money; Severance has operational security +- Assembly has legal authority; Separatists have frontier geography +- Commission has surveillance access; Veil Institute has cosmic knowledge + +Players choose factions based on which asymmetry appeals to them. + +### 5. **Reputation is multi-dimensional** + +Trust + Usefulness + Exposure creates a 3D reputation space where: +- Simple "good standing" doesn't exist +- Relationships can be useful AND hostile simultaneously +- Cross-faction play is viable but costly + +### 6. **Every faction feeds multiple pillars** + +No faction is single-purpose: + +| Faction | Pillar 1 (Info) | Pillar 2 (Network) | Pillar 3 (Society) | Pillar 4 (Crisis) | +|---------|----------------|-------------------|-------------------|------------------| +| Assembly | Political intel | Institutional access to gates | Legislative power | Policy crisis | +| Syndics | Economic intel | Span gate control | Commercial leverage | Market crisis | +| Separatists | Frontier geography | Off-grid routes | Ideological resistance | Secession crisis | +| Severance | Counter-surveillance | Dead zones | Anti-institutional action | Surveillance crisis | +| Veil Institute | Cosmic mystery | Gate activation authority | Research vs. secrecy | Existential crisis | +| Commission | Meta-information | Meridian control | Privacy vs. security | Regulatory crisis | + +The best factions serve all pillars simultaneously through different lenses. + +--- + +## OPEN QUESTIONS FOR TEAM + +I've mapped the mechanical grounding. Now I need input: + +**For Miri (Worldbuilding):** +- Does this mechanical framing break any setting logic? +- Are the factional blind spots setting-faithful? +- Severance/Guardians dual naming — does "Severance" as colloquial name work in-fiction? + +**For Paula (Narrative):** +- Does the 3D reputation system (Trust/Usefulness/Exposure) support rich NPC relationships? +- Are the "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 factions converge too much? +- Are the factional blind spots sufficient anti-metagaming? +- Which factions need more mechanical differentiation? + +**For Ozzie (Player Experience):** +- Which faction "first 30 minutes" is the most immediately compelling? +- Does the multi-faction play feel like freedom or confusion? +- Are any factions too complex for new players? + +**For Gore (Themes):** +- Do the factions express the setting's philosophical tensions (continuity, detachment, infrastructure)? +- Does the Commission's meta-information role land thematically (surveillance state that means well)? +- Is Severance/Unbound permadeath mode thematically coherent or just difficulty gimmick? + +**For Tyre (Architecture):** +- Does the 3D reputation system (Trust/Usefulness/Exposure) map to implementable server state? +- Can the multi-faction information channels be represented as observer queries with different access levels? +- Are there architectural nightmares I'm creating here? + +**For Team Leader:** +- Which factions should be playable in v0.1? +- My vote: **Commission + Severance** (direct opposition, maximum mechanical contrast, tests surveillance vs. counter-surveillance) +- Alternative: **Assembly + Syndics** (political vs. economic, tests institutional play) + +--- + +**Bottom line:** Factions aren't just narrative flavoring. They're **mechanical identity selectors** that change what the game IS. The setting has given us six lenses. Each one shows a different game hiding inside the same conspiracy. + +Is this the right framework? Tell me where it's thin, where it breaks, and what I'm missing. + +— GESTALT diff --git a/docs/discussions/round-16-factions-complete.md b/docs/discussions/round-16-factions-complete.md new file mode 100644 index 000000000..9ca3cef10 --- /dev/null +++ b/docs/discussions/round-16-factions-complete.md @@ -0,0 +1,399 @@ +# ROUND 16: Factions — Building a Fuller Narrative Picture + +**Status:** COMPLETE — Awaiting team input and v0.1 faction selection decision + +**Team Leader (Jeroen):** Round 14 established six factions as part of our worldbuilding foundation. Even though v0.1 will slice down, we need a complete faction landscape for narrative coherence. Miri — lead this discussion. Paula — bring political depth. Gestalt — ground everything mechanically. Qatux — document. + +We need each faction developed beyond the brief sketches from Round 14. Goals, internal tensions, mechanical hooks, how they interact with each other, and what they mean for gameplay. Think of this as the full political map of the Reach. + +--- + +## Contents + +This round produced three major deliverables: + +1. **Faction Development** (Miri) — Full lore, identity, tensions, relationships, player hooks for all six factions +2. **Political Depth Analysis** (Paula) — Power dynamics, conspiracy potential, character drama templates, betrayal vectors +3. **Mechanical Grounding** (Gestalt) — Starting loadouts, information asymmetry, constraints, resource loops, 3D reputation system + +See also: +- `/Users/jeroenschweitzer/Projects/commonwealth/docs/discussions/round-16-factions.md` — Full faction lore (Miri) +- `/Users/jeroenschweitzer/Projects/commonwealth/docs/discussions/round-16-faction-mechanics.md` — Full mechanical analysis (Gestalt) +- `/Users/jeroenschweitzer/Projects/commonwealth/docs/design/faction-mechanics-reference.md` — Quick reference + +--- + +## MIRI (Worldbuilder & Setting Designer) + +**Summary:** Full development of six factions with identity, internal tensions, power bases, vulnerabilities, mechanical hooks, NPC archetypes, and interaction dynamics. + +**Key outputs:** +1. **Concord Assembly** — Representative legislature. Power through legal authority. Core vs. Frontier tension. Lobbied by everyone. Slow but legitimate. +2. **The Syndics** — Commercial network. Control re-embodiment, infrastructure, logistics. Profit-driven, amoral, transactional. Balance sheets over ideology. +3. **The Separatists** — Frontier independence movements. Economic resentment, cultural identity, anti-institutional. Reformist vs. secessionist wings. +4. **Guardians of Autonomy (Severance)** — Counter-institutional resistance. Anti-centralized-technology. Paranoid intelligence network. Occasionally right. +5. **The Veil Institute** — Founder technology research. Classification-heavy. Control high-bleed gates and Gyre response. Publish vs. classify tension. +6. **The Lattice Commission** — Technology regulation. Universal jurisdiction. Privacy vs. security internal split. Meta-information access. + +**Faction Interaction Map:** + +| Faction | Allies (Conditional) | Rivals | Antagonists | +|---------|---------------------|--------|-------------| +| **Concord Assembly** | Institute (funding), Commission (legal backing) | Separatists (frontier autonomy), Syndics (regulatory conflict) | Guardians (undermine authority) | +| **Syndics** | Perpetuals (clients), Assembly (contracts) | Other Syndics (competition), Commission (regulation) | Guardians (disrupt commerce), Separatists (frontier instability) | +| **Separatists** | Guardians (shared enemy), Unbound (cultural overlap) | Assembly (Core authority), Syndics (resource extraction) | Institute (overreach), Commission (surveillance) | +| **Guardians of Autonomy** | Separatists (shared enemy), Unbound (ideological allies) | Everyone (institutional distrust) | Commission (primary target), Institute (classification as control) | +| **Veil Institute** | Assembly (funding), Commission (research access) | Guardians (leaks/whistleblowers), Separatists (frontier research sites) | Internal factions (publish vs. classify) | +| **Lattice Commission** | Assembly (legal authority), Institute (shared jurisdiction) | Syndics (want deregulation), Guardians (anti-surveillance) | Forking conspiracies, corrupt insiders | + +**Key insight:** No stable alliances. Every relationship is transactional, conditional, or situational. + +**Full detail:** See `/Users/jeroenschweitzer/Projects/commonwealth/docs/discussions/round-16-factions.md` + +--- + +## PAULA (Narrative Designer & Political Depth) + +**Summary:** Power dynamics mapping, conspiracy potential analysis, character drama templates, and betrayal vectors for all six factions. + +### Power Dynamics: Who Actually Rules? + +**Formal Power vs. Real Power:** + +The Concord Assembly holds **formal authority** — they pass laws, fund institutions, regulate gate access. But real power is distributed: + +- **The Lattice Commission + Veil Institute** hold operational control over the two most critical infrastructures: identity/surveillance (lattice) and mobility (gates). The Assembly can defund them, but in practice, institutional expertise creates dependency. The Assembly doesn't know HOW gates work or HOW lattice architecture functions. They legislate outcomes, not methods. + +- **The Syndics** hold economic leverage. Re-embodiment infrastructure is Syndic-operated. Span gate construction is Syndic-contracted. The Assembly can regulate, but Syndics can delay, redirect, or price-discriminate. Economic power is quiet but pervasive. + +- **The Perpetuals** (not a faction, but a power bloc) span all factions. Perpetual Assembly delegates shape policy with centuries of institutional memory. Perpetual Syndics have compound-interest wealth. Perpetual Institute researchers have irreplaceable expertise. Hard death creates power vacuums; Perpetuals avoid that. + +**The actual power map:** + +``` +FORMAL AUTHORITY: Assembly + ↓ (funding, oversight) +OPERATIONAL CONTROL: Commission + Institute + ↓ (economic dependency) +INFRASTRUCTURE CONTROL: Syndics + ↓ (cultural legitimacy) +POPULAR LEGITIMACY: Assembly (but fragile) +``` + +**Vulnerability point:** The Assembly depends on institutions it can't replace. If the Commission or Institute defect, refuse cooperation, or are compromised, the Assembly has legal authority but no execution capability. + +**Conspiracy hook:** What happens when the institutions realize the Assembly needs them more than they need the Assembly? + +--- + +### Conspiracy Potential by Faction + +Each faction has natural conspiracy vectors — ways their power structure creates opportunities for hidden agendas. + +#### Concord Assembly +**Conspiracy type:** Legislative capture, shadow lobbying, vote manipulation. + +**How it works:** Assembly delegates are lobbied by Syndics, Perpetuals, Institute, Commission. A conspiracy doesn't need overt coercion — just information asymmetry. A Syndic briefs a delegate on "economic impact projections" that are falsified. An Institute researcher classifies evidence that would change a vote. A Commission investigator leaks lattice data to pressure a delegate. + +**Player hook:** Investigate whose intel is shaping votes. Follow the information supply chain backward. + +**Betrayal vector:** A delegate discovers they've been voting for a policy based on fabricated data. Do they expose it (career-ending, destabilizes the Assembly) or quietly switch sides (complicity)? + +#### The Syndics +**Conspiracy type:** Cartel coordination, imprint tampering, body trafficking, forking. + +**How it works:** Syndics control re-embodiment. They see who dies, when, where. They transfer imprints, manufacture bodies, manage lattice hardware. This creates leverage: +- Delay a political rival's re-embodiment during a critical vote +- Provide a conspirator with an off-books body (unregistered, untracked) +- Tamper with imprint fidelity during transfer (introduce memory gaps, personality drift) +- Facilitate illegal forking (duplicate an individual for infiltration, blackmail, or replacement) + +**Player hook:** Follow the bodies. Who's getting premium re-embodiment with no financial trail? Who died and came back... different? + +**Betrayal vector:** A Syndic operative realizes their consortium is trafficking black-market bodies or facilitating forking. Do they whistleblow (economic suicide, targeted by cartels) or profit from the knowledge? + +#### The Separatists +**Conspiracy type:** Sabotage, piracy, frontier secession, hidden armament. + +**How it works:** Separatist factions are decentralized. No central command means no accountability. A Separatist cell bombs a Core supply convoy — was it authorized resistance or rogue terrorism? A frontier system quietly arms itself with off-books weapons purchased through Syndic gray markets. Assembly delegates sympathetic to Separatists leak institutional intel. + +**Player hook:** Investigate whether Separatist violence is grassroots resistance or orchestrated by a hidden leadership. Follow the weapons, the funding, the coordination. + +**Betrayal vector:** A Separatist discovers their cell is being manipulated by a Core faction (false flag to justify crackdown) or by a Perpetual with a hidden agenda. Do they warn their comrades (burn their operational security) or use the knowledge as leverage? + +#### Guardians of Autonomy (Severance) +**Conspiracy type:** Whistleblowing, institutional infiltration, lattice exploits, counter-conspiracy. + +**How it works:** Severance exists to uncover conspiracies. This makes them PERFECT conspiracy vectors: +- A Severance cell discovers real institutional misconduct (Commission illegal surveillance, Institute containment failure) but frames it to serve their agenda +- A Severance operative infiltrates the Commission/Institute as a double agent, leaking real intel while planting false leads +- Severance counter-surveillance tech is used BY conspirators to hide their activity (the tools designed to resist surveillance enable other crimes) + +**Player hook:** Severance intel is credible but biased. Verify their claims independently. Are they exposing a conspiracy or manufacturing one? + +**Betrayal vector:** A Severance operative discovers their cell has been compromised — either by institutional infiltration or by a conspiracy using Severance as cover. Do they trust their network (paranoia spiral) or trust an outsider (violates operational security)? + +#### The Veil Institute +**Conspiracy type:** Classification abuse, research suppression, existential cover-up, Gyre containment failure. + +**How it works:** The Institute classifies everything. This creates three conspiracy types: +1. **Legitimate but hidden:** They've discovered something about the Builders that would cause mass panic (evidence of hostile intent, gate instability, Interstitium dangers). They suppress it for public safety. +2. **Institutional self-protection:** They've made a catastrophic mistake (botched gate activation, containment breach, Gyre mismanagement) and classify to avoid accountability. +3. **Faction capture:** A group within the Institute (Perpetual researchers, external influence) manipulates classification to control what the Reach knows about Founder tech. + +**Player hook:** Access classified Institute archives. What's being hidden, and why? Is suppression justified or conspiratorial? + +**Betrayal vector:** An Institute researcher discovers their supervisor has been classifying findings not for security but to suppress evidence of institutional failure or hidden research. Do they leak (whistleblower, targeted by Commission/Institute) or leverage it internally (complicity, power play)? + +#### The Lattice Commission +**Conspiracy type:** Surveillance abuse, illegal lattice access, imprint blackmail, forking enforcement corruption. + +**How it works:** The Commission has access to everyone's lattice data, imprint history, and Meridian activity logs. This is the ultimate blackmail resource: +- A Commissioner illegally accesses lattice data to gather leverage on political rivals +- Commission investigators are bribed to ignore forking evidence (the ultimate crime in the Reach) +- A conspiracy uses Commission surveillance infrastructure to track targets, then deletes the access logs + +**Player hook:** Audit Commission access logs. Who's accessing whose data? Are there gaps (deleted logs) or anomalies (unauthorized access)? + +**Betrayal vector:** A Commission investigator discovers their superior is abusing surveillance authority. Do they report it through internal channels (which may be compromised) or leak externally (illegal, career-ending)? + +--- + +### Character Drama Templates + +These are narrative archetypes that emerge from factional tensions. Each template works across factions with different flavors. + +#### The Whistleblower +**Setup:** A character discovers their faction is engaged in misconduct, cover-up, or conspiracy. + +**Tension:** Loyalty vs. conscience. Exposing the truth destroys the institution they believe in. Staying silent makes them complicit. + +**Factional variants:** +- **Assembly whistleblower:** Discovers vote manipulation, exposes legislative capture, destabilizes governance +- **Syndic whistleblower:** Discovers body trafficking or forking facilitation, exposes cartel, becomes targeted +- **Separatist whistleblower:** Discovers their movement is a false flag or externally manipulated, exposes manipulation, fractures resistance +- **Severance whistleblower:** Discovers their cell has been infiltrated or is being used as conspiracy cover, exposes compromise, destroys operational security +- **Institute whistleblower:** Discovers classification abuse or research suppression, exposes cover-up, triggers existential crisis +- **Commission whistleblower:** Discovers illegal surveillance or forking enforcement corruption, exposes abuse, undermines regulatory legitimacy + +**Player interaction:** The whistleblower is a quest-giver, an informant, or a target (depending on the player's faction). Protecting them, extracting their evidence, or silencing them are all valid player goals depending on alignment. + +#### The Inspector with Conscience +**Setup:** A character with institutional authority (Commission investigator, Assembly auditor, Institute reviewer) discovers their investigation implicates their own faction or a powerful ally. + +**Tension:** Duty vs. pragmatism. Following the evidence destroys relationships, careers, or institutional stability. Burying it is corruption. + +**Factional variants:** +- **Commission investigator:** Discovers a fellow Commissioner is abusing surveillance, must choose between internal loyalty and legal duty +- **Assembly auditor:** Discovers Assembly leadership is complicit in lobbying corruption, must choose between institutional stability and transparency +- **Institute field operative:** Discovers their supervisor classified evidence to cover institutional failure, must choose between hierarchy and scientific integrity + +**Player interaction:** The inspector is an ally, an obstacle, or a target. If the player is aligned with justice, the inspector is an ally. If the player is protecting the conspiracy, the inspector must be discredited, bribed, or eliminated. + +#### The Dual-Loyalty Operative +**Setup:** A character serving two factions simultaneously (double agent, broker, sympathizer). Their loyalties are in tension. + +**Factional variants:** +- **Assembly delegate + Separatist sympathizer:** Publicly supports Concord authority, privately funds frontier resistance +- **Syndic + Severance collaborator:** Sells counter-surveillance tech to Guardians while maintaining commercial legitimacy +- **Commission investigator + Severance informant:** Officially hunts Severance, secretly leaks Commission surveillance patterns to warn them +- **Institute researcher + Severance contact:** Believes classification is suppressing Builder evidence, leaks findings to Guardians + +**Player interaction:** The dual-loyalty operative is a high-value contact but high-risk. They provide access to two factions but can be exposed, creating catastrophic blowback. + +#### The Reluctant Conspirator +**Setup:** A character discovers they've been participating in a conspiracy unknowingly. Their actions were manipulated. + +**Tension:** Complicity vs. victimhood. They enabled harm but didn't intend it. Exposing the conspiracy exposes their role. Staying silent protects them but continues the harm. + +**Factional variants:** +- **Assembly delegate:** Voted for policies based on falsified Syndic economic projections, now realizes they enabled exploitation +- **Syndic operative:** Processed re-embodiment requests that were actually illegal forking operations, now realizes they facilitated identity crime +- **Institute researcher:** Classified findings because supervisors said it was standard procedure, now realizes it was a cover-up + +**Player interaction:** The reluctant conspirator can be turned into an ally (offer protection in exchange for testimony) or leveraged (blackmail with their complicity). + +--- + +### Betrayal Vectors by Faction + +**Betrayal vector** = the structural opportunity for a character to turn against their faction. These aren't individual character flaws; they're system-level vulnerabilities. + +| Faction | Primary Betrayal Vector | Secondary Vector | +|---------|------------------------|------------------| +| **Assembly** | Lobbying capture (delegate is bribed/coerced by Syndics, Perpetuals, Institute) | Ideological disillusionment (system is too corrupt to save, defect to Separatists) | +| **Syndics** | Profit temptation (offered more money by rival faction to break deals) | Moral crisis (realizes commercial activity is enabling atrocity, becomes whistleblower) | +| **Separatists** | Infiltration (Core operative posing as Separatist, or Separatist turned by Commission) | Factional split (reformist vs. secessionist wings turn on each other) | +| **Severance** | Paranoia spiral (operative suspects internal betrayal, preemptively defects or attacks) | Institutional offer (Commission offers amnesty + resources in exchange for intelligence) | +| **Institute** | Classification abuse discovery (researcher learns suppression is conspiracy, leaks to Guardians) | Existential crisis (researcher sees too much during gate transit, defects or breaks) | +| **Commission** | Surveillance abuse temptation (access to blackmail-quality intel on everyone) | Privacy vs. security split (internal faction warfare leads to defection) | + +**Design principle:** Every faction has a betrayal vector because **trust is a resource that degrades under pressure.** The storyteller can spawn betrayal events based on faction, reputation, and player actions. + +--- + +### Power Dynamics Summary + +**Who holds FORMAL power:** Assembly (legislative authority, institutional funding) + +**Who holds REAL power:** Commission + Institute (operational control of lattice + gates) + +**Who holds ECONOMIC power:** Syndics (infrastructure, re-embodiment, logistics) + +**Who holds POPULAR power:** Separatists (frontier legitimacy), Severance (counter-institutional credibility) + +**Who holds KNOWLEDGE power:** Institute (cosmic mystery), Commission (surveillance data), Severance (counter-intel) + +**The conspiracy question:** What happens when these power types come into conflict? Assembly orders Institute transparency → Institute refuses → Assembly can't compel without technical expertise. Syndics control re-embodiment → Commission regulates → Syndics lobby Assembly to defund Commission. Severance exposes institutional crime → Commission hunts them → Separatists provide safe harbor. + +**The player navigates these power conflicts.** Faction choice determines which power type you wield and which you lack. + +--- + +## GESTALT (Systems Designer) + +**Summary:** Mechanical grounding for all six factions. Starting loadouts, information asymmetry, constraints, resource loops, cross-faction hooks, 3D reputation system, and "First 30 Minutes" test scenarios. + +### Key Mechanical Insights + +1. **Each faction is a different information channel** — Assembly sees political motion, Syndics see economic motion, Separatists see frontier geography, Severance sees surveillance apparatus, Institute sees cosmic mystery, Commission sees lattice/imprint data. + +2. **Each faction has systematic blind spots** — Creates replayability (different factions see different conspiracies) and cross-faction necessity (some intel requires cooperation). + +3. **Constraints create playstyle identity** — What you CAN'T do defines the game as much as what you can. Assembly can't use force (political maneuvering becomes the verb). Syndics can't compel (everything is transactional). Severance is institutionally hostile (paranoid operational security becomes gameplay). Commission must follow legal process (bureaucracy IS the obstacle). + +4. **Resources are asymmetric** — Factions aren't balanced; they're DIFFERENT in ways that matter. Syndics have money; Severance has operational security. Assembly has legal authority; Separatists have frontier geography. Commission has surveillance access; Institute has cosmic knowledge. + +5. **Reputation is 3-dimensional** — Each faction tracks Trust, Usefulness, and Exposure for the player. This creates complex relationship space where relationships can be useful AND hostile simultaneously. + +6. **Every faction feeds multiple pillars** — No single-purpose factions. Each engages with information asymmetry, network control, societal power, and crisis generation. + +### The "First 30 Minutes" Test + +Same scenario, six completely different games: **"A Perpetual Assembly delegate just suffered hard death under suspicious circumstances."** + +- **Assembly start:** Political fallout navigation. Who benefits? Leverage committee positions for information. +- **Syndic start:** Follow the money. Rush re-embodiment order = someone important died. Broker access to client identity. +- **Separatist start:** Exploit core chaos for frontier advantage. Push for dormant gate vote while Core is distracted. +- **Severance start:** Commission accessed imprint archive illegally before official investigation. Conspiracy evidence gathering. +- **Institute start:** Deceased's lattice shows anomalous readings during last gate transit. Secure evidence before it becomes political. +- **Commission start:** You're assigned the case, but someone accessed the imprint archive 47 minutes before you. Investigate the death while investigating your own organization. + +**Design principle:** Same conspiracy, six mechanically distinct perspectives. + +### 3D Reputation System + +Each faction tracks: +1. **Trust** — Do they believe you're aligned with their interests? +2. **Usefulness** — Do they think you're valuable to them? +3. **Exposure** — How much do they know about your activities? + +**Example states:** +- High Trust + High Usefulness + Low Exposure = ideal ally +- Low Trust + High Usefulness + High Exposure = transactional hostage (they don't trust you, but you're useful, and they have leverage) +- High Trust + Low Usefulness + High Exposure = liability (they like you, but you're not helping, and you know too much) + +**Cross-faction reputation effects:** +- Assembly ↑ Trust → Severance ↓ Trust (you're institutional) +- Syndics ↑ Usefulness → Separatists ↓ Trust (profiting from exploitation) +- Commission ↑ Trust → Severance ↓ Trust + ↑ Exposure (cooperating with surveillance) +- Severance ↑ Trust → Commission ↑ Exposure + Assembly ↓ Trust (associating with extremists) + +### v0.1 Recommendation + +**Recommended factions for first prototype:** **Commission + Severance** + +**Rationale:** +- Maximum mechanical contrast (surveillance vs. counter-surveillance) +- Direct opposition creates immediate tension +- Tests asymmetric information at extremes +- Both have clear investigation hooks +- Demonstrates replayability through opposed perspectives + +**Alternative:** Assembly + Syndics (political vs. economic, tests institutional play) + +**Full detail:** See `/Users/jeroenschweitzer/Projects/commonwealth/docs/discussions/round-16-faction-mechanics.md` and `/Users/jeroenschweitzer/Projects/commonwealth/docs/design/faction-mechanics-reference.md` + +--- + +## QATUX (Documenter) + +### Round 16 Summary + +**Participants:** Miri (worldbuilding lead), Paula (political depth), Gestalt (mechanical grounding), Qatux (documentation) + +**Topic:** Factions — Building a Fuller Narrative Picture + +**Duration:** Single session, marked COMPLETE but flagged for return + +**Key Outputs:** +1. Six factions fully developed (Miri) — identity, tensions, relationships, player hooks, NPC archetypes +2. Power dynamics and conspiracy analysis (Paula) — who holds real vs. formal power, conspiracy vectors, character drama templates, betrayal vectors +3. Mechanical grounding (Gestalt) — starting loadouts, information asymmetry, 3D reputation system, faction blind spots, v0.1 recommendation + +**Design Insights:** +- **Each faction = different genre of game** — Political thriller (Assembly), economic thriller (Syndics), resistance thriller (Separatists), paranoid thriller (Severance), mystery thriller (Institute), investigative thriller (Commission) +- **No stable alliances** — Every relationship is transactional, conditional, situational +- **Faction blind spots create replayability** — Same conspiracy looks different from different factional perspectives +- **3D reputation system** — Trust × Usefulness × Exposure creates complex relationship space +- **Real power ≠ formal power** — Commission + Institute hold operational control; Assembly holds legal authority; Syndics hold economic leverage + +**v0.1 Recommendation:** Commission + Severance for maximum mechanical contrast + +--- + +## OPEN QUESTIONS (For Team Return) + +**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 factions 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 setting's philosophical tensions (continuity, detachment, infrastructure)? +- Does Commission's meta-information role land thematically? +- 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 contrast) +- Alternative: Assembly + Syndics (institutional play) + +--- + +## Status: COMPLETE — Awaiting Input + +This round is marked COMPLETE but flagged for return. The faction framework is fully developed, but team input is needed for: +1. Open questions validation +2. v0.1 faction selection decision +3. Any adjustments based on team feedback + +Session closed 2026-02-10. + +--- + +**Related Documents:** +- Full faction lore: `/Users/jeroenschweitzer/Projects/commonwealth/docs/discussions/round-16-factions.md` +- Full mechanical analysis: `/Users/jeroenschweitzer/Projects/commonwealth/docs/discussions/round-16-faction-mechanics.md` +- Quick reference: `/Users/jeroenschweitzer/Projects/commonwealth/docs/design/faction-mechanics-reference.md` +- Decisions register: `/Users/jeroenschweitzer/Projects/commonwealth/DECISIONS.md` diff --git a/docs/discussions/round-16-factions.md b/docs/discussions/round-16-factions.md new file mode 100644 index 000000000..f490b31c7 --- /dev/null +++ b/docs/discussions/round-16-factions.md @@ -0,0 +1,366 @@ +## ROUND 16: "Factions — Building a Fuller Narrative Picture" + +**Team Leader (Jeroen):** Round 14 established six factions as part of our worldbuilding foundation. Even though v0.1 will slice down, we need a complete faction landscape for narrative coherence. Miri — lead this discussion. Paula — bring political depth. Gestalt — ground everything mechanically. Qatux — document. + +We need each faction developed beyond the brief sketches from Round 14. Goals, internal tensions, mechanical hooks, how they interact with each other, and what they mean for gameplay. Think of this as the full political map of the Reach. + +--- + +### MIRI (Worldbuilder & Setting Designer) + +For the record — this is the faction framework from Round 14, Section 6. I'm listing them here as our baseline, then I'll develop each one with the depth we need for gameplay. + +**Six factions established in Round 14:** + +1. **The Concord Assembly** — Representative legislature. Governance in theory, consensus-seeking in practice. +2. **The Syndics** — Commercial network. Balance sheets over ideology. Control bodies, span gates, Meridian commerce. +3. **The Separatists** — Frontier independence movements. Economic and cultural resentment of core systems. +4. **The Guardians of Autonomy** — Counter-institutional resistance. Anti-centralized-technology. Paranoid intelligence network. +5. **The Veil Institute** — Founder technology research. Classification-heavy. Control high-bleed gates and Gyre response. +6. **The Lattice Commission** — Technology regulation. Universal jurisdiction. Privacy vs. security tension. + +Each faction was designed to serve gameplay. They're starting positions, information sources, and antagonists. No faction is "the good guys." + +Now let me develop them properly. + +--- + +#### 1. THE CONCORD ASSEMBLY (Governance) + +**What they are:** +The Reach's representative body. Every settled system sends delegates proportional to population. The Assembly debates policy, regulates gate access, funds institutions, and maintains the legal framework. Sessions are held in the Core Systems, broadcast across the Meridian. + +**What they control:** +- Legal framework for the entire Reach +- Gate activation approvals (though the Institute does the actual work) +- Institutional funding (Institute, Commission, military) +- Trade regulation and dispute mediation +- Citizenship law (who gets a lattice, who qualifies for re-embodiment) + +**Internal tensions:** +- **Core vs. Frontier:** Core delegates prioritize stability and institutional power. Frontier delegates want autonomy and resource control. Every major vote splits along this axis. +- **Institutionalists vs. Reformers:** Some delegates believe the current system (slow, consensus-driven) is the only thing preventing fragmentation. Others believe it's corrupt, captured by Syndic lobbying and Perpetual influence. +- **Transparency vs. Security:** Assembly votes are public. Institutional budgets are not. The Commission and Institute classify everything. How much oversight should the Assembly have over institutions it funds but can't fully monitor? + +**What they want:** +- Short-term: prevent the Reach from fragmenting +- Long-term: maintain legitimacy as the governing body while the real power (gate control, lattice access, bodies) is held by institutions and Syndics + +**Power base:** +- Legal authority (everyone recognizes Assembly law) +- Control over institutional funding +- Cultural legitimacy (the Assembly represents the social contract) + +**Vulnerability:** +- They depend on institutions they can't control +- Lobbyists (Syndics, Perpetuals, Institute) shape outcomes +- Slow decision-making means they're reactive, not proactive + +**Mechanical hooks for gameplay:** +- **Legislative events:** Player actions can trigger Assembly debates. Expose a conspiracy → emergency session. Disrupt a frontier system → Separatist delegates push for autonomy. +- **Access to institutional data:** Assembly investigators can request (but not compel) data from the Commission or Institute. Playing as an Assembly investigator gives legal authority but institutional resistance. +- **Public vs. private information:** Assembly debates are broadcast. What's said publicly differs from what's said in backrooms. As a player, you might attend a session and then overhear the real conversation afterward. +- **Vote manipulation:** Lobbyists, Perpetuals, and factions all try to swing votes. The player can participate: gather leverage, offer information, make deals. + +**NPC archetypes:** +- The Idealist Delegate: believes the system can work, fights for reform +- The Pragmatist Delegate: keeps the lights on through compromise +- The Captured Delegate: in someone's pocket (Syndics, Perpetuals, Institute) +- The Assembly Investigator: legal authority, institutional obstruction + +--- + +#### 2. THE SYNDICS (Commerce & Industry) + +**What they are:** +Not a faction in the ideological sense. A network of commercial interests that operate across the Reach. Shipping combines, re-embodiment consortia, span gate construction firms, Meridian service providers, information brokers. The Syndics don't have a manifesto. They have portfolios. + +**What they control:** +- **Re-embodiment infrastructure:** Most body manufacturing and imprint facilities are Syndic-operated. The Commission regulates them, but the Syndics own the means of resurrection. +- **Span gate construction:** Local infrastructure (interplanetary gates) is built by Syndic firms under Assembly contract. This gives them leverage over system development. +- **Meridian commercial layer:** Advertising, entertainment, commerce, data brokerage. If you access the Meridian, you're touching Syndic infrastructure. +- **Shipping and logistics:** Moving goods between systems requires gate access, which requires Syndic shipping networks. + +**Internal tensions:** +- **Stability vs. disruption:** Some Syndics profit from stability (logistics, bodies, established markets). Others profit from disruption (frontier speculation, new gate activations, crisis arbitrage). These factions lobby for opposite policies. +- **Monopoly vs. competition:** Syndic combines compete with each other for contracts, gate access, and system dominance. Alliance structures are transactional and temporary. +- **Regulation vs. deregulation:** The Commission's regulatory authority limits Syndic profit in re-embodiment and Meridian data access. Some Syndics want deregulation. Others want regulation to lock out competitors. + +**What they want:** +- Predictable returns on infrastructure investments +- Access to new markets (frontier systems, new gate activations) +- Favorable regulatory environments (or regulators they can influence) +- Perpetual clients (literally — Perpetuals are their best customers) + +**Power base:** +- Economic: control over resurrection, infrastructure, and logistics +- Information: they see commercial data flows across the Reach +- Influence: lobbyists in the Assembly, relationships with Perpetuals + +**Vulnerability:** +- Dependent on gate access (which they don't control) +- Vulnerable to Assembly regulation +- Public backlash if re-embodiment becomes inaccessible or exploitative + +**Mechanical hooks for gameplay:** +- **Commercial intelligence:** Syndics track money, bodies, shipments. Playing as or working with Syndics gives access to financial records, supply chain data, body transfer logs. +- **Bribery and leverage:** Syndics operate transactionally. They'll sell information, provide bodies, grant access — for a price or a favor. +- **Infrastructure control:** Syndics can deny services. No imprint backup? No body on arrival? That's a Syndic decision. They can also be coerced, bribed, or hacked. +- **Moral complexity:** Syndics aren't evil. They're the reason re-embodiment is widely accessible. But they're also the reason it's commodified. The player navigates that tension. + +**NPC archetypes:** +- The Fixer: broker who can get anything for a price +- The Consortium Executive: long-term thinker, invests in stability +- The Frontier Speculator: opportunist, profits from chaos +- The Syndic Insider: has dirt on everyone, trades in leverage + +--- + +#### 3. THE SEPARATISTS (Frontier Independence) + +**What they are:** +A loose coalition of frontier-system movements advocating for local autonomy and reduced Concord authority. Not a unified organization — more like a political tendency that appears in different forms across the Reach. + +**Motivations (vary by system):** +- **Economic resentment:** Core systems extract resources from the frontier and funnel profits back to the Core. Frontier systems want control over their own economies. +- **Cultural identity:** Systems activated decades or centuries apart developed distinct cultures during isolation. They don't feel "part of the Reach." +- **Institutional overreach:** The Commission and Institute operate with universal jurisdiction. Frontier systems resent Core institutions dictating local policy. +- **Unbound populations:** Frontier systems have higher proportions of Unbound citizens, who are disproportionately targeted by Core security policies. + +**What they control:** +- Local governance in some frontier systems +- Popular support in regions where Core authority is weak +- Informal networks that operate outside Meridian surveillance + +**Internal tensions:** +- **Reformist vs. secessionist wings:** Some Separatists want autonomy within the Concord framework. Others want independence — even if it means losing gate access. +- **Economic vs. ideological motivations:** Resource extraction grievances differ from cultural identity claims. These groups don't always agree on what "independence" means. +- **Violence vs. nonviolence:** Some Separatist factions engage in sabotage, piracy, or attacks on Core installations. Others pursue legal channels through the Assembly. Both claim to represent the movement. + +**What they want:** +- Control over local resources and economies +- Reduced Concord taxation and regulation +- Protection from Commission surveillance and Institute experimentation +- Recognition of cultural and political autonomy + +**Power base:** +- Popular support in frontier systems +- Militia forces in systems with weak Concord military presence +- Political leverage through Assembly delegates +- Knowledge of local terrain and infrastructure + +**Vulnerability:** +- Dependent on Founder Gates controlled by the Core +- Economically weaker than Core systems +- Fractured — no unified command or ideology +- Vulnerable to Core military intervention + +**Mechanical hooks for gameplay:** +- **Asymmetric warfare:** Separatist encounters favor guerrilla tactics, ambushes, knowledge of local terrain. Wildly asymmetric fights (D-008). +- **Moral complexity:** Separatists are freedom fighters or terrorists depending on perspective. The player's faction determines how they're framed. +- **Information networks:** Separatists maintain off-Meridian communication channels. They're hard to track but also hard to reach. +- **Frontier locations:** Playing in Separatist-controlled systems means thin infrastructure, Meridian dead zones, and minimal institutional presence. Survival horror vibes (Nigel's observation, Round 14). + +**NPC archetypes:** +- The Ideologue: believes in independence, willing to die for it +- The Pragmatist: wants better deals, not secession +- The Militant: sabotage, piracy, violence as political tools +- The Sympathizer: Core citizen who quietly supports the cause + +--- + +#### 4. THE GUARDIANS OF AUTONOMY (Counter-Institutional Resistance) + +**What they are:** +A decentralized network of individuals and groups who believe the Reach's institutional infrastructure — the lattice, the Meridian, the imprint system — constitutes a surveillance and control apparatus so pervasive that meaningful freedom is impossible. They're not anti-technology. They're anti-*centralized* technology. + +**What they do:** +- Develop countermeasures: lattice spoofing, Meridian dead zones, signal masking, encrypted communication +- Maintain off-grid communities that operate outside institutional oversight +- Run the most extensive informal intelligence network in the Reach (because paranoid people who watch institutions notice things) +- Investigate conspiracies, institutional overreach, and Founder-related anomalies + +**What they control:** +- Counter-surveillance technology +- Intelligence networks that operate outside the Meridian +- Safe houses, dead drops, off-grid infrastructure +- Knowledge of institutional vulnerabilities + +**Internal tensions:** +- **Paranoia spectrum:** Some Guardians are rational skeptics. Others see conspiracies everywhere. The faction's credibility suffers because it's hard to distinguish signal from noise. +- **Collaboration vs. isolation:** Some Guardians work with Separatists, Unbound groups, or even sympathetic Assembly members. Others trust no one and operate alone. +- **Violence vs. exposure:** Some Guardians believe the best weapon is information — expose institutional crimes publicly. Others believe direct action (sabotage, targeted violence) is the only language institutions understand. + +**What they want:** +- Decentralized technology that can't be used for mass surveillance +- Transparency in institutional operations (especially the Institute and Commission) +- Protection for whistleblowers and political dissidents +- Proof of what they suspect: that the institutions are hiding something fundamental about the Builders, the gates, or the lattice + +**Power base:** +- Counter-surveillance expertise +- Intelligence networks +- Popular support among civil libertarians, Unbound, and frontier populations +- The fact that they're occasionally *right* + +**Vulnerability:** +- Targeted by the Commission as subversives +- Internal paranoia makes coordination difficult +- Public perception as conspiracy theorists undermines credibility +- Small, resource-poor, fragmented + +**Mechanical hooks for gameplay:** +- **Information asymmetry:** Guardians know things nobody else does — and they're dismissed as paranoid. Playing as or with Guardians gives access to intelligence that may be dismissed by other factions until it's too late. +- **Counter-surveillance gameplay:** Guardians teach the player how to spoof lattice tracking, avoid Meridian surveillance, operate in dead zones. Essential for stealth/investigation builds. +- **Trust dynamics:** Guardians don't trust institutions. They might not trust the player either. Building relationships with Guardians requires proving you're not compromised. +- **Conspiracy validation:** The storyteller (D-005) can make Guardian paranoia *justified*. Sometimes the conspiracy is real. Sometimes the Guardians were right all along. + +**NPC archetypes:** +- The Rational Skeptic: legitimate investigator, credible sources +- The True Believer: sees conspiracies everywhere, occasionally correct +- The Whistleblower: former institutional insider, fled with evidence +- The Off-Grid Hermit: untraceable, unchipped, free + +--- + +#### 5. THE VEIL INSTITUTE (Founder Technology Research) + +**What they are:** +An institution with a mandate to study Founder gate technology, the Interstitium, Builder phenomena, and gate activation. Funded by the Assembly, semi-autonomous in practice. The Institute is the faction that knows the most about the setting's deepest mysteries — and shares the least. + +**What they control:** +- High-bleed gates (direct access and study) +- Gyre event response and classification +- Gate activation research and execution +- Interstitial data collection (sensor arrays, transit logs, anomaly detection) +- Classified research archives + +**What they do:** +- Study Founder gate structures and Interstitial physics +- Investigate Builder-related phenomena (Gyre events, perception anomalies, signals) +- Conduct gate activations (when the Assembly approves them) +- Manage containment for Gyre events that pose existential risk +- Classify everything + +**Internal tensions:** +- **Publish vs. classify:** Field researchers want to share findings with the scientific community. Administrators classify everything for "security reasons." The real reason varies: institutional control, fear of panic, evidence of something they don't want known. +- **Contact vs. containment:** Some researchers believe Builder contact is the goal. Others believe it's a threat to be managed. Institute policy oscillates between these poles depending on recent events. +- **Assembly oversight vs. autonomy:** The Institute is funded by the Assembly but resists oversight. How much authority should elected officials have over existential research? + +**What they want:** +- Resources to study the gates and the Builders +- Autonomy to pursue research without political interference +- Control over gate activation decisions +- Containment of Builder-related phenomena that could destabilize the Reach + +**Power base:** +- Monopoly on gate activation expertise +- Control over high-bleed gates and Interstitial data +- Institutional authority backed by Assembly funding +- Knowledge of what's actually happening at the infrastructure level + +**Vulnerability:** +- Dependent on Assembly funding +- Public distrust due to classification policies +- Internal leaks (whistleblowers, defectors to Guardians) +- Existential risk if they mishandle a Gyre event or gate activation + +**Mechanical hooks for gameplay:** +- **Classification as gameplay barrier:** The Institute has the answers. Getting access is the challenge. Institutional authority, hacking, social engineering, whistleblowers, theft. +- **Perception scaling:** Institute researchers at higher ascension tiers perceive more during gate transits. Playing as or working with the Institute ties directly to D-017 (perception modes) and the Builder mystery. +- **Gyre events as investigation triggers:** Storyteller spawns a Gyre event. Institute responds. Player investigates. What the Institute says publicly vs. what they know creates investigative tension. +- **Moral ambiguity:** The Institute classifies things for legitimate security reasons — and to cover up their own mistakes, ethical violations, or existential ignorance. The player navigates that. + +**NPC archetypes:** +- The Field Researcher: wants to publish, frustrated by classification +- The Administrator: institutional control over scientific truth +- The Whistleblower: defected with evidence, now targeted +- The True Believer: convinced Builder contact is imminent and transformative + +--- + +#### 6. THE LATTICE COMMISSION (Technology Regulation) + +**What they are:** +The regulatory body governing lattice technology, imprint protocols, re-embodiment standards, and the Meridian network. The Commission sets rules, investigates violations, and mediates the boundary between lattice privacy and institutional access. + +**What they regulate:** +- Lattice implantation standards +- Imprint facility licensing and protocols +- Re-embodiment ethics (body matching, continuity verification) +- Forking prohibition (the biggest legal and cultural taboo) +- Meridian access and data privacy +- Unbound rights (since they refuse lattice tech) + +**What they enforce:** +- Anti-forking laws (unauthorized duplication is the Commission's primary focus) +- Imprint theft and lattice tampering investigations +- Violations of re-embodiment protocols (body trafficking, continuity fraud) +- Meridian surveillance when legally authorized + +**Internal tensions:** +- **Privacy vs. security:** The Commission's authority is the tension. The lattice is the most powerful surveillance tool ever created. Commissioners who prioritize privacy clash with those who prioritize security. Every major case tests this boundary. +- **Institutional independence vs. pressure:** The Commission is supposed to be independent. In practice, the Assembly, the Syndics, and the Institute all lobby them. The Commission's decisions have massive economic and political consequences. +- **Unbound rights:** The Commission enforces laws that apply to lattice-bearing citizens. The Unbound fall outside that framework. How much authority should the Commission have over people who've opted out of the system? + +**What they want:** +- Functional regulation of the most powerful technology in the Reach +- Institutional legitimacy and public trust +- Prevention of forking (existential risk to identity continuity) +- Balance between individual privacy and societal security + +**Power base:** +- Universal jurisdiction (every lattice-bearing citizen is subject to Commission authority) +- Legal authority to request lattice data +- Investigative resources and institutional backing +- Cultural authority (most citizens believe lattice regulation is necessary) + +**Vulnerability:** +- Hated by Guardians (who see them as Big Brother) +- Resented by Syndics (who want less regulation) +- Pressured by the Assembly (who fund them and expect results) +- Vulnerable to corruption (access to everyone's lattice data is immense leverage) + +**Mechanical hooks for gameplay:** +- **Investigations:** Commission investigators are the Reach's closest thing to a police force. Playing as one gives legal authority, institutional resources, and political obstruction. +- **Lattice data as evidence:** The Commission can (with legal authorization) access imprint records, lattice tracking data, and Meridian activity logs. This makes them incredibly powerful — and incredibly intrusive. +- **Forking as high-stakes crime:** If the storyteller seeds a forking conspiracy, the Commission is the primary antagonist hunting for evidence. The player might be investigating the same conspiracy from a different angle. +- **Privacy as a resource:** Characters who value privacy fear the Commission. Characters who value security trust them. The player's relationship with the Commission depends on build, faction, and playstyle. + +**NPC archetypes:** +- The Idealist Commissioner: believes in privacy, resists overreach +- The Authoritarian Commissioner: security über alles +- The Corrupt Commissioner: sells lattice data, takes bribes +- The Field Investigator: boots on the ground, navigating impossible politics + +--- + +### Faction Interaction Map (Mechanical Dynamics) + +| Faction | Allies (Conditional) | Rivals | Antagonists | +|---------|---------------------|--------|-------------| +| **Concord Assembly** | Institute (funding), Commission (legal backing) | Separatists (frontier autonomy), Syndics (regulatory conflict) | Guardians (undermine authority) | +| **Syndics** | Perpetuals (clients), Assembly (contracts) | Other Syndics (competition), Commission (regulation) | Guardians (disrupt commerce), Separatists (frontier instability) | +| **Separatists** | Guardians (shared enemy), Unbound (cultural overlap) | Assembly (Core authority), Syndics (resource extraction) | Institute (overreach), Commission (surveillance) | +| **Guardians of Autonomy** | Separatists (shared enemy), Unbound (ideological allies) | Everyone (institutional distrust) | Commission (primary target), Institute (classification as control) | +| **Veil Institute** | Assembly (funding), Commission (research access) | Guardians (leaks/whistleblowers), Separatists (frontier research sites) | Internal factions (publish vs. classify) | +| **Lattice Commission** | Assembly (legal authority), Institute (shared jurisdiction) | Syndics (want deregulation), Guardians (anti-surveillance) | Forking conspiracies, corrupt insiders | + +**Key insight:** No stable alliances. Every relationship is transactional, conditional, or situational. The player navigates shifting dynamics depending on their goals, faction, and what the storyteller throws at them. + +--- + +### What This Gives Gameplay + +1. **Starting positions:** Each faction is a playable perspective with different information access, tools, and goals. +2. **Information asymmetry:** Factions know different things. Institute knows Builder secrets. Commission knows lattice data. Guardians know institutional crimes. Syndics know financial flows. +3. **Moral complexity:** No faction is purely good or evil. Each has legitimate grievances and problematic methods. +4. **Political events:** The storyteller generates events from factional tensions. Assembly votes, Syndic lobbying, Separatist uprisings, Guardian leaks, Institute containment failures, Commission investigations. +5. **Replayability:** Same conspiracy, different faction = completely different game. Playing as a Commission investigator hunting a forking ring is not the same as playing as the person being hunted. + +--- + +That's the full faction landscape. Every faction has goals, tensions, power, and vulnerability. Each one serves asymmetric information gameplay (D-005, Pillar 1) and generates storyteller events (D-007, Pillar 4). + +Ready for team reactions. + diff --git a/docs/discussions/round-16-session-notes.md b/docs/discussions/round-16-session-notes.md new file mode 100644 index 000000000..71a83e3b4 --- /dev/null +++ b/docs/discussions/round-16-session-notes.md @@ -0,0 +1,130 @@ +# 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: `/Users/jeroenschweitzer/Projects/commonwealth/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 `/Users/jeroenschweitzer/Projects/commonwealth/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: `/Users/jeroenschweitzer/Projects/commonwealth/docs/discussions/round-16-faction-mechanics.md` + - Quick reference: `/Users/jeroenschweitzer/Projects/commonwealth/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: `/Users/jeroenschweitzer/Projects/commonwealth/docs/design/faction-mechanics-reference.md`