Files

T

jpmschweitzerandClaude Opus 4.7 25eb8bd096 content(wiki): purge v0.1 Sova/Van Maanen residue (#865 )

Spring-cleaning accumulated v0.1 vertical-slice residue across the
wiki. Scope per Jeroen's pre-decisions on 2026-04-21:

- Delete outright: wiki/star-systems/GJ-35/sova/ subtree (5 files +
  2 dirs) — v0.1 Station Sova / Transit District content.
- Strip example blocks in authoring guides and _templates/ that
  cited dropped v0.1 NPCs (Kael Davan, Sera Venn, Nils Davan, Devra,
  Torek, Renn, Pell, Tav, Lera Sessik, Sabel). Replaced with short
  "v0.1 examples removed — D-122" notes pointing authors to the
  active NPC roster.
- Rewrite canonical-lore references file-by-file: faction pages,
  technology pages, contraband pages, concepts pages, corp pages
  that cited v0.1 names/places. Preserve institutional/structural
  content, drop specific-name citations.
- Commission name drift: replace "Concord Commission" and "Assembly
  Commission" with "the Lattice Commission" (D-193) throughout.
- Van Maanen's Star cultural references: the canonical in-game name
  is Vuurkloof. "Van Maanen's Star" is retained only as an
  astronomical designation (glossary + GJ-35 Calibration Note).
  All cultural/system references converted to Vuurkloof across
  culture-authoring-guide, cultural-generation-guide, founder-gates,
  and star-system adjacent-system descriptions.
- Strip `v0.1` from faction/triangle frontmatter tags (8 files).
- wiki/triangles/hub-power.md and wiki/factions/the-ring.md:
  rewritten using role-name exemplars (Ring Coordinator / Shift
  Supervisor / THE FRIEND) instead of named v0.1 NPCs. Triangle
  pattern preserved as a structural reference.

Also applies drive-by Commission drift fixes and minor cross-ref
updates to canonical corps (gate-corporation, mastroianni-vehicle-group,
stalownia-kowalski, prometheus-labs, ferreira-monteiro, vins-de-grand-vide,
and 13 others).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-22 10:26:45 +02:00

6.8 KiB

Raw Blame History

title, description, slug, category, status, created, updated, scope, faction_type, tags, decision_refs, cross_refs

title

description

slug

The Concord Assembly

Type: Faction — Legislative Government Status: Canonical Scope: Reach-wide Governance Role: Legislative / Executive Headquarters: Core Systems (TBD) Structure: Representative legislature, proportional delegation by settled system

Overview

The Concord Assembly is the Settled Reach's representative governing body. Every settled system sends delegates proportional to population. The Assembly debates policy, regulates gate access, funds institutions, and maintains the legal framework that holds the Reach together. Sessions are held in the Core Systems and broadcast across the Meridian.

The Assembly is the closest thing the Reach has to a legitimate government — and legitimacy is its only real power. It doesn't control the gates (the Veil Institute does). It doesn't control identity technology (the Lattice Commission does). It doesn't control the economy (the Syndics do). What it controls is the law, the budget, and the fragile consensus that the Reach is better off unified than fragmented.

What They Control

Legal framework for the entire Settled Reach
Gate activation approvals (though the Institute performs the actual work)
Institutional funding (Institute, Commission, military)
Trade regulation and dispute mediation between systems
Citizenship law (who qualifies for lattice implantation, re-embodiment rights)

Internal Tensions

Core vs. Frontier: The Assembly's defining fault line. Core system delegates prioritize stability, institutional power, and centralized governance. Frontier delegates want local autonomy, resource sovereignty, and reduced taxation. Every major vote splits along this axis. The frontier delegates are outnumbered by population but loud enough to be heard.

Institutionalists vs. Reformers: Some delegates believe the current system — slow, consensus-driven, deliberately cautious — is the only thing preventing the Reach from fragmenting. Others believe the system is corrupt, captured by Syndic lobbying, Perpetual influence, and institutional inertia. Both sides have evidence.

Transparency vs. Security: Assembly votes are public. Institutional budgets are not. The Commission and Institute classify everything. The Assembly funds institutions it cannot fully monitor. How much oversight should elected representatives have over organizations they created but can no longer control?

What They Want

Short-term: Prevent the Reach from fragmenting along Core-Frontier lines
Long-term: Maintain legitimacy as the governing body while real power — gate control, lattice access, economic infrastructure — is held by institutions and Syndics they can influence but not command

Power & Vulnerability

Power	Vulnerability
Legal authority (universally recognized)	Depends on institutions it can't directly control
Control over institutional funding	Lobbyists (Syndics, Perpetuals, Institute) shape outcomes
Cultural legitimacy (represents the social contract)	Slow decision-making means reactive, not proactive
Dispute mediation (the alternative is conflict)	Frontier systems questioning the contract itself

Faction Relationships

Faction	Relationship	Dynamic
Lattice Commission	Conditional ally	Legal backing; Commission enforces Assembly law but resists oversight
Veil Institute	Conditional ally	Assembly funds Institute; Institute resists disclosure
Syndics	Rival / Dependent	Assembly regulates commerce; Syndics lobby to weaken regulation
Guardians of Autonomy	Antagonist	Guardians undermine Assembly authority; Assembly dismisses Guardian concerns
The Unbound	Ambivalent	Unbound citizenship rights are an unresolved legal question

Mechanical Hooks for Gameplay

Legislative events: Player actions can trigger Assembly debates. Expose a conspiracy and an emergency session follows. Destabilize a frontier system and Separatist delegates push for autonomy.
Access to institutional data: Assembly investigators can request (but not compel) data from the Commission or Institute. Legal authority with institutional resistance.
Public vs. private information: Assembly debates are broadcast. What's said publicly differs from what's said in backrooms. The player might attend a session and 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 from within
The Pragmatist Delegate: Keeps the lights on through compromise, distasteful but functional
The Captured Delegate: In someone's pocket (Syndics, Perpetuals, Institute) — useful if you know who holds the leash
The Assembly Investigator: Legal authority meets institutional obstruction

Gameplay Relevance

The Concord Assembly is referenced but not directly present in any given district setting. Its influence is felt through:

The legal framework that gives the detective jurisdictional authority
News ticker headlines about Assembly proceedings (background texture)
The institutional hierarchy that assigns Commission investigators to districts
NPC dialogue referencing "the Assembly" as distant governance — recognized, not loved

The Assembly is the water any district's fish swim in. Nobody in a working freight hub thinks about the Assembly day-to-day, the same way nobody thinks about the legislature that passed the labor laws governing their shift schedule. But the Assembly's decisions created the Commission, funded the Institute, and wrote the regulations that make lattice smuggling illegal. Every tension in the district traces back to Assembly policy, however distantly.

Cross-References:

Lattice Commission — Regulatory body the Assembly funds
Veil Institute — Research institution the Assembly funds
Syndics — Commercial interests that lobby the Assembly
Round 16: Full faction development

Status: Canonical Created: 2026-02-12 Updated: 2026-02-12

6.8 KiB Raw Blame History