Files
settled-reach/wiki/star-systems/GJ-222A/gttr.md
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

3.3 KiB

THE DRIFTER'S GUIDE TO THE REACH — KAROO

KAROO is physically comfortable and institutionally precarious, a combination that produces a particular kind of community psychology that the residents have politely declined to name.

The Node

Gate Corporation operates a maintenance node here: not a full base, but a servicing facility capable of aperture calibration, gate ferry overhaul, and the scheduled maintenance that through-route positions require. The community that grew up around the node provides everything the node's rotating staff need and, by extension, exists. The through-route topology means freight is always moving through. The Gate Corp presence means there is always work. The G0V primary — slightly warmer and more luminous than Sol, geologically unremarkable, atmospherically livable — means none of this is caused by adversity.

What it is caused by is contingency. The south Reach corridor's traffic volume depends on the systems beyond it having economic output worth hauling. If the deep systems atrophied — if the frontier's agricultural remnants finally fell below export viability, if trading operations two hops out eroded — the freight volumes through Karoo would decline. A through-route maintenance node handling reduced traffic becomes a node that Gate Corporation's allocation committee might consolidate with another facility. No one at Karoo speaks this possibility aloud, because speaking it aloud would acknowledge that the settlement's existence depends on economic conditions two hops away that Karoo cannot control. The settlement was built around the node. The node is not built around the settlement.

The Council's Jurisdiction

The settlement council handles residential allocation, local commercial licensing, and dispute resolution. Its authority does not extend to the Gate Corp node or the fabrication cluster, which operate under corporate policy. The boundary is clear in formal terms and continuously contested in practice — particularly over environmental and noise standards near the residential districts, which the council wants enforced and which the node's operations team wants treated as operational necessities.

The Guardians of Autonomy have a chapter in the manufacturing cluster's labor districts. Their relationship with the settlement council is cooperative, which is practical rather than ideological: both institutions understand that Gate Corporation does not need Karoo specifically, it needs a through-route maintenance node, and that Karoo remains the location for that node partly because the local environment has not yet become sufficiently difficult to justify relocation. The council and the Guardians share an interest in remaining below that threshold without quite meeting each other's eyes about why.

Practical Information

Karoo is five hops from Gateway with two gate apertures — a through-route between Caparica and Vuurkloof. The fabrication cluster produces replacement parts and maintenance consumables, primarily for the node's own use. Food comes in from Caparica. Consumer goods arrive through the Altair corridor. The G0V primary makes the surface livable without any particular effort, which is the kind of advantage that looks like it should be sufficient and turns out not to be.

Adams of the Guide rates Karoo: Comfortable. Do Not Examine Why.