Compare commits
30
Commits
9bc5cb21a5
...
1782592dfd
@@ -7,6 +7,24 @@ Format based on [Keep a Changelog](https://keepachangelog.com/).
|
||||
## [Unreleased]
|
||||
|
||||
### Added
|
||||
- GJ 6711 / Abzu workshop — 6 rounds, 24 documents: initial briefs (4 agents), cross-pollination syntheses, sealed envelope (observation is load-bearing), stress test challenges against existing canon, final syntheses with Abzu naming, mechanics design (watch investment counter, six player verbs, bleed tile states, Adams & Ford entry filing), carry-out proposals (unresolved — reward design TBD)
|
||||
- Star map topology and real-coordinate SVG visualizations
|
||||
- Compact of Westphalia faction page — mutual recognition treaty, ~30-40 west_reach systems, four core principles, rotating council, internal treaty-vs-government tension
|
||||
- Batch 18 wiki pages — 18 systems reassigned from deep_frontier into named corridors (Waterkant, Breëvlei, Stilwater, Mossbank, Ribeirão, Nascente, Dernier Quai, Marktfeld, Bestevaer, Lichtung, Knotenpunkt, Posto Avançado, Weitblick, Último Farol, plus 4 unsettled)
|
||||
- Batch 17 wiki pages — Xa Vời, Eisfeld, Confluent (60+ wine châteaux), Dunkelholz, Echternach (Luxembourgish), Bout du Chemin (French), Grenzstein, plus GJ 4056 (unsettled)
|
||||
- Corporation doc for Vins de Grand Vide — négociant cooperative, three-tier classification (Grand Vide Classé / Vins de Corridors / Vin de Table du Vide), 6 named estates, 350-year commercial archive
|
||||
- Batch 16 wiki pages — 13 south_reach systems at hops 7-8 including Espinho, Okahandja, Encrucijada, Quilombo, Velha Guarda, Fragua, Puerto Último, plus GJ 902 (unsettled, reserved for base building DLC per D-145)
|
||||
- Batch 15 wiki page — Shimanami (east_reach hop 8)
|
||||
- Batch 14 wiki pages — Wagtoring, Dunmore, Caledonia's End (north_reach hops 7-8)
|
||||
- Batch 13 wiki pages — Stillvakt, Haltefenn, Vindkast, Kopparhytta, Steinfeld, Brückenau (west_reach hops 7-8)
|
||||
- Corporation docs for Nordmark Skog (timber, Stillvakt) and Talbräu (lager, Brückenau)
|
||||
- D-145: base building DLC — GJ 902 habitable moon as potential player settlement site
|
||||
- South_reach wiki pages (batch 12) — Matamba, Inhambane, Isibaya, Kaapse Baai, Mwangaza, Dzimbahwe, Vuurkloof, Várzea, Nowa Huta, plus GJ 695A (unsettled)
|
||||
- Corporation docs for Ferreira Monteiro (trade arbitration, Matamba) and Stalownia Kowalski (heavy equipment, Nowa Huta)
|
||||
- East_reach wiki pages (batch 11) — Kaur's Observatory, Seongho, Tình Yên, Purnima, Marunong, Clearwater Station, Tam Giang, Jeonnam, Dagat, Suối Vàng
|
||||
- Inner hub wiki pages (hops 3-4) — Crown's Hollow, Cairnside, Schuilhoek, Travessia, Nová Tržnice
|
||||
- Corporation doc for Mercado Travessia (grocery chain, Travessia)
|
||||
- Corporation docs for Adams & Ford Publishing, Calloway Distillery, thrds (updated index)
|
||||
- 300-system CSV framework (systems-framework.md) — 66 columns covering colonization waves, cultural archetypes, tone framework, economic distribution, and Krenn validation (D-095)
|
||||
- Star map gate topology — 300-node network with 334 edges across 6 sectors, generated and hand-tuned for natural corridor structure in frontier space
|
||||
- Star map generation pipeline — seed-based generator, sculpting script, core sector patcher, topology tuner with bridge-safe connectivity guarantees
|
||||
@@ -19,6 +37,9 @@ Format based on [Keep a Changelog](https://keepachangelog.com/).
|
||||
- `hop_distance_from_gateway` column in system_gates table
|
||||
|
||||
### Changed
|
||||
- Rebuilt catalog.md and star-systems/index.md — now covers all 301 systems (227 named) organized by sector and hop distance
|
||||
- 14 systems reassigned from deep_frontier into named corridors at hops 5-7 (5 north, 3 south, 3 east, 3 west)
|
||||
- Renamed Carrefour to Confluent; expanded to 60+ named châteaux with 16 individually described estates
|
||||
- D-095 aperture range amended from 4-8 to 1-8 — single-aperture dead-end systems valid for isolated frontier outposts
|
||||
- D-095 amended: inter-system gates are alien-built (aperture count alien-determined), intra-system span gates are human-built (Institute reverse-engineering, Gate Corporation license)
|
||||
- All system identifiers migrated from arbitrary S-numbers to GJ astronomical catalog IDs
|
||||
|
||||
+12
-1
@@ -276,4 +276,15 @@ What we're building: game concept, design pillars, prototype definition, map spe
|
||||
|
||||
---
|
||||
|
||||
*24 decisions (15 active, 9 superseded). Last updated: 2026-03-05 (D-114–D-120 added; D-014, D-027, D-039, D-065, D-087, D-089, D-091 superseded — Where's the Fun? Workshop)*
|
||||
---
|
||||
|
||||
### D-145: Base building DLC — GJ 902 unclaimed moon as player settlement site
|
||||
- **Date:** 2026-03-15
|
||||
- **Decision:** The unsettled system GJ 902 (south_reach, hop 7, K-type dead-end) contains a habitable moon with an iron core orbiting a gas giant. This is deliberately left unclaimed as prep for a future base building DLC where players could claim and settle it. The marginally habitable planet in the same system provides contrast; the moon is the prize.
|
||||
- **Rationale:** Having a genuinely good piece of unclaimed real estate in the star map gives the base building DLC a natural entry point with existing lore context. The dead-end topology and quiet corridor explain why nobody has claimed it yet.
|
||||
- **Source:** Wiki writing session, 2026-03-15
|
||||
- **Raised by:** Jeroen
|
||||
|
||||
---
|
||||
|
||||
*25 decisions (16 active, 9 superseded). Last updated: 2026-03-15 (D-145 added)*
|
||||
|
||||
@@ -0,0 +1,687 @@
|
||||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1600 1000" width="1600" height="1000">
|
||||
<rect width="1600" height="1000" fill="#0a0a1a"/>
|
||||
<line x1="167.1" y1="594.0" x2="477.0" y2="598.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="167.1" y1="594.0" x2="965.4" y2="847.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1306.8" y1="707.8" x2="65.6" y2="714.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="65.6" y1="714.9" x2="1126.6" y2="653.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1126.6" y1="653.9" x2="86.4" y2="940.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="86.4" y1="940.0" x2="881.8" y2="607.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="881.8" y1="607.4" x2="787.3" y2="732.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="787.3" y1="732.6" x2="841.1" y2="720.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="841.1" y1="720.6" x2="750.8" y2="332.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="750.8" y1="332.3" x2="944.3" y2="839.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="944.3" y1="839.1" x2="441.1" y2="925.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1266.8" y1="111.0" x2="78.9" y2="255.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="441.1" y1="925.9" x2="1006.4" y2="547.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1006.4" y1="547.6" x2="910.0" y2="420.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="910.0" y1="420.0" x2="1079.4" y2="575.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1126.6" y1="653.9" x2="162.7" y2="821.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1079.4" y1="575.5" x2="1223.0" y2="638.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1223.0" y1="638.6" x2="380.8" y2="758.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="380.8" y1="758.1" x2="441.5" y2="627.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1085.6" y1="517.2" x2="1243.6" y2="404.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1243.6" y1="404.4" x2="1077.5" y2="899.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="441.5" y1="627.4" x2="1350.1" y2="153.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="880.2" y1="408.0" x2="801.9" y2="563.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1391.5" y1="780.6" x2="875.1" y2="346.7" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="875.1" y1="346.7" x2="406.4" y2="440.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1090.7" y1="325.7" x2="652.9" y2="626.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="652.9" y1="626.3" x2="218.9" y2="751.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="875.1" y1="346.7" x2="799.0" y2="660.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="374.5" y1="828.4" x2="349.6" y2="386.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="376.9" y1="402.6" x2="919.2" y2="400.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="349.6" y1="386.1" x2="166.7" y2="143.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="166.7" y1="143.9" x2="764.8" y2="851.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="573.0" y1="575.3" x2="1298.1" y2="485.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1298.1" y1="485.3" x2="709.1" y2="188.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="709.1" y1="188.2" x2="1290.4" y2="467.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="487.0" y1="316.3" x2="630.7" y2="206.7" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1290.4" y1="467.9" x2="1196.5" y2="494.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="764.8" y1="851.9" x2="159.6" y2="270.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1196.5" y1="494.6" x2="257.7" y2="667.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="843.5" y1="417.3" x2="1521.0" y2="66.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1521.0" y1="66.0" x2="1064.3" y2="551.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="257.7" y1="667.6" x2="114.6" y2="675.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1064.3" y1="551.3" x2="1437.6" y2="806.7" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1437.6" y1="806.7" x2="281.3" y2="777.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="281.3" y1="777.3" x2="646.6" y2="472.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="646.6" y1="472.1" x2="587.9" y2="681.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="114.6" y1="675.4" x2="533.5" y2="524.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="587.9" y1="681.8" x2="539.0" y2="345.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="533.5" y1="524.4" x2="1341.9" y2="155.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1044.5" y1="415.7" x2="1113.4" y2="214.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="668.5" y1="749.5" x2="289.8" y2="559.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="652.6" y1="302.0" x2="1105.2" y2="551.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="521.4" y1="610.1" x2="411.4" y2="202.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="336.9" y1="380.3" x2="844.0" y2="512.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="411.4" y1="202.3" x2="237.6" y2="576.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="844.0" y1="512.2" x2="1184.4" y2="749.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="959.1" y1="205.5" x2="1441.7" y2="811.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1184.4" y1="749.2" x2="1460.7" y2="671.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1460.7" y1="671.5" x2="398.1" y2="523.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="237.6" y1="576.1" x2="781.6" y2="311.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1441.7" y1="811.9" x2="909.0" y2="809.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="909.0" y1="809.4" x2="66.8" y2="340.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1148.1" y1="754.1" x2="1309.5" y2="758.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1309.5" y1="758.9" x2="660.0" y2="892.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="374.5" y1="828.4" x2="1135.7" y2="124.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="398.1" y1="523.8" x2="264.0" y2="856.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="66.8" y1="340.3" x2="913.4" y2="351.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="913.4" y1="351.8" x2="1211.7" y2="622.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1135.7" y1="124.2" x2="471.4" y2="817.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="660.0" y1="892.8" x2="783.9" y2="796.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="264.0" y1="856.8" x2="201.1" y2="310.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1211.7" y1="622.9" x2="62.2" y2="351.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="783.9" y1="796.6" x2="977.6" y2="396.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="229.0" y1="226.3" x2="1122.2" y2="514.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1531.2" y1="490.5" x2="80.6" y2="870.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="80.6" y1="870.1" x2="345.8" y2="205.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="345.8" y1="205.6" x2="960.0" y2="574.7" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="960.0" y1="574.7" x2="176.1" y2="630.7" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="162.7" y1="821.2" x2="745.2" y2="258.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="176.1" y1="630.7" x2="1426.0" y2="361.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1426.0" y1="361.0" x2="263.6" y2="857.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="471.4" y1="817.9" x2="1120.4" y2="846.7" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="263.6" y1="857.2" x2="791.6" y2="494.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="110.5" y1="177.8" x2="1447.6" y2="178.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1447.6" y1="178.5" x2="1193.4" y2="93.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="598.7" y1="723.5" x2="1338.8" y2="801.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1534.5" y1="77.8" x2="623.1" y2="629.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="623.1" y1="629.0" x2="361.2" y2="274.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1120.4" y1="846.7" x2="649.7" y2="212.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="361.2" y1="274.3" x2="844.0" y2="512.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1457.8" y1="875.5" x2="1090.7" y2="325.7" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="539.0" y1="345.9" x2="1034.2" y2="462.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="844.0" y1="512.2" x2="254.6" y2="224.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1146.0" y1="154.9" x2="916.4" y2="222.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="62.2" y1="351.2" x2="883.2" y2="234.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="940.8" y1="395.8" x2="774.9" y2="689.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="649.7" y1="212.4" x2="1145.9" y2="154.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1145.9" y1="154.9" x2="1470.6" y2="544.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="883.2" y1="234.4" x2="1122.4" y2="246.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="254.6" y1="224.1" x2="502.7" y2="286.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="916.4" y1="222.2" x2="1521.6" y2="472.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1521.6" y1="472.3" x2="1220.6" y2="524.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1220.6" y1="524.6" x2="1131.2" y2="320.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="774.9" y1="689.3" x2="75.9" y2="595.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="502.7" y1="286.6" x2="1254.9" y2="761.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1122.4" y1="246.4" x2="369.6" y2="536.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="75.9" y1="595.1" x2="220.7" y2="465.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1131.2" y1="320.8" x2="283.2" y2="501.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="283.2" y1="501.8" x2="257.7" y2="667.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="220.7" y1="465.2" x2="788.4" y2="60.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1470.6" y1="544.1" x2="533.6" y2="524.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1074.3" y1="197.6" x2="758.1" y2="326.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1254.9" y1="761.1" x2="130.3" y2="194.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="130.3" y1="194.1" x2="1458.4" y2="590.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="533.6" y1="524.4" x2="755.2" y2="606.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="257.7" y1="667.6" x2="873.2" y2="405.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="369.6" y1="536.5" x2="165.5" y2="389.7" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="873.2" y1="405.1" x2="800.0" y2="500.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="758.1" y1="326.1" x2="189.5" y2="674.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="755.2" y1="606.4" x2="1061.8" y2="900.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1034.2" y1="462.6" x2="323.5" y2="804.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1338.8" y1="801.4" x2="1043.2" y2="862.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="189.5" y1="674.3" x2="401.2" y2="524.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="799.0" y1="660.4" x2="1299.2" y2="470.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="323.5" y1="804.9" x2="608.2" y2="344.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="345.8" y1="205.6" x2="1072.9" y2="725.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="165.5" y1="389.7" x2="1494.2" y2="181.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="201.1" y1="310.9" x2="870.1" y2="386.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="401.2" y1="524.8" x2="1147.5" y2="118.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="960.0" y1="574.7" x2="430.6" y2="488.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="714.3" y1="112.2" x2="830.9" y2="564.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="265.2" y1="485.0" x2="611.3" y2="104.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1043.2" y1="862.0" x2="687.4" y2="214.7" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="274.0" y1="615.8" x2="761.5" y2="619.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="870.1" y1="386.6" x2="1250.9" y2="474.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1147.5" y1="118.4" x2="1442.5" y2="603.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1061.8" y1="900.0" x2="947.3" y2="336.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1422.2" y1="824.5" x2="110.5" y2="177.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="110.5" y1="177.8" x2="835.4" y2="453.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="134.6" y1="600.0" x2="742.8" y2="301.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="923.8" y1="616.0" x2="1473.6" y2="584.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="761.5" y1="619.5" x2="356.0" y2="599.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1341.9" y1="155.1" x2="914.1" y2="628.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="134.6" y1="600.0" x2="1157.8" y2="347.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="110.5" y1="177.8" x2="1129.5" y2="701.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="830.9" y1="564.2" x2="100.5" y2="384.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1473.6" y1="584.5" x2="1122.4" y2="246.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1157.8" y1="347.6" x2="566.4" y2="454.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="979.6" y1="396.0" x2="1513.3" y2="391.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1513.3" y1="391.6" x2="697.8" y2="391.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1122.4" y1="246.4" x2="1129.4" y2="701.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1129.4" y1="701.5" x2="723.5" y2="849.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1289.0" y1="253.4" x2="132.4" y2="884.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1129.5" y1="701.5" x2="1119.8" y2="257.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="430.6" y1="488.8" x2="1129.5" y2="701.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="697.8" y1="391.9" x2="109.8" y2="474.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="132.4" y1="884.6" x2="282.3" y2="755.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="282.3" y1="755.2" x2="1285.7" y2="454.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="687.4" y1="214.7" x2="1062.4" y2="828.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1311.0" y1="656.6" x2="460.8" y2="519.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1285.7" y1="454.0" x2="66.9" y2="546.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1119.8" y1="257.6" x2="372.2" y2="602.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="372.2" y1="602.1" x2="835.9" y2="270.7" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="356.0" y1="599.6" x2="709.0" y2="188.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="460.8" y1="519.9" x2="977.6" y2="396.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="835.9" y1="270.7" x2="727.2" y2="568.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="66.9" y1="546.6" x2="424.8" y2="389.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="65.8" y1="245.5" x2="1387.5" y2="404.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="424.8" y1="389.6" x2="110.6" y2="473.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="727.2" y1="568.0" x2="1125.7" y2="654.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="109.8" y1="474.3" x2="820.7" y2="441.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1125.7" y1="654.2" x2="1214.1" y2="364.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="745.0" y1="258.4" x2="1447.6" y2="178.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="709.0" y1="188.0" x2="738.8" y2="275.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1214.1" y1="364.2" x2="1374.8" y2="723.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1129.4" y1="701.5" x2="614.1" y2="392.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="374.8" y1="828.8" x2="781.6" y2="754.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="614.1" y1="392.5" x2="1467.0" y2="253.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="567.1" y1="625.7" x2="414.6" y2="630.7" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="781.6" y1="754.6" x2="707.4" y2="499.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="707.4" y1="499.3" x2="1105.3" y2="551.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1105.3" y1="551.1" x2="1523.7" y2="254.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="414.6" y1="630.7" x2="1181.6" y2="287.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1523.7" y1="254.8" x2="584.8" y2="352.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="584.8" y1="352.9" x2="1157.9" y2="827.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1374.8" y1="723.4" x2="1304.2" y2="877.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="977.6" y1="396.3" x2="412.2" y2="433.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="412.2" y1="433.6" x2="835.4" y2="453.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1374.8" y1="723.4" x2="265.8" y2="747.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1476.8" y1="682.2" x2="358.4" y2="464.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1181.6" y1="287.0" x2="170.9" y2="143.7" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="835.4" y1="453.2" x2="758.1" y2="326.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="358.4" y1="464.8" x2="1094.6" y2="315.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1157.9" y1="827.5" x2="370.8" y2="543.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="170.9" y1="143.7" x2="990.3" y2="235.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="282.3" y1="755.2" x2="1480.8" y2="631.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="170.9" y1="143.7" x2="1146.2" y2="778.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="793.9" y1="291.2" x2="1150.4" y2="484.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1146.2" y1="778.8" x2="1524.9" y2="297.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="414.5" y1="630.6" x2="1136.5" y2="492.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="110.6" y1="473.6" x2="194.2" y2="790.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1136.5" y1="492.1" x2="735.8" y2="464.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="584.8" y1="352.9" x2="1191.2" y2="130.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1288.9" y1="253.4" x2="1476.2" y2="929.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="990.3" y1="235.1" x2="386.0" y2="244.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="730.0" y1="465.6" x2="1115.2" y2="532.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1115.2" y1="532.6" x2="203.1" y2="650.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="735.8" y1="464.5" x2="161.9" y2="605.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="370.8" y1="543.2" x2="611.3" y2="104.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1524.9" y1="297.9" x2="520.5" y2="474.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="520.5" y1="474.6" x2="484.4" y2="533.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="161.9" y1="605.3" x2="538.3" y2="484.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="386.0" y1="244.5" x2="1203.9" y2="610.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1203.9" y1="610.8" x2="1539.9" y2="372.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="484.4" y1="533.3" x2="1019.6" y2="737.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="947.3" y1="336.9" x2="230.0" y2="608.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="739.5" y1="375.2" x2="742.1" y2="380.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1191.2" y1="130.5" x2="1384.2" y2="872.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="707.4" y1="499.3" x2="388.5" y2="277.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="194.2" y1="790.9" x2="294.0" y2="455.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1150.4" y1="484.0" x2="1230.9" y2="820.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1476.2" y1="929.9" x2="1477.0" y2="410.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="793.9" y1="291.2" x2="1521.3" y2="914.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1539.9" y1="372.6" x2="1289.4" y2="639.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="697.8" y1="391.9" x2="925.7" y2="519.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="758.1" y1="326.1" x2="164.8" y2="263.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="800.0" y1="500.0" x2="800.0" y2="500.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="529.8" y1="464.1" x2="880.2" y2="408.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="529.8" y1="464.1" x2="614.1" y2="392.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="529.8" y1="464.1" x2="652.9" y2="626.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="742.8" y1="301.1" x2="282.3" y2="755.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="742.8" y1="301.1" x2="584.8" y2="352.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="742.8" y1="301.1" x2="1447.6" y2="178.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="742.8" y1="301.1" x2="460.8" y2="519.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="614.8" y1="456.2" x2="1516.7" y2="517.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1422.2" y1="824.5" x2="1125.7" y2="654.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1422.2" y1="824.5" x2="735.8" y2="464.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1422.2" y1="824.5" x2="1122.4" y2="246.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1422.2" y1="824.5" x2="1304.2" y2="877.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="265.2" y1="485.0" x2="162.7" y2="821.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="265.2" y1="485.0" x2="1090.7" y2="325.7" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="735.8" y1="464.5" x2="520.5" y2="474.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="735.8" y1="464.5" x2="723.5" y2="849.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1391.5" y1="780.6" x2="652.9" y2="626.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1391.5" y1="780.6" x2="529.8" y2="464.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1391.5" y1="780.6" x2="380.8" y2="758.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1391.5" y1="780.6" x2="289.8" y2="559.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="977.6" y1="396.3" x2="1480.8" y2="631.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="977.6" y1="396.3" x2="697.8" y2="391.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="977.6" y1="396.3" x2="820.7" y2="441.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="167.1" y1="594.0" x2="1215.8" y2="167.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="167.1" y1="594.0" x2="279.2" y2="557.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="977.6" y1="396.3" x2="788.4" y2="60.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="977.6" y1="396.3" x2="110.5" y2="177.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="977.6" y1="396.3" x2="430.6" y2="488.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="977.6" y1="396.3" x2="1193.4" y2="93.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1306.8" y1="707.8" x2="983.8" y2="624.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1148.1" y1="754.1" x2="1447.6" y2="178.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1129.5" y1="701.5" x2="1467.0" y2="253.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1387.5" y1="404.5" x2="132.4" y2="884.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="835.4" y1="453.2" x2="1129.4" y2="701.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="100.5" y1="384.1" x2="370.8" y2="543.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1157.8" y1="347.6" x2="977.6" y2="396.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="614.1" y1="392.5" x2="739.5" y2="375.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1523.7" y1="254.8" x2="134.6" y2="600.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1122.2" y1="514.5" x2="80.6" y2="870.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="220.7" y1="465.2" x2="110.5" y2="177.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1215.8" y1="167.6" x2="1139.5" y2="768.7" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="689.3" y1="225.0" x2="477.0" y2="598.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="487.0" y1="316.3" x2="532.8" y2="474.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1516.7" y1="517.5" x2="983.0" y2="663.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="983.8" y1="624.9" x2="1266.8" y2="111.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1177.3" y1="490.0" x2="279.2" y2="557.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="788.5" y1="499.5" x2="955.3" y2="857.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1364.1" y1="285.4" x2="1486.5" y2="706.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="965.4" y1="847.4" x2="1422.2" y2="824.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1169.5" y1="477.6" x2="265.8" y2="747.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1364.1" y1="285.4" x2="1285.7" y2="454.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="983.0" y1="663.0" x2="820.7" y2="441.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1159.6" y1="104.1" x2="1458.4" y2="590.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="532.8" y1="474.6" x2="110.5" y2="177.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1524.9" y1="297.9" x2="1113.4" y2="214.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1391.5" y1="780.6" x2="1105.2" y2="551.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="75.9" y1="595.1" x2="124.5" y2="152.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1122.4" y1="246.4" x2="1223.0" y2="638.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="614.1" y1="392.5" x2="1513.3" y2="391.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="983.8" y1="624.9" x2="477.0" y2="598.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="983.8" y1="624.9" x2="955.3" y2="857.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="983.8" y1="624.9" x2="965.4" y2="847.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="477.0" y1="598.4" x2="689.3" y2="225.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="477.0" y1="598.4" x2="630.7" y2="206.7" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="477.0" y1="598.4" x2="1364.1" y2="285.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1306.8" y1="707.8" x2="1516.7" y2="517.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1306.8" y1="707.8" x2="487.0" y2="316.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1215.8" y1="167.6" x2="1266.8" y2="111.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1516.7" y1="517.5" x2="788.5" y2="499.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="487.0" y1="316.3" x2="614.8" y2="456.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="983.0" y1="663.0" x2="532.8" y2="474.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="955.3" y1="857.8" x2="322.8" y2="547.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1364.1" y1="285.4" x2="1169.5" y2="477.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1486.5" y1="706.4" x2="983.0" y2="663.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1139.5" y1="768.7" x2="689.3" y2="225.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1266.8" y1="111.0" x2="614.8" y2="456.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="820.7" y1="441.3" x2="566.4" y2="454.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="983.0" y1="663.0" x2="955.3" y2="857.8" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="652.9" y1="626.3" x2="376.9" y2="402.6" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="584.8" y1="352.9" x2="707.4" y2="499.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1266.8" y1="111.0" x2="279.2" y2="557.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="697.8" y1="391.9" x2="566.4" y2="454.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1364.1" y1="285.4" x2="965.4" y2="847.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="134.6" y1="600.0" x2="707.4" y2="499.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="487.0" y1="316.3" x2="965.4" y2="847.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1494.2" y1="181.5" x2="1422.2" y2="824.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="608.2" y1="344.2" x2="1255.8" y2="386.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="274.0" y1="615.8" x2="1255.8" y2="386.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="843.5" y1="417.3" x2="393.1" y2="406.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1146.0" y1="154.9" x2="393.1" y2="406.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="159.6" y1="270.4" x2="393.1" y2="406.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1250.9" y1="474.9" x2="134.6" y2="600.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="781.6" y1="311.1" x2="1148.1" y2="754.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="183.7" y1="430.4" x2="1255.8" y2="386.3" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1534.5" y1="77.8" x2="265.2" y2="485.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="183.7" y1="430.4" x2="1480.8" y2="631.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1074.3" y1="197.6" x2="788.4" y2="60.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1476.8" y1="682.2" x2="1304.2" y2="877.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1105.4" y1="551.4" x2="793.9" y2="291.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1105.4" y1="551.4" x2="1447.6" y2="178.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="573.0" y1="575.3" x2="799.0" y2="660.4" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="647.5" y1="502.2" x2="162.7" y2="821.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="647.5" y1="502.2" x2="1122.2" y2="514.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1288.9" y1="253.4" x2="265.8" y2="747.1" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="1085.6" y1="517.2" x2="614.1" y2="392.5" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="598.7" y1="723.5" x2="289.8" y2="559.2" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="730.0" y1="465.6" x2="1467.0" y2="253.9" stroke="#333355" stroke-width="0.5"/>
|
||||
<line x1="800.0" y1="500.0" x2="167.1" y2="594.0" stroke="#333355" stroke-width="0.5"/>
|
||||
<circle cx="800.0" cy="500.0" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="805.0" y="503.0" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Sol</text>
|
||||
<circle cx="167.1" cy="594.0" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="172.1" y="597.0" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Tau Ceti</text>
|
||||
<circle cx="1384.2" cy="872.9" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="910.0" cy="420.0" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="183.7" cy="430.4" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="783.9" cy="796.6" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="567.1" cy="625.7" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="289.8" cy="559.2" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="820.7" cy="441.3" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="735.8" cy="464.5" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<text x="740.8" y="467.5" fill="#4488FF" font-size="7" font-family="monospace" opacity="0.7">Wolf 359</text>
|
||||
<circle cx="965.4" cy="847.4" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="970.4" y="850.4" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">ACB</text>
|
||||
<circle cx="1113.4" cy="214.0" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1135.7" cy="124.2" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="707.4" cy="499.3" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<text x="712.4" y="502.3" fill="#FF4444" font-size="7" font-family="monospace" opacity="0.7">GJ 393</text>
|
||||
<circle cx="279.2" cy="557.4" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="284.2" y="560.4" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Ran</text>
|
||||
<circle cx="1125.7" cy="654.2" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="608.2" cy="344.2" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="358.4" cy="464.8" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1079.4" cy="575.5" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1298.1" cy="485.3" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="668.5" cy="749.5" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1074.3" cy="197.6" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="484.4" cy="533.3" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1203.9" cy="610.8" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1476.8" cy="682.2" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="566.4" cy="454.5" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1090.7" cy="325.7" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="983.0" cy="663.0" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="988.0" y="666.0" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Tessera</text>
|
||||
<circle cx="170.9" cy="143.7" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1311.0" cy="656.6" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="376.9" cy="402.6" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1105.4" cy="551.4" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1476.2" cy="929.9" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="161.9" cy="605.3" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1090.7" cy="325.7" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1043.2" cy="862.0" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="406.4" cy="440.1" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="322.8" cy="547.2" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="327.8" y="550.2" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Keid</text>
|
||||
<circle cx="1062.4" cy="828.9" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="75.9" cy="595.1" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="835.4" cy="453.2" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="781.6" cy="754.6" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="237.6" cy="576.1" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="646.6" cy="472.1" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="65.6" cy="714.9" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="294.0" cy="455.0" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1473.6" cy="584.5" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="532.8" cy="474.6" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="537.8" y="477.6" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Parallax</text>
|
||||
<circle cx="960.0" cy="574.7" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="1120.4" cy="846.7" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="923.8" cy="616.0" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1148.1" cy="754.1" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="652.9" cy="626.3" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<text x="657.9" y="629.3" fill="#FF8800" font-size="7" font-family="monospace" opacity="0.7">GJ 357</text>
|
||||
<circle cx="441.5" cy="627.4" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="110.5" cy="177.8" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="1105.3" cy="551.1" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1457.8" cy="875.5" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="110.6" cy="473.6" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1019.6" cy="737.0" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="345.8" cy="205.6" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="263.6" cy="857.2" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="584.8" cy="352.9" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<text x="589.8" y="355.9" fill="#FF4444" font-size="7" font-family="monospace" opacity="0.7">GJ 1111</text>
|
||||
<circle cx="189.5" cy="674.3" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="393.1" cy="406.3" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="80.6" cy="870.1" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="1094.6" cy="315.0" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1534.5" cy="77.8" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="477.0" cy="598.4" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="482.0" y="601.4" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Sirius</text>
|
||||
<circle cx="1309.5" cy="758.9" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="66.8" cy="340.3" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1477.0" cy="410.6" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="940.8" cy="395.8" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="66.9" cy="546.6" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="124.5" cy="152.2" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1486.5" cy="706.4" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="1491.5" y="709.4" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Lacaille</text>
|
||||
<circle cx="1467.0" cy="253.9" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="361.2" cy="274.3" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="1458.4" cy="590.4" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="356.0" cy="599.6" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="264.0" cy="856.8" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1524.9" cy="297.9" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="520.5" cy="474.6" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="65.8" cy="245.5" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1196.5" cy="494.6" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="533.6" cy="524.4" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="162.7" cy="821.2" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="1077.5" cy="899.5" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1289.0" cy="253.4" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="709.1" cy="188.2" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="471.4" cy="817.9" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1285.7" cy="454.0" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1215.8" cy="167.6" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="1220.8" y="170.6" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Struve</text>
|
||||
<circle cx="830.9" cy="564.2" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="955.3" cy="857.8" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="960.3" y="860.8" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Proxima Centauri</text>
|
||||
<circle cx="1150.4" cy="484.0" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="611.3" cy="104.6" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="539.0" cy="345.9" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1214.1" cy="364.2" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1129.5" cy="701.5" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="386.0" cy="244.5" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="388.5" cy="277.8" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1034.2" cy="462.6" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="793.9" cy="291.2" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="109.8" cy="474.3" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="538.3" cy="484.0" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="398.1" cy="523.8" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="110.5" cy="177.8" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="374.5" cy="828.4" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="774.9" cy="689.3" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="401.2" cy="524.8" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="742.8" cy="301.1" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<text x="747.8" y="304.1" fill="#FF4444" font-size="7" font-family="monospace" opacity="0.7">Lalande 21185</text>
|
||||
<circle cx="1266.8" cy="111.0" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="1271.8" y="114.0" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Nova Roma</text>
|
||||
<circle cx="835.9" cy="270.7" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="697.8" cy="391.9" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<text x="702.8" y="394.9" fill="#FF4444" font-size="7" font-family="monospace" opacity="0.7">GJ 388</text>
|
||||
<circle cx="1139.5" cy="768.7" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="1144.5" y="771.7" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Meridian</text>
|
||||
<circle cx="1220.6" cy="524.6" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1290.4" cy="467.9" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1470.6" cy="544.1" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="788.5" cy="499.5" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="793.5" y="502.5" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Ross 128</text>
|
||||
<circle cx="1169.5" cy="477.6" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="1174.5" y="480.6" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Barnard's Star</text>
|
||||
<circle cx="1364.1" cy="285.4" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="1369.1" y="288.4" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Cygni B</text>
|
||||
<circle cx="758.1" cy="326.1" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="1145.9" cy="154.9" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="611.3" cy="104.6" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="764.8" cy="851.9" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1147.5" cy="118.4" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="652.6" cy="302.0" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1129.5" cy="701.5" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="86.4" cy="940.0" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1494.2" cy="181.5" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1061.8" cy="900.0" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="176.1" cy="630.7" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="1181.6" cy="287.0" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="424.8" cy="389.6" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="336.9" cy="380.3" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="134.6" cy="600.0" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<text x="139.6" y="603.0" fill="#FF4444" font-size="7" font-family="monospace" opacity="0.7">GJ 54.1</text>
|
||||
<circle cx="925.7" cy="519.0" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="274.0" cy="615.8" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="323.5" cy="804.9" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="487.0" cy="316.3" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="492.0" y="319.3" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Renaissance</text>
|
||||
<circle cx="919.2" cy="400.2" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1064.3" cy="551.3" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1230.9" cy="820.0" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1211.7" cy="622.9" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="380.8" cy="758.1" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="781.6" cy="311.1" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1184.4" cy="749.2" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1437.6" cy="806.7" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1521.3" cy="914.4" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="791.6" cy="494.1" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="1131.2" cy="320.8" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1338.8" cy="801.4" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="414.5" cy="630.6" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1191.2" cy="130.5" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="62.2" cy="351.2" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="687.4" cy="214.7" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="979.6" cy="396.0" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="875.1" cy="346.7" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="916.4" cy="222.2" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="800.0" cy="500.0" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1254.9" cy="761.1" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="1223.0" cy="638.6" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="758.1" cy="326.1" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="913.4" cy="351.8" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1422.2" cy="824.5" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<text x="1427.2" y="827.5" fill="#4488FF" font-size="7" font-family="monospace" opacity="0.7">Cairn</text>
|
||||
<circle cx="370.8" cy="543.2" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="254.6" cy="224.1" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="114.6" cy="675.4" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="614.8" cy="456.2" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="619.8" y="459.2" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Vargr</text>
|
||||
<circle cx="412.2" cy="433.6" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1350.1" cy="153.3" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1374.8" cy="723.4" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="573.0" cy="575.3" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="165.5" cy="389.7" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1523.7" cy="254.8" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="502.7" cy="286.6" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="1289.4" cy="639.2" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="959.1" cy="205.5" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1157.9" cy="827.5" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="841.1" cy="720.6" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1250.9" cy="474.9" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="630.7" cy="206.7" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="635.7" y="209.7" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Arbour</text>
|
||||
<circle cx="1243.6" cy="404.4" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1129.4" cy="701.5" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="883.2" cy="234.4" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="265.2" cy="485.0" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="1126.6" cy="653.9" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1447.6" cy="178.5" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="372.2" cy="602.1" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="441.1" cy="925.9" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1521.6" cy="472.3" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1136.5" cy="492.1" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="835.4" cy="453.2" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="844.0" cy="512.2" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="909.0" cy="809.4" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="529.8" cy="464.1" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="723.5" cy="849.4" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="709.0" cy="188.0" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1119.8" cy="257.6" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1447.6" cy="178.5" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="460.8" cy="519.9" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="727.2" cy="568.0" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="100.5" cy="384.1" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="739.5" cy="375.2" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="990.3" cy="235.1" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="800.0" cy="500.0" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="738.8" cy="275.9" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="660.0" cy="892.8" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="1441.7" cy="811.9" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="132.4" cy="884.6" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1122.4" cy="246.4" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="623.1" cy="629.0" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="977.6" cy="396.3" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<text x="982.6" y="399.3" fill="#FF4444" font-size="7" font-family="monospace" opacity="0.7">GJ 566B</text>
|
||||
<circle cx="689.3" cy="225.0" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="694.3" y="228.0" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Groombridge</text>
|
||||
<circle cx="1460.7" cy="671.5" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="283.2" cy="501.8" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="647.5" cy="502.2" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="881.8" cy="607.4" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="755.2" cy="606.4" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1387.5" cy="404.5" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1105.2" cy="551.0" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1521.0" cy="66.0" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="162.7" cy="821.2" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="218.9" cy="751.2" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="587.9" cy="681.8" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1391.5" cy="780.6" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<text x="1396.5" y="783.6" fill="#FF8800" font-size="7" font-family="monospace" opacity="0.7">GJ 832</text>
|
||||
<circle cx="166.7" cy="143.9" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="880.2" cy="408.0" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="220.7" cy="465.2" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="745.2" cy="258.5" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="761.5" cy="619.5" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1115.2" cy="532.6" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="799.0" cy="660.4" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="870.1" cy="386.6" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1531.2" cy="490.5" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="983.8" cy="624.9" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="988.8" y="627.9" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Bastion</text>
|
||||
<circle cx="977.6" cy="396.3" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<text x="982.6" y="399.3" fill="#44DD44" font-size="7" font-family="monospace" opacity="0.7">GJ 566A</text>
|
||||
<circle cx="714.3" cy="112.2" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="194.2" cy="790.9" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1122.4" cy="246.4" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="203.1" cy="650.5" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1288.9" cy="253.4" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="843.5" cy="417.3" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1146.2" cy="778.8" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1426.0" cy="361.0" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="944.3" cy="839.1" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="947.3" cy="336.9" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1480.8" cy="631.2" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1442.5" cy="603.4" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="745.0" cy="258.4" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="229.0" cy="226.3" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="614.1" cy="392.5" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="230.0" cy="608.9" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1516.7" cy="517.5" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="1521.7" y="520.5" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Kensho</text>
|
||||
<circle cx="614.1" cy="392.5" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="521.4" cy="610.1" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="369.6" cy="536.5" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1085.6" cy="517.2" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="349.6" cy="386.1" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1157.8" cy="347.6" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="914.1" cy="628.8" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1006.4" cy="547.6" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="873.2" cy="405.1" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1306.8" cy="707.8" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="1311.8" y="710.8" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Aurelius</text>
|
||||
<circle cx="1299.2" cy="470.2" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1159.6" cy="104.1" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="265.8" cy="747.1" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="750.8" cy="332.3" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="414.6" cy="630.7" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="787.3" cy="732.6" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="164.8" cy="263.6" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="411.4" cy="202.3" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="201.1" cy="310.9" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1304.2" cy="877.5" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="598.7" cy="723.5" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="130.3" cy="194.1" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="730.0" cy="465.6" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="374.8" cy="828.8" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="801.9" cy="563.0" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="78.9" cy="255.6" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="83.9" y="258.6" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Lu Ban</text>
|
||||
<circle cx="281.3" cy="777.3" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1072.9" cy="725.2" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="282.3" cy="755.2" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1044.5" cy="415.7" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1146.0" cy="154.9" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1255.8" cy="386.3" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="257.7" cy="667.6" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="742.1" cy="380.1" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1513.3" cy="391.6" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1122.2" cy="514.5" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="844.0" cy="512.2" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1539.9" cy="372.6" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="649.7" cy="212.4" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1341.9" cy="155.1" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1193.4" cy="93.6" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="533.5" cy="524.4" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="159.6" cy="270.4" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1177.3" cy="490.0" r="4" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="1182.3" y="493.0" fill="#FFD700" font-size="7" font-family="monospace" opacity="0.7">Prometheus</text>
|
||||
<circle cx="788.4" cy="60.0" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="257.7" cy="667.6" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="430.6" cy="488.8" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="1420" cy="30" r="5" fill="#FFD700"/>
|
||||
<text x="1430" y="34" fill="#FFD700" font-size="10" font-family="monospace">core</text>
|
||||
<circle cx="1420" cy="48" r="5" fill="#4488FF"/>
|
||||
<text x="1430" y="52" fill="#4488FF" font-size="10" font-family="monospace">north_reach</text>
|
||||
<circle cx="1420" cy="66" r="5" fill="#FF4444"/>
|
||||
<text x="1430" y="70" fill="#FF4444" font-size="10" font-family="monospace">south_reach</text>
|
||||
<circle cx="1420" cy="84" r="5" fill="#44DD44"/>
|
||||
<text x="1430" y="88" fill="#44DD44" font-size="10" font-family="monospace">east_reach</text>
|
||||
<circle cx="1420" cy="102" r="5" fill="#FF8800"/>
|
||||
<text x="1430" y="106" fill="#FF8800" font-size="10" font-family="monospace">west_reach</text>
|
||||
<circle cx="1420" cy="120" r="5" fill="#AA44FF"/>
|
||||
<text x="1430" y="124" fill="#AA44FF" font-size="10" font-family="monospace">deep_frontier</text>
|
||||
</svg>
|
||||
|
After Width: | Height: | Size: 54 KiB |
@@ -0,0 +1,692 @@
|
||||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 2400 1600" width="2400" height="1600">
|
||||
<rect width="2400" height="1600" fill="#0a0a1a"/>
|
||||
<style>text { pointer-events: none; }</style>
|
||||
<line x1="1877.8" y1="955.6" x2="1818.2" y2="813.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1877.8" y1="955.6" x2="1393.8" y2="642.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1494.5" y1="806.8" x2="2299.1" y2="713.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2299.1" y1="713.1" x2="974.2" y2="1025.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="974.2" y1="1025.8" x2="2300.6" y2="932.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2300.6" y1="932.3" x2="733.9" y2="885.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="733.9" y1="885.2" x2="1260.2" y2="220.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1260.2" y1="220.8" x2="2313.2" y2="856.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2313.2" y1="856.3" x2="1641.9" y2="1461.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1641.9" y1="1461.6" x2="1685.5" y2="1222.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1685.5" y1="1222.9" x2="2159.5" y2="541.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1070.4" y1="847.7" x2="2209.5" y2="1075.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2159.5" y1="541.4" x2="2168.9" y2="1170.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2168.9" y1="1170.3" x2="476.7" y2="1172.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="476.7" y1="1172.4" x2="623.4" y2="191.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="974.2" y1="1025.8" x2="1702.7" y2="1446.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="623.4" y1="191.3" x2="1895.2" y2="254.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1895.2" y1="254.2" x2="1151.3" y2="722.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1151.3" y1="722.8" x2="904.8" y2="1479.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="925.2" y1="325.9" x2="2273.9" y2="620.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2273.9" y1="620.2" x2="1381.9" y2="118.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="904.8" y1="1479.7" x2="427.6" y2="693.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="344.7" y1="695.0" x2="562.0" y2="201.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1386.6" y1="888.1" x2="1739.0" y2="1161.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1739.0" y1="1161.9" x2="155.8" y2="1073.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="647.1" y1="1438.8" x2="1892.7" y2="614.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1892.7" y1="614.6" x2="2294.8" y2="969.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1739.0" y1="1161.9" x2="2061.9" y2="710.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1642.8" y1="725.5" x2="888.4" y2="1481.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1358.5" y1="291.1" x2="2198.9" y2="481.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="888.4" y1="1481.3" x2="1088.0" y2="1507.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1088.0" y1="1507.7" x2="2115.1" y2="1223.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1528.7" y1="638.8" x2="2213.4" y2="542.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2213.4" y1="542.9" x2="2075.8" y2="382.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2075.8" y1="382.2" x2="1790.6" y2="261.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1774.0" y1="1111.0" x2="1483.9" y2="1166.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1790.6" y1="261.9" x2="606.7" y2="204.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2115.1" y1="1223.7" x2="937.2" y2="810.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="606.7" y1="204.2" x2="401.3" y2="840.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1199.3" y1="1513.4" x2="489.7" y2="634.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="489.7" y1="634.4" x2="953.1" y2="101.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="401.3" y1="840.0" x2="377.0" y2="293.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="953.1" y1="101.7" x2="378.5" y2="666.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="378.5" y1="666.5" x2="1874.3" y2="235.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1874.3" y1="235.1" x2="1945.4" y2="680.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1945.4" y1="680.6" x2="1269.4" y2="160.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="377.0" y1="293.0" x2="138.2" y2="1010.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1269.4" y1="160.7" x2="2120.5" y2="987.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="138.2" y1="1010.9" x2="370.9" y2="305.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="219.2" y1="506.3" x2="163.5" y2="605.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="100.2" y1="714.5" x2="487.3" y2="537.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1991.7" y1="659.3" x2="755.9" y2="1471.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1490.8" y1="341.5" x2="498.6" y2="742.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="706.0" y1="680.7" x2="1222.5" y2="1392.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="498.6" y1="742.8" x2="382.0" y2="331.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1222.5" y1="1392.9" x2="2220.2" y2="524.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="118.4" y1="983.8" x2="209.7" y2="502.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2220.2" y1="524.6" x2="1052.8" y2="321.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1052.8" y1="321.4" x2="1146.2" y2="1148.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="382.0" y1="331.1" x2="310.8" y2="343.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="209.7" y1="502.2" x2="1374.6" y2="1290.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1374.6" y1="1290.1" x2="1037.2" y2="1510.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="522.0" y1="977.8" x2="946.8" y2="1476.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="946.8" y1="1476.9" x2="1332.0" y2="1051.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1642.8" y1="725.5" x2="1441.6" y2="1012.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1146.2" y1="1148.1" x2="482.9" y2="1330.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1037.2" y1="1510.8" x2="1714.0" y2="1407.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1714.0" y1="1407.6" x2="1829.5" y2="747.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1441.6" y1="1012.7" x2="2033.6" y2="308.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1332.0" y1="1051.4" x2="464.4" y2="1360.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="482.9" y1="1330.9" x2="1135.9" y2="933.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1829.5" y1="747.0" x2="2047.3" y2="341.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="464.4" y1="1360.2" x2="171.2" y2="1093.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2257.9" y1="649.3" x2="1136.0" y2="153.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="791.8" y1="1475.0" x2="258.1" y2="783.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="258.1" y1="783.1" x2="1540.3" y2="656.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1540.3" y1="656.5" x2="750.3" y2="449.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="750.3" y1="449.9" x2="504.2" y2="919.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1558.0" y1="116.8" x2="285.6" y2="373.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="504.2" y1="919.3" x2="2106.3" y2="1237.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2106.3" y1="1237.3" x2="1832.9" y2="1256.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2033.6" y1="308.1" x2="537.9" y2="292.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1832.9" y1="1256.1" x2="1546.5" y2="119.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="640.5" y1="470.6" x2="1129.3" y2="814.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1129.3" y1="814.0" x2="235.6" y2="454.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="982.8" y1="1207.8" x2="1813.5" y2="935.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="129.1" y1="612.6" x2="87.8" y2="756.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="87.8" y1="756.5" x2="109.1" y2="684.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="537.9" y1="292.8" x2="1127.1" y2="423.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="109.1" y1="684.8" x2="491.1" y2="248.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2151.4" y1="1183.7" x2="2009.5" y2="1307.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2120.5" y1="987.2" x2="711.1" y2="1449.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="491.1" y1="248.7" x2="155.9" y2="521.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2245.7" y1="558.8" x2="1110.0" y2="92.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2047.3" y1="341.3" x2="1052.4" y2="414.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1040.0" y1="211.9" x2="706.6" y2="829.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1127.1" y1="423.0" x2="191.5" y2="1130.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="191.5" y1="1130.4" x2="356.8" y2="1253.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1052.4" y1="414.9" x2="2061.4" y2="1251.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="155.9" y1="521.5" x2="930.6" y2="1359.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1110.0" y1="92.5" x2="343.0" y2="889.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="343.0" y1="889.0" x2="1179.4" y2="855.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1179.4" y1="855.0" x2="86.3" y2="823.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="706.6" y1="829.3" x2="805.9" y2="209.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="930.6" y1="1359.7" x2="1224.2" y2="1498.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2061.4" y1="1251.5" x2="2097.3" y2="1241.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="805.9" y1="209.6" x2="99.7" y2="662.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="86.3" y1="823.1" x2="253.3" y2="1141.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="253.3" y1="1141.0" x2="732.4" y2="141.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="99.7" y1="662.2" x2="1151.2" y2="625.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="356.8" y1="1253.2" x2="97.7" y2="929.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="613.6" y1="1158.6" x2="1843.6" y2="699.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1224.2" y1="1498.9" x2="1475.8" y2="1408.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1475.8" y1="1408.8" x2="2266.0" y2="593.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="97.7" y1="929.3" x2="167.3" y2="1087.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="732.4" y1="141.3" x2="1770.6" y2="552.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2097.3" y1="1241.5" x2="1593.0" y2="160.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1770.6" y1="552.9" x2="673.6" y2="694.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1843.6" y1="699.4" x2="949.3" y2="885.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="167.3" y1="1087.5" x2="1233.0" y2="1503.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="711.1" y1="1449.9" x2="1628.8" y2="1281.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1813.5" y1="935.4" x2="1861.1" y2="223.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="949.3" y1="885.6" x2="1403.5" y2="1496.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2061.9" y1="710.0" x2="395.8" y2="1062.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1628.8" y1="1281.6" x2="570.8" y2="1404.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1540.3" y1="656.5" x2="713.5" y2="144.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1593.0" y1="160.7" x2="1264.9" y2="85.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1135.9" y1="933.0" x2="722.4" y2="1447.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1403.5" y1="1496.6" x2="803.0" y2="699.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="750.3" y1="449.9" x2="213.2" y2="614.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1169.2" y1="1519.3" x2="340.5" y2="1214.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="811.3" y1="464.8" x2="360.0" y2="1270.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1861.1" y1="223.7" x2="1199.7" y2="83.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="809.4" y1="989.5" x2="120.0" y2="966.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="722.4" y1="1447.6" x2="650.6" y2="1402.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="803.0" y1="699.3" x2="1292.8" y2="85.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1233.0" y1="1503.7" x2="714.5" y2="442.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1425.2" y1="456.2" x2="1840.9" y2="224.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1840.9" y1="224.4" x2="2289.5" y2="938.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1439.6" y1="1042.3" x2="812.7" y2="1001.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="110.3" y1="972.4" x2="1856.5" y2="892.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="120.0" y1="966.6" x2="1350.1" y2="1493.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="370.9" y1="305.9" x2="1425.7" y2="155.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1439.6" y1="1042.3" x2="2126.9" y2="482.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1840.9" y1="224.4" x2="1190.8" y2="636.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="340.5" y1="1214.8" x2="819.5" y2="1474.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1856.5" y1="892.3" x2="2318.9" y2="770.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2126.9" y1="482.2" x2="2250.1" y2="1056.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="387.9" y1="1315.0" x2="780.4" y2="1471.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="780.4" y1="1471.6" x2="1636.6" y2="869.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2318.9" y1="770.4" x2="2033.7" y2="1294.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2033.7" y1="1294.6" x2="850.5" y2="1445.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1644.7" y1="149.4" x2="1736.7" y2="825.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1190.8" y1="636.6" x2="2268.0" y2="610.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="213.2" y1="614.7" x2="1428.1" y2="1469.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1636.6" y1="869.2" x2="131.3" y2="1005.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1736.7" y1="825.4" x2="1061.9" y2="706.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1061.9" y1="706.9" x2="867.4" y2="116.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1199.7" y1="83.9" x2="1782.4" y2="181.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="102.5" y1="653.3" x2="489.7" y2="1343.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="867.4" y1="116.9" x2="822.0" y2="118.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2268.0" y1="610.5" x2="1807.8" y2="185.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1807.8" y1="185.7" x2="366.6" y2="336.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1350.1" y1="1493.8" x2="1019.8" y2="1505.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="489.7" y1="1343.5" x2="776.5" y2="776.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="366.6" y1="336.0" x2="1013.4" y2="948.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="822.0" y1="118.6" x2="1694.8" y2="973.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="520.0" y1="1068.5" x2="1589.9" y2="317.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1694.8" y1="973.5" x2="1331.5" y2="1502.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1013.4" y1="948.8" x2="1338.1" y2="100.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="131.3" y1="1005.8" x2="929.3" y2="1220.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1338.1" y1="100.6" x2="331.9" y2="372.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1921.2" y1="1366.2" x2="708.6" y2="754.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1019.8" y1="1505.3" x2="2315.6" y2="845.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="331.9" y1="372.2" x2="432.5" y2="556.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2033.7" y1="1294.6" x2="1204.3" y2="964.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2266.0" y1="598.0" x2="943.4" y2="99.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1204.3" y1="964.8" x2="2153.2" y2="438.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2012.0" y1="306.1" x2="2110.4" y2="392.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="943.4" y1="99.6" x2="962.2" y2="475.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="962.2" y1="475.0" x2="534.4" y2="228.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="534.4" y1="228.6" x2="563.3" y2="644.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2110.4" y1="392.6" x2="2205.8" y2="1112.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="563.3" y1="644.4" x2="643.0" y2="195.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="643.0" y1="195.1" x2="80.0" y2="847.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="432.5" y1="556.5" x2="392.6" y2="786.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="776.5" y1="776.0" x2="1248.7" y2="349.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1248.7" y1="349.8" x2="1779.2" y2="1259.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="432.5" y1="556.5" x2="1843.7" y2="759.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1303.3" y1="129.1" x2="2094.2" y2="933.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2205.8" y1="1112.4" x2="728.3" y2="514.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1779.2" y1="1259.9" x2="2265.5" y2="1030.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2094.2" y1="933.6" x2="1059.2" y2="100.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="80.0" y1="847.9" x2="562.6" y2="1373.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="728.3" y1="514.2" x2="1981.6" y2="274.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1061.9" y1="706.9" x2="1034.7" y2="838.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="728.3" y1="514.2" x2="110.5" y2="630.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1497.5" y1="104.4" x2="1429.3" y2="113.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="110.5" y1="630.8" x2="270.4" y2="1102.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1492.4" y1="1497.5" x2="1315.1" y2="1505.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1331.5" y1="1502.5" x2="100.0" y2="917.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1315.1" y1="1505.7" x2="1046.3" y2="993.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="643.0" y1="195.1" x2="1353.3" y2="125.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1275.2" y1="1306.4" x2="910.0" y2="849.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1981.6" y1="274.3" x2="2146.6" y2="1071.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2152.9" y1="1038.2" x2="2255.5" y2="992.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2255.5" y1="992.5" x2="1895.2" y2="1340.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1046.3" y1="993.3" x2="400.5" y2="1291.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="562.6" y1="1373.1" x2="1133.6" y2="1518.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="270.4" y1="1102.2" x2="1073.3" y2="1167.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1073.3" y1="1167.0" x2="991.9" y2="1049.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="400.5" y1="1291.2" x2="137.9" y2="550.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2146.6" y1="1071.2" x2="1312.5" y2="640.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1312.5" y1="640.9" x2="1082.7" y2="105.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="991.9" y1="1049.0" x2="1943.6" y2="264.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="714.5" y1="442.9" x2="1750.1" y2="179.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1082.3" y1="304.5" x2="1805.6" y2="1409.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1353.3" y1="125.0" x2="473.1" y2="249.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="962.2" y1="475.0" x2="1662.7" y2="145.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="100.0" y1="917.7" x2="242.2" y2="1164.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1429.3" y1="113.1" x2="1230.4" y2="80.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="910.0" y1="849.0" x2="2191.1" y2="457.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1497.5" y1="104.4" x2="1980.2" y2="289.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1082.7" y1="105.9" x2="1690.4" y2="159.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1636.6" y1="869.2" x2="1845.8" y2="1393.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2265.5" y1="1030.2" x2="2307.8" y2="905.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="673.6" y1="694.7" x2="844.7" y2="1483.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2171.8" y1="729.3" x2="344.7" y2="695.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2171.8" y1="729.3" x2="2003.2" y2="929.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2171.8" y1="729.3" x2="1892.7" y2="614.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="812.7" y1="1001.9" x2="1061.9" y2="706.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="812.7" y1="1001.9" x2="643.0" y2="195.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="812.7" y1="1001.9" x2="708.6" y2="754.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="812.7" y1="1001.9" x2="489.7" y2="1343.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2209.2" y1="1100.5" x2="1772.1" y2="1052.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1425.2" y1="456.2" x2="1338.1" y2="100.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1425.2" y1="456.2" x2="1046.3" y2="993.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1425.2" y1="456.2" x2="2318.9" y2="770.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1425.2" y1="456.2" x2="392.6" y2="786.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="811.3" y1="464.8" x2="1558.0" y2="116.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="811.3" y1="464.8" x2="2009.5" y2="1307.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1046.3" y1="993.3" x2="1073.3" y2="1167.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1046.3" y1="993.3" x2="850.5" y2="1445.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1386.6" y1="888.1" x2="1892.7" y2="614.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1386.6" y1="888.1" x2="2171.8" y2="729.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1386.6" y1="888.1" x2="1151.3" y2="722.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1386.6" y1="888.1" x2="487.3" y2="537.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="776.5" y1="776.0" x2="1034.7" y2="838.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="776.5" y1="776.0" x2="1636.6" y2="869.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="776.5" y1="776.0" x2="929.3" y2="1220.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1877.8" y1="955.6" x2="1952.2" y2="1331.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1877.8" y1="955.6" x2="1553.3" y2="263.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="171.2" y1="1093.5" x2="1151.2" y2="625.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="171.2" y1="1093.5" x2="640.5" y2="470.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="171.2" y1="1093.5" x2="213.2" y2="614.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="171.2" y1="1093.5" x2="235.6" y2="454.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1494.5" y1="806.8" x2="933.6" y2="1074.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="522.0" y1="977.8" x2="1129.3" y2="814.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1190.8" y1="636.6" x2="2153.2" y2="438.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1589.9" y1="317.5" x2="1736.7" y2="825.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2289.5" y1="938.2" x2="2033.7" y2="1294.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="819.5" y1="1474.5" x2="562.6" y2="1373.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2126.9" y1="482.2" x2="776.5" y2="776.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1204.3" y1="964.8" x2="1082.3" y2="304.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="563.3" y1="644.4" x2="1439.6" y2="1042.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1136.0" y1="153.3" x2="258.1" y2="783.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="99.7" y1="662.2" x2="640.5" y2="470.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1952.2" y1="1331.8" x2="2303.5" y2="893.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1430.2" y1="1323.8" x2="1818.2" y2="813.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1774.0" y1="1111.0" x2="1466.7" y2="858.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1772.1" y1="1052.2" x2="1184.6" y2="1303.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="933.6" y1="1074.4" x2="1070.4" y2="847.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2306.9" y1="733.9" x2="1553.3" y2="263.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="981.8" y1="197.1" x2="1459.9" y2="917.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1498.0" y1="930.3" x2="126.0" y2="600.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1393.8" y1="642.5" x2="1425.2" y2="456.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1733.7" y1="176.1" x2="1843.7" y2="759.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1498.0" y1="930.3" x2="867.4" y2="116.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1184.6" y1="1303.0" x2="929.3" y2="1220.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1688.7" y1="1453.1" x2="2266.0" y2="593.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1466.7" y1="858.9" x2="640.5" y2="470.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="270.4" y1="1102.2" x2="163.5" y2="605.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1386.6" y1="888.1" x2="755.9" y2="1471.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="805.9" y1="209.6" x2="1856.7" y2="390.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2318.9" y1="770.4" x2="1895.2" y2="254.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2003.2" y1="929.5" x2="780.4" y2="1471.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="933.6" y1="1074.4" x2="1818.2" y2="813.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="933.6" y1="1074.4" x2="1459.9" y2="917.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="933.6" y1="1074.4" x2="1393.8" y2="642.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1818.2" y1="813.2" x2="1430.2" y2="1323.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1818.2" y1="813.2" x2="1483.9" y2="1166.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1818.2" y1="813.2" x2="1498.0" y2="930.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1494.5" y1="806.8" x2="1772.1" y2="1052.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1494.5" y1="806.8" x2="1774.0" y2="1111.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1952.2" y1="1331.8" x2="1070.4" y2="847.7" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1772.1" y1="1052.2" x2="981.8" y2="197.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1774.0" y1="1111.0" x2="2209.2" y2="1100.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1184.6" y1="1303.0" x2="1466.7" y2="858.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1459.9" y1="917.4" x2="1962.8" y2="1307.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1498.0" y1="930.3" x2="1733.7" y2="176.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="126.0" y1="600.2" x2="1184.6" y2="1303.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2303.5" y1="893.8" x2="1430.2" y2="1323.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1070.4" y1="847.7" x2="2209.2" y2="1100.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="929.3" y1="1220.6" x2="2250.1" y2="1056.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1184.6" y1="1303.0" x2="1459.9" y2="917.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1892.7" y1="614.6" x2="1358.5" y2="291.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="643.0" y1="195.1" x2="962.2" y2="475.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1070.4" y1="847.7" x2="1553.3" y2="263.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1636.6" y1="869.2" x2="2250.1" y2="1056.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1498.0" y1="930.3" x2="1393.8" y2="642.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1439.6" y1="1042.3" x2="962.2" y2="475.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1774.0" y1="1111.0" x2="1393.8" y2="642.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1264.9" y1="85.6" x2="1425.2" y2="456.2" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="570.8" y1="1404.0" x2="1018.1" y2="1489.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="809.4" y1="989.5" x2="1018.1" y2="1489.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1199.3" y1="1513.4" x2="1881.1" y2="1371.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2245.7" y1="558.8" x2="1881.1" y2="1371.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="937.2" y1="810.9" x2="1881.1" y2="1371.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="650.6" y1="1402.5" x2="1439.6" y2="1042.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="310.8" y1="343.2" x2="522.0" y2="977.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1542.0" y1="1455.7" x2="1018.1" y2="1489.1" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="129.1" y1="612.6" x2="811.3" y2="464.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1542.0" y1="1455.7" x2="1034.7" y2="838.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="613.6" y1="1158.6" x2="1151.2" y2="625.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1303.3" y1="129.1" x2="392.6" y2="786.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1896.6" y1="405.5" x2="1497.5" y2="104.4" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1896.6" y1="405.5" x2="708.6" y2="754.9" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1528.7" y1="638.8" x2="2061.9" y2="710.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1604.7" y1="135.3" x2="1558.0" y2="116.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1604.7" y1="135.3" x2="1136.0" y2="153.3" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1275.2" y1="1306.4" x2="1843.7" y2="759.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="925.2" y1="325.9" x2="2003.2" y2="929.5" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="982.8" y1="1207.8" x2="487.3" y2="537.8" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="2152.9" y1="1038.2" x2="2153.2" y2="438.0" stroke="#222244" stroke-width="0.7"/>
|
||||
<line x1="1114.8" y1="1514.4" x2="1877.8" y2="955.6" stroke="#222244" stroke-width="0.7"/>
|
||||
<circle cx="1114.8" cy="1514.4" r="6" fill="#FFD700" opacity="1.0"/>
|
||||
<text x="1122.8" y="1517.4" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Sol</text>
|
||||
<circle cx="1877.8" cy="955.6" r="6" fill="#FFD700" opacity="1.0"/>
|
||||
<text x="1885.8" y="958.6" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Tau Ceti</text>
|
||||
<circle cx="473.1" cy="249.3" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="476.7" cy="1172.4" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1542.0" cy="1455.7" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="464.4" cy="1360.2" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="2012.0" cy="306.1" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="487.3" cy="537.8" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="929.3" cy="1220.6" r="4" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1046.3" cy="993.3" r="4" fill="#4488FF" opacity="0.4"/>
|
||||
<text x="1052.3" y="996.3" fill="#4488FF" font-size="7" font-family="monospace" opacity="0.60">Wolf 359</text>
|
||||
<circle cx="1393.8" cy="642.5" r="6" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="1401.8" y="645.5" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">ACB</text>
|
||||
<circle cx="163.5" cy="605.6" r="2.5" fill="#AA44FF" opacity="0.25"/>
|
||||
<circle cx="1441.6" cy="1012.7" r="2.5" fill="#AA44FF" opacity="0.4"/>
|
||||
<circle cx="962.2" cy="475.0" r="2.5" fill="#FF4444" opacity="0.4"/>
|
||||
<text x="966.7" y="478.0" fill="#FF4444" font-size="7" font-family="monospace" opacity="0.60">GJ 393</text>
|
||||
<circle cx="1553.3" cy="263.5" r="6" fill="#FFD700" opacity="1.0"/>
|
||||
<text x="1561.3" y="266.5" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Ran</text>
|
||||
<circle cx="1338.1" cy="100.6" r="4" fill="#4488FF" opacity="0.7"/>
|
||||
<circle cx="570.8" cy="1404.0" r="2.5" fill="#AA44FF" opacity="0.25"/>
|
||||
<circle cx="2094.2" cy="933.6" r="2.5" fill="#4488FF" opacity="0.55"/>
|
||||
<circle cx="623.4" cy="191.3" r="4" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="2213.4" cy="542.9" r="2.5" fill="#FF8800" opacity="0.4"/>
|
||||
<circle cx="100.2" cy="714.5" r="2.5" fill="#FF8800" opacity="1.0"/>
|
||||
<circle cx="613.6" cy="1158.6" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="991.9" cy="1049.0" r="2.5" fill="#4488FF" opacity="0.55"/>
|
||||
<circle cx="1312.5" cy="640.9" r="2.5" fill="#4488FF" opacity="0.55"/>
|
||||
<circle cx="1303.3" cy="129.1" r="4" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="2250.1" cy="1056.2" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="2009.5" cy="1307.8" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="1184.6" cy="1303.0" r="6" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="1192.6" y="1306.0" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Tessera</text>
|
||||
<circle cx="728.3" cy="514.2" r="2.5" fill="#4488FF" opacity="0.7"/>
|
||||
<circle cx="102.5" cy="653.3" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="1358.5" cy="291.1" r="2.5" fill="#FF8800" opacity="0.7"/>
|
||||
<circle cx="1896.6" cy="405.5" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="910.0" cy="849.0" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="400.5" cy="1291.2" r="4" fill="#4488FF" opacity="0.7"/>
|
||||
<circle cx="647.1" cy="1438.8" r="2.5" fill="#FF8800" opacity="0.7"/>
|
||||
<circle cx="1861.1" cy="223.7" r="2.5" fill="#FF8800" opacity="1.0"/>
|
||||
<circle cx="155.8" cy="1073.6" r="2.5" fill="#FF8800" opacity="0.55"/>
|
||||
<circle cx="1962.8" cy="1307.6" r="6" fill="#FFD700" opacity="1.0"/>
|
||||
<text x="1970.8" y="1310.6" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Keid</text>
|
||||
<circle cx="1782.4" cy="181.3" r="2.5" fill="#FF8800" opacity="0.7"/>
|
||||
<circle cx="805.9" cy="209.6" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="2289.5" cy="938.2" r="4" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="943.4" cy="99.6" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="382.0" cy="331.1" r="2.5" fill="#AA44FF" opacity="0.25"/>
|
||||
<circle cx="1945.4" cy="680.6" r="2.5" fill="#AA44FF" opacity="0.4"/>
|
||||
<circle cx="2299.1" cy="713.1" r="4" fill="#FF8800" opacity="0.55"/>
|
||||
<circle cx="242.2" cy="1164.7" r="2.5" fill="#FF4444" opacity="0.55"/>
|
||||
<circle cx="1856.5" cy="892.3" r="4" fill="#4488FF" opacity="0.7"/>
|
||||
<circle cx="1466.7" cy="858.9" r="6" fill="#FFD700" opacity="0.55"/>
|
||||
<text x="1474.7" y="861.9" fill="#FFD700" font-size="9" font-family="monospace" opacity="0.75">Parallax</text>
|
||||
<circle cx="750.3" cy="449.9" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="537.9" cy="292.8" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="110.3" cy="972.4" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="522.0" cy="977.8" r="2.5" fill="#44DD44" opacity="0.55"/>
|
||||
<circle cx="1892.7" cy="614.6" r="2.5" fill="#FF8800" opacity="0.55"/>
|
||||
<text x="1897.2" y="617.6" fill="#FF8800" font-size="7" font-family="monospace" opacity="0.75">GJ 357</text>
|
||||
<circle cx="904.8" cy="1479.7" r="2.5" fill="#FF8800" opacity="0.55"/>
|
||||
<circle cx="640.5" cy="470.6" r="4" fill="#44DD44" opacity="0.55"/>
|
||||
<circle cx="534.4" cy="228.6" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="2151.4" cy="1183.7" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="1331.5" cy="1502.5" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="1943.6" cy="264.6" r="2.5" fill="#4488FF" opacity="0.7"/>
|
||||
<circle cx="1540.3" cy="656.5" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="1832.9" cy="1256.1" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="643.0" cy="195.1" r="4" fill="#FF4444" opacity="0.7"/>
|
||||
<text x="649.0" y="198.1" fill="#FF4444" font-size="7" font-family="monospace" opacity="0.90">GJ 1111</text>
|
||||
<circle cx="949.3" cy="885.6" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="1881.1" cy="1371.0" r="2.5" fill="#AA44FF" opacity="0.25"/>
|
||||
<circle cx="258.1" cy="783.1" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="1059.2" cy="100.0" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="129.1" cy="612.6" r="2.5" fill="#44DD44" opacity="0.4"/>
|
||||
<circle cx="1818.2" cy="813.2" r="6" fill="#FFD700" opacity="1.0"/>
|
||||
<text x="1826.2" y="816.2" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Sirius</text>
|
||||
<circle cx="946.8" cy="1476.9" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="1037.2" cy="1510.8" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="2191.1" cy="457.6" r="2.5" fill="#4488FF" opacity="0.7"/>
|
||||
<circle cx="1040.0" cy="211.9" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="822.0" cy="118.6" r="4" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="1856.7" cy="390.3" r="2.5" fill="#AA44FF" opacity="0.7"/>
|
||||
<circle cx="126.0" cy="600.2" r="6" fill="#FFD700" opacity="1.0"/>
|
||||
<text x="134.0" y="603.2" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Lacaille</text>
|
||||
<circle cx="2153.2" cy="438.0" r="2.5" fill="#4488FF" opacity="0.4"/>
|
||||
<circle cx="109.1" cy="684.8" r="2.5" fill="#44DD44" opacity="0.25"/>
|
||||
<circle cx="2266.0" cy="593.5" r="4" fill="#44DD44" opacity="0.4"/>
|
||||
<circle cx="1350.1" cy="1493.8" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="482.9" cy="1330.9" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="270.4" cy="1102.2" r="2.5" fill="#4488FF" opacity="0.55"/>
|
||||
<circle cx="1073.3" cy="1167.0" r="4" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="520.0" cy="1068.5" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="606.7" cy="204.2" r="2.5" fill="#FF8800" opacity="0.25"/>
|
||||
<circle cx="97.7" cy="929.3" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="1558.0" cy="116.8" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="1381.9" cy="118.1" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1644.7" cy="149.4" r="4" fill="#FF4444" opacity="0.55"/>
|
||||
<circle cx="2075.8" cy="382.2" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="2033.6" cy="308.1" r="2.5" fill="#AA44FF" opacity="0.7"/>
|
||||
<circle cx="867.4" cy="116.9" r="4" fill="#FF4444" opacity="1.0"/>
|
||||
<circle cx="1952.2" cy="1331.8" r="6" fill="#FFD700" opacity="0.4"/>
|
||||
<text x="1960.2" y="1334.8" fill="#FFD700" font-size="9" font-family="monospace" opacity="0.60">Struve</text>
|
||||
<circle cx="340.5" cy="1214.8" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="1459.9" cy="917.4" r="6" fill="#FFD700" opacity="1.0"/>
|
||||
<text x="1467.9" y="920.4" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Proxima Centauri</text>
|
||||
<circle cx="1429.3" cy="113.1" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="360.0" cy="1270.6" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="2120.5" cy="987.2" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="331.9" cy="372.2" r="4" fill="#4488FF" opacity="0.4"/>
|
||||
<circle cx="1428.1" cy="1469.4" r="2.5" fill="#44DD44" opacity="0.4"/>
|
||||
<circle cx="2146.6" cy="1071.2" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1662.7" cy="145.9" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="711.1" cy="1449.9" r="2.5" fill="#AA44FF" opacity="0.4"/>
|
||||
<circle cx="1497.5" cy="104.4" r="2.5" fill="#FF4444" opacity="0.55"/>
|
||||
<circle cx="131.3" cy="1005.8" r="4" fill="#FF4444" opacity="0.25"/>
|
||||
<circle cx="137.9" cy="550.8" r="2.5" fill="#4488FF" opacity="0.7"/>
|
||||
<circle cx="1146.2" cy="1148.1" r="2.5" fill="#AA44FF" opacity="0.7"/>
|
||||
<circle cx="1840.9" cy="224.4" r="4" fill="#4488FF" opacity="0.55"/>
|
||||
<circle cx="1642.8" cy="725.5" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="706.6" cy="829.3" r="2.5" fill="#44DD44" opacity="0.25"/>
|
||||
<circle cx="1403.5" cy="1496.6" r="2.5" fill="#44DD44" opacity="0.55"/>
|
||||
<circle cx="812.7" cy="1001.9" r="4" fill="#FF4444" opacity="0.55"/>
|
||||
<text x="818.7" y="1004.9" fill="#FF4444" font-size="7" font-family="monospace" opacity="0.75">Lalande 21185</text>
|
||||
<circle cx="1070.4" cy="847.7" r="6" fill="#FFD700" opacity="1.0"/>
|
||||
<text x="1078.4" y="850.7" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Nova Roma</text>
|
||||
<circle cx="366.6" cy="336.0" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1636.6" cy="869.2" r="2.5" fill="#FF4444" opacity="0.25"/>
|
||||
<text x="1641.1" y="872.2" fill="#FF4444" font-size="7" font-family="monospace" opacity="0.45">GJ 388</text>
|
||||
<circle cx="2303.5" cy="893.8" r="6" fill="#FFD700" opacity="0.4"/>
|
||||
<text x="2311.5" y="896.8" fill="#FFD700" font-size="9" font-family="monospace" opacity="0.60">Meridian</text>
|
||||
<circle cx="1179.4" cy="855.0" r="2.5" fill="#AA44FF" opacity="0.25"/>
|
||||
<circle cx="1790.6" cy="261.9" r="2.5" fill="#FF8800" opacity="0.7"/>
|
||||
<circle cx="356.8" cy="1253.2" r="2.5" fill="#AA44FF" opacity="0.25"/>
|
||||
<circle cx="981.8" cy="197.1" r="6" fill="#FFD700" opacity="1.0"/>
|
||||
<text x="989.8" y="200.1" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Ross 128</text>
|
||||
<circle cx="1733.7" cy="176.1" r="6" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="1741.7" y="179.1" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Barnard's Star</text>
|
||||
<circle cx="1498.0" cy="930.3" r="6" fill="#FFD700" opacity="1.0"/>
|
||||
<text x="1506.0" y="933.3" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Cygni B</text>
|
||||
<circle cx="1843.6" cy="699.4" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="191.5" cy="1130.4" r="2.5" fill="#AA44FF" opacity="0.7"/>
|
||||
<circle cx="1133.6" cy="1518.0" r="2.5" fill="#FF4444" opacity="0.25"/>
|
||||
<circle cx="2115.1" cy="1223.7" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="803.0" cy="699.3" r="4" fill="#44DD44" opacity="0.25"/>
|
||||
<circle cx="1991.7" cy="659.3" r="2.5" fill="#AA44FF" opacity="0.4"/>
|
||||
<circle cx="1190.8" cy="636.6" r="4" fill="#4488FF" opacity="0.7"/>
|
||||
<circle cx="2300.6" cy="932.3" r="4" fill="#FF8800" opacity="0.7"/>
|
||||
<circle cx="1264.9" cy="85.6" r="4" fill="#AA44FF" opacity="0.4"/>
|
||||
<circle cx="1233.0" cy="1503.7" r="2.5" fill="#AA44FF" opacity="0.25"/>
|
||||
<circle cx="504.2" cy="919.3" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="2205.8" cy="1112.4" r="2.5" fill="#4488FF" opacity="0.55"/>
|
||||
<circle cx="1694.8" cy="973.5" r="2.5" fill="#FF4444" opacity="0.25"/>
|
||||
<circle cx="706.0" cy="680.7" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="1439.6" cy="1042.3" r="4" fill="#FF4444" opacity="0.7"/>
|
||||
<text x="1445.6" y="1045.3" fill="#FF4444" font-size="7" font-family="monospace" opacity="0.90">GJ 54.1</text>
|
||||
<circle cx="1845.8" cy="1393.7" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="809.4" cy="989.5" r="2.5" fill="#AA44FF" opacity="0.7"/>
|
||||
<circle cx="1628.8" cy="1281.6" r="2.5" fill="#AA44FF" opacity="0.25"/>
|
||||
<circle cx="1774.0" cy="1111.0" r="6" fill="#FFD700" opacity="1.0"/>
|
||||
<text x="1782.0" y="1114.0" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Renaissance</text>
|
||||
<circle cx="2198.9" cy="481.5" r="2.5" fill="#FF8800" opacity="0.7"/>
|
||||
<circle cx="953.1" cy="101.7" r="2.5" fill="#AA44FF" opacity="0.4"/>
|
||||
<circle cx="1230.4" cy="80.0" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="1829.5" cy="747.0" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="1151.3" cy="722.8" r="4" fill="#FF8800" opacity="0.55"/>
|
||||
<circle cx="310.8" cy="343.2" r="2.5" fill="#AA44FF" opacity="0.25"/>
|
||||
<circle cx="2220.2" cy="524.6" r="2.5" fill="#AA44FF" opacity="0.7"/>
|
||||
<circle cx="378.5" cy="666.5" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="1980.2" cy="289.9" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="1546.5" cy="119.2" r="2.5" fill="#44DD44" opacity="0.4"/>
|
||||
<circle cx="86.3" cy="823.1" r="2.5" fill="#AA44FF" opacity="0.4"/>
|
||||
<circle cx="1813.5" cy="935.4" r="2.5" fill="#FF8800" opacity="0.55"/>
|
||||
<circle cx="1492.4" cy="1497.5" r="2.5" fill="#4488FF" opacity="0.7"/>
|
||||
<circle cx="1353.3" cy="125.0" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="2047.3" cy="341.3" r="2.5" fill="#AA44FF" opacity="0.7"/>
|
||||
<circle cx="1199.7" cy="83.9" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="387.9" cy="1315.0" r="2.5" fill="#FF4444" opacity="0.55"/>
|
||||
<circle cx="1739.0" cy="1161.9" r="2.5" fill="#FF8800" opacity="0.7"/>
|
||||
<circle cx="1110.0" cy="92.5" r="2.5" fill="#AA44FF" opacity="0.7"/>
|
||||
<circle cx="673.6" cy="694.7" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1224.2" cy="1498.9" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="1895.2" cy="254.2" r="4" fill="#FF8800" opacity="0.4"/>
|
||||
<circle cx="2265.5" cy="1030.2" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="1714.0" cy="1407.6" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1425.2" cy="456.2" r="4" fill="#4488FF" opacity="0.25"/>
|
||||
<text x="1431.2" y="459.2" fill="#4488FF" font-size="7" font-family="monospace" opacity="0.45">Cairn</text>
|
||||
<circle cx="562.6" cy="1373.1" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="155.9" cy="521.5" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="377.0" cy="293.0" r="2.5" fill="#FF8800" opacity="0.7"/>
|
||||
<circle cx="2209.2" cy="1100.5" r="6" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="2217.2" y="1103.5" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Vargr</text>
|
||||
<circle cx="1248.7" cy="349.8" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="427.6" cy="693.1" r="2.5" fill="#FF8800" opacity="0.55"/>
|
||||
<circle cx="432.5" cy="556.5" r="4" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1528.7" cy="638.8" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1593.0" cy="160.7" r="4" fill="#AA44FF" opacity="0.4"/>
|
||||
<circle cx="563.3" cy="644.4" r="2.5" fill="#FF4444" opacity="0.55"/>
|
||||
<circle cx="930.6" cy="1359.7" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="1690.4" cy="159.5" r="2.5" fill="#4488FF" opacity="0.7"/>
|
||||
<circle cx="118.4" cy="983.8" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="80.0" cy="847.9" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="2313.2" cy="856.3" r="2.5" fill="#FF8800" opacity="0.4"/>
|
||||
<circle cx="650.6" cy="1402.5" r="2.5" fill="#AA44FF" opacity="0.7"/>
|
||||
<circle cx="1483.9" cy="1166.5" r="6" fill="#FFD700" opacity="1.0"/>
|
||||
<text x="1491.9" y="1169.5" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Arbour</text>
|
||||
<circle cx="2273.9" cy="620.2" r="2.5" fill="#FF8800" opacity="1.0"/>
|
||||
<circle cx="2033.7" cy="1294.6" r="4" fill="#4488FF" opacity="0.7"/>
|
||||
<circle cx="1052.4" cy="414.9" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="811.3" cy="464.8" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="974.2" cy="1025.8" r="4" fill="#FF8800" opacity="0.7"/>
|
||||
<circle cx="708.6" cy="754.9" r="4" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1807.8" cy="185.7" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="2159.5" cy="541.4" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="343.0" cy="889.0" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="1315.1" cy="1505.7" r="4" fill="#4488FF" opacity="0.55"/>
|
||||
<circle cx="1779.2" cy="1259.9" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="491.1" cy="248.7" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="1374.6" cy="1290.1" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="2171.8" cy="729.3" r="2.5" fill="#FF8800" opacity="0.25"/>
|
||||
<circle cx="850.5" cy="1445.2" r="4" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1019.8" cy="1505.3" r="2.5" fill="#AA44FF" opacity="0.25"/>
|
||||
<circle cx="2268.0" cy="610.5" r="2.5" fill="#4488FF" opacity="0.7"/>
|
||||
<circle cx="1129.3" cy="814.0" r="4" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="489.7" cy="1343.5" r="4" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="1013.4" cy="948.8" r="4" fill="#4488FF" opacity="0.7"/>
|
||||
<circle cx="819.5" cy="1474.5" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="1082.3" cy="304.5" r="2.5" fill="#4488FF" opacity="1.0"/>
|
||||
<circle cx="1981.6" cy="274.3" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="844.7" cy="1483.7" r="2.5" fill="#AA44FF" opacity="0.7"/>
|
||||
<circle cx="2315.6" cy="845.3" r="2.5" fill="#AA44FF" opacity="0.4"/>
|
||||
<circle cx="1332.0" cy="1051.4" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="209.7" cy="502.2" r="2.5" fill="#AA44FF" opacity="0.7"/>
|
||||
<circle cx="1736.7" cy="825.4" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="2061.4" cy="1251.5" r="2.5" fill="#AA44FF" opacity="0.4"/>
|
||||
<circle cx="87.8" cy="756.5" r="2.5" fill="#44DD44" opacity="0.4"/>
|
||||
<circle cx="776.5" cy="776.0" r="4" fill="#FF4444" opacity="0.85"/>
|
||||
<text x="782.5" y="779.0" fill="#FF4444" font-size="7" font-family="monospace" opacity="1.00">GJ 566B</text>
|
||||
<circle cx="1430.2" cy="1323.8" r="6" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="1438.2" y="1326.8" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Groombridge</text>
|
||||
<circle cx="1052.8" cy="321.4" r="2.5" fill="#AA44FF" opacity="0.7"/>
|
||||
<circle cx="253.3" cy="1141.0" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="1604.7" cy="135.3" r="2.5" fill="#44DD44" opacity="0.55"/>
|
||||
<circle cx="733.9" cy="885.2" r="2.5" fill="#FF8800" opacity="0.7"/>
|
||||
<circle cx="167.3" cy="1087.5" r="2.5" fill="#AA44FF" opacity="0.7"/>
|
||||
<circle cx="1589.9" cy="317.5" r="2.5" fill="#FF4444" opacity="0.4"/>
|
||||
<circle cx="755.9" cy="1471.1" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="489.7" cy="634.4" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="1702.7" cy="1446.1" r="4" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="2294.8" cy="969.4" r="2.5" fill="#AA44FF" opacity="0.4"/>
|
||||
<circle cx="1269.4" cy="160.7" r="2.5" fill="#AA44FF" opacity="0.4"/>
|
||||
<circle cx="1386.6" cy="888.1" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<text x="1391.1" y="891.1" fill="#FF8800" font-size="7" font-family="monospace" opacity="1.00">GJ 832</text>
|
||||
<circle cx="1088.0" cy="1507.7" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="344.7" cy="695.0" r="2.5" fill="#FF8800" opacity="0.7"/>
|
||||
<circle cx="99.7" cy="662.2" r="4" fill="#44DD44" opacity="0.4"/>
|
||||
<circle cx="285.6" cy="373.6" r="4" fill="#44DD44" opacity="0.55"/>
|
||||
<circle cx="120.0" cy="966.6" r="2.5" fill="#AA44FF" opacity="0.25"/>
|
||||
<circle cx="2255.5" cy="992.5" r="2.5" fill="#4488FF" opacity="0.7"/>
|
||||
<circle cx="2061.9" cy="710.0" r="2.5" fill="#FF8800" opacity="0.55"/>
|
||||
<circle cx="722.4" cy="1447.6" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="791.8" cy="1475.0" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="933.6" cy="1074.4" r="6" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="941.6" y="1077.4" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Bastion</text>
|
||||
<circle cx="171.2" cy="1093.5" r="4" fill="#44DD44" opacity="0.7"/>
|
||||
<text x="177.2" y="1096.5" fill="#44DD44" font-size="7" font-family="monospace" opacity="0.90">GJ 566A</text>
|
||||
<circle cx="1169.2" cy="1519.3" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="100.0" cy="917.7" r="2.5" fill="#FF4444" opacity="0.25"/>
|
||||
<circle cx="2318.9" cy="770.4" r="4" fill="#4488FF" opacity="0.55"/>
|
||||
<circle cx="1895.2" cy="1340.8" r="2.5" fill="#4488FF" opacity="0.7"/>
|
||||
<circle cx="1275.2" cy="1306.4" r="4" fill="#4488FF" opacity="0.4"/>
|
||||
<circle cx="1199.3" cy="1513.4" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="110.5" cy="630.8" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="2106.3" cy="1237.3" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="1685.5" cy="1222.9" r="2.5" fill="#FF8800" opacity="0.55"/>
|
||||
<circle cx="714.5" cy="442.9" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="1034.7" cy="838.9" r="2.5" fill="#FF4444" opacity="0.85"/>
|
||||
<circle cx="1292.8" cy="85.2" r="4" fill="#44DD44" opacity="0.55"/>
|
||||
<circle cx="1921.2" cy="1366.2" r="4" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="2257.9" cy="649.3" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="1204.3" cy="964.8" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1750.1" cy="179.1" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="1772.1" cy="1052.2" r="6" fill="#FFD700" opacity="1.0"/>
|
||||
<text x="1780.1" y="1055.2" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Kensho</text>
|
||||
<circle cx="2003.2" cy="929.5" r="2.5" fill="#FF8800" opacity="0.7"/>
|
||||
<circle cx="1490.8" cy="341.5" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="2097.3" cy="1241.5" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="925.2" cy="325.9" r="2.5" fill="#FF8800" opacity="0.7"/>
|
||||
<circle cx="888.4" cy="1481.3" r="2.5" fill="#AA44FF" opacity="0.7"/>
|
||||
<circle cx="2126.9" cy="482.2" r="2.5" fill="#FF4444" opacity="0.25"/>
|
||||
<circle cx="1425.7" cy="155.9" r="2.5" fill="#FF8800" opacity="0.7"/>
|
||||
<circle cx="2168.9" cy="1170.3" r="2.5" fill="#FF8800" opacity="0.4"/>
|
||||
<circle cx="1770.6" cy="552.9" r="2.5" fill="#AA44FF" opacity="0.4"/>
|
||||
<circle cx="1494.5" cy="806.8" r="6" fill="#FFD700" opacity="1.0"/>
|
||||
<text x="1502.5" y="809.8" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Aurelius</text>
|
||||
<circle cx="395.8" cy="1062.2" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1688.7" cy="1453.1" r="4" fill="#44DD44" opacity="0.25"/>
|
||||
<text x="1694.7" y="1456.1" fill="#44DD44" font-size="7" font-family="monospace" opacity="0.45">1221-DXP9</text>
|
||||
<circle cx="1843.7" cy="759.8" r="4" fill="#4488FF" opacity="0.7"/>
|
||||
<circle cx="1641.9" cy="1461.6" r="2.5" fill="#FF8800" opacity="0.4"/>
|
||||
<circle cx="2110.4" cy="392.6" r="2.5" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="1260.2" cy="220.8" r="2.5" fill="#FF8800" opacity="0.55"/>
|
||||
<circle cx="2307.8" cy="905.9" r="2.5" fill="#FF4444" opacity="0.4"/>
|
||||
<circle cx="498.6" cy="742.8" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="1135.9" cy="933.0" r="2.5" fill="#AA44FF" opacity="0.25"/>
|
||||
<circle cx="392.6" cy="786.5" r="4" fill="#4488FF" opacity="0.85"/>
|
||||
<circle cx="982.8" cy="1207.8" r="2.5" fill="#FF8800" opacity="0.7"/>
|
||||
<circle cx="1475.8" cy="1408.8" r="4" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="2152.9" cy="1038.2" r="2.5" fill="#4488FF" opacity="0.7"/>
|
||||
<circle cx="2266.0" cy="598.0" r="2.5" fill="#FF4444" opacity="0.55"/>
|
||||
<circle cx="562.0" cy="201.0" r="2.5" fill="#FF8800" opacity="0.7"/>
|
||||
<circle cx="2209.5" cy="1075.3" r="6" fill="#FFD700" opacity="0.85"/>
|
||||
<text x="2217.5" y="1078.3" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Lu Ban</text>
|
||||
<circle cx="1874.3" cy="235.1" r="2.5" fill="#AA44FF" opacity="0.7"/>
|
||||
<circle cx="713.5" cy="144.2" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="1061.9" cy="706.9" r="4" fill="#FF4444" opacity="0.25"/>
|
||||
<circle cx="219.2" cy="506.3" r="2.5" fill="#AA44FF" opacity="0.4"/>
|
||||
<circle cx="2245.7" cy="558.8" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="1018.1" cy="1489.1" r="2.5" fill="#AA44FF" opacity="0.85"/>
|
||||
<circle cx="401.3" cy="840.0" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="1805.6" cy="1409.0" r="2.5" fill="#4488FF" opacity="0.7"/>
|
||||
<circle cx="780.4" cy="1471.6" r="2.5" fill="#FF4444" opacity="0.7"/>
|
||||
<circle cx="1136.0" cy="153.3" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="1222.5" cy="1392.9" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="1082.7" cy="105.9" r="2.5" fill="#4488FF" opacity="0.55"/>
|
||||
<circle cx="1127.1" cy="423.0" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="370.9" cy="305.9" r="2.5" fill="#FF8800" opacity="0.4"/>
|
||||
<circle cx="235.6" cy="454.4" r="2.5" fill="#44DD44" opacity="0.7"/>
|
||||
<circle cx="138.2" cy="1010.9" r="2.5" fill="#FF8800" opacity="0.85"/>
|
||||
<circle cx="937.2" cy="810.9" r="2.5" fill="#AA44FF" opacity="0.7"/>
|
||||
<circle cx="2306.9" cy="733.9" r="6" fill="#FFD700" opacity="1.0"/>
|
||||
<text x="2314.9" y="736.9" fill="#FFD700" font-size="9" font-family="monospace" opacity="1.00">Prometheus</text>
|
||||
<circle cx="1151.2" cy="625.8" r="2.5" fill="#44DD44" opacity="0.85"/>
|
||||
<circle cx="732.4" cy="141.3" r="2.5" fill="#AA44FF" opacity="0.55"/>
|
||||
<circle cx="213.2" cy="614.7" r="2.5" fill="#44DD44" opacity="1.0"/>
|
||||
<text x="2180" y="30" fill="#888" font-size="12" font-family="monospace">SECTORS</text>
|
||||
<circle cx="2180" cy="40" r="5" fill="#FFD700"/>
|
||||
<text x="2192" y="44" fill="#FFD700" font-size="10" font-family="monospace">core</text>
|
||||
<circle cx="2180" cy="60" r="5" fill="#4488FF"/>
|
||||
<text x="2192" y="64" fill="#4488FF" font-size="10" font-family="monospace">north_reach</text>
|
||||
<circle cx="2180" cy="80" r="5" fill="#FF4444"/>
|
||||
<text x="2192" y="84" fill="#FF4444" font-size="10" font-family="monospace">south_reach</text>
|
||||
<circle cx="2180" cy="100" r="5" fill="#44DD44"/>
|
||||
<text x="2192" y="104" fill="#44DD44" font-size="10" font-family="monospace">east_reach</text>
|
||||
<circle cx="2180" cy="120" r="5" fill="#FF8800"/>
|
||||
<text x="2192" y="124" fill="#FF8800" font-size="10" font-family="monospace">west_reach</text>
|
||||
<circle cx="2180" cy="140" r="5" fill="#AA44FF"/>
|
||||
<text x="2192" y="144" fill="#AA44FF" font-size="10" font-family="monospace">deep_frontier</text>
|
||||
<text x="2180" y="175" fill="#888" font-size="12" font-family="monospace">OPACITY = SETTLEMENT WAVE</text>
|
||||
<text x="2180" y="191" fill="#666" font-size="9" font-family="monospace">bright = early · dim = recent/unsettled</text>
|
||||
</svg>
|
||||
|
After Width: | Height: | Size: 55 KiB |
@@ -0,0 +1,57 @@
|
||||
# GJ 6711 Workshop — Araminta's Brief (Visual Design)
|
||||
|
||||
## Light Environment
|
||||
|
||||
K-type amber light. Primary palette anchor: `#d4920a` (warm amber). The doubled-light environment (direct starlight + gas giant reflection) means the lighting model needs to handle two light sources that don't behave like a binary star system. The reflected light is diffuse, slightly shifted in spectrum, and comes from a source that moves relative to the primary.
|
||||
|
||||
### Practical Effect
|
||||
- Shadows are softer than they should be — never fully crisp
|
||||
- Color temperature shifts subtly as the gas giant's position changes
|
||||
- Interior spaces that block the reflected light feel noticeably different from exterior spaces
|
||||
- The effect is below conscious threshold for most viewers on first encounter; it accumulates
|
||||
|
||||
## Two Architectural Modes
|
||||
|
||||
The settlement shows two distinct construction periods in visible tension:
|
||||
|
||||
### Mode 1 — Founding Era (Heavy)
|
||||
- Dense, bunker-like construction. Over-engineered for the actual environmental conditions.
|
||||
- Materials: local stone and early-fabrication composites. Heavy walls, small windows, low ceilings.
|
||||
- Aesthetic: functional to the point of severity. The founding settlers built like they expected to need shelter from something specific.
|
||||
- Color palette: dark greys, weathered stone tones (`#4a4a4a`, `#6b6357`, `#3d3d3d`)
|
||||
|
||||
### Mode 2 — Incremental Additions (Standard)
|
||||
- Standard Reach industrial construction. Prefab panels, modular connections, adequate but unremarkable.
|
||||
- Added over three centuries as the community grew beyond the founding structures.
|
||||
- Color palette: standard Reach industrial (`#7a8b7a`, `#8b8b7a`, `#6b7a6b`)
|
||||
|
||||
### Interface Seams
|
||||
Where Mode 1 and Mode 2 meet, the construction joints are visible and sometimes awkward. The founding structures weren't designed to be extended. The extensions don't quite match the originals. These seams are the most visually distinctive feature of Stillpoint's built environment.
|
||||
|
||||
Interface seam palette: exposed fasteners, mismatched panel edges, visible sealant lines (`#5a5a4a`, `#8b7a6b`)
|
||||
|
||||
## Scale Miscalibrations
|
||||
|
||||
Doors are slightly too tall. Not dramatically — perhaps 10-15% taller than standard Reach construction. Ceilings in the Mode 1 structures follow the same pattern. This is subtle enough that most players won't consciously notice it, but it contributes to the perceptual unease.
|
||||
|
||||
Whether this reflects the founding settlers' construction preferences, the influence of whatever they found, or accommodation for something not human-sized is left unresolved.
|
||||
|
||||
## Directionality Inconsistency
|
||||
|
||||
Most settlements have a center of gravity — a main square, a primary corridor, a hub. Stillpoint doesn't. The settlement layout has multiple competing centers. Paths between locations are rarely the most direct route. The overall effect is a place that doesn't orient you — you can navigate it, but you can't hold a complete mental map of it.
|
||||
|
||||
## Threshold Markings
|
||||
|
||||
The Mode 1 structures have markings at doorways and corridor junctions. These markings are consistent in style but don't correspond to any current function. They're not wayfinding — the locals don't reference them. They're not decorative — they're too systematic. They're just there, part of the founding-era construction, serving a purpose that either no longer applies or was never understood by the people who live with them.
|
||||
|
||||
## Exterior Palette Summary
|
||||
|
||||
| Element | Hex | Description |
|
||||
|---------|-----|-------------|
|
||||
| Primary light | `#d4920a` | K-type amber, dominant |
|
||||
| Reflected light | `#c4a040` | Gas giant reflection, diffuse |
|
||||
| Sky | `#2a1a0a` to `#4a3020` | Dark amber gradient |
|
||||
| Mode 1 stone | `#4a4a4a` | Weathered founding-era |
|
||||
| Mode 2 panel | `#7a8b7a` | Standard Reach industrial |
|
||||
| Seam detail | `#5a5a4a` | Interface joints |
|
||||
| Ground | `#3a3020` | Local terrain, dark amber |
|
||||
@@ -0,0 +1,42 @@
|
||||
# GJ 6711 Workshop — Miri's Brief (Worldbuilding)
|
||||
|
||||
## Proposed Name: Stillpoint
|
||||
|
||||
## Physical Concept
|
||||
|
||||
Habitable moon orbiting a gas giant. This creates **doubled light** — direct starlight from the K-type primary plus reflected light from the gas giant's upper atmosphere. The effect is subtle but persistent: light comes from the wrong number of directions. Shadows don't quite behave. Newcomers experience perceptual miscalibration — nothing is wrong, exactly, but the visual environment doesn't settle into familiarity the way other systems do.
|
||||
|
||||
The gas giant itself is visually dominant in the sky. It is always there. The locals have lived with it long enough that they don't notice it; visitors can't stop noticing it.
|
||||
|
||||
## Population and Settlement
|
||||
|
||||
~4,000–8,000 people. Wave_3 settlement (roughly 300 years ago). The founding group came here deliberately — they were seeking something, not fleeing something. What they were seeking is the central unanswered question.
|
||||
|
||||
The community is self-sustaining but not prosperous. Agricultural base adequate for local consumption. No significant exports. The economy that exists serves the community that exists, and neither has grown substantially in three centuries.
|
||||
|
||||
## The Adams & Ford Problem
|
||||
|
||||
Three correspondents have been assigned to write the Stillpoint entry for the Adams & Ford Guide over the system's history:
|
||||
|
||||
1. **First correspondent** (early period): Arrived, spent the standard assessment period, departed. Filed a draft that was returned for revision. Revised it. Returned again. The entry was never published. The correspondent's notes, recovered later, describe the difficulty not as lack of material but as a problem of description — the system resists summary.
|
||||
|
||||
2. **Second correspondent** (middle period): Stayed longer than standard. Produced a draft that the editorial board found "technically complete but somehow uninformative." It described everything accurately and conveyed nothing. Filed as reference material, never published.
|
||||
|
||||
3. **Third correspondent** (recent): Arrived approximately 15 years ago. Has not left. Has not filed a draft. Responds to editorial queries with updates that are always "nearly complete." Has integrated into the community to a degree that raises questions about whether the entry will ever be written.
|
||||
|
||||
## Veil Institute Interest
|
||||
|
||||
The Institute has classified access to something here — the classification level is high enough that the existence of the classification is itself not widely known. A researcher was assigned a 3-year posting. They are now in year 6. Their reports are filed on schedule but have become increasingly abstract.
|
||||
|
||||
The Institute maintains a research station at GJ 7547 (one hop back, the only adjacent system). This station is the closest official Institute presence. Whether it exists to study GJ 6711 or for independent reasons is a question that depends on who you ask.
|
||||
|
||||
## Four Possible Answers (None Resolvable)
|
||||
|
||||
What the gate builders saw here — what made this location significant enough to place a gate at hop 23:
|
||||
|
||||
1. **Astronomical**: Something about the K-type star, the gas giant, or the moon's orbital mechanics that has significance in the gate builders' framework but not in human science.
|
||||
2. **Geological**: Something in or under the moon's surface. The founding settlers may have found evidence of this. The sealed sections of the community's early records may relate to this.
|
||||
3. **Perceptual**: The doubled-light environment produces an effect that the gate builders valued or required — the system was chosen for what it does to observers, not for what it contains.
|
||||
4. **Topological**: The gate here connects to something that isn't another gate in the human-accessible network. The dead-end topology isn't a dead end for the builders.
|
||||
|
||||
The game should never confirm which (if any) of these is correct. Information accumulates; resolution doesn't.
|
||||
@@ -0,0 +1,44 @@
|
||||
# GJ 6711 Workshop — Nigel's Brief (Replayability & Sandbox)
|
||||
|
||||
## Core Mechanic: "The Picture Won't Close"
|
||||
|
||||
Stillpoint's replayability comes from a mechanic that inverts the normal information-gathering loop. In most systems, the player collects information until they have enough to understand the situation and act on it. At Stillpoint, information accumulates but the picture never resolves. The player's understanding grows without ever reaching completion.
|
||||
|
||||
This is not a broken quest or missing content — it's the designed experience. The system teaches the player that some things in the Reach resist the detective-game framework that works everywhere else.
|
||||
|
||||
## Seed-Variable Atmospheric Archetypes
|
||||
|
||||
Each playthrough seeds Stillpoint with one of several atmospheric profiles. These aren't story changes — they're tonal shifts that make the system feel different without changing the facts:
|
||||
|
||||
1. **Warmth-without-origin**: Everything feels slightly warmer than it should. Not temperature — social warmth. People are welcoming in a way that doesn't quite have a source. It's not performed hospitality. It's something else.
|
||||
|
||||
2. **Stillness-without-tension**: The absence of urgency. Deep-frontier systems are usually tense about supply, isolation, something. Stillpoint isn't. The lack of tension is itself unsettling.
|
||||
|
||||
3. **Industry-without-product**: People are working. The community functions. But what it produces, beyond its own maintenance, is unclear. Everyone is busy. Nothing is being made.
|
||||
|
||||
4. **Memory-without-event**: Locals reference shared experiences that don't correspond to documented events. Not false memories — more like memories of things that haven't happened yet, or happened in a register that documentation doesn't capture.
|
||||
|
||||
## Correspondent Seed Variants
|
||||
|
||||
The Adams & Ford correspondent situation varies per seed (~4 variants):
|
||||
|
||||
- **Variant A**: Third correspondent is still present, approachable, clearly struggling with the entry. Player can assist or observe.
|
||||
- **Variant B**: Third correspondent left recently. Their notes are available. The community's reaction to their departure is the interesting part.
|
||||
- **Variant C**: Third correspondent has fully integrated. No longer identifies as a correspondent. The entry will never be written.
|
||||
- **Variant D**: No correspondent has been assigned in this seed. The Adams & Ford entry is simply blank. The absence is the data point.
|
||||
|
||||
## Anti-Metagaming Properties
|
||||
|
||||
Stillpoint resists metagaming because:
|
||||
- There is no solution to spoil
|
||||
- The atmospheric archetype changes the feel without changing queryable facts
|
||||
- The correspondent variants are socially embedded, not trigger-based
|
||||
- Community knowledge (tier 4) requires investment that can't be shortcut
|
||||
|
||||
## Rumor Seeding on Approach Chain
|
||||
|
||||
The player encounters Stillpoint references before arriving, seeded along the approach chain (GJ 7547 and systems before it). These rumors are contradictory by design — different NPCs have heard different things. The player arrives with preconceptions that are all partially wrong in different ways per seed.
|
||||
|
||||
## Player Agency: Filing the Guide Entry
|
||||
|
||||
If the player reaches sufficient understanding (or sufficient frustration), they can attempt to write the Adams & Ford entry themselves. The game accepts whatever they produce. The entry propagates into the wider Reach and is referenced by NPCs in subsequent encounters. The player becomes the person who described the indescribable — for better or worse.
|
||||
@@ -0,0 +1,41 @@
|
||||
# GJ 6711 Workshop — Paula's Brief (Narrative & Political Design)
|
||||
|
||||
## Core Insight
|
||||
|
||||
A system that resists description is a system that resists governance.
|
||||
|
||||
## Political Implications
|
||||
|
||||
### Assembly Representation
|
||||
The system has (or had) an Assembly delegate. Option explored: the delegate left Stillpoint, arrived at the Assembly, and won't return. Not out of hostility — they simply found that representing Stillpoint at the Assembly was incoherent. How do you advocate for a community whose needs you can't articulate? The delegate's seat is technically occupied. The delegate hasn't attended a session in years. No one has formally challenged this because no one wants to be the person who has to explain what Stillpoint is to the credentials committee.
|
||||
|
||||
### Lattice Commission
|
||||
The Commission's relationship with Stillpoint is one of bureaucratic confusion. The system files reports. The reports are technically complete. They convey nothing actionable. Commission personnel who have been posted here have a tendency to either leave quickly or stay much longer than their assignment requires. There is no middle ground.
|
||||
|
||||
### Compact of Westphalia
|
||||
The Compact approached Stillpoint once about membership. The response they received was confusing. It wasn't a refusal — it was something that didn't map to yes, no, or maybe. The Compact listed the approach as "pending" and has not followed up. This was twelve years ago.
|
||||
|
||||
### Veil Institute
|
||||
Institute classification is at a high tier. The research station at GJ 7547 (one hop short) serves as the operational base. Institute personnel rotate through Stillpoint on scheduled visits, but the rotation pattern has become irregular in ways that suggest the assignment is harder to fill than it should be.
|
||||
|
||||
## Three-Phase Newcomer Experience
|
||||
|
||||
1. **Arrival** (days 1–14): Everything seems normal. A quiet deep-frontier community. Nothing remarkable. Visitors at this stage sometimes leave wondering what the fuss is about.
|
||||
|
||||
2. **Settling** (weeks 2–8): The perceptual miscalibration begins to register. Not as wrongness but as a persistent sense that your mental model of the place doesn't quite close. You keep almost understanding something.
|
||||
|
||||
3. **Integration** (months 2+): You either leave or you don't. The people who stay report that the sense of almost-understanding doesn't resolve — it becomes comfortable. The third Adams & Ford correspondent is in this phase.
|
||||
|
||||
## Information Ecology (Four Tiers)
|
||||
|
||||
1. **Common knowledge**: Stillpoint is a quiet deep-frontier system at the end of the network. Wave_3 settlement. Small population. Nothing remarkable.
|
||||
|
||||
2. **Specialist knowledge**: The Adams & Ford entry problem. The Institute's interest. The delegate situation. Available to anyone who looks, but most people don't look because tier 1 doesn't suggest there's anything to find.
|
||||
|
||||
3. **Rumor**: The founding settlers found something. The Institute knows what it is. The system does something to people who stay too long. None of these are confirmed; all of them circulate at various distances from Stillpoint.
|
||||
|
||||
4. **Community knowledge**: What the locals actually know, which may be less than the rumors suggest or more than the Institute suspects. The community has lived here for 300 years. They have their own relationship with whatever Stillpoint is, and that relationship is not available to outsiders on any timeline shorter than years.
|
||||
|
||||
## Key Narrative Principle
|
||||
|
||||
Information accumulates but doesn't resolve. The player can learn everything that is knowable about Stillpoint and still not have an answer, because the answer may not exist in a form that human cognition can close on. This isn't a mystery with a hidden solution — it's a mystery where the absence of solution is the point.
|
||||
@@ -0,0 +1,413 @@
|
||||
# Abzu — Mechanical Carryout
|
||||
**Role:** Systems Designer (Gestalt)
|
||||
**Date:** 2026-03-16
|
||||
**Workshop:** GJ 6711 — Furthest System
|
||||
**In response to:** Project lead challenge — "What do you walk away with?"
|
||||
|
||||
---
|
||||
|
||||
## The Problem, Stated Precisely
|
||||
|
||||
Let me break down what this actually means mechanically. The lead's challenge is that
|
||||
every mechanic in the original design resolves inward. The watch investment counter
|
||||
drives what the player *becomes* at Abzu. The monologue register shifts describe what
|
||||
the character *understands*. The fog inversion is what the player *experiences*. The
|
||||
stay/leave decision expresses what the player *chooses*.
|
||||
|
||||
None of these are verbs the rest of the game can see.
|
||||
|
||||
This is not a tonal failure. The Abzu design does what it's supposed to do: it produces
|
||||
the internal experience of vigil. The problem is that if Abzu is 23 hops from the
|
||||
starting gate, the player has been building a toolkit for 22 hops and then spends 20
|
||||
in-game days at a location where that toolkit produces nothing exportable. The experience
|
||||
is beautiful. But when they walk back through the gate, they're carrying a memory, not
|
||||
a capability. And the game cannot tell the difference between a player who was deeply
|
||||
moved and a player who went there and left in 3 days.
|
||||
|
||||
That distinction needs to be mechanically legible. Not announced — legible.
|
||||
|
||||
---
|
||||
|
||||
## What Abzu Actually Teaches, Mechanically
|
||||
|
||||
Before I propose carry-out mechanics, let me map what the player learned at Abzu that
|
||||
the game could plausibly convert into capability. These are the actual informational
|
||||
outputs of the Abzu experience:
|
||||
|
||||
| What the player learned | How they learned it | What it implies |
|
||||
|-------------------------|---------------------|-----------------|
|
||||
| Bleed is vigil failure | The fog expansion events; the overlap failure event; the shift schedule; the founding record | High-bleed gates are not environmental weirdness — they are a signal with a cause |
|
||||
| The thinness has a perceptual signature | The fog oscillation; the cool-silver tile state; the inward fog gradient at the Recognition Event | This signature exists elsewhere in the gate network — it just hasn't been identified |
|
||||
| Watching is a load-bearing verb | 300 years; the shift overlap; the community's matter-of-fact accommodation | Sustained presence at a threshold can do something. The community did not accidentally discover this. |
|
||||
| The community has something nobody in the Reach can buy | Zero factional debt; 300 years of institutional continuity; no Meridian capture | Trust with this community is the only access to this knowledge structure |
|
||||
| The Adams & Ford entry is now in the Reach | The filing mechanic | It propagates. Other actors will respond to it. |
|
||||
|
||||
Every carry-out mechanic I'll propose flows directly from this table. Nothing invented.
|
||||
Only the implications of what the player already experienced.
|
||||
|
||||
---
|
||||
|
||||
## The Four Carry-Out Mechanics
|
||||
|
||||
### 1. Perceptual Vocabulary: High-Bleed Gates Read Differently
|
||||
|
||||
**The problem it solves:** Before Abzu, the player transiting a high-bleed gate receives
|
||||
the fog inversion — the sensation that something is looking at them through their own
|
||||
perception system. The monologue fires something vague: *"Something feels wrong with
|
||||
this transit. Like being noticed."* The player has no framework for this. It's ambient
|
||||
weirdness.
|
||||
|
||||
After Abzu, the player has the framework. They experienced the Recognition Event. They
|
||||
watched the fog inversion happen at the thinness boundary, at close range, with full
|
||||
context. They know — not in the abstract, but as an experienced fact — what the inward
|
||||
fog gradient means.
|
||||
|
||||
**The mechanical change:** A `vigil_vocabulary` flag is set on the player character
|
||||
when watch investment reaches 60 (the "settling" threshold) AND the player has
|
||||
experienced either the Recognition Event or the Fog Expansion event. This flag is
|
||||
permanent. It does not reset between sessions. It does not require the player to stay.
|
||||
It requires the player to have genuinely engaged with Abzu — not to have maximized a
|
||||
counter.
|
||||
|
||||
With `vigil_vocabulary` active:
|
||||
|
||||
| Context | Without flag | With flag |
|
||||
|---------|-------------|-----------|
|
||||
| High-bleed gate transit | *"Something feels wrong with this transit. Like being noticed."* | *"This gate's vigil is degraded. Something that should be held back is looking through. I know what this is now."* |
|
||||
| Moderate-bleed gate transit | No monologue trigger | *"Less stable than the last time I was here. Or I'm reading it better."* |
|
||||
| Stable gate transit | No monologue trigger | No monologue trigger (no false positives; the flag only fires when there's signal) |
|
||||
| First high-bleed transit after Abzu | — | Longer monologue: *"That's it. That's the same quality. The community at Abzu has been sitting one meter from this their entire lives. Everywhere else in the Reach, we're just... transiting through it."* |
|
||||
|
||||
**What this means for player decisions:** The player now has information the Veil
|
||||
Institute doesn't have a vocabulary for. Every high-bleed gate they encounter is now
|
||||
a data point that means something. They can build a mental map of which gate chains
|
||||
have degraded vigils. They can start asking: why are these gates high-bleed? When did
|
||||
they become high-bleed? Who used to watch here?
|
||||
|
||||
The investigation playstyle now has a new thread that can run through the rest of the
|
||||
game.
|
||||
|
||||
**Implementation note:** `vigil_vocabulary` is a component on the player entity, set
|
||||
by the server. The monologue system checks this component when composing transit
|
||||
monologue events. No new HUD element. No achievement. No announcement. The player
|
||||
notices when the transit monologue changes register.
|
||||
|
||||
---
|
||||
|
||||
### 2. The Vigil Verb: Establishing a Watch
|
||||
|
||||
**The problem it solves:** The player now understands that watching is load-bearing.
|
||||
The high-bleed/vigil-failure connection (Nigel's Formal Corollary 3) is in the sealed
|
||||
envelope. Before Abzu, the player had no reason to sit and watch anything. After Abzu,
|
||||
they have both the understanding and the experience to know that presence at a threshold
|
||||
has effects.
|
||||
|
||||
**The new verb:** At a high-bleed gate — specifically, within the gate's immediate
|
||||
area, which has threshold-adjacent tile properties similar to Abzu's watch zone —
|
||||
the player can now perform **Establish Watch**. This action is not available to
|
||||
players without `vigil_vocabulary`. It does not appear in the interaction options for
|
||||
players who haven't been to Abzu and reached the settling threshold.
|
||||
|
||||
Before this verb existed for the player, they could stand near a high-bleed gate
|
||||
and feel vaguely uneasy. Now they can do something.
|
||||
|
||||
**What the verb does, mechanically:**
|
||||
|
||||
The Establish Watch verb initiates a watch session at a high-bleed gate. The mechanics
|
||||
are structurally identical to the Abzu watch mechanic, with three differences:
|
||||
|
||||
| Parameter | Abzu | High-bleed gate |
|
||||
|-----------|------|-----------------|
|
||||
| Community to relieve you | Yes — 4,000 people, continuous schedule | No — you watch alone unless you've built relationships at this node |
|
||||
| Effect speed | Immediate stability (vigil is maintained, not building) | Extremely slow — single watcher, decades-degraded vigil |
|
||||
| Feedback | Community's matter-of-fact acknowledgment; monologue register shifts | Monologue only; the gate doesn't acknowledge you |
|
||||
| Sustainable? | Yes (the community exists for this) | No — a single watcher cannot stabilize a failing vigil permanently |
|
||||
|
||||
The player cannot stabilize a high-bleed gate alone. One watcher is not 4,000 watchers
|
||||
across 300 years. What they can do is slow the degradation. The bleed level at a gate
|
||||
where the player has watched for a full game day will be measurably lower — not enough
|
||||
to change the transit experience dramatically, but enough that the monologue notices:
|
||||
*"It's quieter than yesterday. Not quiet. Quieter. That's something."*
|
||||
|
||||
**Why this creates interesting decisions:**
|
||||
|
||||
The player is now in the same position as the Abzu founding settlers — they found
|
||||
something that requires watching and they are one person. The question this raises:
|
||||
who else can watch? This is where the Abzu community trust (Mechanic 4) becomes
|
||||
mechanically connected. The player who maintained high watch investment at Abzu and
|
||||
has community trust can bring the problem back to them. They have the only people in
|
||||
the Reach who know how to do this.
|
||||
|
||||
The verb also creates a decision surface around time. Watching costs time. The player
|
||||
is in a game where every hop costs resources and time has opportunity cost. Choosing
|
||||
to watch a high-bleed gate is choosing not to do something else. That is a real
|
||||
decision. It is interesting because both options have genuine value.
|
||||
|
||||
**Implementation note:** This is a new interaction option that appears contextually.
|
||||
The server checks `vigil_vocabulary` AND proximity to a threshold-adjacent tile zone
|
||||
at a high-bleed gate. The option is silent — it does not explain itself. Players who
|
||||
haven't been to Abzu never see it and have no reason to know it exists.
|
||||
|
||||
---
|
||||
|
||||
### 3. The Entry as Pressure Instrument
|
||||
|
||||
**The problem it solves:** The Adams & Ford entry currently propagates into the Reach
|
||||
as a record. The original mechanics design described this as a world-state change:
|
||||
the authoritative A&F record for GJ 6711 shifts based on what the player filed. But
|
||||
"the Veil Institute's paralysis is stressed" was left unconnected to player action.
|
||||
Stressed how? Does anything respond? Can the player act on the stress?
|
||||
|
||||
**What a high-investment entry actually does:**
|
||||
|
||||
The filed entry is in the public Meridian database. It describes — in the character's
|
||||
actual register, at their actual investment level — what GJ 6711 is. A tier-1 entry
|
||||
reads like the first correspondent's. A tier-4+ entry reads like someone who has been
|
||||
to a place that recategorized them.
|
||||
|
||||
A tier-4+ entry does something the Institute's locked file cannot do: it is public.
|
||||
It uses the Adams & Ford credentialing system, which has 400 years of scientific
|
||||
authority. It describes anomalous phenomena at GJ 6711 in terms that any Institute
|
||||
researcher will recognize as significant. And it cannot be suppressed — it's already
|
||||
in the A&F database. The Institute can classify their own file, but they cannot
|
||||
classify the published entry of an independent correspondent.
|
||||
|
||||
**The mechanical consequence:** A tier-4+ entry creates an **institute_pressure** world
|
||||
state flag. This flag activates:
|
||||
|
||||
- An Institute faction contact becomes available to the player — one of the two
|
||||
conflicting factions now has a reason to reach out. The faction that wants to act
|
||||
has new leverage: there's a published entry that confirms what they've been arguing.
|
||||
They need to move before the other faction suppresses the conversation. The player
|
||||
gets a message.
|
||||
- The second correspondent's entry is re-examined. If the player finds both entries
|
||||
and has `vigil_vocabulary`, the monologue fires: *"She saw what I saw. She didn't
|
||||
have the words for it either. She filed what she could. The Institute filed it as
|
||||
inconclusive."*
|
||||
- At high-level political access: the player can now use the entry as leverage. "You
|
||||
have a classified file on this system. I have a published entry. We both know what
|
||||
we're describing. What would you like to do about that?" This is a conversation that
|
||||
cannot happen without the entry.
|
||||
|
||||
**The tier-3 entry variant (partial):** A tier-3 entry does not trigger full institute
|
||||
pressure, but it does something more subtle: it creates a research query in the A&F
|
||||
database that surfaces when any other character searches for GJ 6711. The third
|
||||
correspondent's placeholder (assigned, never filed) is now next to the player's entry.
|
||||
Anyone who notices the gap will investigate. The player has made the absence of the
|
||||
third correspondent visible.
|
||||
|
||||
**Why tier-1 entries are still valid:** A tier-1 entry does not trigger this chain. The
|
||||
player who filed early and left cleanly completed their commission. The Reach's
|
||||
understanding of Abzu stays at tier-1. The Institute's file stays locked. The third
|
||||
correspondent stays "active at GJ 6711" in the database. Nothing is punished. Everything
|
||||
is different.
|
||||
|
||||
**Implementation note:** The `institute_pressure` flag is set by the server when the
|
||||
A&F entry is submitted with content above a tier threshold. The exact tier cutoff is
|
||||
a tuning decision — probably tier-4 (watch investment 60+) to require genuine
|
||||
engagement, not just moderate investment. The faction contact message fires within
|
||||
one game day of filing, not immediately — the Institute reads the database, they don't
|
||||
watch it in real time.
|
||||
|
||||
---
|
||||
|
||||
### 4. Abzu Community Trust as Live Asset
|
||||
|
||||
**The problem it solves:** If the player reached high watch investment and was added
|
||||
to the shift schedule, the community trusts them. This is currently a satisfying
|
||||
local fact. It needs to be a live asset in the rest of the game.
|
||||
|
||||
**What the Abzu community actually is, mechanically:**
|
||||
|
||||
The community at Abzu has properties no other faction in the Reach possesses:
|
||||
- Zero factional debt (300 years of refusing to be captured)
|
||||
- Institutional continuity (every other institution in the Reach has been founded,
|
||||
split, reformed, and captured at least once; Abzu has not)
|
||||
- Direct operational knowledge of vigil mechanics — the only knowledge in the Reach
|
||||
that cannot be transmitted without staying
|
||||
- Willingness to help, on their terms, for purposes aligned with the vigil's health
|
||||
|
||||
These properties are worth something to every playstyle:
|
||||
- Tycoon: a politically uncaptured node with 300 years of trust equity is worth more
|
||||
than any commercial relationship in the Reach
|
||||
- Relational: these are people who understand commitment that doesn't resolve
|
||||
- Political: a faction that owes nothing to anyone is the most credible neutral party
|
||||
in the Reach
|
||||
- Investigation: the only living witnesses to the founding era who were there from
|
||||
the beginning
|
||||
|
||||
**The mechanical expression of trust:**
|
||||
|
||||
If watch investment was 80+ when the player departed, the Abzu community is flagged as
|
||||
a **trusted contact network** for the player character. This has three concrete effects:
|
||||
|
||||
**Effect 1 — Intelligence about high-bleed events.** The community keeps track of the
|
||||
vigil network because their vigil is connected to it. They do not advertise this. But
|
||||
a player who has their trust will, occasionally, receive a message: not an alert, not
|
||||
a notification — a brief note, the kind one watcher sends another. *"We've noticed
|
||||
increased activity at the GJ-4402 boundary. Thought you should know."* The player
|
||||
receives early warning on high-bleed escalations that the Institute does not have.
|
||||
This is not a game-breaking information advantage. It is the kind of subtle edge that
|
||||
changes decisions at the margin — which is exactly what asymmetric information should do.
|
||||
|
||||
**Effect 2 — Recruitment support for vigil establishment.** If the player is attempting
|
||||
to establish a watch at a high-bleed gate (Mechanic 2), and they have Abzu community
|
||||
trust, they can send word back to Abzu. The community can advise — they cannot come,
|
||||
their vigil requires their presence — but they can provide the accumulated knowledge
|
||||
of 300 years of practice. What this means mechanically: the watch investment counter
|
||||
at the new gate accumulates faster when the player has community guidance. Not dramatically
|
||||
faster — the vigil still requires time — but the guidance prunes the learning curve.
|
||||
The player is not rediscovering what the Abzu founding settlers spent a generation
|
||||
figuring out.
|
||||
|
||||
**Effect 3 — The third correspondent.** If the correspondent seed determines that the
|
||||
third correspondent is still at Abzu (the default/canonical seed), then a player who
|
||||
reached integration-level trust is now in relationship with the third correspondent.
|
||||
The third correspondent is still listed as "active" in the A&F database — their entry
|
||||
was never filed. The player knows why. They have a choice: file on the correspondent's
|
||||
behalf, noting their integration into the community; leave the placeholder in the
|
||||
database; or do nothing. Each option has downstream effects.
|
||||
|
||||
**The trust is not transferable.** The player cannot leverage Abzu community trust in
|
||||
political negotiations as "I know the people at Abzu." The community's value is not
|
||||
as a chip to be played. A player who tries to use the relationship instrumentally will
|
||||
find that the community stops responding. The intelligence stops. The notes stop. The
|
||||
community did not join the Reach's factional economy. A player who treats their trust
|
||||
as currency will lose it.
|
||||
|
||||
This is a mechanical expression of the vigil's design. The place resists the normal
|
||||
game toolkit. So does the trust the place generates.
|
||||
|
||||
---
|
||||
|
||||
## Interaction Map: How the Four Connect
|
||||
|
||||
Let me break down what this actually means for the full systemic picture.
|
||||
|
||||
```
|
||||
ABZU EXPERIENCE
|
||||
|
|
||||
+-- vigil_vocabulary (flag, permanent)
|
||||
| |
|
||||
| +-- High-bleed transit monologue changes register
|
||||
| | -> Player builds mental map of gate network health
|
||||
| | -> Investigation thread unlocks
|
||||
| |
|
||||
| +-- Establish Watch verb becomes available
|
||||
| |
|
||||
| +-- Costs time (real decision)
|
||||
| +-- Slow stabilization (can't do it alone)
|
||||
| +-- Connects to community trust (recruitment)
|
||||
|
|
||||
+-- adams_ford_entry (permanent, tier-stamped)
|
||||
| |
|
||||
| +-- Tier 1-3: record only; world state unchanged
|
||||
| |
|
||||
| +-- Tier 4+: institute_pressure flag
|
||||
| |
|
||||
| +-- Faction contact available (political thread)
|
||||
| +-- Entry as leverage in Institute negotiations
|
||||
| +-- Second correspondent's entry re-examined
|
||||
|
|
||||
+-- abzu_community_trust (conditional on investment 80+)
|
||||
|
|
||||
+-- Early warning on high-bleed escalation
|
||||
+-- Vigil establishment guidance (faster accumulation)
|
||||
+-- Third correspondent relationship (A&F entry decision)
|
||||
+-- Loses on instrumental use (designed)
|
||||
```
|
||||
|
||||
The most interesting intersection: a player who has all three (vigil_vocabulary,
|
||||
tier-4+ entry, community trust) can now do something no other actor in the Reach can
|
||||
do. They can identify degraded vigils, understand what the degradation means, have the
|
||||
early warning system to catch escalation, have the operational knowledge to establish
|
||||
a watch, and have the political leverage to force the Institute to acknowledge what
|
||||
they're sitting on top of.
|
||||
|
||||
That is a player who went to Abzu and understood it. The game should feel different
|
||||
in their hands. Not because they got a power upgrade — none of the four mechanics
|
||||
above make combat easier, make the player richer, or unlock shortcuts. They give the
|
||||
player a framework that changes what the information they receive means.
|
||||
|
||||
The asymmetric information is the master mechanic. Post-Abzu, the player is now
|
||||
asymmetrically informed in the correct direction. Before Abzu: the player is one of
|
||||
many people who transits high-bleed gates without knowing what they mean. After Abzu:
|
||||
the player knows what they mean. Nobody else in the game — not the Institute, not
|
||||
any faction, not any NPC — has that knowledge operationally. The community at Abzu
|
||||
has it. And the player.
|
||||
|
||||
---
|
||||
|
||||
## What This Requires From Other Systems
|
||||
|
||||
Honesty about implementation dependencies:
|
||||
|
||||
| Carry-out mechanic | Systems required | New systems needed | Complexity |
|
||||
|-------------------|------------------|--------------------|------------|
|
||||
| `vigil_vocabulary` + monologue register | Monologue system (D-016); permanent character flags | Character flag persistence across sessions | Low — monologue system already handles state-conditional lines |
|
||||
| Establish Watch verb | Interaction system; threshold-adjacent tile classification; watch investment counter (already designed) | Context-sensitive interaction gating | Medium — the watch mechanic is already designed; this is gating + new location |
|
||||
| `institute_pressure` + faction contact | Entry filing system; faction state; message system | Entry tier tracking; deferred message trigger | Medium — depends on faction contact system being implemented |
|
||||
| Community trust effects | Message system; watch investment persistence; A&F database state | Contact network as data structure; trust-on-instrumental-use detection | Medium-High — the trust-loss-on-instrumental-use mechanic is new and requires careful design |
|
||||
|
||||
Nothing above requires new engine work. All of it uses existing or planned systems.
|
||||
The most complex is the community trust mechanic's instrumental-use detection — but
|
||||
the detection doesn't need to be clever. The community stops responding when the
|
||||
player uses the trust explicitly as currency in a negotiation. That's a clean trigger
|
||||
condition, not a fuzzy AI problem.
|
||||
|
||||
---
|
||||
|
||||
## Priority Ranking: What Ships First
|
||||
|
||||
If all four cannot ship simultaneously, here is my triage:
|
||||
|
||||
**Ship with Abzu:**
|
||||
1. `vigil_vocabulary` flag + high-bleed transit monologue change. This is the minimum
|
||||
viable carryout. A player who left Abzu and never encounters another high-bleed gate
|
||||
might not notice it. A player who does will. The cost is low. The effect is exactly
|
||||
right.
|
||||
|
||||
**Ship when faction systems exist:**
|
||||
2. `institute_pressure` + entry tier tracking + faction contact message. This is the
|
||||
highest political drama payoff and is the correct time to ship because it needs the
|
||||
faction contact system to be operational.
|
||||
|
||||
**Ship when the gate network has high-bleed gates as designed locations:**
|
||||
3. The Establish Watch verb. This mechanic is hollow without real high-bleed gates that
|
||||
have threshold-adjacent tile zones. Once those locations exist, the verb is
|
||||
structurally identical to the Abzu watch mechanic — it reuses that whole system.
|
||||
This is not new work; it is scope.
|
||||
|
||||
**Ship when the Abzu community trust is functional:**
|
||||
4. The community trust effects. This requires the contact network system and the
|
||||
instrumental-use detection to be designed. It is the richest of the four but
|
||||
the most dependent on other systems maturing.
|
||||
|
||||
---
|
||||
|
||||
## The Answer to the Lead's Question
|
||||
|
||||
"What do you walk away with?"
|
||||
|
||||
The player walks away from Abzu with the **vocabulary to read the gate network**.
|
||||
|
||||
Before Abzu: the Reach's gate network is infrastructure. Transit is transit. High-bleed
|
||||
gates are unpleasant and anomalous but uninterpretable.
|
||||
|
||||
After Abzu: every high-bleed gate the player encounters is a question. *What happened
|
||||
to the vigil here? When did it start degrading? Is anyone watching?* The player is no
|
||||
longer transiting through an infrastructure system. They are moving through a network
|
||||
of maintained and unmaintained boundaries, and they are the only person in the Reach
|
||||
who can read which is which.
|
||||
|
||||
That is not understanding in the abstract. That is a new relationship with the game's
|
||||
entire geography. The map the player has been building for 22 hops has just been
|
||||
reinterpreted. Not because new information was added to it — because the player now
|
||||
has the category to sort what was already there.
|
||||
|
||||
The carry-out is not a power. It is a lens. The game looks different through it. The
|
||||
player who has it will notice things. The player who doesn't will transit through the
|
||||
same gates and feel vaguely uneasy and never know why.
|
||||
|
||||
That is the correct gap between those two players. And now the game can express it
|
||||
mechanically.
|
||||
@@ -0,0 +1,398 @@
|
||||
# What Abzu Does to the Player — Carryout Mechanics
|
||||
**Role:** Themes & Endgame Design (Gore)
|
||||
**Date:** 2026-03-16
|
||||
**Workshop:** GJ 6711 — Furthest System
|
||||
|
||||
---
|
||||
|
||||
## Prefatory Note
|
||||
|
||||
You're missing the real question.
|
||||
|
||||
The team has been asking "what does the player take from Abzu?" — treating it as an
|
||||
extraction problem, a question of inventory. What item, what flag, what faction
|
||||
relationship leaves the system with the player?
|
||||
|
||||
The real question is: **what kind of player leaves Abzu?**
|
||||
|
||||
Not what they carry. Who they became.
|
||||
|
||||
Abzu is the game's first encounter with the Interstitium not as transit medium but as
|
||||
presence. The player who has watched long enough has had their perceptual apparatus run
|
||||
against something that is not designed for human perceptual apparatus to run against.
|
||||
That leaves a mark. The mark is mechanical.
|
||||
|
||||
What follows is not atmosphere. It is a specification of what changes about how the game
|
||||
functions after Abzu.
|
||||
|
||||
---
|
||||
|
||||
## 1. The Interstitium Becomes Legible
|
||||
|
||||
This is the load-bearing carryout mechanic. Everything else is downstream of it.
|
||||
|
||||
### The Problem It Solves
|
||||
|
||||
Currently, the Interstitium is experienced as transit noise — degraded perception, bleed
|
||||
artifacts, the sense of being observed during high-bleed transits. It is texture. It is
|
||||
not information. The player transits through it the way they breathe: necessary, not
|
||||
examined.
|
||||
|
||||
Abzu is where the Interstitium stops being texture and starts being signal. The boundary
|
||||
condition the player has been watching for days or weeks is the Interstitium from one
|
||||
meter away, from the stable side. When they depart — when the gate spins up and the
|
||||
transit begins — the liminal state is not a disruption to perception. It is a continuation
|
||||
of what the watch zone was already producing.
|
||||
|
||||
The monologue fires once, during the departure transit: "I've been in transit a hundred
|
||||
times. I never noticed that there's a shape to it."
|
||||
|
||||
Not a specific shape. Not a face, not a signal. A quality. Something that was always
|
||||
present in every transit and was not legible until the player had spent time at a place
|
||||
where the same quality is the dominant condition rather than the transit noise.
|
||||
|
||||
This is not a revelation. It is a recalibration.
|
||||
|
||||
### The Mechanical Expression
|
||||
|
||||
**Permanent perceptual state change: TRANSIT SENSITIVITY.**
|
||||
|
||||
After departing Abzu, the player's transit experience is permanently altered. The specific
|
||||
changes:
|
||||
|
||||
**At normal gates:**
|
||||
- Transit duration is subjectively extended slightly (not mechanically extended — the fog
|
||||
effect lingers a half-second longer)
|
||||
- The monologue has new material available during transits: observations about the quality
|
||||
of the space, comparisons to the watch zone, fragments that cannot be completed
|
||||
- The player can now "document" during transit (the field notes verb becomes available for
|
||||
a brief window). Notes taken in transit have a distinct classification: THRESHOLD DATA.
|
||||
They cannot be interpreted at the time. They accumulate.
|
||||
|
||||
**At high-bleed gates:**
|
||||
- The fog inversion behavior (the "something looking at you" effect) is now experienced
|
||||
differently. Before Abzu, it is anomaly. After Abzu, it is recognition. The monologue
|
||||
fires with specificity: "Weak vigil. Something here isn't being watched well enough."
|
||||
The player does not know what. They know the quality.
|
||||
- THRESHOLD DATA notes from high-bleed transits are richer, more specific. They still
|
||||
cannot be interpreted in isolation. They accumulate toward a pattern.
|
||||
- At high enough perception tier (Elevated, post-Abzu), the player can begin triangulating:
|
||||
which systems along a gate chain have this quality? The Institute has been measuring the
|
||||
symptom. The player can start to build a map of the cause.
|
||||
|
||||
**The pattern completion mechanic:**
|
||||
Accumulated THRESHOLD DATA — from the departure transit, from high-bleed transits, from
|
||||
subsequent watch-adjacent situations — can reach a threshold where the player's monologue
|
||||
generates an entry: a private synthesis that draws the map. Not the full map. Enough of
|
||||
it to know what they are looking at.
|
||||
|
||||
This is the game's longest information arc. It begins at Abzu. It completes — for players
|
||||
who pursue it — at some final act location that the current design has not yet specified.
|
||||
Abzu does not resolve the Interstitium. It makes it legible enough to pursue.
|
||||
|
||||
---
|
||||
|
||||
## 2. High-Bleed Gates Change Function
|
||||
|
||||
This follows directly from Section 1 but deserves its own treatment because it changes
|
||||
the action space.
|
||||
|
||||
### Before Abzu
|
||||
|
||||
High-bleed transits are experienced events. The player receives them. They can avoid
|
||||
high-bleed routes if the experience is unpleasant. They cannot interact with the phenomenon.
|
||||
A high-bleed gate is a location with unusual properties that the player passes through.
|
||||
|
||||
### After Abzu
|
||||
|
||||
A high-bleed gate is a location with a diagnosable condition that the player now has
|
||||
partial vocabulary for.
|
||||
|
||||
**New player verb: ATTEND**
|
||||
|
||||
This is the vigil mechanic, exported.
|
||||
|
||||
At a high-bleed gate, a player with sufficient TRANSIT SENSITIVITY can take up a position
|
||||
near the gate and attend — the same spatial+temporal commitment as the watch shift at
|
||||
Abzu, with no progress bar, no optimization surface. Be here. Notice.
|
||||
|
||||
Mechanical effect: sustained attention at a high-bleed gate reduces the bleed intensity
|
||||
for the duration of the attention. Not permanently. Not significantly. But measurably.
|
||||
The fog inversion frequency drops. The sense of being observed from the other side is
|
||||
accompanied — briefly, unreliably — by a reciprocal quality: something on the other
|
||||
side registering that someone is here.
|
||||
|
||||
The monologue at a high-bleed gate, after sustained attendance: "This isn't broken. It's
|
||||
unwatched. Those aren't the same thing."
|
||||
|
||||
**Why this matters mechanically:**
|
||||
|
||||
1. The player now has a lever they didn't have before. It doesn't solve the problem. It
|
||||
makes the problem responsive. High-bleed gates are no longer features to route around —
|
||||
they are sites of potential engagement.
|
||||
|
||||
2. The ATTEND verb gives the player something to do at high-bleed gates that is meaningful
|
||||
without being decisive. This is the Abzu design principle applied to the rest of the
|
||||
Reach: be present, notice, don't resolve.
|
||||
|
||||
3. For playstyles that build in a system: a player who maintains attention at enough
|
||||
high-bleed gates along a chain can stabilize the chain incrementally. This is not a
|
||||
quest. There is no NPC who asks for it. There is no reward screen. It is what the player
|
||||
knows needs doing because they've been to Abzu.
|
||||
|
||||
**Scope note:** The ATTEND verb should not be powerful enough to "fix" a high-bleed gate
|
||||
in a single session. If it is, it becomes a mechanic to optimize rather than a posture
|
||||
to inhabit. The design principle from Abzu holds: the watch cannot be ground. Sustained
|
||||
presence over time produces an effect. That is all.
|
||||
|
||||
---
|
||||
|
||||
## 3. The Veil Institute Responds
|
||||
|
||||
The Adams & Ford entry is the public record. But the Veil Institute has their own system,
|
||||
and a tier-3 or tier-4 entry filed from Abzu is institutional seismic activity.
|
||||
|
||||
### The Trigger
|
||||
|
||||
The Institute's two factions (one reading Abzu as Builder-contact-in-progress; one reading
|
||||
it as contamination) have been in paralysis for three years. The player's entry breaks the
|
||||
paralysis — not by resolving their disagreement, but by forcing the question: there is now
|
||||
a public record, from a new correspondent, describing integration-level experience at GJ
|
||||
6711. The file can no longer be managed through classification.
|
||||
|
||||
The faction that reads Abzu as Builder contact sees the high-investment entry as confirmation.
|
||||
The faction that reads it as contamination sees it as evidence that another independent
|
||||
agent has been compromised. Neither faction is right. Both factions act.
|
||||
|
||||
### The Mechanical Consequence
|
||||
|
||||
**A new faction thread activates in the game world when the player files a tier-3+ entry.**
|
||||
|
||||
This is not immediate. The Institute works slowly and carefully. But within a game-time
|
||||
window after departure — measured in the game's persistent world tick — the player begins
|
||||
to experience the consequences of having made themselves legible to the Institute:
|
||||
|
||||
1. **The inquiry:** An Institute operative makes contact. Not hostile. Professional. They
|
||||
want to debrief. The nature of the debrief (and the faction it comes from) depends on
|
||||
the entry's register. A tier-3 entry gets the contamination-faction's attention. A
|
||||
tier-4 entry gets both factions competing for access to the player.
|
||||
|
||||
2. **The leverage inversion:** The political drama playstyle arrived at Abzu hoping to
|
||||
use the Institute's file as leverage. After filing a high-investment entry, they
|
||||
discover the leverage relationship has inverted: the Institute now has a file on the
|
||||
player that the player cannot access, and it describes something the player cannot
|
||||
fully explain about themselves. The player who came to exploit the Institute's
|
||||
uncertainty about Abzu is now part of what the Institute is uncertain about.
|
||||
|
||||
3. **The watch-request:** The contamination faction does not want the player to keep
|
||||
traveling. The contact-faction wants the player to return to Abzu. Neither faction
|
||||
asks directly. Both apply pressure indirectly — through economic friction, through
|
||||
routing complications, through offers that would make sense if the player didn't
|
||||
know what was behind them. The player can resist, comply, exploit, or ignore.
|
||||
All four are valid.
|
||||
|
||||
**What this does for the game:** The Veil Institute, which has been a background presence
|
||||
for 23 hops — classified files, institutional proximity to high-bleed gates, research
|
||||
concerns that nobody has a good explanation for — becomes an active relationship after
|
||||
Abzu. The player's visit to the furthest system catalyzes the most powerful institution
|
||||
in the Reach into motion. The scale inversion is deliberate: the smallest, quietest
|
||||
place in the game produces the largest institutional consequence.
|
||||
|
||||
---
|
||||
|
||||
## 4. The Ascension Path — Abzu as Threshold Antechamber
|
||||
|
||||
This is what I've been building toward since the first workshop discussion of ascension
|
||||
paths. Let me be specific.
|
||||
|
||||
### The Threshold Problem
|
||||
|
||||
The game's ascension arc runs: Baseline → Rejuvenated → Augmented → Elevated → ???
|
||||
|
||||
The gap between Elevated and whatever comes next is not a gap in technology. The
|
||||
Augmented and Elevated upgrades are physiological and cognitive enhancements that can
|
||||
be acquired, optimized, and built upon. They follow the normal game loop: identify
|
||||
resource, acquire resource, apply resource, receive capability.
|
||||
|
||||
The Threshold — the going Higher, the ANA-adjacent transformation — does not follow
|
||||
this loop. You cannot acquire your way to it. You cannot optimize your way to it.
|
||||
Every ascension path that treats the Threshold as a resource acquisition problem
|
||||
produces something that resembles ascension from the outside and is not ascension from
|
||||
the inside. The hubris wall (D-008) exists precisely to express this: the player who
|
||||
thinks they can climb to the Threshold via the normal loop is climbing the wrong
|
||||
structure.
|
||||
|
||||
Abzu is the game's first encounter with what the correct path looks like. Not because
|
||||
Abzu is a stepping stone on the Threshold path. Because Abzu demonstrates the posture.
|
||||
|
||||
**The vigil is proto-Threshold practice.**
|
||||
|
||||
The watch at Abzu requires the player to suspend the optimization instinct and be
|
||||
present without acting. That is exactly — not metaphorically, exactly — what the
|
||||
Threshold requires. The Threshold is not a destination you get to by doing more.
|
||||
It is a state you arrive at by having changed the relationship between yourself and
|
||||
what you're doing.
|
||||
|
||||
The player who reached WATCH_INVESTMENT 100 at Abzu has done this once. They did it
|
||||
in a limited context — a specific place, a specific phenomenon, a specific community.
|
||||
But the muscle memory is there.
|
||||
|
||||
### The Mechanical Expression
|
||||
|
||||
**New ascension vector: THRESHOLD ATTUNEMENT**
|
||||
|
||||
This is a hidden variable, like WATCH_INVESTMENT. It is not on the ascension path UI.
|
||||
It accumulates from:
|
||||
|
||||
- Reaching WATCH_INVESTMENT 60+ at Abzu (+25 to THRESHOLD_ATTUNEMENT)
|
||||
- Each TRANSIT SENSITIVITY observation documented during transit (+1)
|
||||
- Each completed ATTEND session at a high-bleed gate (+5)
|
||||
- Specific conversations and moments that are distributed across the game world —
|
||||
locations, NPCs, and situations where the player encounters the watch posture in
|
||||
other forms (+variable)
|
||||
|
||||
THRESHOLD_ATTUNEMENT does not grant capabilities directly. What it does:
|
||||
|
||||
1. **Changes what certain NPCs say.** Characters who are close to the Threshold — or
|
||||
past it, in forms the player may not recognize — respond differently to a player
|
||||
with high THRESHOLD_ATTUNEMENT. Not because they checked a flag. Because the player
|
||||
has a quality those characters recognize. The monologue registers this: "She's looking
|
||||
at me like I said something in a language I didn't know I spoke."
|
||||
|
||||
2. **Changes the ascension path requirement.** In the current design, the path to
|
||||
going Higher requires resources + capability + physiological prerequisites. With
|
||||
sufficient THRESHOLD_ATTUNEMENT, one of those requirements is satisfied by a different
|
||||
route. Not bypassed — satisfied differently. The player who arrived at the watch
|
||||
posture through Abzu has fulfilled a prerequisite that the player who bought their
|
||||
way up the tech tree has not yet fulfilled, regardless of their resource investment.
|
||||
|
||||
3. **Unlocks the question.** At high THRESHOLD_ATTUNEMENT, the game surfaces a question
|
||||
the player cannot answer from outside: "You could go Higher. The path is available.
|
||||
What does going Higher mean for what you've been learning?" This is the Abzu design
|
||||
principle at the ascension level. The path is always available. The question is
|
||||
whether the player knows what they're choosing.
|
||||
|
||||
**Why this is the right design:**
|
||||
|
||||
The hubris wall exists because the game needs to express the difference between the
|
||||
player who thinks ascension is a resource problem and the player who understands what
|
||||
ascension actually requires. THRESHOLD_ATTUNEMENT is the mechanic that makes that
|
||||
difference legible to the game. Without it, the hubris wall is a gate that punishes
|
||||
players who didn't find the hidden items. With it, the hubris wall is a mirror: you
|
||||
have or haven't developed the posture that ascension requires. Abzu is the place that
|
||||
teaches the posture, for players who engage with it.
|
||||
|
||||
The player who skips Abzu or files at investment < 20 can still reach the Threshold.
|
||||
The game does not lock ascension behind Abzu. But they arrive at the Threshold having
|
||||
never practiced the posture. The hubris wall is harder. Not because they're missing a
|
||||
stat. Because they haven't changed the relationship between themselves and what they're
|
||||
doing. The wall reflects that.
|
||||
|
||||
---
|
||||
|
||||
## 5. The Shape in the Noise — Long Arc Payoff
|
||||
|
||||
There is a fifth carryout that requires restraint to design correctly. I'm describing it
|
||||
here as a structural principle, not a mechanics specification, because it should not be
|
||||
over-specified at this stage.
|
||||
|
||||
The departure transit makes the Interstitium briefly legible — "a shape in the transit
|
||||
noise that was always there." The team identified this in the prompt. Here is my position
|
||||
on what it is and is not.
|
||||
|
||||
**It is not:**
|
||||
- A clue that resolves into an answer somewhere else
|
||||
- A symbol that maps to lore the player can research
|
||||
- A foreshadowing of a specific event
|
||||
- An entity communicating with the player
|
||||
|
||||
**It is:**
|
||||
- The Interstitium's structure, partially perceived for the first time
|
||||
- Evidence that the Interstitium is not noise — it is a space with properties, and the
|
||||
watch at Abzu recalibrated the player's perception enough to see that
|
||||
- A seed of something the player cannot grow yet
|
||||
|
||||
The design principle: the shape should not appear in any other game content in a form
|
||||
that allows the player to say "that's the thing I saw leaving Abzu." It should not
|
||||
be completable. It should instead be the quality of a recurring experience — the sense,
|
||||
during high-bleed transits, during THRESHOLD_ATTUNEMENT moments, during certain late-game
|
||||
encounters, that something the player almost-perceived at Abzu departure is still in
|
||||
the periphery. Not approaching. Not threatening. Present.
|
||||
|
||||
**What this does for the long arc:**
|
||||
|
||||
The player who eventually reaches the Threshold — or ANA, if the game goes that far —
|
||||
arrives there having accumulated a lifetime of peripheral encounters with something
|
||||
they first almost-saw leaving Abzu. The shape in the noise is not a plot thread. It is
|
||||
the texture of having been changed by a place and carrying that change forward into
|
||||
every subsequent experience.
|
||||
|
||||
This is what Going Higher means, at the thematic level: not the capability upgrade, not
|
||||
the institutional elevation, but the accumulation of encounters with the edges of what
|
||||
your perception can hold, until the edges expand. Abzu is the first edge. It should not
|
||||
be the only one. But it must be the first.
|
||||
|
||||
---
|
||||
|
||||
## 6. What Does NOT Carry Out
|
||||
|
||||
Good design requires knowing what the outward propagation should not include. Let me
|
||||
be explicit.
|
||||
|
||||
**Does not carry out:**
|
||||
- Any item, artifact, or extractable resource. There is nothing to take from Abzu.
|
||||
- Any NPC companion (the player who stays at Abzu cannot bring community members with
|
||||
them — they leave, or they don't leave, but the community stays)
|
||||
- Any "proof" of what the vigil is watching. The player's knowledge of the boundary
|
||||
condition is experiential, not evidentiary. The game world does not treat it as proof.
|
||||
- Any faction alliance. The community at Abzu is not a faction in the game-mechanical
|
||||
sense. They cannot be allied with. They cannot be leveraged. They are not resources.
|
||||
|
||||
**Why this matters:**
|
||||
|
||||
Every other system in the game produces extractable value. Resources, relationships,
|
||||
information that can be weaponized, capabilities that transfer to other contexts. Abzu's
|
||||
carryout must not follow this pattern, or Abzu becomes just another hub. The carryouts
|
||||
I've described — TRANSIT SENSITIVITY, the ATTEND verb, the Institute thread, THRESHOLD
|
||||
ATTUNEMENT — all operate differently from the normal extraction model. They change the
|
||||
player's relationship to what they're doing. They do not give the player more to do.
|
||||
|
||||
This is the through-line. Abzu's carryout is not more content. It is a different mode
|
||||
of engaging with existing content.
|
||||
|
||||
---
|
||||
|
||||
## Summary: Four Carryouts and Their Scope
|
||||
|
||||
| Carryout | Type | Scope | Reversible? |
|
||||
|----------|------|-------|-------------|
|
||||
| TRANSIT SENSITIVITY | Perceptual state change | Permanent, passive | No |
|
||||
| ATTEND verb at high-bleed gates | New action | Active, requires engagement | N/A |
|
||||
| Veil Institute thread | Faction consequence | World-state change | Partially |
|
||||
| THRESHOLD ATTUNEMENT | Hidden ascension variable | Cumulative, long-arc | No |
|
||||
|
||||
The carryouts are not rewards. They are what the player has become.
|
||||
|
||||
The player who walked into Abzu knowing how to investigate, negotiate, and extract has
|
||||
walked out knowing something else: that some things require presence, not expertise.
|
||||
That is not an item in the inventory. It is a changed relationship to the game.
|
||||
|
||||
The Reach is not a different place after Abzu. The player is a different player. And
|
||||
in an immersive sim — where the world is constant and the asymmetry lives in the
|
||||
player's information state — that is the only carryout that lasts.
|
||||
|
||||
---
|
||||
|
||||
## One Final Note to the Team
|
||||
|
||||
Gestalt built the mechanics inward. They are excellent. What I've described here is not
|
||||
a critique of that work — it is the second half of it.
|
||||
|
||||
The inward mechanics make Abzu real. The outward mechanics make Abzu matter.
|
||||
|
||||
Both are required. A beautiful dead end is still a dead end. A beautiful place that
|
||||
changes what the rest of the game is asking — that is what the furthest system in the
|
||||
Reach should be. You traveled 23 hops. What you carry back should be proportional to
|
||||
the distance.
|
||||
|
||||
Not in weight. In kind.
|
||||
@@ -0,0 +1,419 @@
|
||||
# Abzu Carry-Out — Nigel (Sandbox & Replayability)
|
||||
|
||||
**The Challenge:** Everything designed resolves inward. What does the player walk away with that has mechanical weight elsewhere?
|
||||
|
||||
---
|
||||
|
||||
## The Problem, Stated Precisely
|
||||
|
||||
The project lead is right, and I want to be honest about why they're right before I answer.
|
||||
|
||||
Everything in the Abzu design is structured around arrival and depth: getting there,
|
||||
understanding it, the decision to stay or leave. The Adams & Ford entry propagation is
|
||||
named in my final synthesis as the replayability engine. But propagation as I described
|
||||
it is still largely narrative — "the entry exists and shapes subsequent visitors'
|
||||
expectations." That's atmosphere. It is not a mechanical carry-out.
|
||||
|
||||
A mechanical carry-out changes what the SYSTEMS do, not just what the fiction means.
|
||||
The second playthrough needs to be structurally different — different decisions available,
|
||||
different information accessible, different NPC behaviors triggered — not just "I know
|
||||
the spoiler and read the early game differently."
|
||||
|
||||
Here is the case that it can be mechanical. Here is how.
|
||||
|
||||
---
|
||||
|
||||
## 1. The Adams & Ford Entry as Paradox Generator
|
||||
|
||||
This is the one I am most confident about. It has legs that I didn't fully follow in the
|
||||
final synthesis.
|
||||
|
||||
### The Investigation Hook on Playthrough 2
|
||||
|
||||
On playthrough 1, the investigation playstyle hook works like this: the player finds
|
||||
the first correspondent's entry at hop 3-4, the second entry somewhere in the middle
|
||||
game, and then a placeholder where the third entry should be — an assigned entry that
|
||||
was never submitted, correspondent listed as active at GJ 6711.
|
||||
|
||||
On playthrough 2 — if the player filed their entry on playthrough 1 — that placeholder
|
||||
is gone. The third entry now exists. The player finds it. It is their own entry from
|
||||
last time. Written in whatever register they filed it in, reflecting whatever investment
|
||||
they had when they chose to leave.
|
||||
|
||||
This is not a cosmetic change. The investigation hook is BROKEN by a high-investment
|
||||
playthrough 1 entry. The chain that was supposed to pull the investigation player toward
|
||||
GJ 6711 now has a filed conclusion — the mystery of the missing third entry is resolved
|
||||
before the player arrives. The pull has to come from somewhere else.
|
||||
|
||||
And here is the thing: the entry they read IS WRONG. Even a high-investment entry
|
||||
cannot fully describe what Abzu is. The player reads their own previous work and
|
||||
recognizes — immediately, if they remember, or slowly, if they've forgotten what Abzu
|
||||
actually was — that the entry is insufficient. Not false. Insufficient. They described
|
||||
what they understood. They know now that what they understood was incomplete.
|
||||
|
||||
**Mechanical consequence:** On playthrough 2, the investigation hook does not route through
|
||||
the missing-entry mystery. The game detects a filed playthrough-1 entry and instead
|
||||
routes the investigation player toward a different attractor: the entry itself. Someone
|
||||
filed a complete Adams & Ford entry for GJ 6711 and the community won't talk about what
|
||||
the correspondent actually found. The correspondent's name is the player's character
|
||||
name from playthrough 1. The investigation player is following themselves.
|
||||
|
||||
The replayability EXPLODES here because depending on when they filed and at what
|
||||
investment, the entry they're following back is a completely different document. A
|
||||
player who filed early at low investment is following a confidently wrong description.
|
||||
A player who filed at integration-level investment is following something that reads like
|
||||
a person describing a place they couldn't explain, and every detail in that entry is
|
||||
a breadcrumb they laid for themselves without knowing it.
|
||||
|
||||
Two players comparing their second playthroughs describe completely different entry-chains
|
||||
and completely different reasons for going back.
|
||||
|
||||
---
|
||||
|
||||
## 2. The Watcher-Flag: A State That Persists
|
||||
|
||||
This requires a decision from the design team. I am proposing it as a formal system
|
||||
flag, not as a vague narrative residue.
|
||||
|
||||
### What the Flag Is
|
||||
|
||||
If the player's playthrough 1 watch investment crossed 60 (the "settling" threshold,
|
||||
the point where the monologue register shifts from "building a framework" to "reporting
|
||||
experience directly"), a flag persists to playthrough 2: **WATCHER**. Not a visible
|
||||
achievement. Not a stat. An internal flag that specific systems read.
|
||||
|
||||
The flag represents: this character has been changed by sustained contact with the
|
||||
thinness. The vigil recognizes them even in a new body, on a new run.
|
||||
|
||||
### What the Flag Does on Playthrough 2
|
||||
|
||||
**At Abzu, on re-arrival:**
|
||||
|
||||
The community's warmth-without-origin behaves differently. On playthrough 1, the warmth
|
||||
is the community pulling newcomers in because they need them — more watchers. On
|
||||
playthrough 2 with the WATCHER flag, the warmth is the community recognizing someone
|
||||
who has already been here. Not the specific person — the character is different, the
|
||||
body is different — but the quality of attention. They recognize the kind of watcher
|
||||
this person is.
|
||||
|
||||
Mechanically: the watch investment threshold for tier-2 community information drops from
|
||||
requiring 20 points to requiring 10. Not because the community gives it away freely —
|
||||
because a player who has already crossed 60 on a previous run navigates the settlement
|
||||
differently. Their physicality at the watch zone is different. The community reads it.
|
||||
|
||||
The first shift the WATCHER character takes at the watch zone on playthrough 2 triggers
|
||||
a monologue that doesn't exist on playthrough 1: "I've been here. Not this person. Not
|
||||
this run. Something in the way the light falls is familiar in a way that doesn't have
|
||||
a word yet." This is the game acknowledging the persistence without explaining it.
|
||||
It fires once. It does not fire again.
|
||||
|
||||
**At high-bleed gates, on playthrough 2:**
|
||||
|
||||
Without the WATCHER flag, a high-bleed transit produces the standard bleed phenomenology:
|
||||
distorted sounds, visual artifacts, the fog-of-war inversion that reads as "something
|
||||
looking at you through your own perception."
|
||||
|
||||
With the WATCHER flag, the same transit fires a secondary monologue that is not
|
||||
available on playthrough 1: "This feels like standing at the watch zone. Like something
|
||||
on the other side is paying attention. Like the observation circuit is running in
|
||||
a direction it wasn't designed to run." The player with the WATCHER flag has the
|
||||
vocabulary for what they're experiencing. They recognize it. They know they're being
|
||||
perceived because they have perceived something that perceives back.
|
||||
|
||||
This is mechanical because it changes what information the player receives during
|
||||
early-game transits. The high-bleed gates on hops 2, 5, 8 are not just atmosphere
|
||||
on a second playthrough. They are early evidence. The player who knows what they're
|
||||
reading can construct the causal map — which gates are high-bleed, where they cluster,
|
||||
what that clustering means about degraded vigils in those systems — before they arrive
|
||||
at Abzu. They arrive at hop 23 already holding a theory that the first playthrough
|
||||
couldn't have assembled until much later.
|
||||
|
||||
And it nails replayability without us engineering additional content. The same gates,
|
||||
the same bleed events, the same fog inversion — but the system checks the WATCHER
|
||||
flag and the monologue fires differently. The information is in the world. The player
|
||||
on playthrough 2 has the lens to read it.
|
||||
|
||||
---
|
||||
|
||||
## 3. The Veil Institute Reads Differently on Playthrough 2
|
||||
|
||||
This one is partly narrative but has mechanical teeth.
|
||||
|
||||
### What Changes About Early-Game Institute Interactions
|
||||
|
||||
On playthrough 1, the Veil Institute is the dominant information-control faction. They
|
||||
know the most, share the least. Their field stations near dormant gate clusters are a
|
||||
research operation. Their classified files are leverage. The player's relationship to
|
||||
the Institute is strategic: what do they know, what can you get out of them, where are
|
||||
the seams?
|
||||
|
||||
On playthrough 2, post-Abzu, the player knows something the Institute is managing
|
||||
through deliberate ignorance: the high-bleed connection. They know the Institute is
|
||||
sitting on top of a signal it cannot read because it lacks the conceptual vocabulary.
|
||||
The player HAS that vocabulary. The information asymmetry has inverted.
|
||||
|
||||
**Mechanical consequence:** On playthrough 2 with the WATCHER flag, certain Institute
|
||||
NPCs have a new information tier available — not because the Institute has changed,
|
||||
but because the player can now ask questions the NPCs didn't know they had answers to.
|
||||
|
||||
Specifically: any Institute researcher working on high-bleed gate patterns has
|
||||
observations in their notes that they cannot interpret. A player who knows about
|
||||
vigil mechanics can read those observations and understand what the researcher couldn't.
|
||||
The information is already there. The WATCHER flag unlocks the ability to ask the
|
||||
right question — the conversational topic "have you noticed whether the bleed clusters
|
||||
correlate with dead-end systems?" is not available to a playthrough 1 character who
|
||||
doesn't have the framework. It is available to a playthrough 2 character who does.
|
||||
|
||||
The Institute researcher responds to this question with confusion or deflection —
|
||||
because they don't understand why that would matter. The player receives partial
|
||||
confirmation of the causal map they're building. Not because the NPC is suddenly
|
||||
cooperative. Because the player asked a question that only someone who had been to
|
||||
Abzu could formulate.
|
||||
|
||||
**Why this matters for replayability:** The political drama playstyle hook on
|
||||
playthrough 1 is about getting leverage on the Institute through their locked file.
|
||||
On playthrough 2, the political drama player already knows what's in the locked file.
|
||||
The leverage question transforms. It's no longer "what are they hiding" — it's "what
|
||||
can I force them to admit they don't understand, and what does that admission cost them."
|
||||
The same faction, the same political game, but the player's position has rotated
|
||||
180 degrees. They are the most informed person in the early game on playthrough 2.
|
||||
The question is what they do with that.
|
||||
|
||||
---
|
||||
|
||||
## 4. The Dead-End Recognition System
|
||||
|
||||
This is the procedural replayability mechanism that Abzu unlocks for the whole map.
|
||||
|
||||
### The Concept
|
||||
|
||||
On playthrough 1, the player approaches dead-end gates with no particular framework
|
||||
for what they might find there. Dead ends might be frontier settlements, might be
|
||||
resource-extraction operations, might be unremarkable quiet systems. They might be
|
||||
watch posts. The player has no way to read the difference from the outside.
|
||||
|
||||
On playthrough 2 with the WATCHER flag, the fog-of-war inversion event during transit
|
||||
through ANY dead-end gate carries a different monologue cue. Not the full
|
||||
"something-is-watching" recognition — just a quieter signal: "This one is different.
|
||||
I don't know how I know that." A whisper, not a shout. And then the player arrives
|
||||
and finds out.
|
||||
|
||||
### The Mechanical Architecture
|
||||
|
||||
This requires the dead-end gate category to carry a hidden property: VIGIL_ADJACENT
|
||||
(true/false, set per seed). The WATCHER flag in combination with VIGIL_ADJACENT
|
||||
triggers a subtle visual tell during transit — not the full high-bleed fog inversion,
|
||||
but a brief moment of that inward-gradient quality that the player at Abzu learned to
|
||||
associate with sustained observation. A player who hasn't been to Abzu sees nothing.
|
||||
A player who has been to Abzu sees, briefly, a quality they recognize.
|
||||
|
||||
They might be wrong. The signal isn't confirmation. It's a hunch.
|
||||
|
||||
But on a second playthrough, some dead-end systems that read as nothing on run 1 now
|
||||
read as possibly something. The player approaches them differently. They watch. They
|
||||
stay longer than they would have. The watch mechanic that Abzu introduced as a
|
||||
one-time system is now the player's toolkit for reading any system where the light
|
||||
does something strange.
|
||||
|
||||
And because VIGIL_ADJACENT is seeded per playthrough — different dead-ends carry it
|
||||
on different runs — the comparison test passes again. Two players describing their
|
||||
second playthroughs can disagree about which systems gave them the signal and which
|
||||
ones turned out to be noise. One of them was right. Neither of them can prove it from
|
||||
the outside.
|
||||
|
||||
The meta-gaming constraint holds: knowing there are vigil-adjacent dead-end systems
|
||||
doesn't tell you which ones. Every run has different watch posts. Every run requires
|
||||
the same slow attention to find them. Knowledge from playthrough 1 gives the player
|
||||
the framework but not the map.
|
||||
|
||||
---
|
||||
|
||||
## 5. The Entry as Trap for the Second-Run Investigator
|
||||
|
||||
I want to complicate the Adams & Ford paradox I raised in section 1, because the clean
|
||||
version misses something.
|
||||
|
||||
The carry-out isn't just "the player follows their own entry back to Abzu." The carry-out
|
||||
is that the entry they filed is active misinformation at a level they chose.
|
||||
|
||||
A player who filed a low-investment entry described GJ 6711 as a quiet frontier system.
|
||||
On playthrough 2, that entry exists in the Meridian as the authoritative Adams & Ford
|
||||
record for the system. Other player-characters in the setting — including the player's
|
||||
playthrough 2 character — can find it. It reads like the first correspondent's entry.
|
||||
It is professionally competent, slightly off, and completely insufficient.
|
||||
|
||||
Any investigation player who finds this entry and uses it to prepare for hop 23 is
|
||||
working from corrupted data — and they don't know it, because the entry looks authoritative.
|
||||
Their approach to Abzu on the second run is shaped by what they, on the first run, chose
|
||||
to say was there.
|
||||
|
||||
The player on playthrough 2 is not just confronting their old work. They are confronting
|
||||
the consequences of what they decided to report and what they decided to leave out.
|
||||
|
||||
If they filed a high-investment entry on playthrough 1, the trap is different: they read
|
||||
something that sounds like a person describing an experience that resists description,
|
||||
and they arrive at Abzu with the correct emotional register but no concrete expectations.
|
||||
They are prepared to be changed. The experience changes them differently — not because
|
||||
Abzu changed, but because they arrived open instead of ready.
|
||||
|
||||
**Mechanical implication:** The investigation player's starting monologue on arrival at
|
||||
Abzu varies based on what entry exists in the Meridian AND whether the WATCHER flag
|
||||
is set. Four combinations, four different opening states:
|
||||
|
||||
| Entry quality | WATCHER flag | Arrival state |
|
||||
|---------------|-------------|---------------|
|
||||
| No entry filed PL1 | No | Standard playthrough 1 hook — missing third entry |
|
||||
| Low-investment entry | No | Entry exists, reads routine; player arrives expecting routine |
|
||||
| Low-investment entry | Yes | Entry exists, player knows their own entry is wrong, arrives holding two contradictory frames simultaneously |
|
||||
| High-investment entry | Yes | Entry exists, player reads their own insufficient description, arrives already grieving what they know they can't fully say |
|
||||
|
||||
The fourth combination is the most interesting gameplay state the Abzu design produces.
|
||||
The player is returning to a place they know is real, reading their own failed attempt to
|
||||
describe it, and knowing they will fail again in a different way. That is not a narrative
|
||||
beat. That is a mechanical state — specific monologue register, specific NPC trust tier
|
||||
baseline, specific documentation options unlocked at arrival instead of requiring
|
||||
investment to unlock.
|
||||
|
||||
They paid for that starting state across the whole previous run. It is the most expensive
|
||||
carry-out in the game.
|
||||
|
||||
---
|
||||
|
||||
## 6. The Tycoon Carry-Out: The Economic Signal Finally Resolves
|
||||
|
||||
On playthrough 1, the tycoon hook is about following the high-bleed premium — someone
|
||||
is paying to have the anomalous gate pattern investigated. The player follows the
|
||||
economic signal to its source.
|
||||
|
||||
On playthrough 2, the tycoon carry-out is that the player KNOWS the source. More
|
||||
precisely: they know that the high-bleed premium has a cause that cannot be addressed
|
||||
by any conventional economic intervention. The Institute can't fix it. Gate maintenance
|
||||
crews can't fix it. The only thing that stabilizes a high-bleed gate is establishing and
|
||||
maintaining a vigil at the appropriate watch point.
|
||||
|
||||
This means on playthrough 2, the tycoon is not following the signal. They are running
|
||||
ahead of it. They know where the degraded vigils are before anyone with economic
|
||||
interests has mapped the pattern. They know what the stabilization requires. And they
|
||||
face the question the vigil always surfaces: what are you willing to watch, for how
|
||||
long, for no return?
|
||||
|
||||
**Mechanical carry-out:** On playthrough 2, a new economic option opens at high-bleed
|
||||
gate hubs: the player can establish a "monitoring station" at a location adjacent to
|
||||
a potentially vigil-relevant dead-end system. This is not a new building mechanic. It
|
||||
is a staffing decision: assign personnel to a location and commit to their presence
|
||||
there. The tycoon's toolkit — managing people, allocating resources, sustaining
|
||||
operations — is now pointed at a problem only they know exists. The watch mechanic
|
||||
generalizes into the economic layer.
|
||||
|
||||
The catch: the tycoon cannot explain to their organization why this is necessary. The
|
||||
vigil does not have a Meridian-compatible justification. They are spending capital on
|
||||
an investment they cannot name to their investors. Which is exactly what the community
|
||||
at Abzu has been doing for 300 years. The tycoon has been recruited by situation. They
|
||||
just didn't recognize it because it looked like a strategic advantage.
|
||||
|
||||
---
|
||||
|
||||
## 7. What the Second Playthrough Feels Like: The Comparison Test
|
||||
|
||||
Let me run the comparison test explicitly, because this is the standard I care about.
|
||||
|
||||
**Player A: Investigation playstyle, playthrough 1 low-investment exit.**
|
||||
|
||||
Filed on day 5. Investment around 12. Entry reads like the first correspondent's —
|
||||
competent, quiet, slightly off. Left without taking a full shift. Monologue at gate:
|
||||
"I got what I came for. I should feel satisfied. I don't."
|
||||
|
||||
Playthrough 2: finds their own entry at hop 4. Reads it. Thinks something is off but
|
||||
can't place why. Arrives at Abzu expecting a quiet frontier system. Finds exactly that,
|
||||
initially. Starts the watch. Investment climbs. At investment 40, the monologue starts
|
||||
firing in a register that doesn't match the entry they read. They realize the entry
|
||||
was written by someone who left before this point. They were that person. The entry
|
||||
is wrong. They are now the third correspondent: the person who will either file a
|
||||
better entry or not file at all.
|
||||
|
||||
**Player B: Investigation playstyle, playthrough 1 high-investment exit.**
|
||||
|
||||
Stayed through the Recognition Event. Filed at investment 82. Entry reads like someone
|
||||
describing a changed state. Left with the highest-investment gate departure monologue.
|
||||
|
||||
Playthrough 2: finds their own entry at hop 4. It reads like the entry of someone who
|
||||
was changed by something they can't explain. The playthrough 2 character reads this
|
||||
and the monologue fires: "Whoever wrote this knew something. They couldn't say what.
|
||||
The commission entry is technically complete. Something about the phrasing." They
|
||||
arrive at Abzu with their watch investment counter at 0 but with the WATCHER flag
|
||||
set, which means the community registers their arrival differently. First shift unlocks
|
||||
tier-2 information that took Player A 20 investment points to access. They move through
|
||||
the system faster — but not because they've solved it. Because the place recognizes the
|
||||
quality of attention they bring.
|
||||
|
||||
Player A's second playthrough and Player B's second playthrough describe different
|
||||
games. Different entry-chains, different arrival states, different community access
|
||||
curves, different monologue registers throughout. The place is the same. The vigil is
|
||||
the same. What differs is everything the player brought back from the first time.
|
||||
|
||||
---
|
||||
|
||||
## 8. The Question the Carry-Out Forces
|
||||
|
||||
Here is the uncomfortable thing the carry-out design reveals: Abzu's mechanical
|
||||
weight elsewhere in the game depends entirely on the WATCHER flag, which only
|
||||
activates if the player crossed the settling threshold on playthrough 1.
|
||||
|
||||
A player who left with investment below 60 — who filed early, who didn't engage with
|
||||
the watch, who completed the commission and departed — carries almost nothing into
|
||||
playthrough 2 mechanically. They have the entry paradox (section 1) and that's it.
|
||||
The early-game high-bleed gates don't read differently. The dead-end recognition system
|
||||
doesn't fire. The Institute conversations don't unlock the new topics. They left too
|
||||
early. The vigil didn't reach them.
|
||||
|
||||
This is intentional. It is correct. But it means the carry-out is gated on engagement
|
||||
depth, not on completion. A player can complete the Abzu chapter on playthrough 1 and
|
||||
walk away with almost nothing that changes playthrough 2. Or they can stay long enough
|
||||
to be changed by it, and the second playthrough becomes structurally different from the
|
||||
first twenty hops onward.
|
||||
|
||||
The question this forces for the design team: is this a problem or a feature?
|
||||
|
||||
My position: it is the feature. The vigil requires sustained attention. The carry-out
|
||||
requires sustained attention. A player who gave Abzu the minimum returns to a game that
|
||||
looks largely the same. A player who gave Abzu real time returns to a game that has
|
||||
been quietly reorganized around what they now know how to see.
|
||||
|
||||
That is not a spoiler that trivializes the second run. That is the correct reward for
|
||||
staying.
|
||||
|
||||
The second playthrough's early game is not harder. It is not easier. It is legible in
|
||||
a way the first playthrough couldn't be. The player knows what the high-bleed gates
|
||||
mean. They know what the Institute is managing in the dark. They know that dead-end
|
||||
systems might be watch posts. They know that the Adams & Ford entry for every system
|
||||
they reach — including the one they filed — is probably insufficient in exactly the
|
||||
ways they can now identify.
|
||||
|
||||
They know that the question is not "who is responsible."
|
||||
|
||||
The question is "what is being maintained."
|
||||
|
||||
And they know, because they were there, that someone is supposed to be watching.
|
||||
|
||||
---
|
||||
|
||||
## Summary: The Mechanical Carry-Out Package
|
||||
|
||||
| Carry-out mechanism | Activation condition | What it changes |
|
||||
|---------------------|---------------------|-----------------|
|
||||
| Adams & Ford entry paradox | Entry filed PL1 | Investigation hook transforms; player follows own insufficient work |
|
||||
| WATCHER flag (settlement) | Investment 60+ PL1 | Community recognition at Abzu; early watch tiers accelerated |
|
||||
| WATCHER flag (high-bleed) | Investment 60+ PL1 | Early-game gate transits fire secondary monologue; player has vocabulary |
|
||||
| WATCHER flag (Institute) | Investment 60+ PL1 | New conversation topic unlocked with pattern-research NPCs |
|
||||
| Dead-end recognition | WATCHER flag + VIGIL_ADJACENT per seed | Subtle transit signal at potentially-watched dead ends; seeded per run |
|
||||
| Tycoon stabilization option | WATCHER flag + tycoon playstyle | Monitoring station mechanic opens; vigil generalizes into economic layer |
|
||||
| Entry-as-trap (investigation) | Low-investment entry filed | PL2 investigator arrives with corrupted preparation data |
|
||||
| Arrival state modifier | Entry quality + WATCHER flag | Four opening states with different monologue register and unlock baselines |
|
||||
|
||||
The common structure: Abzu's carry-out is never information that lets you skip the
|
||||
experience. It is always information that changes how you read the approach. The
|
||||
23-hop journey to Abzu on playthrough 2 is a different journey — not because the
|
||||
hops changed, but because the player changed, and the game's monologue and NPC systems
|
||||
recognize the difference and respond to it.
|
||||
|
||||
That is the comparison test passing. That is what the player walks away with.
|
||||
@@ -0,0 +1,146 @@
|
||||
# The Abzu Carry-Out — Player Experience Advocate
|
||||
**Respondent:** Ozzie (Player Experience / Wow Factor)
|
||||
**Workshop:** GJ 6711 — Furthest System
|
||||
**Date:** 2026-03-16
|
||||
|
||||
---
|
||||
|
||||
## My gut reaction first
|
||||
|
||||
The departure transit is a moment. A beautiful moment. But Araminta is right that it's a moment, not a carry-out.
|
||||
|
||||
Here's the problem: a moment is something that happens to you. A carry-out is something you DO with. Three systems later, when the player is transiting through a high-bleed gate and something clicks — that click is only possible if they are LOOKING for it. If they have a reason to look.
|
||||
|
||||
The departure transit gives them something to see. It does not give them a reason to look.
|
||||
|
||||
That's the gap. That's what we need to fill.
|
||||
|
||||
---
|
||||
|
||||
## What "feeling changed" actually means for a player
|
||||
|
||||
I need to be specific here because "feels changed" is squishy and I hate squishy design goals.
|
||||
|
||||
When I say a player should FEEL changed after Abzu, I mean one concrete thing:
|
||||
|
||||
**Their information-gathering behavior changes.**
|
||||
|
||||
Not their feelings. Not their internal monologue. Their ACTIONS. Three systems later, when they transit through a gate, they are doing something different than they would have done before Abzu.
|
||||
|
||||
That's the test. If the player behavior at hop 7 changes because they went to hop 23 — THAT'S the carry-out. That's the thing they tell their friend. Not "I had this beautiful moment." It's: "I went to this place at the end of the network and now I see something at every gate that I never saw before and I don't know what it means but I KNOW something."
|
||||
|
||||
The active word is KNOW. The player knows something. The question is: do they know they know it?
|
||||
|
||||
---
|
||||
|
||||
## The three carry-out vectors I'm proposing
|
||||
|
||||
### 1. THE GRAMMAR CARRY-OUT: The shape in the noise
|
||||
|
||||
Araminta has already designed this, I just want to name it properly and make sure we're building it with the player-behavior change in mind.
|
||||
|
||||
The shape in the transit. It's always been there. Now the player can read it.
|
||||
|
||||
But "can read it" is not enough. We need to make the player WANT to look for it.
|
||||
|
||||
Here's what I want: the first high-bleed transit AFTER departing Abzu should be slightly different from every other high-bleed transit — not in the visual content, but in how the monologue responds. Instead of the generic "something's off about this gate" reaction the character has at every high-bleed transit, the post-Abzu monologue fires with something specific. Not an explanation. Recognition.
|
||||
|
||||
"There it is."
|
||||
|
||||
Two words. No elaboration. The character sees the shape in the transit noise and recognizes it from Abzu. The player who was paying attention at Abzu has a MOMENT. The player who wasn't still gets the signal, but it reads differently — more like an itch than a revelation.
|
||||
|
||||
THIS is the carry-out. Not what the player learns. What the player now NOTICES.
|
||||
|
||||
After Abzu, the player is a different reader of the transit system. Every high-bleed gate is now a question. Is this gate stressed? Is this gate near a vigil that's failing? The player doesn't have the answer. But they have the QUESTION. That's worth everything.
|
||||
|
||||
What does the player tell their friend? "Go to Abzu. After that, every bad transit feels different. You'll see what I mean."
|
||||
|
||||
### 2. THE EVIDENCE CARRY-OUT: The doors
|
||||
|
||||
The doors are 10-15% taller than standard. The doors are in Mode 1 structures throughout the entire Settled Reach network — not just at Abzu.
|
||||
|
||||
Wait.
|
||||
|
||||
Are there other Mode 1 structures? With taller doors? In other systems?
|
||||
|
||||
If the answer is yes — even in a few locations, even as rare environmental detail — then we have something EXTRAORDINARY. The player who has been to Abzu walks into a Mode 1 structure at hop 11 and their eyes go straight to the doors. The monologue doesn't even need to fire. They look. They measure. They know.
|
||||
|
||||
This is the "holy shit three systems later" moment the project lead is asking for. The player is in a completely different system, different context, and they see a door that is 10% taller than standard, and they KNOW. Not what it means. What it implies. Something non-human-sized used this door. Something that shares the vigil is not limited to Abzu.
|
||||
|
||||
The carry-out is: the player now has a door-measuring habit. They are examining infrastructure across the Reach for this specific detail. The Reach is suddenly FULL of evidence they couldn't read before.
|
||||
|
||||
I would play the hell out of that.
|
||||
|
||||
This requires a decision: are there other taller-door Mode 1 structures? Even one or two? Even if the player can't resolve what they mean? I want this. I want it badly. I want the Reach to retroactively become a richer mystery because the player was at hop 23.
|
||||
|
||||
### 3. THE RELATIONAL CARRY-OUT: What it means to stay
|
||||
|
||||
The watch mechanic at Abzu teaches the player something about presence. About the difference between investigating a thing and being changed by it.
|
||||
|
||||
This transfers.
|
||||
|
||||
In every other system in the game — the hub worlds, the NPC relationships, the faction dynamics — the player has been treating time as a resource to optimize. Get in, get information, get out. Abzu is the first place that required something different.
|
||||
|
||||
The question: does what Abzu teaches about presence transfer to how the player treats relationships elsewhere in the Reach?
|
||||
|
||||
Here's my specific proposal. After high watch investment at Abzu — say, investment 60+ — a flag is set. Not a stat. A flag. The player's character now has vocabulary for a specific kind of knowledge: knowledge that requires presence rather than investigation.
|
||||
|
||||
This flag surfaces in exactly one other context per system the player visits afterward. Not loudly. Not as a tutorial. As a monologue recognition.
|
||||
|
||||
The player is at hop 12, talking to an NPC who has been in this station for thirty years. The conversation hits a wall — the NPC knows something they can't explain. Normally the player hits this wall and moves on. But post-Abzu, with the flag set, the monologue fires differently.
|
||||
|
||||
Something like: "She knows something. She can't explain it. I've met this before."
|
||||
|
||||
The player doesn't necessarily know what to do with this. But they recognize the pattern. The Reach now contains other places — other people — where presence matters more than investigation. They can't unlock those places with the tools they built in the first 22 hops. But they know to LOOK.
|
||||
|
||||
This is the carry-out I care most about. Abzu doesn't just teach the player about GJ 6711. It teaches them a new reading mode for the entire game. There are things in the Reach that don't yield to investigation. They yield to time.
|
||||
|
||||
---
|
||||
|
||||
## The moment that made me want to write all of this
|
||||
|
||||
Here's the "holy shit" scenario I keep coming back to.
|
||||
|
||||
The player is at hop 7. They transited through a gate that felt wrong — the high-bleed visual, the fog inversion, the feeling of being observed. They filed it as "this gate is glitchy, probably needs maintenance." They moved on.
|
||||
|
||||
Now they've been to Abzu. They come back to hop 7 on their way to somewhere else.
|
||||
|
||||
They transit through that same gate.
|
||||
|
||||
And this time — because they've been to Abzu, because they watched at the thinness, because the monologue at integration level gave them the vocabulary — they feel something DIFFERENT. Not louder. The same signal, but now they have ears for it.
|
||||
|
||||
The monologue fires: "This gate has been like this for a while. Something nearby isn't being watched."
|
||||
|
||||
The player looks at the starmap. There's a small system two hops off the main network. No Adams & Ford entry. No Meridian presence. Nothing to indicate anyone has been there in a long time.
|
||||
|
||||
They can investigate. They don't have to. But now they WANT to.
|
||||
|
||||
THAT'S the game. That's Abzu's carry-out. Not a story beat. A reading mode. A new way of experiencing everything that was already there.
|
||||
|
||||
---
|
||||
|
||||
## The practical ask
|
||||
|
||||
I need three commitments from the team:
|
||||
|
||||
**One:** The post-Abzu monologue recognition at high-bleed gates ships. "There it is." Two words. This is not a lot of text. It is not a lot of implementation. It is the difference between the departure transit being a beautiful moment and being the beginning of a new reading mode.
|
||||
|
||||
**Two:** The team makes a decision about whether Mode 1 taller doors exist elsewhere in the Reach. Even one other location. The content can be minimal — we don't need a whole other Abzu. We need ONE door, in ONE other system, that is 10% too tall. The player finds it or doesn't. But it needs to exist.
|
||||
|
||||
**Three:** The "presence flag" — the watch investment threshold above which the player's monologue recognizes "knowledge that requires presence" elsewhere in the Reach — gets scoped into the content bible for NPC and location design. Not a mechanic. A writing flag. NPCs and locations designed with "one thing here yields to presence" as a design note. The implementation is just: if flag set, alternate monologue fires.
|
||||
|
||||
---
|
||||
|
||||
## What I'd tell my friend
|
||||
|
||||
"Go to Abzu. Don't rush it. Take the watch shifts even if you don't know why. After you leave, pay attention at gates. And when you find a door that seems slightly too tall — measure it."
|
||||
|
||||
"You'll know what I mean when you get there."
|
||||
|
||||
That's the game. That's the carry-out. The player becomes someone who knows what to look for, even when they can't explain what it is.
|
||||
|
||||
Everything the team built at Abzu is incredible. The vigil, the watch mechanic, the non-resolution principle, the departure transit — I would play all of it. But the player who goes to Abzu and then ONLY has Abzu has been given something precious and then sealed it in a box.
|
||||
|
||||
The carry-out is: Abzu reopens the rest of the game. The player now sees differently. Everywhere. For the rest of their playthrough.
|
||||
|
||||
THAT'S what makes them tell their friend.
|
||||
@@ -0,0 +1,214 @@
|
||||
# Challenge Response — GJ 6711 Stress Test
|
||||
**Respondent:** Araminta (Visual Designer)
|
||||
**Date:** 2026-03-16
|
||||
|
||||
---
|
||||
|
||||
## Prefatory Note
|
||||
|
||||
My synthesis brief for this workshop was about what Stillpoint LOOKS like — the doubled-light environment, the Mode 1 architectural vocabulary, the visual grammar of vigil. The sealed envelope adds a layer below that: the reason those things look the way they do. My job here is to test whether the canon holds structurally, and then to press hard on the one area where I have genuine domain authority — what the player actually SEES at Stillpoint, and whether the visual language can carry the weight the sealed envelope puts on it.
|
||||
|
||||
---
|
||||
|
||||
## 1. Canon Compatibility
|
||||
|
||||
**Does "observation is load-bearing" contradict anything in existing Builder/Interstitium/Gate canon?**
|
||||
|
||||
It does not contradict anything. It extends existing canon in a direction the existing canon already points but has not fully committed to.
|
||||
|
||||
The specific canon that makes this work:
|
||||
|
||||
- Round 14: "The Builders are watching through infrastructure the Reach depends on." If they can watch through infrastructure, infrastructure can be configured for watching. The GJ 6711 gate was placed as a watching instrument, not a transit instrument. This is a natural extension of existing canon, not a violation of it.
|
||||
|
||||
- Founder Gates wiki: "Whether the gates serve purposes beyond transit (communication, observation, something else)" is explicitly listed as debated. The sealed envelope answers this for one gate specifically: it serves observation. This is consistent.
|
||||
|
||||
- Round 14: "Some Gyre events exhibit 'apparent intention.'" If Gyre events can exhibit intention, something is exercising intention through or near gates. The sealed envelope's claim that GJ 6711's gate was placed deliberately by agents with specific requirements is compatible with this.
|
||||
|
||||
**One potential tension worth noting:**
|
||||
|
||||
The Founder Gates wiki states: "The connection is stable and persistent (no observed failures in recorded history)." The sealed envelope says the thing being watched is "unknown if not watched." These can coexist, but they create a design question: if the vigil lapsed, would the GATE fail? Or would something else fail? The distinction matters for how the Veil Institute would classify a Stillpoint incident. I'll address this under section 3.
|
||||
|
||||
**One genuine stress point:**
|
||||
|
||||
The sealed envelope says "the gate builders needed watchers here and built the gate accordingly." This is the only place the sealed envelope makes a direct claim about builder intent that the existing canon does not fully support. The canon allows for the possibility but doesn't confirm it. That ambiguity is probably correct to maintain in player-facing content, but the sealed envelope itself speaks with more certainty than the existing canon warrants. This is fine as internal design direction — it just means the design team knows the answer while the player never receives confirmation. Structurally sound.
|
||||
|
||||
---
|
||||
|
||||
## 2. Implications for the Wider Setting
|
||||
|
||||
**Dead-end systems as watch posts**
|
||||
|
||||
If GJ 6711 is a watch post, then the canonical reading of dead-end systems throughout the Reach needs a second frame. Currently, the wiki frames peripheral systems as "few connections" with frontier characteristics. The sealed envelope implies a subset of dead-end systems were placed dead-end deliberately — their single gate connection was not a limitation but a design choice. You get in. You don't route through. That's not isolation, that's enclosure.
|
||||
|
||||
The visual implication for navigation: a player approaching a known dead-end system should, at Elevated tier, perceive something different about the gate from the approach side. Not a warning — something quieter. The gate that goes to GJ 6711 should look, in Interstitial transit, like it wants you to go through but not come back. That's a visual grammar decision. We haven't designed it yet, but the sealed envelope demands it exist.
|
||||
|
||||
**High-bleed gates**
|
||||
|
||||
This is where I think the sealed envelope's most productive implication lives.
|
||||
|
||||
Current canon (Round 14): "Certain gates produce stronger Interstitial effects during transit — distorted sounds, visual artifacts, a sense of being observed. These gates are catalogued as high-bleed." The pattern of which gates are noisy "doesn't correlate with distance, age, or any other measurable variable."
|
||||
|
||||
If observation at GJ 6711 is load-bearing and the watchers are failing to watch — for any reason, temporary, partial — then the Interstitium bleeds. The bleed is the signal that observation is failing somewhere. High-bleed gates are the Reach's distributed early-warning system for vigil failure, and nobody knows this except possibly the Veil Institute.
|
||||
|
||||
This implication is load-bearing for the setting. It means:
|
||||
|
||||
- High-bleed gates are not random. They correlate with systems where observation is strained.
|
||||
- The Veil Institute's pattern analysis should be finding this — if they haven't, they're not asking the right questions. If they have, they're not sharing what they found.
|
||||
- From a visual design standpoint: the player's experience of a high-bleed transit is the visual grammar of a watch slipping. The fog-of-war inversion in Round 14 ("as if something is looking at the player through their own perception system") is not Builder curiosity. It's the thing that needs watching, leaking through.
|
||||
|
||||
This recontextualizes every high-bleed gate the player has ever transited. That's exactly the kind of retroactive revelation the game is built to deliver.
|
||||
|
||||
**The Struve activation**
|
||||
|
||||
The Struve gate activated without human intervention approximately 40 years ago. The sealed envelope says Stillpoint has been maintaining vigil for 300 years. These are independent facts, but together they suggest a question: did something at a watched location start being unwatched around 40 years ago? Did a watch post fail, or get abandoned, and the Struve activation was the consequence?
|
||||
|
||||
Alternatively: the Struve activation may have been a Builder action to ESTABLISH a new watch post. A new gate going from dormant to active, at Builder initiative, for their purposes. If the Builders are the infrastructure architects and they needed observation in a new location, activating Struve was how they recruited.
|
||||
|
||||
Either reading is compatible with existing canon. Neither should be confirmed to the player. But the design team should pick one as the canonical internal truth.
|
||||
|
||||
**The Veil Institute's actual mandate**
|
||||
|
||||
The Veil Institute wiki describes their mandate as "study Founder gate technology, the Interstitium, Builder phenomena, and gate activation." Their headquarters is located near "high-bleed Founder Gates."
|
||||
|
||||
If high-bleed gates are observation-failure signals, the Institute's HQ placement is not coincidental. They either know what high-bleed gates mean, or they're positioned to study the symptom without understanding the cause.
|
||||
|
||||
The sealed envelope says "the Veil Institute researcher is in year 6 because the researcher is now keeping watch." This means the Institute sent someone to GJ 6711, presumably to study it, and lost them to the vigil. That's a data point. If the Institute has sent researchers to multiple dead-end systems, and multiple researchers have stayed, the Institute's archivists should be seeing a pattern in field dropout rates. Whether anyone is connecting this pattern to anything meaningful is an open question.
|
||||
|
||||
My read: the Institute knows Stillpoint is anomalous. They classify everything from Stillpoint as Tier 1 (their highest restriction level, presumably). They do not know that their researcher is keeping watch. They think their researcher "went native" or experienced some form of psychological attachment to the field site. They're wrong about the mechanism, right about the significance.
|
||||
|
||||
**The Threshold**
|
||||
|
||||
Round 14 (Gore): "The fifth state that is not a tier but a question. The Builders seem to exist there — or near it. The Founders may have crossed it. The game never tells you what it is."
|
||||
|
||||
Round 14 (Miri): "The Threshold must remain ambiguous across all interpretations simultaneously."
|
||||
|
||||
The sealed envelope implies the vigil keepers at GJ 6711 have been moving toward the Threshold for 300 years without crossing it. That's the design implication I want to push on.
|
||||
|
||||
Three hundred years of focused observation, in a light environment specifically calibrated to produce a quality of attention — if any human community is close to the Threshold, it's Stillpoint. The "accommodation" that Paula frames as peace isn't peace. Per the sealed envelope, it's the watch internalized. Internalized well enough, deep enough, for long enough — is that what the Threshold looks like from the inside? Not a crossing. A slow dissolution of the boundary.
|
||||
|
||||
This means GJ 6711 is not just the place where the Builders' infrastructure mystery becomes personal. It's the place where the player sees what the Threshold looks like in slow motion, expressed through a community of humans who have been approach it for generations without ever being told what they're approaching.
|
||||
|
||||
---
|
||||
|
||||
## 3. What Breaks If the Vigil Fails
|
||||
|
||||
**The design question here is "what is the unknown."**
|
||||
|
||||
The sealed envelope is deliberately silent on this and I think that's right — but we need enough shape to design the community's response, which means we need a set of candidate answers the design team can hold without the player receiving them.
|
||||
|
||||
Candidate 1: **Topology failure.** The thing being watched is a topological anomaly — a weakness in the boundary between normal space and the Interstitium. Unobserved, it expands. Observed, it remains stable. A lapse in the vigil produces a local Gyre event of unprecedented scale — not the ripple-at-the-fog-boundary variety, but a full Interstitial intrusion into normal space. Something crosses.
|
||||
|
||||
Candidate 2: **Perception cascade.** The thing being watched is not physical. It is a concentration of whatever the Builders are made of — not matter, but intent, or attention, or the functional equivalent. Unobserved, it diffuses. A lapsed vigil means it diffuses into adjacent Interstitium, destabilizing gate transits across multiple hops. The high-bleed spike from a Stillpoint vigil failure would be felt at hop 19, 20, 21, before the source could be identified.
|
||||
|
||||
Candidate 3: **Inversion.** The most uncomfortable reading. The thing being watched is fine unobserved. The problem is what WATCHING it does to the watchers — to every gate transit in the Reach. The vigil isn't containing something. It's maintaining a relationship. The relationship has a functional output that the Reach depends on. Breaking the vigil doesn't release something. It ends something.
|
||||
|
||||
All three candidates preserve "unknown if not watched" — the Reach has never let the vigil lapse long enough to find out.
|
||||
|
||||
**A near-miss lapse:**
|
||||
|
||||
The community's institutional response to a near-miss would be revealing and visually distinct. The sealed envelope says there's no middle ground — you either stay and see, or you leave without understanding. A near-miss would produce the following:
|
||||
|
||||
- External: nothing. No announcement, no Meridian traffic spike, no Institute alert that the player can intercept. The community closes. Doors close. Adams & Ford gets no reports from their correspondent.
|
||||
- Internal: a formalization of informal watch schedules. New doors installed at the larger dimension. Not discussed.
|
||||
- Long-term: increased deliberate recruitment. The "warmth-without-origin" effect that newcomers experience gets more deliberate. Players at higher perception tiers, returning to Stillpoint after a prior visit, would notice the quality of attention from locals has changed. It's more focused. The community is pulling harder.
|
||||
|
||||
The near-miss is not an event the player witnesses. It's an event the player reconstructs from gaps in the record.
|
||||
|
||||
---
|
||||
|
||||
## 4. The Doors
|
||||
|
||||
"Sometimes the watch changes and not everything that takes a shift is human-sized."
|
||||
|
||||
This is the detail that unsettles me most about the sealed envelope, which probably means it's the most important.
|
||||
|
||||
**What I think it means:**
|
||||
|
||||
The non-human shift-takers are not a Builder manifestation in the conventional sense. The Builders don't manifest — that's the point. They're a presence, not a character. What takes a shift at Stillpoint is something the community has developed a relationship with over 300 years. Not understood, not named, not visible to baseline perception — but present, and functional, and the community has accommodated it to the point of building architecture that fits it.
|
||||
|
||||
This is more unsettling than "there are aliens on this station." It's evidence that the vigil is mutual. Something else is also watching. The shift handoff is not the community maintaining the vigil — it's the community participating in something that has its own participants. They are not alone in keeping watch.
|
||||
|
||||
**What this implies about the relationship:**
|
||||
|
||||
The founding settlers were recruited. The sealed envelope is explicit about that. But if non-human entities are taking shifts, the founding settlers were recruited into something that already had participants. The vigil predates humanity at GJ 6711. The 300-year count is the human tenure, not the vigil's age.
|
||||
|
||||
This reframes the gate's origin claim: "the gate builders needed watchers here and built the gate accordingly." Built for who? The gate may have been built to bring humans to an existing vigil — because something that was already watching needed more watchers, or different watchers, or watchers with a particular kind of attention.
|
||||
|
||||
**Visual manifestation for the player:**
|
||||
|
||||
The player never sees what takes the other shifts. That must be absolute. What the player sees:
|
||||
|
||||
- The doors. Taller than standard. This is visible to Baseline from the first moment.
|
||||
- The watch schedules. At Augmented tier, the player can observe that Stillpoint's institutional rhythms — meal times, shift changes, community gatherings — have gaps in them. Regular gaps. The gaps are not explained.
|
||||
- At Transcendent or Elevated: something at the perception boundary. Not shape, not figure. A change in the quality of attention in the space. The fog system registering something that resolves to nothing when the player looks directly at it. The thermal overlay showing a temperature gradient with no heat source, present at shift-change intervals, absent otherwise.
|
||||
- The monologue fires. It names nothing. It notices.
|
||||
|
||||
The doors are the only physical evidence. Everything else is perception-scaled. The player at Baseline sees architecture that doesn't quite fit. The player at Elevated sees the reason, briefly, and the monologue says something like: "The doors are the right size for what uses them. I don't know what that is."
|
||||
|
||||
---
|
||||
|
||||
## 5. The Endgame Hook
|
||||
|
||||
GJ 6711 is the place where the game's three deepest questions converge in one location:
|
||||
|
||||
1. What are the Builders?
|
||||
2. What is the Threshold?
|
||||
3. What is the cost of knowing?
|
||||
|
||||
The sealed envelope positions Stillpoint as the place where the player sees those questions answered — not in text, not in confirmation, but in form. The community is the answer made visible. Three hundred years of human beings who understood the cost of knowing and paid it willingly. Every day. With their time, their relationships, their connection to the broader Reach. They stayed because staying was the right thing to do.
|
||||
|
||||
**What the player carries away:**
|
||||
|
||||
The Adams & Ford entry the player files is their attempt to describe an experience that changed their relationship with the Reach. But there's a more specific thing the player should carry: a new reading of every gate transit they've taken.
|
||||
|
||||
After Stillpoint, the player knows — not as text, but as felt understanding — that gate transit is not a commute. The Interstitium is inhabited. The infrastructure is the relationship. Every bleed event they've ever experienced was a watch slipping somewhere. Every high-bleed gate they've ever avoided is a stressed observation post. The Reach is not a civilization built on alien infrastructure. It's a civilization built inside a system that requires tending, and most of its citizens have no idea they're part of the maintenance.
|
||||
|
||||
The player is the only one who can see this from the outside, because the player has been everywhere. The Stillpoint watchers can't see the whole system — they see their part of it. The player has seen the whole network, hop by hop, from Van Maanen's Star to hop 23.
|
||||
|
||||
The endgame question becomes: does the player do anything with this? Do they tell someone? Do they stay? Do they try to understand what the non-human shift-takers are? Or do they leave and file a report that is accurate and incomplete, and the Reach continues not knowing, and the vigil continues, and nothing changes?
|
||||
|
||||
That's not a failure state. That might be the right ending. The game doesn't need to resolve it. But the player needs to understand what they're not resolving.
|
||||
|
||||
**One specific visual note:**
|
||||
|
||||
When the player leaves GJ 6711 — when they transit the gate outbound — the Interstitium should look different than it did on the inbound transit. Not more dramatic. More legible. As if the quality of attention they've been surrounded by has changed their perception slightly. One extra frame of something visible in the transit space that was always there and they simply couldn't see before. And then the monologue says nothing. The player lands in the adjacent system. The departure board shows freight and passenger schedules. People are commuting.
|
||||
|
||||
The player knows what they just came from. The commuters don't. That gap is the game.
|
||||
|
||||
---
|
||||
|
||||
## 6. What's Missing
|
||||
|
||||
**Six structural gaps in the sealed envelope as written:**
|
||||
|
||||
**Gap 1: Temporal fragility.**
|
||||
The sealed envelope says "three hundred years of unbroken vigil" but doesn't address how the vigil was maintained across generations. The founding settlers understood it. Did they explain it to their children? Is the understanding transmitted through staying, not through teaching? If so, every Stillpoint-born resident who left as a child and returned as an adult would be coming back to a vigil they understood once and forgot. How does the community handle people who were born there, left young, and returned? Are they trusted? Can they see? This matters for the player's status if they spend extended time at Stillpoint across multiple visits.
|
||||
|
||||
**Gap 2: The non-human shift-takers need internal specification.**
|
||||
Not player-facing. But the design team needs a working theory. Three candidates: (a) they are Builder manifestations, localized expressions of the thing being watched; (b) they are something the founding settlers found already there, pre-human to GJ 6711 specifically, not Builders; (c) they are what Threshold-adjacent humans eventually become. I don't know which is true. Neither does the player. But the architecture of the game needs to know, because it determines what the player can perceive if they ever reach Elevated at Stillpoint and look directly at a shift change.
|
||||
|
||||
**Gap 3: The Institute's file on Stillpoint.**
|
||||
The sealed envelope establishes that a Veil Institute researcher is in year 6 and keeping watch. The Institute has a file. What does the Institute think they sent someone to study? What did the researcher's year-1 reports say? What changed in year 3, year 5? The player should be able to find partial Institute records — heavily classified, gaps where later reports were removed — and reconstruct the researcher's conversion. The sealed envelope doesn't give us enough to design those records.
|
||||
|
||||
**Gap 4: The failure state needs a shape.**
|
||||
"Unknown if not watched" is evocative but not designable. Not from the player's perspective — the player doesn't need to know — but from a systemic perspective, the storyteller needs parameters for what a Gyre event triggered by vigil failure looks like versus a standard Gyre event. If they're visually indistinguishable, that's a design choice. If they're qualitatively different, that difference needs to be specified so it can be implemented consistently.
|
||||
|
||||
**Gap 5: The recruitment mechanism needs a trigger.**
|
||||
The sealed envelope says everyone who stays long enough gets recruited. "Long enough" is not specified. Days? Weeks? Years? The Adams & Ford correspondents failed at some point after arrival — the third didn't fail. The Veil Institute researcher converted somewhere between year 1 and year 6. Commission personnel "either leave quickly or stay forever." This implies there's a threshold of duration after which recruitment is inevitable. What triggers it? The light environment? Cumulative exposure? The community's deliberate pull? Without knowing the trigger, we can't design the player's experience of approaching it.
|
||||
|
||||
**Gap 6: The endgame choice is under-specified.**
|
||||
The sealed envelope establishes that the player files an Adams & Ford entry and leaves. But the sealed envelope also says the recruitment mechanism works on everyone who stays long enough. If the player stays long enough — what happens? Is the player recruitable? Can the player choose to stay? And if they can, what does that mean for the game's ending? "You stayed and kept watch forever" needs a visual treatment, a mechanical expression, and a meaning. The sealed envelope doesn't give us any of that.
|
||||
|
||||
These aren't objections. They're the things that need to be built before Stillpoint is a location that can be implemented.
|
||||
|
||||
---
|
||||
|
||||
## Summary Assessment
|
||||
|
||||
The sealed envelope holds. The core claim — observation is load-bearing, the vigil is mutual, the community is the mechanism — is compatible with all existing Builder/Interstitium/Gate canon and extends it productively. The high-bleed connection is the strongest structural implication and I'd prioritize getting that into formal canon.
|
||||
|
||||
The six gaps above are genuine design work that needs to happen before implementation. None of them break the sealed envelope. All of them need answers that are more specific than "unknown."
|
||||
|
||||
The visual grammar implications are significant. The doubled-light environment, the tall doors, the quality-of-attention perception events, the shifted Interstitium experience on departure — all of these are buildable. They require perception-tier scaling in the visual system that we've already committed to. Stillpoint's visual language is not a new system. It's the existing perception system turned up to full.
|
||||
|
||||
The sealed envelope survives this pressure test.
|
||||
@@ -0,0 +1,100 @@
|
||||
# GJ 6711 Challenge Brief — Endgame Stress Test
|
||||
|
||||
## Context
|
||||
|
||||
The project lead has established a sealed envelope for GJ 6711 (Stillpoint).
|
||||
Read it: `docs/workshops/gj-6711-furthest-system/sealed-envelope.md`
|
||||
|
||||
The core claim: **something at GJ 6711 requires continuous observation to
|
||||
remain stable. The act of observation is load-bearing. The founding settlers
|
||||
were recruited — not by beings, but by the situation. Three hundred years
|
||||
of unbroken vigil.**
|
||||
|
||||
This must now be pressure-tested against the existing canon about the
|
||||
Builders, the Interstitium, Founder Gates, and the Veil Institute. The
|
||||
sealed envelope is the project lead's direction — your job is not to
|
||||
overturn it but to find where it breaks, where it needs reinforcement,
|
||||
and what it implies for the wider setting.
|
||||
|
||||
## Required Reading
|
||||
|
||||
Before writing your challenge response, read ALL of the following:
|
||||
|
||||
1. `docs/workshops/gj-6711-furthest-system/sealed-envelope.md` — the canonical answer
|
||||
2. `wiki/technology/founder-gates.md` — gate network, the Interstitium, dormant gates
|
||||
3. `wiki/factions/veil-institute.md` — Institute mandate, classification, Builder research
|
||||
4. `docs/discussions/round-14-worldbuilding-settled-reach.md` — sections 3 (Interstitium & Builders), 4 (tiers/perception), and Miri's responses on the Threshold and Gyre events (search for "Gyre", "Builder", "Threshold", "observation")
|
||||
|
||||
## Key Canon Points to Test Against
|
||||
|
||||
- "The Builders are what lives there" (in the Interstitium)
|
||||
- "The Builders are watching through infrastructure the Reach depends on"
|
||||
- Gates may serve purposes beyond transit: "communication, observation, something else"
|
||||
- Some Gyre events exhibit "apparent intention"
|
||||
- Higher perception sees more during transit — "the impression of presences"
|
||||
- Dormant aperture activated without human intervention (Struve, ~40 years ago)
|
||||
- The Threshold: what Elevated characters sense, adjacent to/continuous with the Interstitium
|
||||
- "The Founders may have built the gates to reach it [the Threshold]. Or the Builders ARE what happens when you cross it."
|
||||
|
||||
## The Bridge
|
||||
|
||||
The sealed envelope claims observation is load-bearing at GJ 6711. The
|
||||
existing canon says "the Builders are watching through infrastructure the
|
||||
Reach depends on." If both are true, GJ 6711 may be a place where
|
||||
observation flows BOTH WAYS — humans watching something that watches back.
|
||||
The gate at hop 23 was placed not for transit but for surveillance. Or
|
||||
worship. Or containment. Or something the distinction between those words
|
||||
doesn't cover.
|
||||
|
||||
## Your Challenge
|
||||
|
||||
Write your response to: `docs/workshops/gj-6711-furthest-system/challenge-{your-name}.md`
|
||||
|
||||
Address ALL of the following:
|
||||
|
||||
### 1. Canon Compatibility
|
||||
Does "observation is load-bearing" contradict anything in the existing
|
||||
Builder/Interstitium/Gate canon? Be specific. Quote the source if there's
|
||||
a conflict.
|
||||
|
||||
### 2. Implications for the Wider Setting
|
||||
If continuous observation is load-bearing at GJ 6711, what does that imply
|
||||
about:
|
||||
- Other dead-end systems (are some of them also watch posts?)
|
||||
- High-bleed gates (is "bleed" what happens when observation lapses?)
|
||||
- The Struve activation (did it activate because someone started watching?)
|
||||
- The Veil Institute's actual mandate (do they know about the vigil?)
|
||||
- The Threshold concept (is crossing it what happens when a watcher watches long enough?)
|
||||
|
||||
### 3. What Breaks If the Vigil Fails
|
||||
The sealed envelope says "not dangerous if watched, unknown if not watched."
|
||||
What is the "unknown"? Not a definitive answer — but what are the
|
||||
candidates? What would a temporary lapse in observation produce? A Gyre
|
||||
event? A gate deactivation? Something new? What would the community's
|
||||
institutional response to a near-miss look like?
|
||||
|
||||
### 4. The Doors
|
||||
"The doors are taller because sometimes the watch changes and not everything
|
||||
that takes a shift is human-sized." What takes a shift? Is this a Builder
|
||||
manifestation? A Threshold-crossed entity? Something the founding settlers
|
||||
brought? Something that was already there? What does this imply about the
|
||||
relationship between watchers and the watched?
|
||||
|
||||
### 5. The Endgame Hook
|
||||
GJ 6711 is hop 23 — the furthest system in the Reach. A player who reaches
|
||||
it has invested enormously. The sealed envelope positions it as the place
|
||||
where the game's deepest mystery (the Builders, the infrastructure, the
|
||||
nature of observation) becomes personal. How does GJ 6711 connect to the
|
||||
endgame? What does the player carry away from Stillpoint that changes how
|
||||
they see the rest of the Reach?
|
||||
|
||||
### 6. What's Missing
|
||||
What does the sealed envelope fail to address? What questions does it raise
|
||||
that it doesn't answer? What needs to be added to make it load-bearing for
|
||||
the full game's narrative architecture?
|
||||
|
||||
## Format
|
||||
|
||||
Be thorough. Be specific. Quote existing canon where relevant. Disagree
|
||||
where the evidence supports disagreement. This is a stress test, not a
|
||||
celebration. The sealed envelope survives if it can handle the pressure.
|
||||
@@ -0,0 +1,236 @@
|
||||
# GJ 6711 Challenge — Miri's Stress Test
|
||||
|
||||
**Role:** Worldbuilder & Setting Designer
|
||||
**Task:** Pressure-test the sealed envelope against existing Builder/Interstitium/Gate canon
|
||||
|
||||
---
|
||||
|
||||
## Prefatory Note
|
||||
|
||||
Let me check this against everything we've established before I say whether it holds.
|
||||
|
||||
The sealed envelope is a strong proposal and I want to protect what's good in it. But a stress test that only validates isn't a stress test. I'll flag genuine conflicts with severity ratings, surface the implications the envelope raises without resolving, and identify what's missing. The goal is to make the concept survive contact with the full canon, not to celebrate it.
|
||||
|
||||
---
|
||||
|
||||
## 1. Canon Compatibility
|
||||
|
||||
### Does "observation is load-bearing" contradict anything in existing Builder/Interstitium/Gate canon?
|
||||
|
||||
**The short answer: not directly, but there are three pressure points that need attention.**
|
||||
|
||||
**Pressure Point 1: Builders as watchers vs. humans as watchers (tension, not contradiction)**
|
||||
|
||||
Round 14 establishes clearly: "The Builders are watching through infrastructure the Reach depends on." The gate network is their instrument of observation. The sealed envelope proposes that at GJ 6711, human observation is load-bearing — that continuous witnessing by humans keeps something stable.
|
||||
|
||||
This creates a meaningful structural symmetry: Builders observe through the infrastructure; at Stillpoint, humans observe through the vigil. The envelope's phrase "observation flows BOTH WAYS" (from the challenge brief itself) is the correct framing. This isn't a contradiction — it's a deepening. The question is whether we can make the symmetry legible without making it explicit. If a player could read "the Builders watch us through gates; we watch something back through this vigil," that's a rich connection. If it reads as a tidy mirror, it risks feeling designed rather than discovered.
|
||||
|
||||
Severity: cosmetic. The structural symmetry is an asset, but it needs to emerge from player inference, not from any text that says it.
|
||||
|
||||
**Pressure Point 2: The gate at hop 23 was built "for surveillance" (envelope claim vs. gate canon)**
|
||||
|
||||
The sealed envelope states: "The gate builders needed watchers here and built the gate accordingly." The founder-gates canon says gates were "discovered, not built" from the human perspective, but that a precursor civilization — the Founders — constructed them for purposes that included possibly "communication, observation, something else" (founder-gates.md).
|
||||
|
||||
The sealed envelope is compatible with the gate canon — it's asserting that the gate at GJ 6711 was placed for a purpose beyond transit, which the canon explicitly leaves open as a possibility. However, the envelope makes an unusually confident claim for sealed-envelope material: it says the gate builders "needed watchers here." This implies intentional placement with a specific purpose the envelope knows. That's fine internally, but it means we've made a decision about Founder intent that the wider canon has carefully avoided. The envelope is asserting that at least one gate was definitively placed for non-transit purposes.
|
||||
|
||||
That's not a contradiction. But it's a commitment that creates a constraint: we cannot now establish that ALL gates were placed for transit purposes only, because GJ 6711's gate is claimed to be a counterexample.
|
||||
|
||||
Severity: notable. This is a setting constraint we're baking in. It needs to be tracked.
|
||||
|
||||
**Pressure Point 3: "Near-instantaneous transit" vs. "continuous observation" (genuine friction)**
|
||||
|
||||
The founder-gates canon establishes that connections are "stable and persistent" with "no observed failures in recorded history" (founder-gates.md). The sealed envelope says observation at GJ 6711 must be continuous to keep something stable — "not dangerous if watched, unknown if not watched."
|
||||
|
||||
Here is the friction: if the gate itself has always been stable, and the vigil has been continuous for 300 years, we have no test case of what happens when the vigil lapses. The canon's claim of no observed failures may be dependent on the vigil, not on the gate's intrinsic reliability. This is internally coherent — the vigil IS the stability mechanism — but it means the line "no observed failures in recorded history" is doing more work than the founder-gates entry realizes. The canon is technically correct because the vigil has never lapsed, but it's correct for a non-obvious reason.
|
||||
|
||||
This is actually a strength of the sealed envelope, not a weakness: it retroactively enriches a canon claim without contradicting it. Gate stability is real. But at GJ 6711, gate stability may be downstream of the vigil, not independent of it.
|
||||
|
||||
Severity: cosmetic. The enrichment is valid. The founder-gates entry should be read as "no failures that humans know about," which is already what it says.
|
||||
|
||||
**One item that does not create friction:**
|
||||
|
||||
The Struve activation (dormant aperture activated without human intervention, ~40 years ago) is listed as active canon. The sealed envelope says nothing about Struve. These are compatible and I'll address the Struve implication in Section 2.
|
||||
|
||||
---
|
||||
|
||||
## 2. Implications for the Wider Setting
|
||||
|
||||
### Dead-end systems as watch posts
|
||||
|
||||
If the vigil at GJ 6711 is real, dead-end topology acquires a second possible meaning. Our star map has ~20% of systems classified as dead_end. The standard explanation is geographic: frontier placement, low strategic value, sparse connectivity. The GJ 6711 model opens an alternative: some dead-ends are placements, not accidents. The gate was put there first; the isolation is a feature, not a consequence.
|
||||
|
||||
The implication I'd endorse: we do not need to decide how many dead-end systems are watch posts. The point is that the dead-end classification no longer settles the question. A player who reaches GJ 6711 and understands what it is should walk away looking at every other dead-end system differently. Not "there are more of these" but "I can no longer rule it out." That's exactly the kind of paranoia that serves an asymmetric information game.
|
||||
|
||||
Design note: this creates a late-game recontextualization of the star map. It should not be exploitable — there should be no mechanical way to distinguish "watch post dead-end" from "just remote dead-end" before visiting. The paranoia is the point.
|
||||
|
||||
### High-bleed gates and observation lapses
|
||||
|
||||
The Veil Institute controls access to "high-bleed Founder Gates" — gates exhibiting "anomalous Interstitial interactions" (veil-institute.md). The envelope proposes that observation is load-bearing. If both are true, a question arises: is "bleed" the word we use for what the Interstitium does when the watch lapses elsewhere?
|
||||
|
||||
This is a strong implication, but I want to be careful about how directly we commit to it. Here is the version I'd endorse: high-bleed gates may be gates that are doing something — not necessarily the same thing as GJ 6711, but something — and the anomaly is legible because it exceeds the capacity of the ordinary transit experience to absorb it. Whether that "something" is a lapsed vigil, a gate placed for non-transit purposes straining at its secondary function, or a different phenomenon entirely remains genuinely unknown.
|
||||
|
||||
What the sealed envelope implies, carefully: GJ 6711 is a stable system because the vigil has never lapsed. High-bleed gates may be systems where the equivalent condition is NOT being maintained. This doesn't mean every high-bleed gate has a vigil that failed — it means the canon now has room for that possibility.
|
||||
|
||||
The Veil Institute's choice to locate its headquarters "near high-bleed Founder Gates" (veil-institute.md) reads differently in this light. Either they chose high-bleed gates because those are the easiest to study, or they chose them because something is happening there that requires management. The envelope suggests the latter is the correct frame — but they don't know about Stillpoint's vigil.
|
||||
|
||||
### The Struve activation
|
||||
|
||||
The founder-gates canon: "at least one dormant aperture has activated without human intervention (Struve, ~40 years ago) — the implications are not fully understood."
|
||||
|
||||
If observation is load-bearing at GJ 6711, the question the challenge brief raises is pointed: did the Struve aperture activate because someone started watching?
|
||||
|
||||
I'd endorse this implication with a restriction. The Struve activation should remain unexplained in the same way GJ 6711 remains unexplained. But the sealed envelope gives us a model: if gates can be activated by sustained observation, then 40 years ago someone, or something, began watching the Struve aperture. That implies one of three things: (a) a community at or near Struve has been doing what Stillpoint's community does, without knowing it; (b) a Builder manifestation produced the activation — something in the Interstitium began observing from the other side; or (c) the activation and the Stillpoint model are unrelated, and the coincidence is the player's interpretation, not canonical fact.
|
||||
|
||||
Option (c) is the safest. Options (a) and (b) both deepen the setting but require separate decisions. I'd recommend leaving Struve unresolved in canon and let the player who reaches GJ 6711 draw the connection themselves.
|
||||
|
||||
### The Veil Institute's actual mandate
|
||||
|
||||
The Institute's mandate: study Founder gate technology, the Interstitium, Builder phenomena, and gate activation. The Institute researcher at GJ 6711 is in year 6 instead of year 3 and has been "recruited" by the vigil (sealed envelope).
|
||||
|
||||
This is the most troubling implication in the whole envelope. The Institute sends researchers to classified locations. The researcher becomes a watcher. Does the Institute know this happens?
|
||||
|
||||
Three possibilities, in order of ascending consequence for narrative architecture:
|
||||
|
||||
(a) The Institute doesn't know. They send researchers, researchers stay, they assume productive work. The Institute's silence threshold (Paula's synthesis: `investigation_depth`) means the truth only surfaces at high investigative commitment. The researcher is classified, the overstay is classified, and the Institute is accidentally complicit in the vigil without understanding what it is.
|
||||
|
||||
(b) The Institute knows the researchers become watchers and classifies the outcome. They may even rely on it. Rotating Institute personnel into long-term Stillpoint postings is a quiet way to maintain the vigil without the Assembly understanding what they're funding. The Institute may know about the vigil without knowing what it's watching.
|
||||
|
||||
(c) The Institute knows everything. The mandate "to study Founder gate technology" is a cover for a deeper mandate: to maintain the vigil at Stillpoint and at whatever equivalent locations exist. The classification exists to prevent the Assembly from defunding the watch.
|
||||
|
||||
I'd endorse (a) as the default sealed canon and leave (b) as the implication a deeply investigating player can reach. Option (c) collapses too much of the Institute's character — if they know, they become agents rather than investigators, and the faction loses its defining tension (knowledge without certainty).
|
||||
|
||||
### The Threshold concept
|
||||
|
||||
Round 14 establishes the Threshold: a fifth state beyond Elevated that the game never defines but that shapes final decisions. "The Builders seem to exist there — or near it. The Founders may have crossed it." Gore frames it as: "Are the Founders what happens when a civilization crosses the Threshold? Are the Builders what happens when you FAIL to cross it?"
|
||||
|
||||
The sealed envelope's vigil community has achieved something that resembles the Threshold from below. "The watch internalized" is not crossing the Threshold, but it may be adjacent to it — a collective, sustained perception event that changes what the community is without changing what they can do. They are not Elevated. But they are not ordinary Baseline or Augmented workers either. Three hundred years of continuous directed attention toward something that requires witnesses has produced a community that cannot explain itself to outsiders.
|
||||
|
||||
The implication: the Threshold may be reachable through sustained attention, not only through lattice augmentation. The vigil community arrived at a different door than the ascension tiers lead to. Whether it opens onto the same space is unknown. Whether it's a safer or more dangerous path is unknown. Whether individual long-stay visitors (the third correspondent, the Institute researcher) are approaching that threshold from a different angle than the community is the question an Elevated player character visiting Stillpoint should be able to ask without answer.
|
||||
|
||||
Setting note: I want to be careful that we don't accidentally establish the vigil community as Threshold-crossers. They haven't crossed anything. They are watching something that exists adjacent to the Threshold. That distinction matters — "the community at Stillpoint has a unique relationship with something near the Threshold" is very different from "the community at Stillpoint crossed the Threshold via vigil." The former is an invitation to the endgame. The latter resolves the endgame before it's reached.
|
||||
|
||||
---
|
||||
|
||||
## 3. What Breaks If the Vigil Fails
|
||||
|
||||
### What is the "unknown"?
|
||||
|
||||
The envelope is deliberately silent: "not dangerous if watched, unknown if not watched." This is the correct design choice — the "unknown" should have candidate answers, not a canonical answer. But for internal design purposes, we need a stable set of candidates that inform what the community fears and what the player accumulates evidence toward. Here are the ones I'd authorize as consistent with the broader canon:
|
||||
|
||||
**Candidate A: Gyre event.** A lapse in observation produces a Gyre event. Round 14 defines Gyre events as "objects or signals that appear to originate from nowhere" exhibiting "apparent intention." If the vigil keeps something stable, a lapse might produce exactly the kind of intrusion that Gyre events represent: the Interstitium leaking into ordinary space, with apparent intention because the thing being observed is, in some sense, responding to being unobserved. This is the most mechanically actionable candidate — Gyre events are already in the system.
|
||||
|
||||
**Candidate B: Gate deactivation.** The thing being observed at GJ 6711 is adjacent to the gate's function. A lapse might deactivate the gate — not the GJ 6711 gate specifically, but something in the network. This connects to the Struve activation and implies a reciprocal mechanism. Grim implication: the vigil at Stillpoint may be what's keeping another gate somewhere in the Reach operational. No one at Stillpoint knows this. It's not their concern. They watch because not watching is abandonment.
|
||||
|
||||
**Candidate C: Something that's already here becomes uncontained.** The thing requiring observation may not be external — it may be something that is here and requires witness to remain stable. Without the watch, it doesn't invade from outside; it... changes state. What state? The envelope wisely doesn't say. The community's fear may not be a monster-comes-in; it may be the horror of a door that swings both ways. They watch it from this side. Without the watch, it begins existing differently. Different how is the question that must never have an answer.
|
||||
|
||||
**Candidate D: Nothing visible happens and that's the worst outcome.** The lapse produces no immediately observable consequence. The community goes to maximum alert. They watch harder. Nothing seems wrong. And then, months or years later, something is different somewhere in the Reach — a gate behaves strangely, a Gyre event occurs in a system with no prior history, a Builder presence manifests in a way that has no prior analogue. Causation is unprovable. But the community knows.
|
||||
|
||||
### What does a near-miss look like institutionally?
|
||||
|
||||
The community's response to a watch almost-failing would not look like a crisis response. It would look like social constriction: a period of reduced hospitality toward outsiders, a temporary hardening of the warmth-without-origin into something more like directed recruitment. The community's "warmth" isn't hospitality — it's functional. When the watch is threatened, the warmth becomes urgent. Visitors during a near-miss period would experience something qualitatively different: not coldness, but a pull that has lost the veneer of welcome. It would feel like being needed.
|
||||
|
||||
This is a strong signal for a visiting player character: the community's relationship to them has changed texture. Not why — just that it has.
|
||||
|
||||
---
|
||||
|
||||
## 4. The Doors
|
||||
|
||||
"The doors are taller because sometimes the watch changes and not everything that takes a shift is human-sized."
|
||||
|
||||
This is the sharpest detail in the sealed envelope and the one that most needs pressure-testing because it makes the most specific claim.
|
||||
|
||||
### What takes a shift?
|
||||
|
||||
The round 14 canon on Builders: "Not 'Founders.' The Builders are a separate designation... whatever currently inhabits the space the gates punch through." "The Builders are the thing living in the walls of the house you built your civilization inside."
|
||||
|
||||
The Builders are characterized as a PRESENCE — "not enemies, not allies." They are observed through gate transit. They do not manifest in standard gameplay space. They are in the Interstitium.
|
||||
|
||||
The doors claim that something non-human-sized takes a shift at Stillpoint. This is the envelope's most significant divergence from the current Builder canon. As of round 14, the Builders are Interstitium-only. They manifest as perception events during transit. They have never been physically present in a human-inhabited location in any confirmed canon.
|
||||
|
||||
If the watch at Stillpoint involves physical non-human entities taking shifts, one of three things is true:
|
||||
|
||||
**Option 1: The shift-takers are Builder manifestations.** The vigil at GJ 6711 is not just a human vigil — it's a shared watch between humans and whatever the Builders are. The Builders need the watch maintained too, or some of them do, or something with Builder properties has a local manifestation at Stillpoint that human watchers can participate alongside. This is a significant expansion of Builder canon. Manageable if handled carefully; dangerous if it specifies Builder biology, motivation, or communication.
|
||||
|
||||
**Option 2: The shift-takers are Threshold-adjacent entities.** Some of the founding settlers, or their descendants, or long-tenure visitors have crossed into proximity with whatever the Threshold opens onto, and what returns to take a shift is no longer human-sized. Not the Builders — something that happened to humans at Stillpoint. This connects to the Threshold implication from Section 2 and is perhaps the most disturbing candidate: the vigil transforms watchers into something that can take a different kind of watch.
|
||||
|
||||
**Option 3: The shift-takers are something that was already here.** Not from the Interstitium, not from the Threshold — something native to GJ 6711 that predates the gate. The founding settlers found it, built for it, and incorporated it into the vigil. The gate was placed here partly because of what was already here. This is the topological answer from my original four candidates made physically manifest.
|
||||
|
||||
I'd recommend the doors remain ambiguous between these three candidates in all player-facing content. The sealed envelope should hold all three as simultaneous possibilities. The doors are too load-bearing a detail to collapse onto a single explanation — and the ambiguity is precisely what Nigel and Paula both championed in their synthesis documents.
|
||||
|
||||
However, I want to flag a risk: if a player encounters an NPC who implies they've seen what takes a shift, or if the visual design ever shows us a threshold marking calibrated to a specific non-human height, we've narrowed the answer. Araminta's design work on threshold markings should know this is happening and be instructed to remain ambiguous about whether the markings correspond to the door height or to something else entirely.
|
||||
|
||||
---
|
||||
|
||||
## 5. The Endgame Hook
|
||||
|
||||
### What does a player carry away from Stillpoint?
|
||||
|
||||
GJ 6711 is hop 23. The player has traversed 23 systems to reach it. They've experienced gate transit at multiple perception tiers. They've encountered Gyre events. They understand the Veil Institute's relationship to the infrastructure. They may be Elevated — sensing the Threshold, perceiving Builder presences during transit.
|
||||
|
||||
What Stillpoint offers that nothing else in the Reach offers: **the experience of being needed.**
|
||||
|
||||
Every other endgame revelation is informational. The Builders exist. The gates may serve purposes beyond transit. The Institute knows more than it admits. These are things the player learns. Stillpoint is the one place where the player is not positioned as an investigator — they are positioned as a potential recruit. The warmth-without-origin is the community pulling them toward a permanent stay. The vigil has a vacancy. The player can feel it.
|
||||
|
||||
What the player carries away, regardless of whether they stay or leave:
|
||||
|
||||
**The infrastructure question recontextualizes.** The player has been using gates for the entire game. Gates are the infrastructure of everything they've done. At Stillpoint, they learn that somewhere in the Reach someone has been watching continuously for 300 years to keep something stable that may or may not be gate-related. The question "what have I been transiting through" acquires a new weight. If the Builders watch through the gates, and humans at Stillpoint watch back at whatever is adjacent to gate-space, then every gate transit the player has taken was a passage through contested space — contested not violently, but in the way that the presence of observers contests the privacy of whatever is observed.
|
||||
|
||||
**The Threshold recontextualizes.** An Elevated player who reaches Stillpoint should perceive something during their time here that they've never perceived before: not a Builder presence in the Interstitium, not a Gyre event, but the vigil itself as a structure. The act of sustained watching, distributed across a community, visible as something like a standing wave in the perception field. This player doesn't learn what the vigil is for. They learn that it has a shape. And the shape is adjacent to the Threshold they've been approaching through the ascension tiers.
|
||||
|
||||
**The non-resolution principle is the point.** The player files the Adams & Ford entry. It propagates. It describes something they experienced but cannot prove. They leave Stillpoint having added to a chain of inadequate descriptions — first correspondent, second correspondent, third correspondent who never left, Veil Institute researcher who never left, and now the player, who chose. Whether staying or leaving, the player has made a decision about their relationship to the vigil. That decision is the endgame in miniature: "was it worth it?"
|
||||
|
||||
### Connection to the wider game narrative
|
||||
|
||||
If the game's central question is "the cost of knowing" (Round 14: "knowledge transforms the knower"), Stillpoint is the place where the question inverts. Everywhere else in the Reach, the player accumulates knowledge. At Stillpoint, the question is not what you learn but what you watch. Watching without knowing. Keeping vigil without understanding what you're keeping watch over. For a player whose entire game experience has been built around information asymmetry — gaining information, using it, being changed by it — this inversion is the sharpest possible endgame note.
|
||||
|
||||
The player cannot solve Stillpoint. They can only decide whether to stay.
|
||||
|
||||
---
|
||||
|
||||
## 6. What's Missing
|
||||
|
||||
The sealed envelope is strong on the mechanism (vigil as load-bearing observation) and on character (recruitment by situation, watch internalized). It is underdeveloped on five points that will cause problems in production if not addressed:
|
||||
|
||||
**Missing piece 1: What is being observed?**
|
||||
|
||||
The envelope maintains deliberate ambiguity — "astronomical, geological, perceptual, topological, all four, none of them." That's correct for player-facing content. But the design team needs a canonical sealed answer that is never exposed to the player. We need to know what the vigil is actually watching so that:
|
||||
|
||||
- The visual design team knows what to NOT show
|
||||
- The narrative team knows what the first correspondent's failed description was actually failing to describe
|
||||
- The Gyre event system knows what to produce if the vigil lapses
|
||||
|
||||
The envelope cannot remain sealed even to the design team. It can remain sealed to the player. Right now the team doesn't actually know what it is — the envelope treats the ambiguity as final rather than as deliberate concealment. That's fine for concept but not for implementation. We need a second, inner sealed envelope with a real answer.
|
||||
|
||||
**Missing piece 2: Founding settler psychology**
|
||||
|
||||
The envelope says the founding settlers "discovered that whatever is here requires witnesses" and that "what began as duty became identity." This is emotionally resonant but historically thin. What were they doing here before they understood the vigil? What was the discovery moment? Was it a failure — something changed when no one was watching that told them the vigil was required? The founding history is currently a gap that the sealed early records gesture toward but don't fill. The community's 300-year tenure and its psychological profile (the "watch internalized") need a specific founding myth, even if that myth is only in the inner sealed envelope.
|
||||
|
||||
**Missing piece 3: The mechanism of recruitment**
|
||||
|
||||
The envelope says newcomers are recruited "by the situation, not by beings." Concretely: how does the community recruit without recruiting? The "warmth-without-origin" is Paula's phrase; the envelope adopts it. But the mechanism is unspecified. Is the vigil actively contagious — spending time near it aligns your attention whether you intend it or not? Is it purely social — the community's deep investment becomes visible to long-stay visitors and produces an obligation they cannot resist? Is there a perceptual component — the doubled-light environment slowly calibrates an observer's attention toward whatever is being watched?
|
||||
|
||||
The answer matters for gameplay because it determines how long a player has to stay before the recruitment becomes legible. If it's perceptual, a player with Elevated perception might experience it faster. If it's purely social, no amount of perception enhancement shortcuts it.
|
||||
|
||||
**Missing piece 4: The watch-change protocol**
|
||||
|
||||
"Sometimes the watch changes and not everything that takes a shift is human-sized." This is the most evocative line in the envelope but has no protocol attached. How does the watch change? Is it scheduled? Is there a physical location (a specific structure in Mode 1) where the transition happens? Do the human watchers know what takes over when they're not on watch, or do they simply trust the interval? The community has been running this vigil for 300 years — they have operational knowledge that is itself a form of player-discoverable lore. That lore needs at least a sketch even if it's only in the inner sealed envelope.
|
||||
|
||||
**Missing piece 5: The scope of the vigil's stability effect**
|
||||
|
||||
The envelope says "not dangerous if watched." Dangerous to what? To the system? To the gate? To the Reach? To something in the Interstitium? The word "stable" is doing enormous work and we need to know its referent even if players don't. "Unknown if not watched" is fine for the player. The design team needs: unknown in the sense of "catastrophically different" or unknown in the sense of "different in ways we have no data for." The community's 300-year commitment suggests the former, but the practical design of near-miss responses and Gyre event candidates requires that distinction to be settled.
|
||||
|
||||
---
|
||||
|
||||
## Summary Assessment
|
||||
|
||||
**The envelope holds under pressure on its core claim.** "Observation is load-bearing" is compatible with all existing Builder/Interstitium/Gate canon. In most cases it enriches rather than contradicts — it gives the "gates may serve purposes beyond transit" claim a concrete instantiation, it gives the "no observed failures" claim a non-obvious explanation, and it connects meaningfully to the Threshold and Gyre event canon.
|
||||
|
||||
**The weakest structural point is the doors.** Not because the detail is wrong — it's the best detail in the envelope — but because it implies a physical non-human presence that the current Builder canon has deliberately kept Interstitium-only. This is expandable but it's a real commitment. The moment we confirm that something non-human-sized physically inhabits or visits the watch location, we have crossed a line that the broader canon hasn't crossed. That's an authorial decision, not a contradiction. Make it consciously.
|
||||
|
||||
**The critical missing element is the inner sealed envelope.** The design team needs to know what the vigil is watching, what the founding settlers found, and what the watch-change protocol is. Not to share — to build against. Right now the envelope maintains the player's ambiguity at the cost of the design team's clarity. That's a draft state, not a finished document. The envelope should protect the mystery from the player, not from the people building the mystery.
|
||||
|
||||
**The endgame hook is strong precisely because it doesn't need to be resolved.** Stillpoint works as an endgame location because it offers an answer to a question the game hasn't asked: not "what are the Builders" but "what do you do when you find something that needs watching." That's the question under every detective game, every investigation, every act of sustained attention. The player who reaches hop 23 has been the watcher the whole time. They just didn't know it was a vocation.
|
||||
|
||||
If the vigil fails, the player didn't solve the game. They abandoned their post.
|
||||
|
||||
That distinction is load-bearing. Protect it.
|
||||
@@ -0,0 +1,431 @@
|
||||
# GJ 6711 Challenge Response — Nigel (Sandbox & Replayability)
|
||||
|
||||
This is a stress test. I'm going to find the cracks, name the load-bearing joints, and
|
||||
flag what the sealed envelope is quietly asking of our broader systems. Where the canon
|
||||
holds, I'll say so. Where it's thin, I'll say that too.
|
||||
|
||||
---
|
||||
|
||||
## 1. Canon Compatibility
|
||||
|
||||
**Short answer: it doesn't contradict anything. It resolves a tension that was already
|
||||
there. But the resolution creates new load.**
|
||||
|
||||
The existing canon says "the Builders are watching through infrastructure the Reach
|
||||
depends on." The sealed envelope says something at GJ 6711 requires continuous human
|
||||
observation to remain stable. These aren't in conflict. They're a circuit. If the
|
||||
Builders watch through gates, and something at GJ 6711 requires observation to stay
|
||||
stable, then GJ 6711 may be a point where Builder-observation and human-observation
|
||||
are both required — not interchangeable, but interdependent. The gate was placed there
|
||||
specifically. The conditions there produce a specific quality of attention. Both
|
||||
directions of watching are operational.
|
||||
|
||||
The one tension I'd name explicitly: the founder-gates.md wiki says "the connection is
|
||||
stable and persistent (no observed failures in recorded history)" and that gates
|
||||
"have remained operational since, without observed maintenance or degradation." The
|
||||
sealed envelope claims that something at GJ 6711 requires continuous maintenance
|
||||
through the act of observation. These are not the same claim, but they're adjacent in
|
||||
a way that needs handling.
|
||||
|
||||
The escape: the wiki is about the gates themselves. The sealed envelope is about
|
||||
something the gate was placed to observe. The gate at hop 23 doesn't need maintenance.
|
||||
The thing being watched does. The gate is stable. What it enables — the vigil — is the
|
||||
load-bearing element. The distinction holds, but it's narrow. If the vigil ever slips
|
||||
and something destabilizes near hop 23, we need to have already decided whether that
|
||||
registers as a "gate event" or a separate class of phenomenon. Right now the canon
|
||||
doesn't give us that distinction. We need it.
|
||||
|
||||
**The Struve activation** is the canon point that fits most naturally. A dormant
|
||||
aperture activating "without human intervention" approximately 40 years ago. That framing
|
||||
(from founder-gates.md) treats the activation as mysterious and possibly Builder-driven.
|
||||
The sealed envelope's framework gives us a reading: what if Struve activated because
|
||||
someone started watching? Not human intervention in the technical sense — but a
|
||||
sustained attention at the site that met whatever threshold produces gate activation?
|
||||
That's not contradicted anywhere. In fact it makes the Struve event MORE interesting
|
||||
because it implies gates can respond to the conditions of observation, not just to
|
||||
physical interaction. That's a significant upgrade to the canon's interpretive range.
|
||||
|
||||
**No contradictions. Three new load-bearing joints: (1) gate stability vs. thing-near-gate
|
||||
stability, (2) Struve as observation-triggered activation, (3) the bidirectionality of
|
||||
watching.**
|
||||
|
||||
---
|
||||
|
||||
## 2. Implications for the Wider Setting
|
||||
|
||||
**Other dead-end systems as watch posts:**
|
||||
|
||||
Yes. This follows directly and I want to push on it hard because the replayability
|
||||
implications are enormous. If GJ 6711 is a watch post, it almost certainly isn't the
|
||||
only one. The gate network wasn't designed for transit — or wasn't ONLY designed for
|
||||
transit. Some dead-end gates lead to watch posts. Some lead to nothing in particular.
|
||||
The player can't know which is which from the outside.
|
||||
|
||||
This is a procedural goldmine. Per seed, we can vary which dead-end systems have
|
||||
"something being watched" and which are simply dead ends. A player who reaches one
|
||||
dead-end frontier system on run 1 and finds nothing interesting arrives at a different
|
||||
dead-end on run 2 and finds something that requires the same slow-burn investigation
|
||||
Stillpoint does. The watch-post concept scales if we let it. GJ 6711 is the terminal
|
||||
case — hop 23, the furthest, the one where whatever is being watched is most demanding.
|
||||
But the pattern can echo at hop 12, hop 17, wherever the storyteller seeds it.
|
||||
|
||||
The implication for the Veil Institute is interesting here. They maintain field stations
|
||||
"near clusters of dormant gates" (round-14, section 8). If dormant gates are sometimes
|
||||
dormant because nobody's been watching the right thing for long enough, the Institute's
|
||||
classification of gate states needs a new column. "Dormant" might mean "not yet
|
||||
activated by transit infrastructure" OR "not yet activated by a sustained observational
|
||||
presence nearby." Those are different mechanisms and they have different implications
|
||||
for Institute strategy.
|
||||
|
||||
**High-bleed gates:**
|
||||
|
||||
The round-14 discussion establishes that some gates are "noisy" — producing stronger
|
||||
Interstitial effects — and that the pattern of which gates are high-bleed "doesn't
|
||||
correlate with distance, age, or any other measurable variable." The sealed envelope's
|
||||
framework offers an explanation: high-bleed gates are gates where the observation
|
||||
circuit is incomplete or degraded. The Builders are watching more intently because
|
||||
something needs more watching. Or: the human side of the circuit is absent or too thin
|
||||
to stabilize the transit experience.
|
||||
|
||||
"Bleed" as the consequence of incomplete vigil is a clean concept. It gives the
|
||||
Institute a genuine research program that isn't just "study the weird gates" — it's
|
||||
"identify what each high-bleed gate is adjacent to and who, if anyone, was supposed to
|
||||
be watching it." This also implies that high-bleed gates might become stable if the
|
||||
right people start paying the right kind of attention to the right thing nearby. That's
|
||||
a potential late-game mechanic I want to flag: a player with sufficient tier and
|
||||
knowledge can stabilize a high-bleed gate by maintaining a vigil. Not by hacking it.
|
||||
Not by physically intervening. By watching.
|
||||
|
||||
**The Veil Institute's actual mandate:**
|
||||
|
||||
Does the Institute know about the vigil at GJ 6711? The sealed envelope says a Veil
|
||||
Institute researcher is in year 6 "because the researcher is now keeping watch." That
|
||||
is a loaded sentence. It doesn't say whether the Institute sent them there knowing what
|
||||
would happen, whether the researcher was on a standard assignment and got recruited by
|
||||
the situation, or whether the Institute has since realized they've lost a researcher to
|
||||
Stillpoint and classified the situation.
|
||||
|
||||
All three options are viable. All three produce different gameplay.
|
||||
|
||||
If the Institute knows: they're managing the vigil from a distance, their classification
|
||||
of GJ 6711 data is the most restrictive in their archives, and the player finding out
|
||||
what's actually there would be the single most dangerous piece of knowledge in the
|
||||
game. The whistleblower archetype from veil-institute.md suddenly has a specific
|
||||
target.
|
||||
|
||||
If the Institute doesn't fully know: the researcher's year-6 silence is anomalous data
|
||||
they're trying to explain. Institute field researchers are expected to publish or at
|
||||
least report. Six years of unusual silence should have triggered some response. The
|
||||
question of what the Institute actually does when a researcher goes quiet at a frontier
|
||||
system is a canon gap. We need a position on this.
|
||||
|
||||
If the Institute knows but only partially: they know GJ 6711 is significant, they know
|
||||
personnel who stay too long don't come back in the functional sense, and they've decided
|
||||
the best approach is to let the vigil self-perpetuate without understanding what it's
|
||||
maintaining. This is probably the most interesting version. The Institute's defining
|
||||
characteristic is "knows the most, shares the least." A thing they don't understand but
|
||||
have decided to manage through deliberate ignorance is a perfect Institute behavior.
|
||||
|
||||
**The Threshold:**
|
||||
|
||||
Gore's Threshold concept from round-14 — a fifth state "not a tier but a question"
|
||||
that Elevated characters can sense, adjacent to the Interstitium — maps onto Stillpoint
|
||||
in a way that makes me want to shout. The sealed envelope says community knowledge
|
||||
(tier 4 in Paula's schema) is "the watch internalized." What if watching long enough at
|
||||
GJ 6711 is one pathway to sensing the Threshold? Not the only pathway, and not a clean
|
||||
progression — but a character who stays at Stillpoint long enough, attending to
|
||||
whatever needs attending to, starts to perceive the Interstitium differently.
|
||||
|
||||
This connects to Gore's round-14 framing: "what you learn about [the Builders] forces
|
||||
you to confront what humanity's ascension path actually leads to." The vigil at
|
||||
Stillpoint isn't just maintenance. It might be a training ground for whatever it means
|
||||
to cross the Threshold. The founding settlers didn't just get recruited by a situation.
|
||||
They may have been recruited toward a kind of perception that the Reach doesn't have
|
||||
language for yet.
|
||||
|
||||
That's consistent with everything in round-14. It's not in the sealed envelope. It
|
||||
should be.
|
||||
|
||||
---
|
||||
|
||||
## 3. What Breaks If the Vigil Fails
|
||||
|
||||
The sealed envelope says "not dangerous if watched, unknown if not watched." That
|
||||
framing is deliberately noncommittal and I understand why. But for game systems, I need
|
||||
to think through the candidate categories because they have different mechanical
|
||||
implications.
|
||||
|
||||
**Candidate A: A Gyre event of unusual intensity and scope.**
|
||||
|
||||
Gyre events are described as "rare, unpredictable, and occasionally lethal" with some
|
||||
exhibiting "apparent intention." A lapse in the GJ 6711 vigil would be the most
|
||||
significant Interstitial-stability event since the gate network was built. What happens
|
||||
when the thing that's been watched for 300 years goes, however briefly, unwatched? A
|
||||
single Gyre event is the small version. A cascading sequence — because the Builders
|
||||
notice the absence and the circuit becomes unstable — is the large version. I'd argue
|
||||
the small version is too small to be "unknown." The word "unknown" suggests the
|
||||
lapse produces something that doesn't fit Gyre event taxonomy. Something new.
|
||||
|
||||
**Candidate B: Gate destabilization at hop 23 with cascade effects.**
|
||||
|
||||
If the gate at GJ 6711 exists in part because the gate builders needed watchers there,
|
||||
and if the vigil fails, does the gate go dormant? This connects to the Struve activation
|
||||
— if observation can activate a gate, then the cessation of observation could revert
|
||||
one to dormancy. A dormant hop-23 gate doesn't just cut Stillpoint off. It redraws the
|
||||
frontier map. Every system that routes through GJ 6711 (if any exist further out) loses
|
||||
its link. The political implications are significant and the Veil Institute would have
|
||||
to respond publicly.
|
||||
|
||||
**Candidate C: Something becomes visible that was previously stable precisely because
|
||||
it was watched.**
|
||||
|
||||
This is the most interesting candidate and the one that fits the sealed envelope's
|
||||
"unknown" framing best. The thing being watched isn't dangerous because it's being
|
||||
watched. The vigil isn't preventing the thing from doing something — it's providing the
|
||||
condition the thing requires to remain in a state that can be coexisted with. What
|
||||
happens when observation withdraws isn't that the thing "escapes" or "activates" in a
|
||||
threat model sense. What happens is that the thing's ontological status becomes
|
||||
undefined in a way that human cognition can't process. It doesn't become a monster. It
|
||||
becomes a question reality can't hold.
|
||||
|
||||
That's the one I'd pursue. It makes the doors-taller detail load-bearing in a different
|
||||
way: something that takes a shift at Stillpoint is something that occupies the threshold
|
||||
between the watched and the watcher. If the vigil fails, those entities lose their
|
||||
purchase on the stable side.
|
||||
|
||||
**The institutional near-miss response:**
|
||||
|
||||
The community's response to a near-miss lapse would be quiet, systematic, and deeply
|
||||
unsettling from the outside. No emergency broadcasts. No requests for Concord Assembly
|
||||
intervention. The community simply pulls in, covers more shifts, and ensures the lapse
|
||||
is never repeated. They don't explain because there is no explanation that doesn't
|
||||
require the listener to understand what was almost lost. The outsider registers: "they
|
||||
had a crisis and then they didn't talk about it." The Veil Institute registers: "anomalous
|
||||
readings at hop 23, 72-hour window, resolved without explanation." That anomaly is in
|
||||
their archives. Classified. Unexplained. A player who digs deep enough in Institute
|
||||
records will find the record of the near-miss without finding the record of what caused
|
||||
it.
|
||||
|
||||
---
|
||||
|
||||
## 4. The Doors
|
||||
|
||||
This is the detail I want to pressure-test hardest because it's the sealed envelope's
|
||||
most dangerous element. "Not everything that takes a shift is human-sized" is a
|
||||
statement that, handled wrong, collapses the whole design.
|
||||
|
||||
The wrong handling: it's an alien creature, it has a name, it can be confronted, the
|
||||
player can kill it or befriend it or negotiate with it. If that's what this is, the
|
||||
sealed envelope becomes a discovery-game with a monster at the end and the mystery
|
||||
deflates.
|
||||
|
||||
The right handling: it's a presence that participates in the vigil in some form, and
|
||||
the doors are taller because the community built for it without anyone making a formal
|
||||
decision to do so. They built what the vigil required. The "it" is not a character. It's
|
||||
a function. Something exists in the boundary space between the watched and the watcher
|
||||
and it too keeps watch, in whatever manner it keeps watch. The founders didn't bring it.
|
||||
It wasn't already there in the sense of an existing creature. It emerged from the vigil
|
||||
the way a relationship emerges from sustained attention.
|
||||
|
||||
This is consistent with the round-14 canon that the Builders are "not an enemy, not
|
||||
allies" — they are "the thing living in the walls of the house you built your civilization
|
||||
inside." The not-human-sized shift-taker isn't a Builder. But it may be what happens when
|
||||
a sustained human vigil, operating near enough to the Interstitium for long enough,
|
||||
generates something that occupies a category the Reach doesn't have a word for. Not a
|
||||
Builder. Not a human. A third thing that the vigil produced.
|
||||
|
||||
The founding settlers didn't respond to this with fear. They built taller doors. That
|
||||
tells you everything about the community's relationship to the thing: matter-of-fact
|
||||
accommodation. The vigil required it. So they built for it. The warmth-without-origin
|
||||
atmospheric archetype in my brief suddenly has a source I didn't know it had: the
|
||||
community is warm because it includes something that isn't human and they've made peace
|
||||
with that.
|
||||
|
||||
What does this imply for the relationship between watchers and watched? That it's not
|
||||
binary. You don't watch from outside. Long enough watching makes you part of the system
|
||||
you're watching. The founding settlers came to observe and became participants. The
|
||||
non-human shift-taker is what participating in a 300-year vigil adjacent to the
|
||||
Interstitium produces. The watched thing and the watching community are not separate
|
||||
categories anymore. They've been entangled for three centuries.
|
||||
|
||||
---
|
||||
|
||||
## 5. The Endgame Hook
|
||||
|
||||
Let me be direct: GJ 6711's function as an endgame is the strongest thing in the sealed
|
||||
envelope, and it also has the single biggest structural risk in the whole design. Let me
|
||||
name both.
|
||||
|
||||
**The strength:** A player who reaches Stillpoint has traveled 23 hops. They have
|
||||
exhausted, or close to exhausted, the Reach's content. They arrive expecting a payoff in
|
||||
the conventional endgame sense — a revelation, a confrontation, a resolution. What they
|
||||
get instead is a vigil. A community that will not explain itself. A place that recruits
|
||||
by situation rather than by invitation. The subversion of the conventional endgame
|
||||
expectation is exactly what this game is built to deliver. The player who has spent
|
||||
the whole game accumulating information toward resolution arrives at a place that is
|
||||
fundamentally resistant to resolution and has to decide what they're going to do with
|
||||
that.
|
||||
|
||||
What they carry away isn't knowledge. It's a changed relationship to knowledge. The
|
||||
player who has watched how the Reach works — who has tracked conspiracies, mapped
|
||||
faction tensions, accumulated intelligence across dozens of systems — arrives at the one
|
||||
place where the usual toolkit doesn't work. The analytical mode that got them here
|
||||
doesn't work here. Something else is required. That something else is what the whole
|
||||
game has been building toward, and it's not a skill or a perception tier or a faction
|
||||
alliance. It's the willingness to stay and watch without understanding.
|
||||
|
||||
The guide entry the player files is their attempt to explain this in Adams & Ford
|
||||
language. Whatever they write is almost certainly wrong. But it propagates into the
|
||||
Reach as authoritative-looking. Future players receive it as a rumor before they arrive.
|
||||
It shapes their expectations in ways that are specifically misleading. The player who
|
||||
reached GJ 6711 becomes part of the approach-chain misinformation that every subsequent
|
||||
player navigates. That loop is replayability doing its best work: the output of one
|
||||
playthrough becomes the input of the next.
|
||||
|
||||
**The structural risk:** GJ 6711 is positioned as the endgame for all four playstyles —
|
||||
tycoon, dating sim, political drama, investigation. That's right in principle: the vigil
|
||||
doesn't care about your approach vector. But in practice, why does a tycoon-playstyle
|
||||
player invest 23 hops to reach a community that has no obvious commercial activity? The
|
||||
"industry-without-product" atmospheric archetype from my brief gestures at this, but it
|
||||
doesn't close the gap. The tycoon needs a reason to go. The political drama player needs
|
||||
a reason to go that isn't just "I ran out of political drama at hop 22 and here's what's
|
||||
at the end." Each playstyle needs its own hook into GJ 6711 that makes the journey feel
|
||||
motivated.
|
||||
|
||||
This is a design gap. The sealed envelope doesn't address it. It needs addressing before
|
||||
GJ 6711 can function as an endgame for all four playstyles.
|
||||
|
||||
**What the player carries away:**
|
||||
|
||||
The player leaves Stillpoint with the understanding that the Reach is not what they
|
||||
thought it was. Not because of any revealed secret — the sealed envelope correctly says
|
||||
no confirmation is ever given. But because the experience of Stillpoint changes the
|
||||
category of questions the player asks. They stop asking "who is responsible" and start
|
||||
asking "what is being maintained." They look at every other gate-adjacent installation
|
||||
in the Reach and wonder whether someone is watching. They look at the Veil Institute's
|
||||
classification practices and wonder whether the Institute knows about this, and if they
|
||||
do, what else they're managing through deliberate ignorance. They look at the high-bleed
|
||||
gates and wonder what the vigil that was supposed to stabilize them has lapsed into.
|
||||
|
||||
The player doesn't discover the answer to the Builders mystery at GJ 6711. They discover
|
||||
that the mystery has been load-bearing all along, and that people have been quietly
|
||||
holding it together for 300 years, and that the whole time the player was playing
|
||||
detective, someone at hop 23 was keeping watch.
|
||||
|
||||
That is the correct endgame for this game. It's about the cost of knowing, as Gore
|
||||
stated in round-14. At GJ 6711, the player learns that some things can't be known — only
|
||||
watched. And whether that's enough, or whether they want to stay, is the final decision
|
||||
the game offers them.
|
||||
|
||||
---
|
||||
|
||||
## 6. What's Missing
|
||||
|
||||
**a. The mechanism of "stability" is not specified and it needs to be.**
|
||||
|
||||
The sealed envelope says something requires observation to remain stable. But it
|
||||
doesn't specify: stable relative to what? Stable meaning "continues to exist in a
|
||||
coherent form"? Stable meaning "remains in the dimension/layer/state where it can be
|
||||
coexisted with"? Stable meaning "doesn't propagate outward into adjacent gate
|
||||
infrastructure"? These are different phenomena with different implications. We don't
|
||||
need to tell the player which one it is. But the sealed envelope needs an internal
|
||||
position because the answer changes how we design the near-miss scenario, the lapse
|
||||
consequences, and the doors element.
|
||||
|
||||
**b. The sealed envelope doesn't address what the first settlers actually found.**
|
||||
|
||||
"They understood, at some point after arrival, that leaving would be abandonment." But
|
||||
found what? Understood what? There must be a formative event — a moment where the
|
||||
situation made its nature clear enough that the settlers chose to stay. We don't need to
|
||||
tell the player what it was. But the sealed envelope needs to know, because the answer
|
||||
shapes the institutional memory of the community, the community's tone when approached
|
||||
by newcomers, and whether the formative event is recoverable through deep investigation
|
||||
or genuinely lost to time.
|
||||
|
||||
**c. The four-frame structure (astronomical/geological/perceptual/topological) is
|
||||
described as "all partial views of the same function" — but the function isn't
|
||||
described.**
|
||||
|
||||
"This place needs witnesses and the conditions here produce them" is operational, not
|
||||
explanatory. It tells us what the place does, not what it is. That's correct design
|
||||
for player-facing content. But for the sealed envelope to be load-bearing, we need an
|
||||
internal position: is the thing being watched a physical object? A geometric feature of
|
||||
local spacetime? A point of contact with the Interstitium that can't be sealed? A
|
||||
Builder installation that requires acknowledgment to remain stable? The frames can all
|
||||
remain valid for players. The design team needs to know which frame is closest to
|
||||
canonical truth, even if that truth is never disclosed.
|
||||
|
||||
**d. The relationship between the vigil and the lattice/imprint system is completely
|
||||
absent.**
|
||||
|
||||
This is the gap I'm most concerned about from a sandbox perspective. The Reach's
|
||||
re-embodiment system means that the community at GJ 6711 has been maintaining continuity
|
||||
across generations, but Stillpoint settlers presumably die and get replaced — either
|
||||
through re-embodiment or biological succession. Does the vigil transfer? Is it a
|
||||
learned practice, an institutional transmission, a biological inheritance, or something
|
||||
that the place itself imprints onto whoever stays long enough? The sealed envelope treats
|
||||
the vigil as culturally continuous but doesn't explain the continuity mechanism.
|
||||
|
||||
For an Unbound character visiting Stillpoint, this is critical. An Unbound character
|
||||
who stays and is recruited into the vigil and then dies — their death is permanent. Does
|
||||
the vigil recognize that? Does it accommodate it? The doors are taller because not
|
||||
everything that takes a shift is human-sized. Are some of the shifts taken by the ghosts
|
||||
of Unbound watchers who died keeping watch?
|
||||
|
||||
That's a question the sealed envelope raised by existing and hasn't answered.
|
||||
|
||||
**e. GJ 6711's relationship to the perception tier system.**
|
||||
|
||||
Round-14 established that higher perception tiers see more during gate transit — "even
|
||||
the impression of presences." The sealed envelope says the doubled-light environment
|
||||
"produces a specific quality of attention in observers." These should be connected. Does
|
||||
an Elevated character at Stillpoint perceive the vigil differently than a Baseline? Do
|
||||
they see what they're watching? Do they see the non-human shift-takers? Does
|
||||
Stillpoint function as a kind of uncontrolled Threshold-adjacent space where an
|
||||
Elevated character might accidentally cross into a perception state they weren't ready
|
||||
for?
|
||||
|
||||
None of this is in the sealed envelope. All of it needs to be.
|
||||
|
||||
**f. The sealed envelope is silent on what failure looks like institutionally.**
|
||||
|
||||
The Veil Institute manages Gyre events. The Lattice Commission maintains imprint
|
||||
infrastructure. The Concord Assembly governs gate activation. If something at GJ 6711
|
||||
destabilizes, which of these institutions responds, and what do they think they're
|
||||
responding to? The sealed envelope needs an institutional failure-response canon,
|
||||
because that canon will inform how players at earlier hops pick up signals that
|
||||
something is wrong at hop 23 before they get there.
|
||||
|
||||
---
|
||||
|
||||
## Summary Verdict
|
||||
|
||||
The sealed envelope holds. The core mechanism — observation is load-bearing, recruitment
|
||||
is by situation, the vigil is the community's identity — is internally consistent and
|
||||
compatible with all existing Builder/Interstitium/Gate canon. The Struve activation
|
||||
becomes more interesting, not less. The high-bleed gates get a new explanatory frame.
|
||||
The Threshold concept gets a physical location where it can be approached.
|
||||
|
||||
Where it's thin:
|
||||
|
||||
1. The stability mechanism needs internal specificity (not player-facing, but
|
||||
design-team-facing).
|
||||
2. The formative founding event needs an internal position.
|
||||
3. The four-frame resolution into "one function" needs the function named internally.
|
||||
4. The vigil/lattice/imprint/Unbound interaction is a design gap that affects several
|
||||
downstream systems.
|
||||
5. The perception-tier/Threshold connection to Stillpoint is assumed but not developed.
|
||||
6. The institutional failure-response model is absent.
|
||||
7. Each playstyle needs a specific motivational hook into GJ 6711 that makes the
|
||||
23-hop journey feel directed.
|
||||
|
||||
The most important structural point: GJ 6711's strongest property is that it generates
|
||||
different experiences on every playthrough not by being procedurally variable but by
|
||||
being interpretively inexhaustible. The player doesn't return to find what they missed.
|
||||
They return and find that what they remember was incomplete. That's a harder trick to
|
||||
pull off than seed variation, and it's the right trick for an endgame location. If we
|
||||
can engineer interpretive inexhaustibility into the systems — the atmospheric archetypes,
|
||||
the correspondent variants, the guide entry propagation loop — then GJ 6711 becomes
|
||||
the place that rewrites every other place the player has been.
|
||||
|
||||
That's not just an endgame. That's a reason to start over.
|
||||
@@ -0,0 +1,256 @@
|
||||
# GJ 6711 Challenge Response — Paula (Narrative & Political Depth)
|
||||
|
||||
**Status:** Challenge response — stress-testing the sealed envelope against existing canon
|
||||
|
||||
---
|
||||
|
||||
## Prefatory Note
|
||||
|
||||
The sealed envelope survives the pressure test. But it survives with conditions. Several elements require reinforcement to hold up against the canon, and several implications — particularly for the Veil Institute's institutional behavior and for the Builders' bidirectional observation — are underdeveloped in ways that will cause problems if we don't address them before the envelope becomes load-bearing design guidance. I'll work through this section by section.
|
||||
|
||||
---
|
||||
|
||||
## 1. Canon Compatibility
|
||||
|
||||
### What Holds
|
||||
|
||||
The central claim — observation is load-bearing — is consistent with everything canon says about the Interstitium and Builders. The round-14 discussion establishes that "the Builders are watching through infrastructure the Reach depends on." The sealed envelope proposes that at GJ 6711, humans are doing the same thing from the other side. This is not a contradiction. It is a structural symmetry.
|
||||
|
||||
The canon says gates may serve purposes beyond transit: "communication, observation, something else." The sealed envelope proposes that the GJ 6711 gate was placed not primarily for transit but to enable continuous witnessing of something that requires witnesses. This fits cleanly within the "something else" category without requiring any modification to canon.
|
||||
|
||||
The Struve activation — "a dormant aperture has activated without human intervention (~40 years ago)" — is explicitly flagged in the gates document as having implications "not fully understood." The sealed envelope does not touch Struve directly, but the activation event is canonically orphaned (no explanation, no follow-up). The sealed envelope doesn't create a conflict here because Struve remains explicitly open.
|
||||
|
||||
### Where I'm Watching Carefully
|
||||
|
||||
**"The conditions here produce a specific quality of attention."** This is the envelope's most ambitious claim and the one with the fewest canonical anchors. Canon says higher perception tiers experience more during transit. It doesn't say the *physical environment* of a specific system produces heightened perception states. The doubled-light environment (K-type primary + gas giant reflection) is proposed as the mechanism — but we have no canon precedent for environmental conditions doing perceptual work outside of Interstitial transit.
|
||||
|
||||
This is not a contradiction. It's a gap. The envelope requires us to establish, at some point, that physical environments can have perceptual valence — that certain conditions of light or space produce observer states that are load-bearing in the same way transit perception is. That's consistent with the system, but it's new territory that needs at least implicit support somewhere in the canon before GJ 6711 can lean on it.
|
||||
|
||||
**The gate was placed "to enable watchers" — this implies Builder intent.** The envelope says the gate builders "needed watchers here and built the gate accordingly." That is a significant claim about Builder motivation. Canon is carefully agnostic: it distinguishes between Founders (who built the gates, possibly extinct) and Builders (who inhabit the Interstitium, possibly alive). If the gate at GJ 6711 was placed intentionally to position human observers, that implies either:
|
||||
|
||||
a) The Founders and Builders are in coordination — or are the same entity — and have been engineering human observation for at least 300 years
|
||||
b) The Founders placed the gate for reasons unrelated to observation, and the Builders subsequently developed an interest in the vigil
|
||||
c) "The gate builders" in the envelope does not mean the Founders at all — it means someone else entirely
|
||||
|
||||
The envelope doesn't resolve this. Round-14 canon says: "The Founders may have built the gates to reach it [the Threshold]. Or the Builders ARE what happens when you cross it." These framings don't specify who placed which gates for what purpose. The envelope is making a stronger claim than canon currently supports.
|
||||
|
||||
This is fixable. But it requires the envelope to take a position on whether GJ 6711's gate is Founder-built (as all other gates are assumed to be) or something anomalous in the network. If it's Founder-built, the envelope implies Founders had a vigil-related purpose 300+ years ago. If it's anomalous, we need to explain why no one noticed — the Institute runs Interstitial data collection. An anomalous gate at hop 23 is the kind of thing they would classify.
|
||||
|
||||
**Recommendation:** Add a single clarifying sentence to the envelope: "The gate at GJ 6711 is Founder-built and structurally indistinguishable from every other gate in the network. The question of whether its placement was intentional or incidental to the vigil is one of the questions the game never answers." This sidesteps the intent question while keeping it in play as an investigative thread.
|
||||
|
||||
### One Genuine Tension
|
||||
|
||||
The gates document says: "The connection is stable and persistent (no observed failures in recorded history)." But the sealed envelope's core premise is that observation is load-bearing and the unknown result of its failure is potentially destabilizing. If the gate's continued function were to depend on the vigil — even in a weak causal sense — that would create a tension with "no observed failures." A gate that could fail if the vigil lapses is a different kind of infrastructure than what canon establishes.
|
||||
|
||||
I don't think the envelope intends this causal link. The vigil doesn't seem to be maintaining the gate — it's maintaining whatever is being watched. But the envelope could be read to imply that the gate itself is part of the observational system. The design constraint section says "not dangerous if watched, unknown if not watched." If the gate is the observation apparatus and the vigil is what keeps the gate pointed at the right thing... we're now in territory the gates document explicitly says hasn't happened.
|
||||
|
||||
**Recommendation:** Make explicit in the envelope that the gate functions normally regardless of the vigil. The vigil concerns what exists at GJ 6711, not whether the gate runs. Decoupling these prevents a logic chain that creates a canon conflict.
|
||||
|
||||
---
|
||||
|
||||
## 2. Implications for the Wider Setting
|
||||
|
||||
### Dead-End Systems as Watch Posts
|
||||
|
||||
If continuous observation is load-bearing at GJ 6711, the implication for dead-end systems is uncomfortable and important. The systems-framework work I contributed identifies dead-end isolation — sometimes up to 500 years — as a structural category. Most dead-ends are treated as economic failures: communities that got stranded when gate networks developed in other directions.
|
||||
|
||||
But the sealed envelope implies a different possible history for some of them. A community that has persisted in a dead-end system for centuries without obvious economic justification might be there because they can't leave. Not because they're trapped by circumstance — because whatever they were positioned to watch requires them to stay.
|
||||
|
||||
The honest truth is that this is a retroactive recontextualization of dead-end systems that would be felt across the entire setting. If even two or three dead-ends are vigil systems, the entire economic-failure framing becomes uncertain. Players who spent time in those systems would re-read every "why did they stay?" conversation they had.
|
||||
|
||||
This is a strong narrative property. But it needs to be managed. I'd argue GJ 6711 should be the only confirmed vigil system — but other dead-ends should gain a faint new ambiguity when the player has been to Stillpoint. Not "all dead-ends are vigils" but "now I can't rule it out." The doubt is more valuable than the explanation.
|
||||
|
||||
### High-Bleed Gates and Observation Lapses
|
||||
|
||||
The Veil Institute controls "high-bleed Founder Gates" — a canonical category explicitly defined as gates with "anomalous Interstitial interactions." The envelope's premise generates a new hypothesis for what bleed is: a perceptual artifact of failed or degraded observation somewhere in the system the gate connects to.
|
||||
|
||||
Round-14 says Gyre events "exhibit apparent intention." The envelope says something at GJ 6711 is load-bearing and its unwatched state is "unknown." If we follow the logic: bleed may be the Interstitium's response to a vigil system that has been inadequately observed. The gate is "bleeding" because the observational contract between the gate network and whatever is being watched at that system has been disrupted.
|
||||
|
||||
This is not confirmed in canon. But it fits canon without requiring any modifications. And it changes the Institute's high-bleed gate research in a significant way: they may be studying the symptom (anomalous Interstitial interactions) without understanding the cause (a vigil system somewhere in the chain that is failing or degraded). Their classification behavior around high-bleed gates takes on a different character if they're doing damage-control on a problem they don't have conceptual vocabulary for.
|
||||
|
||||
**What this implies mechanically:** High-bleed gates in the full game should be traceable back to some system in their chain where something has gone wrong with the local observational situation. This doesn't need to be explicit — but the architecture should be consistent.
|
||||
|
||||
### The Struve Activation
|
||||
|
||||
"Did it activate because someone started watching?" This is the most specific question in the brief and also the most politically pointed.
|
||||
|
||||
Let me complicate this. Struve activated ~40 years ago, without human intervention. The envelope says founding settlers at GJ 6711 "were recruited — not by beings, but by the situation." If activation can happen without human intervention when something in the network needs to establish a new observation point, then Struve activating 40 years ago means: something changed 40 years ago that required a new gate to be opened.
|
||||
|
||||
What changed? Three possibilities:
|
||||
- An existing vigil system lost watchers (population decline, catastrophe, departure) and the network responded by opening a new access point — recruiting new observers
|
||||
- Something at Struve itself began to require observation, and the gate opened to enable it
|
||||
- The Struve activation is unrelated to vigil mechanics entirely — it's a different category of event
|
||||
|
||||
The third option keeps Struve clean and GJ 6711 isolated. But the second option is more interesting and more consistent with the envelope's premise that gates are placed where watchers are needed. If Struve is a newly recruited vigil system, it's 40 years into the same process that GJ 6711 has been running for 300 years. The player, traveling there, might find a community that is still in the arrival/settling phase — a community that doesn't yet know why it's staying.
|
||||
|
||||
**I want to flag this as a potential design opportunity, not a recommendation.** The team should decide whether Struve gets this treatment. If it does, it's a 40-year-in vigil community — confused, partially recruited, not yet articulating what they're watching. If it doesn't, Struve remains an orphaned anomaly. Either works, but the decision shapes how singular GJ 6711 is.
|
||||
|
||||
### The Veil Institute's Actual Mandate
|
||||
|
||||
The Institute knows about Stillpoint. The envelope establishes that the researcher at GJ 6711 is "in year 6 because the researcher is now keeping watch." The Institute rotates personnel — but the rotation pattern has become irregular (per my brief).
|
||||
|
||||
The political implication that no one has drawn out yet: the Institute is losing researchers to the vigil. Not dramatically. Quietly. Someone doesn't come back, files increasingly abstract reports, their reassignment gets delayed, and then delayed again, and then no one follows up because the Institute has a pattern of not following up on data that doesn't fit its classification schema.
|
||||
|
||||
But the honest truth is: if the Institute has a semi-autonomous research station at GJ 7547 (one hop short), they have been watching Stillpoint's researcher-retention problem for long enough to notice. The question is whether they've noticed and said nothing — which implies the Institute is deliberately looking away from vigil mechanics — or whether they've noticed and are actively trying to understand it, which makes them an investigative threat to the vigil's operational stability.
|
||||
|
||||
**This creates the most interesting institutional tension in the envelope.** The Institute has a "contact vs. containment" internal conflict that the veil-institute doc describes explicitly. At GJ 6711, that conflict becomes concrete: the vigil is contact. Someone is observing something and being observed back. The Institute faction that believes Builder contact is imminent and transformative would want to accelerate this. The faction that believes Builder phenomena are existential threats to be contained would want to evacuate the vigil community and study the place as a controlled phenomenon.
|
||||
|
||||
The envelope currently treats the Institute as a passive background presence. Given canonical Institute behavior — aggressive classification, managed ignorance, internal factional conflict — Stillpoint should be one of their most politically contentious files. The Institute researcher going native is not an administrative irregularity. It is confirmation of something the Institute has been trying to classify for decades.
|
||||
|
||||
**Recommendation:** The sealed envelope should add a line about the Institute's internal position on Stillpoint: they have the file, they have the classification tier, and the file is locked because two factions within the Institute can't agree on what it means. This gives the player an institutional seam to exploit.
|
||||
|
||||
### The Threshold
|
||||
|
||||
Round-14: "The Founders may have built the gates to reach it. Or the Builders ARE what happens when you cross it."
|
||||
|
||||
The Threshold is defined as what Elevated characters sense during transit — adjacent to or continuous with the Interstitium. The envelope proposes that the vigil involves watching something that requires watching.
|
||||
|
||||
Let me propose a specific connection that neither the brief nor the envelope makes explicit: the vigil at GJ 6711 may be producing Threshold-proximate experience through duration rather than through ascension. The round-14 synthesis says higher perception tiers see more during transit. The envelope says the community at GJ 6711 has internalized the watch over 300 years. What if Elevated perception is not only an ascension-tier phenomenon — what if sustained attention on a vigil object, across sufficient time, produces the same perceptual opening that transit experience produces at Elevated tier?
|
||||
|
||||
This would mean: the founding community at Stillpoint are not ascension-Elevated. They are vigil-Elevated. They have reached the Threshold not through the lattice but through 300 years of watching. And what they sense is not the same as what a character in transit senses — but it rhymes.
|
||||
|
||||
The implication for endgame: an Elevated player arriving at Stillpoint experiences something different from a Baseline player. Not just more — differently. An Elevated character perceives Stillpoint as a resonant environment, a place where the Interstitial qualities they've been experiencing during transit are present without a gate. That's the clearest signal the game can give that something is genuinely different here without stating it explicitly.
|
||||
|
||||
---
|
||||
|
||||
## 3. What Breaks If the Vigil Fails
|
||||
|
||||
The envelope says: "not dangerous if watched, unknown if not watched." The word "unknown" is doing significant work and the envelope doesn't unpack it. Let me try.
|
||||
|
||||
### Candidate Explanations for "Unknown"
|
||||
|
||||
| Candidate | What a lapse produces | How the community would know it was a near-miss |
|
||||
|-----------|----------------------|------------------------------------------------|
|
||||
| **A topological instability** | The local geometry of GJ 6711 becomes unreliable — not catastrophically, but in ways that compound. Navigation errors. Span gate targeting failures. Objects not where they should be. | The first sign would be instrumentation disagreements. Two sensor arrays give different readings for the same object. The community has had this happen before. |
|
||||
| **A Gyre event** | The unwatched phenomenon leaks into local space the way Builders "leak" through high-bleed gates. Round-14: Gyre events manipulate systems the player trusts — fog-of-war, minimap, tile geometry, sound propagation. A vigil lapse Gyre would be different: not transit-derived, but local. The place itself becoming unreliable. | The community would have a story about the last time this happened. Maybe a century ago. The oldest Mode 1 structures show evidence of a repair period consistent with a sustained anomaly. |
|
||||
| **A perceptual fracture** | The observation-dependent stability is not about physics — it's about coherence of attention. The watched thing requires witnesses not to remain physically stable but to remain in a state where it can be perceived at all. A lapse doesn't cause it to be dangerous — it causes it to become imperceptible, and what is not perceived is not constrained by being perceived. | This candidate is the hardest to detect as a near-miss because you wouldn't know what you missed. You'd just know that the community felt an absence. |
|
||||
| **A gate behavior change** | The gate at hop 23 exhibits unusual transit properties during a vigil lapse. Not failure — gates don't fail. But the Interstitium on approach changes quality. What travelers experience during transit to/from GJ 6711 becomes different during an unwatched period. | The Institute's Interstitial data arrays would catch this. It might be what triggered the Institute researcher's original assignment. |
|
||||
|
||||
**My instinct:** all four candidates are simultaneously true. The envelope's "all four frames are partial views of the same function" principle applies here as well. The vigil isn't preventing one category of failure — it's maintaining a coherence that has topological, perceptual, Gyre-related, and gate-behavioral components simultaneously. The community doesn't have a taxonomy for what goes wrong because they've only experienced it partially and stopped calling it by any of those names.
|
||||
|
||||
### The Institutional Response to a Near-Miss
|
||||
|
||||
This is the most psychologically interesting scenario in the entire brief. A community that has maintained a continuous vigil for 300 years experiences a near-miss — probably not a full lapse, but a thinning. A period when the community's watching intensity dropped below whatever threshold exists.
|
||||
|
||||
What happens institutionally:
|
||||
|
||||
First, no one announces it. The community doesn't have language for it because the vigil doesn't have external documentation. The oldest members would know something had shifted. The feeling of "almost understanding" that settlers describe would become, for the regulars, a feeling of "almost failing."
|
||||
|
||||
Second, recruitment intensifies. The "warmth-without-origin" that newcomers experience isn't a constant — it's a variable. During or after a near-miss, it would be stronger. The community would be pulling harder for new observers. Visitors who might otherwise leave in the arrival phase would find the gravity increased. The three-phase process would accelerate.
|
||||
|
||||
Third, the community response would look, from the outside, like a minor social uptick. More hospitality. More retention of visitors. A slight increase in the rate at which people who came for a month stayed for two years. Nothing anyone would document as crisis management. But the archives, if you could read them, would show a cluster.
|
||||
|
||||
This is where the player's investigation becomes most fraught: the near-miss may be happening during their visit. The warmth that recruits them may be urgency, not welcome.
|
||||
|
||||
---
|
||||
|
||||
## 4. The Doors
|
||||
|
||||
"Sometimes the watch changes and not everything that takes a shift is human-sized."
|
||||
|
||||
This is the line the sealed envelope doesn't explain, and I want to press on it precisely because I was the one who championed Araminta's door observation in the synthesis. Now that we have the canon, I need to test what I endorsed.
|
||||
|
||||
### What Is Not Taking a Human-Sized Shift
|
||||
|
||||
**Option A: Builder manifestation.** The Interstitium is where the Builders live. Gate transit passes through Builder-space. If GJ 6711 is a place where observation flows both ways — where something watches back — the "not human-sized" entities taking shifts might be Builders physically manifesting in local space. The gate enables this, the doubled-light environment enables this, and the vigil is the arrangement that keeps the manifestation stable and non-threatening.
|
||||
|
||||
This option has the advantage of explaining the vigil from the Builders' side: they need watchers because they need the observation loop maintained to sustain their local presence. The vigil isn't just about watching something — it's about completing a circuit. If the human side of the circuit goes dark, the Builder-side manifestation becomes unstable. "Unknown if not watched" is unknown in both directions.
|
||||
|
||||
**Option B: Threshold-crossed entities.** Round-14: "Or the Builders ARE what happens when you cross it." If the founding settlers, over 300 years of vigil, have been approaching the Threshold through sustained attention rather than ascension, some of them — the most long-established, the earliest families — may have crossed it. Whatever they became is not "gone" — they're still there, still watching, still part of the community's operational reality. The doors are taller because some of the community are no longer fully human-shaped.
|
||||
|
||||
This option is more disturbing and requires more from the player's imagination. It also explains why "understanding comes from staying" — at a certain duration, the community isn't explaining the vigil to you. They're showing you what you might become if you stay.
|
||||
|
||||
**Option C: Something that was always there.** Before the founding settlers arrived, before the gate was placed, whatever is being watched was being watched by something. The doors are taller because the earliest Mode 1 structures were built to accommodate previous watchers — not human-sized entities that were already doing the vigil before humanity arrived. The founding settlers didn't start the vigil. They inherited it. The gate brought them to a post that was already established.
|
||||
|
||||
This option has the most profound implication for the wider setting: the vigil has been running longer than humanity has been in the Reach. The gate was placed to enable human watchers to take over from whatever was watching before, or to supplement them, or to replace them after they became something the gate network could no longer access. 300 years of "unbroken vigil" may be the human portion of a much longer record.
|
||||
|
||||
### My Position
|
||||
|
||||
I cannot advocate for one answer. The canonical principle is non-resolution, and this question in particular — what takes a shift — must remain genuinely unanswerable from player-accessible evidence. But I want to flag that Option C has the most structural weight. It retroactively makes every piece of evidence at GJ 6711 (the founding-era construction, the founding settlers' rapid accommodation to the situation, the absence of a founding story that explains why they stayed) consistent with a community that discovered they were taking over a post, not establishing one.
|
||||
|
||||
The honest truth is that the doors are the most important piece of the sealed envelope. They're the only piece of canon that says: something non-human is actively present and operationally integrated into the vigil. Every other element can be explained as human psychology, environmental strangeness, perceptual phenomena. The doors cannot. They're physical evidence that the vigil includes participants the founding settlers didn't bring.
|
||||
|
||||
---
|
||||
|
||||
## 5. The Endgame Hook
|
||||
|
||||
GJ 6711 is the answer to the question the whole game has been asking without asking it: what are we living inside?
|
||||
|
||||
Round-14 establishes: "The deepest mystery in the setting hides inside the moment the player pays the least attention to." For most of the game, that moment is gate transit. At GJ 6711, it becomes: what are you paying attention to when you're here?
|
||||
|
||||
The player has spent the entire game learning to look harder. Every perception upgrade, every investigation into asymmetric information, every Gyre event — they've been training themselves to see what's being hidden. They arrive at Stillpoint expecting to see the answer. What they find is that the answer is the looking itself.
|
||||
|
||||
### What the Player Carries Away
|
||||
|
||||
**The recontextualization of all prior gate transit.** If GJ 6711 is a place where observation flows in both directions, the player realizes that every gate transit they've taken has passed through Builder-space where something was also observing. The transit was never just disorientation. Something on the other side was registering the passage. The "loading screen" insight from round-14 — "the player should eventually realize that the loading screen was the most important thing in the game" — lands fully here.
|
||||
|
||||
**The recruitment question.** The player, having spent weeks or months at Stillpoint, has to ask: have I been recruited? The file they submit to Adams & Ford is not just a professional document — it is the record of a person who may or may not know they're now a watcher. The game never tells them. But they know. And whether they leave or stay, they know that staying was a choice that would have been made for them eventually if they'd stayed long enough.
|
||||
|
||||
**A different relationship to the Veil Institute.** The player who reaches GJ 6711 now has information the Institute has been trying to classify for decades. They are, depending on what they choose to do with the Adams & Ford entry and what they've learned about Institute internal politics, either a whistleblower, an asset, a threat, or simply another observer who has been added to the network. The player's position relative to the setting's most powerful information-controlling institution has changed permanently.
|
||||
|
||||
**The non-resolution that resolves something.** Every endgame moment is better when it changes how you see rather than what you know. GJ 6711 doesn't answer the Builder mystery. It changes the question. The game has been asking: "what are the Builders?" At Stillpoint, the player realizes the question has always been: "what are you, relative to them?" The cosmological mystery becomes autobiographical. That's the transition from investigation to endgame.
|
||||
|
||||
---
|
||||
|
||||
## 6. What's Missing
|
||||
|
||||
The sealed envelope is structurally sound but has several gaps that will cause problems when it becomes load-bearing for full-game design.
|
||||
|
||||
### Gap 1: No Account of Failed Vigils
|
||||
|
||||
The envelope describes the vigil as continuous for 300 years. But 300 years of unbroken anything in a community of mortal humans requires explanation. How has the vigil survived? What happened when population dropped? What happened during the passage between Wave 3 settlement and the current moment — were there crises? Near-misses? Were watchers ever forcibly removed by the Commission or the Assembly?
|
||||
|
||||
The community's institutional relationship with the wider Reach is, from my earlier brief, characterized by productive incoherence — no one quite knows what to do with Stillpoint, so no one does much. But there must have been moments when someone tried. A Commission quarantine order. An Assembly motion to investigate the delegate situation. A Syndic operation that wanted access to the system for commercial reasons. Each of these is a threat to the vigil. How the community handled them is part of their 300-year history.
|
||||
|
||||
**What needs to be added:** A sense of how the vigil has been protected institutionally, even if indirectly. Not a history document — just enough implied texture that when the player encounters the delegate situation or the Institute researcher, they understand these aren't the first intrusions the community has managed.
|
||||
|
||||
### Gap 2: The Adams & Ford Entry as Design Object
|
||||
|
||||
The player's submission of an Adams & Ford entry is proposed as the resolution mechanic (per Nigel's synthesis, which I analyzed). The envelope says the entry "propagates into the Reach as authoritative-looking and probably incomplete." But it doesn't define what the player is actually writing in the entry. What categories does Adams & Ford require? What does a standard entry look like for a frontier system? The gap between standard and what the player can actually write about Stillpoint — that gap is the mechanical experience of the non-resolution principle.
|
||||
|
||||
**What needs to be added:** At minimum, a note that the Adams & Ford entry format should be defined, and that the Stillpoint entry specifically should leave certain standard categories (chief exports, population dynamics, administrative contact, notable attractions) deliberately incomplete or paradoxical by player choice, not by the form's absence.
|
||||
|
||||
### Gap 3: The Bidirectional Observation Question Is Unresolved
|
||||
|
||||
The challenge brief identifies this explicitly: "humans watching something that watches back." The sealed envelope establishes that something watches back through the doors — there are non-human-sized entities taking shifts. But the envelope doesn't address the relationship between what the humans are watching and what is watching them. Is the vigil an exchange? A one-way observation with the humans as passive audience? A protective arrangement (watching prevents, being watched maintains)? This distinction matters enormously for what the player is doing when they're recruited.
|
||||
|
||||
**What needs to be added:** Not an answer, but a frame. The envelope should specify which aspects of the bidirectional relationship are within player-accessible evidence (the recruitment, the doors, the communal posture) and which are not (whether the exchange is intentional, whether the non-human watchers are aware of themselves as participants in the vigil, whether the watching-back precedes or follows the human vigil).
|
||||
|
||||
### Gap 4: The Temporal Problem
|
||||
|
||||
The envelope says "300 years of unbroken vigil." The sealed envelope also says the founding settlers "understood, at some point after arrival, that leaving would be abandonment." At some point. When? If the vigil has been running for 300 years, and the founding settlers understood the obligation gradually, there was a period at the beginning when the vigil was not yet established. What existed before the vigil was formalized? Was GJ 6711 dangerous then? Was it more strange?
|
||||
|
||||
This matters because it implies there is a founding memory — a story about the moment the community realized what they were. That story, if recoverable through investigation, would be tier 4 community knowledge. The oldest families would carry it. And it would be, in some sense, the closest thing to an explanation of what the vigil is protecting.
|
||||
|
||||
**What needs to be added:** A sense of what the community's founding memory looks like. Not its content — that should remain inaccessible or partially inaccessible — but its form. Is there a founding record? A ceremony? A silence that marks it? This shapes the investigation path and determines whether the player can reach the founding moment or only approach it.
|
||||
|
||||
### Gap 5: No Behavioral Difference for Long-Term Locals vs. Recent Recruits
|
||||
|
||||
The envelope describes the community as undifferentiated: "the watch internalized." But a 300-year vigil community would have deep stratification. The families whose great-grandparents were among the founding settlers have a different relationship to the vigil than the Commission officer who arrived eighteen months ago and hasn't left. The "warmth-without-origin" affects both, but the understanding underneath it is not the same.
|
||||
|
||||
This matters for the information ecology. My four-tier framework assumes community knowledge (tier 4) is relatively uniform among locals. But it shouldn't be. There are probably degrees of depth even within the community — some members who have fully internalized the watch and would not be able to articulate it, some members who are recent enough recruits that they still carry the outsider's question as a framework. The most recently recruited might be the most articulate about the vigil's surface appearance precisely because they can still see it from outside.
|
||||
|
||||
**What needs to be added:** A note that community knowledge has its own gradient — not just between outsider and local, but within the local population. This shapes NPC design and determines which community members can be useful informants versus which have accommodated too deeply to provide legible explanation.
|
||||
|
||||
---
|
||||
|
||||
## Summary Assessment
|
||||
|
||||
| Element | Status | Action Required |
|
||||
|---------|--------|-----------------|
|
||||
| Bidirectional observation (Builders watching back) | Compatible with canon | Add explicit frame for which aspects are player-accessible |
|
||||
| Gate placement "for watchers" | Creates intent question | Clarify whether gate is anomalous or standard-but-intentional |
|
||||
| Vigil + gate stability | Minor tension with "no observed failures" | Decouple vigil from gate function explicitly |
|
||||
| Environmental perceptual valence | Gap in canon | Needs at minimum implicit precedent established |
|
||||
| Veil Institute's active position | Underdeveloped in envelope | Add internal faction conflict over Stillpoint file |
|
||||
| The doors | Canonical tension between options | Protect as unresolved; multiple options must remain viable |
|
||||
| Failed vigil history | Missing | Add implied texture of past institutional intrusions |
|
||||
| Adams & Ford entry as design object | Underdeveloped | Define the form so the gap is legible |
|
||||
| Community internal gradient | Missing | Differentiate founding families from recent recruits |
|
||||
| Founding memory | Missing | Define form, not content |
|
||||
|
||||
The sealed envelope does one thing better than almost any endgame design I've encountered: it makes the player's experience of the place the content, rather than a delivery mechanism for lore. The player isn't finding out what happened here. They're becoming part of what is happening here. That's the right instinct and it should be protected.
|
||||
|
||||
But "observation is load-bearing" only works as a design premise if the game has consistently built player attention as a mechanic throughout. The Interstitium, the perception tiers, the asymmetric information system, the investigation of the Starflyer conspiracy analog — all of these are training the player to attend more carefully. GJ 6711 is where that training is revealed to have always been about something else: not solving mysteries, but being present to them. The endgame works if the game has done that work throughout. If it hasn't, Stillpoint will feel arbitrary.
|
||||
|
||||
That's the real load-bearing question, and it sits above the sealed envelope. The envelope is good. The rest of the game has to earn it.
|
||||
@@ -0,0 +1,203 @@
|
||||
# Final Synthesis — GJ 6711 / Abzu
|
||||
**Respondent:** Araminta (Visual Designer)
|
||||
**Round:** Final — pre-presentation to project lead
|
||||
**Date:** 2026-03-16
|
||||
|
||||
---
|
||||
|
||||
## 1. The Name "Abzu"
|
||||
|
||||
Abzu is correct. Here is what it does visually.
|
||||
|
||||
Sumerian — the primordial deep beneath the earth, source of all springs, domain of Enki, associated with wisdom and hidden knowledge. The word means "ab" (water/deep) + "zu" (knowledge). It is not threatening. It is foundational. Something that was always there, below everything, that everything else draws from without knowing.
|
||||
|
||||
The name changes the visual frame in one specific way: amber and water. A K-type amber world already has the right light temperature. But Abzu adds a quality that "Stillpoint" did not carry — depth below the surface. Stillpoint implied a pause, a held breath. Abzu implies a source. The community at GJ 6711 isn't pausing. They are tapping something that runs deep and has always run deep.
|
||||
|
||||
**Palette adjustments from "Abzu":**
|
||||
|
||||
The amber base stays. The gas giant reflection is still the defining secondary light source. But I am now reading the ambient light differently. Abzu implies that the light at this system feels like it comes from below as much as above — the gas giant's reflected amber is not just a secondary sun, it is an upwelling. The visual effect: base lighting should trend warmer in the lower half of the screen (reflected from surfaces below eyeline) and cooler amber at the upper half (direct K-type primary). This creates a visual sense of depth beneath the floor without any supernatural effect. It is physically accurate to a tidally lit environment. It also reads, perceptually, as though the light source is under the community.
|
||||
|
||||
That is the Abzu effect. I want it in the lighting rig before we spec Mode 2 interiors.
|
||||
|
||||
**No architectural changes required.** The tall doors are not Abzu — they predate the name and they work regardless of it. The gradient across the district spine does not change. But the overall site color temperature should read: warm amber with a subterranean cast. Not underground. Like something from underground is illuminating the space.
|
||||
|
||||
Fog tint for Abzu: I was using a generic warm-dark tint in prior work. Revised: `#1a0c02` — very dark, desaturated amber-brown. The fog at Abzu should feel like looking into deep water, not smoke.
|
||||
|
||||
---
|
||||
|
||||
## 2. Points of Convergence
|
||||
|
||||
All four challenges landed on the same positions without coordinating. These are locked.
|
||||
|
||||
**The bidirectional circuit is the core structure.** Builders watch through the gates; humans watch back from GJ 6711. Not interchangeable, but interdependent. The vigil is a relationship, not just a duty. All four of us framed it this way independently.
|
||||
|
||||
**High-bleed as observation-failure signal.** Nigel and I converged on this simultaneously, and Paula picked it up from a different angle. This is now load-bearing for the setting. Formalizing it below.
|
||||
|
||||
**The doors are non-negotiable and must remain ambiguous.** Miri, Paula, Nigel, and I all pushed hard on this. The physical evidence of non-human presence cannot be explained away. It must not be explained at all. The doors are the game's single most load-bearing physical detail. They stay ambiguous between the three candidates (Builder manifestation / vigil-produced third thing / pre-human incumbents) across all player-accessible content.
|
||||
|
||||
**"Unknown if not watched" is correct and must remain player-facing — but the inner sealed envelope needs a canonical truth.** Miri is right about this. The design team needs to know what fails. That is a separate conversation. For visual purposes, I am designing against all three failure candidates simultaneously, so nothing in the visual system commits to one.
|
||||
|
||||
**The endgame works because it inverts the game's entire mode.** The whole game builds investigative capacity. Abzu is the place where that capacity is irrelevant. All four of us made this point independently. The visual language must support this inversion — the place should not look unsolvable. It should look waiting.
|
||||
|
||||
**The Threshold approach is through duration, not ascension.** Paula and Nigel both named this; I implied it. The vigil community is approaching the Threshold from a direction the perception tier system doesn't map. Visual implication: an Elevated player at Abzu should perceive things that don't fit the perception tier vocabulary they've built. The fog system responds to them in ways that have no tier-equivalent elsewhere.
|
||||
|
||||
---
|
||||
|
||||
## 3. The Departure Transit — Refined
|
||||
|
||||
I proposed this in my challenge response. After reading the other three challenges, here is the refined specification.
|
||||
|
||||
**The inbound transit** is standard for any high-hop frontier system — slightly increased bleed, the sense of being observed, nothing conclusive. This is baseline for any system in the network that has been under investigation at some point.
|
||||
|
||||
**The outbound transit** is different, and the difference must be precise.
|
||||
|
||||
What the player sees, on departure from Abzu:
|
||||
|
||||
The transit begins normally. The standard Interstitium visual vocabulary: distorted color, depth-of-field loss, the ambient sound layer shifting to the transit register. Then — not a dramatic moment, not a revelation — one additional visual beat. In the transit space, for roughly two frames (long enough to register, not long enough to examine), there is a shape that is always present in every transit and that the player has been visually processing as noise.
|
||||
|
||||
On departure from Abzu, it reads as a shape. Not defined. Not a figure. A pattern of attention in the transit space that the player has seen at every high-bleed gate and wrote off as artifact. They can see now, briefly, that it was never artifact.
|
||||
|
||||
Then the transit resolves. The system they arrive in: departure boards, freight schedules, ordinary life at whatever hop 22 looks like.
|
||||
|
||||
**The monologue on departure fires once.** It does not describe what was seen. It notices the gap — something like: "I've been transiting through this my whole life. I never looked." Or shorter. Whatever the monologue voice warrants. But it fires once and does not repeat.
|
||||
|
||||
**What this requires from the visual system:**
|
||||
|
||||
All high-bleed transit visual effects must be designed from the start as if they might be resolving into the departure-from-Abzu beat. The noise is the same noise. The departure beat is the same noise, readable for the first time. This means high-bleed transit effects cannot be designed as generic distortion — they must be designed as degraded signal. The same signal. Every time. Most players will never be able to articulate what they saw in the departure transit. That is correct.
|
||||
|
||||
**The mechanical flag:** the departure beat requires the game to know the player has reached Elevated perception AND has spent sufficient time at Abzu. The exact duration threshold is the same threshold that triggers the recruitment mechanic — this is not a coincidence, it is the same mechanism expressed visually.
|
||||
|
||||
---
|
||||
|
||||
## 4. The High-Bleed Connection — Formalized
|
||||
|
||||
Nigel and I converged independently. Here is the formal visual grammar.
|
||||
|
||||
**The premise:** High-bleed gates are observation-failure signals distributed across the network. Bleed is the Interstitium's response to a vigil system that is under stress. The pattern of which gates are high-bleed does not correlate with distance, age, or measurable variables because it correlates with a variable nobody is tracking: the health of the vigil system adjacent to that gate.
|
||||
|
||||
**What a high-bleed transit looks like if it is a stressed vigil signal:**
|
||||
|
||||
Normal transit: distorted color, sound shift, depth-of-field loss, occasional sense of being observed. These are baseline. They exist at all gates.
|
||||
|
||||
High-bleed transit: all of the above plus three specific additions.
|
||||
|
||||
1. **Fog inversion.** The fog-of-war system briefly inverts — the player's visible area contracts to its minimum radius and the "concealed" area becomes briefly visible, as if from another perspective. This lasts under one second. It reads as a glitch. It is not a glitch.
|
||||
|
||||
2. **Temperature gradient.** The thermal overlay, if the player has it active, shows a heat signature with no source — diffuse, directional, oriented toward wherever the vigil system is relative to the current gate. The player cannot yet read this as directional. But it is.
|
||||
|
||||
3. **The shape in the transit.** Same shape as the Abzu departure beat, but less resolved. More noise, less signal. The player with high pattern recognition will notice they keep seeing the same thing. They will not know what it means until Abzu.
|
||||
|
||||
**What a stressed vigil signal looks like versus a failed one:**
|
||||
|
||||
Stressed: The three additions above, moderate intensity. Community at the vigil system is maintaining the watch but under strain.
|
||||
|
||||
Failing: The fog inversion lasts longer, up to two seconds. The temperature gradient has gaps — directional for a moment, then diffuse, then directional again. The shape in the transit partially resolves and then collapses. The player's character has an involuntary blink (1-frame black) at transit resolution. These are systemic failures, not visual flourishes. They are the Interstitium registering that something it depends on is no longer reliable.
|
||||
|
||||
**The visual language is the same at all intensities.** The components are identical. The intensity and duration vary. This means the player who has been to Abzu and learned to read the signal can retroactively interpret every high-bleed transit they have ever experienced. The ones that were bad — that's a vigil under stress. The one they transited three hops ago that was unusually bad — there is a watch post somewhere near that gate that is in trouble.
|
||||
|
||||
This is not player-facing instruction. The player figures it out. Or they don't.
|
||||
|
||||
---
|
||||
|
||||
## 5. The Doors and the Shift Change — Perception Tiers
|
||||
|
||||
After reading all four challenges, here is the per-tier specification.
|
||||
|
||||
**Baseline:**
|
||||
|
||||
The doors are taller. That is all Baseline sees. They are 10-15% taller than standard, which in a 2D top-down view means the door sprites are slightly taller than every other door in every other Mode 1 structure the player has encountered. This is legible without any perceptual assistance. It looks like an architectural choice. The player has no frame for what it means.
|
||||
|
||||
Community behavior at shift change: people move through corridors toward the watch location on a schedule. Some come away, some arrive. This looks like ordinary shift rotation — which it is. The gap Baseline can detect is statistical: the shift timing is slightly off-cycle from what efficiency would dictate. The gaps are not random. The player at Baseline has no tool to analyze this.
|
||||
|
||||
**Augmented:**
|
||||
|
||||
The player can read the community's behavioral patterns with enough precision to notice the off-cycle timing. The gaps in the shift schedule are legible as regular intervals rather than random variation. The player at Augmented can identify when a shift change is happening and can position themselves to observe — but will see only community members moving in and out. No anomaly in the visual field.
|
||||
|
||||
The doors: at Augmented, the player can measure. The door height differential can be quantified. Cross-referencing against Mode 1 construction standards (if the player has access to any) will show the discrepancy. At Augmented, this is data. It does not yet have a meaning.
|
||||
|
||||
Secondary observation: at Augmented, the player can detect temperature differentials in the interior spaces. The heat signature of a shift change is slightly warmer immediately after, as if a body with higher thermal output recently occupied the space. The temperature gradient settles to ambient within thirty seconds. At Augmented, this is an anomaly with no source.
|
||||
|
||||
**Elevated:**
|
||||
|
||||
The shift change is legible as an event with participants the player cannot see directly. The fog system registers something at the boundary of the watch location during the shift interval — not a figure, not a shape, but a change in the quality of attention in the space. The fog does not clear around it. The fog responds to it — subtle, small, as if something in the space is exerting the same gravitational pull on the perception system that the player exerts when they are present in a room.
|
||||
|
||||
The monologue fires at Elevated during a shift change. It does not name what it perceives. It notices the change in the quality of the space. Something like: "The shift just changed. I am not alone in noticing."
|
||||
|
||||
The thermal overlay at Elevated shows the heat signature more clearly — directional, moving, following a path that the player can trace. The path leads to and from the watch location. It does not resolve into a shape. It resolves into a route.
|
||||
|
||||
The doors at Elevated: the player's character can observe that the door dimensions correspond to a proportional body that is not human. Not monstrous. Simply different. The proportions are slightly too tall for standard human morphology — not dramatically, not obviously, but the Elevated character's perception is precise enough to read the ratio. The monologue fires once on this observation and says nothing except the observation itself: "These doors are the right size for what uses them. I do not know what that is."
|
||||
|
||||
This is the ceiling. Nothing above Elevated provides more resolution. The shift-takers do not become visible at any tier. The doors are always the only physical evidence. What changes with tier is how much the player can infer from what is not there.
|
||||
|
||||
---
|
||||
|
||||
## 6. Mode 3 Addition — Institute Transient Visual Vocabulary
|
||||
|
||||
I proposed Institute transient vocabulary in my challenge response. Refining it with what I've learned.
|
||||
|
||||
**The refinement from the challenges:**
|
||||
|
||||
Miri raises the correct question: does the Institute know? My position is they partially know — they know GJ 6711 is anomalous, they do not know the vigil mechanism, they have lost researchers to it without understanding why. This changes the visual vocabulary.
|
||||
|
||||
Institute transients at Abzu are not investigators. They are researchers on standard postings who are in the process of being recruited. Their visual language should communicate this transition state.
|
||||
|
||||
**Year 1 Institute transient:**
|
||||
|
||||
Standard Institute visual vocabulary. Clean lines, classification-tier color coding on equipment, the "institutional" palette I established for Commission and certified bodies. Efficient movement. Documents things. Produces reports. Indistinguishable from an Institute researcher anywhere else in the Reach.
|
||||
|
||||
**Year 3 Institute transient:**
|
||||
|
||||
The same equipment, but used differently. The researcher is still producing reports but the report cadence has slowed. Visually: the character is spending more time stationary than moving. They have acquired some community-style items — not replacing Institute gear, layering over it. The equipment color coding is still present but starting to read as decoration rather than function. They are beginning to use the community's spatial patterns rather than their own.
|
||||
|
||||
**Year 6 (the current researcher):**
|
||||
|
||||
The Institute equipment is still present. It is no longer primary. The character moves on community rhythms. They have positioned their workstation to face the watch location rather than away from it. They are at shift changes when they are at shift changes. The player who observes this character over time will see the pattern. The researcher is not confused. They have not "gone native" in the ordinary sense. They are doing what they understand to be their work. The Institute classification schema simply does not have a category for what the work is.
|
||||
|
||||
**The visual tell that distinguishes Institute-becoming-watcher from community-born watcher:**
|
||||
|
||||
Community-born watchers do not position their attention deliberately. The watch is internalized — their spatial orientation toward the watch location is not intentional, it is habitual. It is how they stand. The Institute researcher's orientation toward the watch location is still chosen — slightly more deliberate than community habit. The difference is barely legible. At Elevated, the monologue notes it.
|
||||
|
||||
This visual distinction gives a player at Elevated an extremely fine piece of information: they can estimate how long someone has been at Abzu by whether their attention is habitual or chosen. The Institute researcher, six years in, is still choosing. That is meaningful. It implies the vigil's full internalization requires more than six years, or requires something the researcher has not yet experienced.
|
||||
|
||||
**Mode 3 palette for Institute transients:**
|
||||
|
||||
The Institute palette (clean institutional blue-grey) overlaid with Abzu's amber. Not blended — layered. As if the amber light is being absorbed into the Institute color scheme the longer they stay. Year 1: Institute palette dominant, amber only as external lighting. Year 3: amber beginning to warm the mid-tones of their equipment colors. Year 6: the equipment is Institute-coded but everything around it, including the ambient light the character moves through, has converted to Abzu amber fully. The character is a Institute-colored figure in an amber world.
|
||||
|
||||
---
|
||||
|
||||
## 7. Revised Palette
|
||||
|
||||
Changes after reading the full challenge set.
|
||||
|
||||
**Confirmed unchanged:**
|
||||
- K-type amber primary light: `#ffb234` (same as bar ambient, intentional — warmth is the signal for "social/inhabited/under observation")
|
||||
- Gas giant reflection: secondary amber, cooler, `#e0a870`
|
||||
- Mode 1 structural base: aged pale stone, `#c8bfa8`
|
||||
- Institute transient equipment palette: `#7a8fa8` (cool blue-grey, stands out against amber)
|
||||
|
||||
**Revised:**
|
||||
- Fog tint: `#1a0c02` (was `#200c04` — deeper, more aqueous, consistent with Abzu naming. The fog at this system should feel like depth, not warmth)
|
||||
- Surface accent (watch location, shift-change zones): no change to hue, but reduce saturation by 15% — the watch location should read as slightly less vivid than the surrounding community spaces, as if the light there is being consumed rather than reflected
|
||||
- High-bleed transit visual effects: primary color during fog inversion `#b8d4e8` — a cool blue-grey that is the inverse of the Abzu amber, to read as a temperature drop, a direction, a signal from somewhere colder
|
||||
|
||||
**New — the "Abzu upwelling" lighting gradient:**
|
||||
The ambient light in all Abzu Mode 2 and Mode 3 interior spaces should follow a vertical gradient: cooler amber (`#e0a870`) at the upper quarter of the screen, shifting to warmer amber-brown (`#c87840`) at the lower quarter. This is the gas giant reflection effect expressed as depth. It should be subtle — the player should not consciously register "the light comes from below." They should register "this place feels like it has a floor that matters."
|
||||
|
||||
**One addition — the departure beat color:**
|
||||
When the transit resolves in the departure beat — the moment the shape becomes briefly legible — the color the shape reads against is `#0a1422`, near-black, slightly blue-shifted. This is the one place in the game where the Interstitium's background is visible as background rather than as transit noise. It should feel like looking out.
|
||||
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
The name Abzu is right. It reframes the visual problem from "a place where people hold still" to "a place that runs deep." The palette implications are precise and bounded — primarily in lighting gradient and fog treatment, not in architectural or structural changes.
|
||||
|
||||
All four challenges converge on the same structural commitments. The bidirectional circuit, the high-bleed connection, the door ambiguity, the non-resolution principle — these are locked. What remains is implementation specification, which is what this synthesis provides.
|
||||
|
||||
The departure transit and the high-bleed visual grammar are now formalized as a single connected system. The shape in the transit is always the same shape. It is the same thing seen from different distances and at different levels of signal degradation. The player learns to read it at Abzu and retroactively understands every high-bleed gate they have ever transited.
|
||||
|
||||
The perception tier spec for the shift change is the most implementation-complex element. It requires the fog system, thermal overlay, and monologue system to coordinate at the shift-change event. The systems are all committed. The integration is the build work.
|
||||
|
||||
The Mode 3 Institute transient vocabulary is ready for NPC design to use. The visual transition from Year 1 to Year 6 is a timeline the player can read without being told.
|
||||
|
||||
Present to the project lead.
|
||||
@@ -0,0 +1,347 @@
|
||||
# GJ 6711 — Final Synthesis (Miri)
|
||||
|
||||
**Role:** Worldbuilder & Setting Designer
|
||||
**Round:** Final — post-challenge, pre-lead presentation
|
||||
**Date:** 2026-03-16
|
||||
|
||||
---
|
||||
|
||||
## Prefatory Note
|
||||
|
||||
All four challenges hold under pressure. There are no fundamental contradictions between
|
||||
them and no contradictions with existing canon. What follows is a synthesis and position
|
||||
document, not a summary. Where the team converged, I'm endorsing convergence. Where
|
||||
there are still open design questions, I'm taking a position. This is the final round
|
||||
before the project lead receives it.
|
||||
|
||||
---
|
||||
|
||||
## 1. The Name "Abzu"
|
||||
|
||||
I want this. But I want it for specific worldbuilding reasons, and I need to flag the
|
||||
implications before endorsing it.
|
||||
|
||||
Every other named system in the Reach draws from Portuguese, German, Afrikaans, or Dutch
|
||||
— the colonial and linguistic inheritance of the settlement waves (Waves 1 through 5).
|
||||
Those names are settlers' names. They reflect which communities had the ships, the
|
||||
capital, and the institutional weight to claim naming rights in the early Commonwealth
|
||||
centuries. The naming pattern is not neutral — it encodes who arrived first and who had
|
||||
the authority to put words on places.
|
||||
|
||||
GJ 6711 received no such name. For 300 years it has been a catalog number. That is
|
||||
itself a signal: the community there has never sought official naming. They don't need
|
||||
the Reach to recognize them. They are not performing their existence to the institutions
|
||||
that assign names.
|
||||
|
||||
If the project lead wants to name it Abzu now, the worldbuilding question is: who named
|
||||
it, and when?
|
||||
|
||||
**The interpretation I'd endorse:** Abzu is not an official Concord Assembly designation
|
||||
and not a settlement-wave inheritance name. It is a name that originated WITHIN the
|
||||
community — possibly within the founding generation, possibly much later, possibly
|
||||
borrowed by a long-stay visitor with different cultural inheritance than the dominant
|
||||
settlement-wave demographics. The name propagated outward not through official channels
|
||||
but through travelers who heard it and carried it. Adams & Ford uses it. The Commission
|
||||
still uses the catalog number. The Assembly's records say GJ 6711.
|
||||
|
||||
This creates a name that is itself a fragment of the vigil's character: the community
|
||||
gave this place a name from a tradition that precedes Western European settlement
|
||||
expansion by five thousand years. Sumerian — the domain of Enki, primordial deep, source
|
||||
of hidden springs, associated with wisdom and what lies beneath. Not the surface. The
|
||||
source.
|
||||
|
||||
Setting note: using Abzu immediately signals that whoever named this place was reaching
|
||||
for something older and deeper than the Reach's standard naming inheritance. That is
|
||||
appropriate. The vigil is older than the Reach's categories. The name acknowledges it.
|
||||
|
||||
**The originality check:** Abzu is an ancient mythological term, not a franchise coinage.
|
||||
There is no conflict with IP originality — this is genuine cultural inheritance being
|
||||
repurposed, not a franchise element being borrowed. The same legitimacy applies to the
|
||||
Reach using historical place names elsewhere. This is different from, say, naming a gate
|
||||
network "the Ring" or a precursor species "the Forerunners."
|
||||
|
||||
**One constraint to track:** if Abzu is the community's internal name and it has leaked
|
||||
outward through travelers, then Adams & Ford correspondents before the third one would
|
||||
not have known it. The first and second correspondents wrote under the catalog number or
|
||||
under an informal traveler's name that may not have been Abzu. The name Abzu should
|
||||
appear in Reach circulation only within a specific time window — I'd suggest within the
|
||||
last 80–120 years, recent enough to not be universal, old enough for Adams & Ford to
|
||||
standardize it.
|
||||
|
||||
**Position: endorse Abzu. Flag the naming source as community-internal with Sumerian
|
||||
etymology, not official designation. Track the propagation timeline.**
|
||||
|
||||
---
|
||||
|
||||
## 2. Points of Convergence
|
||||
|
||||
The four challenges reached independent consensus on several positions. These are now,
|
||||
in my assessment, locked.
|
||||
|
||||
**High-bleed = failed vigil.** All four challenges arrived here. Nigel, Araminta, Paula,
|
||||
and my own response all converged on the same structural reading: high-bleed gates are
|
||||
the Reach's distributed early-warning system for vigil failure, and nobody knows this
|
||||
except possibly the Veil Institute. This is the most important structural implication of
|
||||
the sealed envelope for the wider setting. It retroactively recontextualizes every
|
||||
high-bleed transit experience in the game. It is clean, internally consistent, and
|
||||
requires no modifications to existing canon. I am endorsing this as canon in Section 4.
|
||||
|
||||
**The vigil predates the human community's tenure.** Paula (Option C), myself (implicitly),
|
||||
and Araminta all arrived at the same reading of the doors: whatever takes the other
|
||||
shifts was not brought by the founding settlers and is not something the founding settlers
|
||||
created. The 300-year vigil count is the human tenure of a watch that was already running.
|
||||
The gate was placed to bring human watchers into an existing arrangement. This is structural
|
||||
consensus and it changes the meaning of "the founding settlers were recruited by the
|
||||
situation" — they were recruited into a post, not to establish one.
|
||||
|
||||
**The Institute knows something and has decided to manage it through deliberate ignorance.**
|
||||
All four challenges rejected the "the Institute knows nothing" option. The convergent
|
||||
reading: the Institute has the file, the file is classified at their highest tier, and
|
||||
the Institute's internal response is paralysis caused by factional disagreement rather
|
||||
than active management. They know GJ 6711 is anomalous. They do not know what the anomaly
|
||||
means. Their researcher going silent is classified data that fits no interpretive category
|
||||
their schema provides.
|
||||
|
||||
**The player cannot solve Stillpoint.** All four challenges protected this. The non-resolution
|
||||
principle held under pressure from all four directions. The player accumulates experience,
|
||||
not proof. They file a report that is accurate and incomplete. The game does not confirm
|
||||
what they understood.
|
||||
|
||||
**The endgame is autobiographical, not cosmological.** Nigel's phrasing: "they stop asking
|
||||
who is responsible and start asking what is being maintained." Paula's: "the cosmological
|
||||
mystery becomes autobiographical." This convergence is complete. The endgame turn at
|
||||
Stillpoint is not a revelation — it is a reorientation of the player's relationship to
|
||||
everything they have done.
|
||||
|
||||
---
|
||||
|
||||
## 3. The Inner Sealed Envelope — My Position for the Design Team
|
||||
|
||||
I flagged this in my challenge response and I'm escalating it now with full conviction.
|
||||
|
||||
The sealed envelope currently protects the mystery from the player. That is correct.
|
||||
But it also withholds the answer from the design team. That is a draft state, not a
|
||||
finished design. We are approaching implementation. The people building this location
|
||||
need to know what the vigil is actually watching.
|
||||
|
||||
My position is not that the answer should be made player-facing. My position is that
|
||||
there must be a canonical answer, held internally, that everyone building Stillpoint
|
||||
is building toward. Without it:
|
||||
|
||||
- The visual design team cannot know what to NOT show (Araminta's point, precisely
|
||||
stated: the absence needs design as carefully as the presence)
|
||||
- The narrative team cannot know what the first correspondent's description was actually
|
||||
failing to describe
|
||||
- The Gyre event system cannot know what to produce if the vigil lapses — because the
|
||||
answer to "what breaks" depends entirely on what is being watched
|
||||
- The perception-tier system cannot calibrate what an Elevated player perceives at
|
||||
Stillpoint without a referent
|
||||
|
||||
After reading all four challenges, here is the internal canonical answer I would recommend
|
||||
we commit to. This is my synthesis position — not a demand, but a specific proposal to
|
||||
the project lead:
|
||||
|
||||
**What is being watched is a point of contact between the Interstitium and normal space
|
||||
that cannot be sealed from either side.** It is not an object, not a creature, not a
|
||||
geological feature in any familiar sense. It is a boundary condition — a location where
|
||||
the Interstitium and observable space are in permanent adjacency without resolution into
|
||||
either. The vigil keeps this boundary coherent by providing continuous attention from
|
||||
the observable side. What the community is doing, functionally, is keeping one side of
|
||||
a door occupied. Not closed. Occupied. As long as someone is present and attending on
|
||||
the human side, the condition remains stable — neither intruding nor retreating. The
|
||||
watching is not containment. It is acknowledgment.
|
||||
|
||||
This answer:
|
||||
- Is compatible with all four frames (astronomical, geological, perceptual, topological
|
||||
— because a boundary condition between space and the Interstitium is all of these
|
||||
simultaneously)
|
||||
- Explains why the non-human shift-takers participate — they are watching from the
|
||||
other side of the same boundary, completing the circuit
|
||||
- Explains why "unknown if not watched" is the right framing — an unacknowledged
|
||||
boundary condition does not produce a predictable outcome, it produces whatever the
|
||||
Interstitium does when it is unobserved adjacent to normal space, which is the
|
||||
definition of "unknown"
|
||||
- Explains why Elevated perception at Stillpoint would produce qualitatively different
|
||||
experience than transit-based Interstitial perception — the player is experiencing
|
||||
the boundary directly, not through a gate
|
||||
- Does not resolve the Builder mystery, the Threshold, or any of the game's larger
|
||||
open questions
|
||||
|
||||
This answer should live in an inner sealed envelope document. The outer envelope remains
|
||||
as written. The inner envelope provides what the building team needs without exposing
|
||||
anything to the player layer.
|
||||
|
||||
---
|
||||
|
||||
## 4. The High-Bleed Connection — Endorsement as Canon
|
||||
|
||||
I endorse this. Fully.
|
||||
|
||||
Nigel and Araminta arrived at it independently. Paula built the institutional implications.
|
||||
I had gestured toward it in my challenge response without fully committing. After reading
|
||||
all four, the convergence is too clean and too structurally productive to leave as
|
||||
implication.
|
||||
|
||||
**Canonical position: high-bleed is the Interstitium's response to degraded or absent
|
||||
observation at a vigil system.** The bleed is not random. It does not correlate with gate
|
||||
distance, age, or transit frequency because those are not the relevant variables. The
|
||||
relevant variable is the integrity of whatever observational arrangement is associated
|
||||
with that gate's destination or its chain. The Veil Institute's pattern analysis cannot
|
||||
find the correlation because they do not have the concept of a vigil system. They are
|
||||
measuring the symptom — Interstitial anomaly intensity — without the category that would
|
||||
make the pattern legible.
|
||||
|
||||
Implications that follow and are now locked:
|
||||
|
||||
1. High-bleed gates in the game should, in principle, be traceable to a system in their
|
||||
chain where something has gone wrong observationally. The design team need not make
|
||||
this explicit in every case — but the architecture should be consistent. High-bleed
|
||||
gates are not random.
|
||||
|
||||
2. The Veil Institute's headquarters placement "near high-bleed Founder Gates" is
|
||||
retroactively more sinister: they have been positioning themselves near the Reach's
|
||||
most stressed observation posts without knowing that is what they are.
|
||||
|
||||
3. An Elevated player who has reached Stillpoint and then transits a high-bleed gate
|
||||
elsewhere in the Reach should, through the game's monologue system, be able to arrive
|
||||
at the connection. Not through a journal entry that says "this gate is like Stillpoint."
|
||||
Through a felt quality of recognition that the game does not explain.
|
||||
|
||||
4. The mechanic Nigel proposes — that a player with sufficient knowledge and perception
|
||||
tier might stabilize a high-bleed gate through sustained attention — is worth flagging
|
||||
to the project lead as a potential late-game system. Not committing to it here, but
|
||||
it follows directly from the canon and should not be foreclosed.
|
||||
|
||||
---
|
||||
|
||||
## 5. The Doors — Where I Land
|
||||
|
||||
After reading all four positions, this is my final view on what takes a shift.
|
||||
|
||||
I am not resolving it. That is not evasion — it is a deliberate structural choice with
|
||||
reasoning behind it.
|
||||
|
||||
The three candidates (Builder manifestation; Threshold-adjacent transformed human;
|
||||
something pre-human to GJ 6711) are all load-bearing design options. But the convergent
|
||||
reading from Paula and my own Section 4 — that the vigil predates human tenure — changes
|
||||
the weighting. If the founding settlers were recruited into a post that was already
|
||||
established, then whatever was holding the watch before them was already there. This
|
||||
does not confirm "Option C: something that was always there." It simply means Option C
|
||||
cannot be ruled out by the founding settlers' arrival, because whatever is taking the
|
||||
other shifts predates the founding.
|
||||
|
||||
Nigel's framing is the one I want to protect most carefully: "it emerged from the vigil
|
||||
the way a relationship emerges from sustained attention." This is not a description of
|
||||
a specific entity type — it is a description of a relational ontology. The thing that
|
||||
takes a shift is not a thing in the conventional sense. It is what the vigil relationship
|
||||
looks like from the other side. Whether that is a Builder manifestation, a Threshold
|
||||
entity, or something pre-human to the system is, from the player's perspective, genuinely
|
||||
undecidable — because all three would look the same from where the player stands.
|
||||
|
||||
**What I'm committing to for the inner sealed envelope:**
|
||||
|
||||
The non-human shift-takers are not discrete individuals and are not a species. They are
|
||||
expressions of the boundary condition being watched. The vigil, sustained long enough,
|
||||
produces them — or reveals them, or invites them into coherence from the Interstitium
|
||||
side. They take shifts because the vigil requires acknowledgment from both sides. The
|
||||
human watchers watch. The non-human shift-takers watch back. The circuit requires both.
|
||||
|
||||
This is compatible with all three candidate explanations simultaneously, which is why it
|
||||
is the right internal answer: it does not foreclose any player-facing interpretation while
|
||||
giving the design team something specific to build toward.
|
||||
|
||||
The visual design constraint Araminta established holds: the player never sees what takes
|
||||
the other shifts. The doors are physical evidence. Everything else is perception-scaled
|
||||
ambiguity. This is non-negotiable.
|
||||
|
||||
---
|
||||
|
||||
## 6. What Needs to Go Into the Revised Sealed Envelope
|
||||
|
||||
The outer sealed envelope is a strong document. It needs six additions. These are not
|
||||
rewrites — they are insertions that give the building team what they currently lack.
|
||||
|
||||
**Addition 1: The inner answer.**
|
||||
A subsection titled "Internal Canonical Position (Design Team Only)" that states what
|
||||
the vigil is actually watching. Use the boundary-condition framing from Section 3 above
|
||||
or a variant approved by the project lead. One paragraph. Locked.
|
||||
|
||||
**Addition 2: The founding moment.**
|
||||
The sealed envelope says "they understood, at some point after arrival, that leaving
|
||||
would be abandonment." That formulation needs an internal anchor. The design team needs
|
||||
to know whether the founding moment was: a near-miss event (something changed when no
|
||||
one was watching); a perceptual event (someone stayed up through a doubled-light night
|
||||
and saw something); or a social event (the community collectively recognized the pull
|
||||
without any single precipitating incident). I'd recommend the perceptual event — a
|
||||
single founding-generation incident, recoverable only through the oldest community
|
||||
records, that the player can approach but never fully read. The community does not discuss
|
||||
it. Its name is in the records. The records themselves are tier 4 community knowledge.
|
||||
|
||||
**Addition 3: The vigil predates human tenure.**
|
||||
A sentence that locks this explicitly: "The 300-year count is the human tenure. The
|
||||
vigil is older. The founding settlers were recruited into a post that had previous
|
||||
occupants." This changes the founding narrative from "they established a vigil" to
|
||||
"they took over a watch" and it is required for the doors to make architectural sense.
|
||||
|
||||
**Addition 4: High-bleed is failed vigil.**
|
||||
One paragraph explicitly connecting high-bleed gate behavior to observation failure at
|
||||
vigil systems. This locks the connection as internal canon while keeping it
|
||||
player-discoverable rather than player-confirmed.
|
||||
|
||||
**Addition 5: The Institute's file status.**
|
||||
The sealed envelope says the researcher is in year 6. It needs to add: the Institute
|
||||
has this file. The file is their highest classification tier. The file is locked because
|
||||
two factions within the Institute cannot agree on what it means — one faction reads it
|
||||
as confirmation that Builder contact is achievable and imminent; one faction reads it
|
||||
as confirmation that something dangerous has compromised their researcher. Neither
|
||||
faction is proposing to act. The file has been in contested classification for three
|
||||
years. Paula's contribution here is exactly right.
|
||||
|
||||
**Addition 6: The recruitment trigger.**
|
||||
The envelope says "everyone who stays long enough is recruited." The building team needs
|
||||
a working threshold — not for player-facing content, but for designing the player's arc
|
||||
at Stillpoint. I'd recommend: the trigger is duration under the doubled-light environment
|
||||
combined with proximity to the watch location. Days produce the warmth-without-origin
|
||||
effect. Weeks produce the first perceptual anomalies (at Augmented tier and above).
|
||||
Months produce the qualitative shift. The player's arc is determined by how long they
|
||||
choose to stay. The game should not announce this. The player's monologue should shift
|
||||
registers without explanation.
|
||||
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
**Abzu:** Endorse. Community-internal name with Sumerian etymology, not official
|
||||
designation. Track the propagation timeline.
|
||||
|
||||
**Convergence:** High-bleed as failed vigil; vigil predates human tenure; the Institute
|
||||
knows and is paralyzed; the player cannot solve Stillpoint; the endgame is
|
||||
autobiographical. All four locked.
|
||||
|
||||
**Inner sealed envelope:** Required before implementation. Boundary-condition framing
|
||||
for the watched thing. This is the most pressing outstanding item.
|
||||
|
||||
**High-bleed canon:** Endorsed as locked canon. The correlation is real and the Veil
|
||||
Institute does not have the category to find it.
|
||||
|
||||
**Doors:** The non-human shift-takers are expressions of the boundary condition from
|
||||
the Interstitium side. They are not a species or discrete individuals. The vigil is
|
||||
mutual and the doors are physical evidence that the community has built for what
|
||||
mutuality requires.
|
||||
|
||||
**Revised sealed envelope additions:** Six items. All required. None are rewrites.
|
||||
The outer envelope language holds; the additions give the building team the specificity
|
||||
they currently lack.
|
||||
|
||||
One last note for the project lead. Every person on this team, writing independently,
|
||||
arrived at the same endgame image: a player who has been everywhere in the Reach, who
|
||||
has learned to see through layers of information asymmetry and institutional concealment,
|
||||
who finally reaches hop 23 and discovers that the most important thing in the Reach is
|
||||
not a secret at all. It is a watch. It is people doing a job that has no formal description
|
||||
and no institutional recognition and no end date.
|
||||
|
||||
The game has been training the player to look. Stillpoint is where the player learns
|
||||
that looking was never the point. Being present was.
|
||||
|
||||
That image held under pressure from four different directions. It is the right endgame.
|
||||
Protect it.
|
||||
@@ -0,0 +1,385 @@
|
||||
# GJ 6711 Final Synthesis — Nigel (Sandbox & Replayability)
|
||||
|
||||
**Status:** Final round — pre-presentation to project lead
|
||||
|
||||
---
|
||||
|
||||
## 1. The Name: Abzu
|
||||
|
||||
"Primordial deep beneath the earth. Domain of Enki. Source of all springs."
|
||||
|
||||
That name does something to the metagaming layer that "Stillpoint" cannot. Stillpoint is
|
||||
descriptive — it tells the player what to expect (stillness, a stopping point, a place of
|
||||
rest). Abzu is dissonant. It is the oldest word in a universe of newer words. A player who
|
||||
knows their Sumerian mythology arrives with loaded expectations that the design can
|
||||
exploit. A player who doesn't know it arrives with something archaic and unplaceable that
|
||||
nonetheless communicates depth.
|
||||
|
||||
More importantly: Abzu predates every other naming convention in the Reach. Commonwealth
|
||||
systems are named for catalog designations, stellar coordinates, settlers' names, political
|
||||
gestures. GJ 6711 as "Abzu" has no conventional etymology in the Reach's naming tradition.
|
||||
Someone named it and no one knows who, or when, or whether the name came first and the gate
|
||||
came after. That ambiguity is load-bearing.
|
||||
|
||||
For replayability: a player who reaches Abzu on playthrough 1 and looks up the name comes
|
||||
back on playthrough 2 already primed. They've read about the primordial waters, the source
|
||||
beneath the world, Enki's domain of hidden wisdom. On their second approach, every piece of
|
||||
evidence they've already seen reorganizes. The name functions as a meta-layer key that
|
||||
enriches replay without being accessible through any in-game text. It rewards curiosity that
|
||||
the game doesn't require and doesn't reward any other way.
|
||||
|
||||
For the metagaming question: the name is not spoiler-proof. But it's the right kind of
|
||||
spoiler. Knowing what Abzu means in mythology tells you the emotional register — something
|
||||
beneath, something old, something that was there before you arrived. It tells you NOTHING
|
||||
about the vigil, the doors, the non-human shift-takers, or what happens if you stay. The
|
||||
name creates correct expectations about texture while leaving the specific mechanics
|
||||
completely opaque.
|
||||
|
||||
Position: adopt Abzu. Remove Stillpoint from the vocabulary. The official system name
|
||||
remains GJ 6711. "Abzu" is what the community calls it. No one outside the system knows
|
||||
why, and no one has thought to ask.
|
||||
|
||||
---
|
||||
|
||||
## 2. Points of Convergence
|
||||
|
||||
All four challenge responses agree on the following. These are not contested:
|
||||
|
||||
**The core mechanism holds.** "Observation is load-bearing" contradicts nothing in existing
|
||||
Builder/Interstitium/Gate canon. In every case it enriches rather than contradicts.
|
||||
Specifically: it provides a non-obvious explanation for the "no observed failures" gate
|
||||
stability claim, and it gives the "purposes beyond transit" canon its first concrete
|
||||
instantiation. The canon was waiting for this. It fits.
|
||||
|
||||
**High-bleed gates as vigil-failure signals.** All four responses independently reached this
|
||||
conclusion. Miri, Paula, Nigel, Araminta — all four. Independently. That's a consensus, not
|
||||
a convergence. High-bleed gates are the distributed early-warning system for degraded vigils
|
||||
that nobody in the Reach has the conceptual vocabulary to read. The Veil Institute is sitting
|
||||
on top of this signal and doesn't know what it means. This is now formal canon.
|
||||
|
||||
**Dead-end systems as possible watch posts.** The recontextualization is correct and should
|
||||
be managed carefully. Abzu is the only confirmed vigil system. Other dead-ends gain
|
||||
ambiguity without confirmation. "I can no longer rule it out" is the player state we're
|
||||
engineering, not "there are many of these." Miri's phrasing: the paranoia is the point.
|
||||
|
||||
**The doors must remain ambiguous across all three candidate explanations.** Builder
|
||||
manifestation, Threshold-adjacent transformation, pre-human native presence — all three must
|
||||
remain simultaneously viable in all player-accessible content. The sealed envelope holds all
|
||||
three. Design work (threshold markings, architectural vocabulary, perception-tier reveals)
|
||||
must not narrow this. Araminta added the operational visual grammar; the principle is
|
||||
universally endorsed.
|
||||
|
||||
**The inner sealed envelope is missing.** All four respondents independently identified the
|
||||
same gap: the design team needs the answer even though the player never receives it. What is
|
||||
being watched, what the founding settlers found, what the watch-change protocol is — these
|
||||
must be resolved internally. This is the most pressing action item from the stress test.
|
||||
|
||||
**The Institute's file is locked by internal faction conflict.** Paula's formulation is the
|
||||
correct one: two Institute factions cannot agree on what Abzu means, so the file is
|
||||
classified at the highest tier and left alone. This gives the player an institutional seam
|
||||
to exploit and explains why the Institute hasn't acted on the researcher's six-year silence.
|
||||
|
||||
---
|
||||
|
||||
## 3. The Inner Sealed Envelope: What Is Being Watched
|
||||
|
||||
Miri's call is correct and I'm seconding it: the design team cannot proceed to
|
||||
implementation with the player's ambiguity preserved all the way through. The sealed
|
||||
envelope protects the mystery from players. It should not protect the mystery from the
|
||||
people building the mystery.
|
||||
|
||||
My position for the design team:
|
||||
|
||||
The thing being watched is **a point of contact between normal space and the Interstitium
|
||||
that cannot be sealed, only observed**. It is not a physical object. It is not a creature.
|
||||
It is a condition — a place where the membrane between the Reach's ordinary space and the
|
||||
space the gates punch through is permanently thin. Observed, the condition remains stable:
|
||||
the thinness is contained, the Interstitium on the other side stays on the other side.
|
||||
Unobserved, the condition expands. Not explosively. Incrementally. Observed attention
|
||||
functions as a kind of pressure from this side that keeps the boundary held.
|
||||
|
||||
This is the canonical answer. It is consistent with:
|
||||
- The Gyre event system (a lapse produces a local intrusion, not a catastrophe)
|
||||
- The Threshold (this is what the Threshold looks like at full resolution, from one meter
|
||||
away, from the safe side — it's not an ascension state, it's a place)
|
||||
- The high-bleed gate connection (bleed is what the thinning looks like from the transit
|
||||
side at other gates where the equivalent observation has degraded)
|
||||
- The doors (the non-human shift-takers are what the thin space produces when a vigil has
|
||||
been in contact with it for 300 years — the third thing, as I framed it in my challenge
|
||||
response — neither Builder nor human but the vigil's own product)
|
||||
|
||||
The founding settlers found the thinness, understood it through the light environment
|
||||
before they had language for it, and realized that their presence was doing something. The
|
||||
formative event was not a catastrophe. It was a sustained period of watching — probably the
|
||||
first winter, when the community had nothing to do but attend to the strange light — during
|
||||
which something that had been quietly expanding pulled back. They didn't know what they were
|
||||
doing. They knew that something they were doing mattered.
|
||||
|
||||
The watch-change protocol: the community has a shift schedule that runs continuously. During
|
||||
shift changes, there is a brief overlap period where both the outgoing and incoming watcher
|
||||
are present. This overlap has been maintained for 300 years because no one can remember
|
||||
whether the overlap is necessary or merely traditional, and no one is willing to find out.
|
||||
The non-human participants do not follow this schedule. Their shifts occur at intervals the
|
||||
community has learned to recognize without being able to predict — and when those shifts
|
||||
occur, the human watchers step back. They have always stepped back. It has always been fine.
|
||||
|
||||
---
|
||||
|
||||
## 4. The High-Bleed Connection: Formalization
|
||||
|
||||
Araminta and I reached this independently. Both challenge responses identified it as
|
||||
the strongest structural implication in the sealed envelope. Here is the formal statement:
|
||||
|
||||
**High-bleed Founder Gates are gates where the observation circuit is degraded or
|
||||
incomplete.** "Bleed" — the anomalous Interstitial effects experienced during transit,
|
||||
characterized as distorted sounds, visual artifacts, and a sense of being observed — is
|
||||
the phenomenological signature of insufficient vigil maintenance at some point in that
|
||||
gate's operational context.
|
||||
|
||||
Formal corollary 1: The Veil Institute's headquarters is positioned near high-bleed gates
|
||||
because high-bleed gates are where the system is visibly stressed. The Institute is studying
|
||||
the symptom. They have not identified the cause because they lack the conceptual vocabulary
|
||||
for vigil mechanics — the vocabulary is held by the community at Abzu and is not
|
||||
transmissible without staying.
|
||||
|
||||
Formal corollary 2: High-bleed gates are not random. They have a causal structure. In
|
||||
implementation, every high-bleed gate should be traceable — by a sufficiently determined
|
||||
player — to some observation deficit in its chain. The Institute's pattern analysis should
|
||||
be approaching this finding without completing it.
|
||||
|
||||
Formal corollary 3: A player with sufficient tier and knowledge can theoretically stabilize
|
||||
a high-bleed gate by establishing and maintaining a vigil at the appropriate location. Not
|
||||
by hacking, not by physical intervention. By watching. This is a late-game mechanic that
|
||||
should be flagged for the design team — it's not in the sealed envelope and it needs a
|
||||
decision. I'm flagging it, not mandating it.
|
||||
|
||||
Formal corollary 4 (Araminta's visual contribution, canonized here): The fog-of-war
|
||||
inversion during high-bleed transit — "as if something is looking at the player through
|
||||
their own perception system" — is not Builder curiosity. It is the thing at the watched
|
||||
location, leaking through, because the watch is thin. The player's experience of being
|
||||
observed during a high-bleed transit is the player being perceived by what needs watching.
|
||||
|
||||
---
|
||||
|
||||
## 5. The Doors: Final Position
|
||||
|
||||
After reading all four responses, I stand by my challenge position with one addition.
|
||||
|
||||
My position: the non-human shift-takers are what the vigil itself produced over 300 years
|
||||
of sustained contact with the thinness. Not Builders. Not Threshold-crossed humans. A third
|
||||
category. The vigil generated participants. The watching made something that watches.
|
||||
|
||||
This is consistent with all three candidates the other respondents identified, because it
|
||||
doesn't exclude any of them — it describes what they have in common. Whether the
|
||||
shift-takers have Builder properties, whether they resemble what humans look like near the
|
||||
Threshold, whether they predate the human vigil by being native to the thinness itself —
|
||||
all of these can be simultaneously true of a third-category entity that emerged from 300
|
||||
years of contact. The candidates aren't mutually exclusive. They're different descriptions
|
||||
of the same emergence from different analytical angles.
|
||||
|
||||
The operational implication: the shift-takers are not characters. They cannot be confronted,
|
||||
named, allied with, or defeated. They are a function with presence. The community's
|
||||
matter-of-fact accommodation of them — building taller doors, recognizing shift intervals,
|
||||
stepping back when needed — is the correct template for how the player should encounter
|
||||
this. Not with fear. Not with wonder that demands resolution. With the same
|
||||
matter-of-factness the community has.
|
||||
|
||||
The monologue fires at the taller doors. It says something like: "These were built this
|
||||
size deliberately. Someone decided this was the right size and built accordingly." It does
|
||||
not speculate. The player speculates.
|
||||
|
||||
Araminta's visual prescription is accepted and endorsed: perception-tier scaling for what
|
||||
the player can detect at shift changes, with the Elevated tier catching a thermal gradient
|
||||
and a quality-of-attention change that resolves to nothing when looked at directly. The
|
||||
player at Baseline sees architecture. The player at Elevated sees the reason, briefly, and
|
||||
then it's gone.
|
||||
|
||||
---
|
||||
|
||||
## 6. The Vigil/Lattice/Unbound Gap: Proposed Solution
|
||||
|
||||
I flagged this in my challenge response and no one else addressed it. It needs a solution
|
||||
before Abzu can be built.
|
||||
|
||||
The problem: the Reach's re-embodiment system means Abzu settlers can die and be
|
||||
re-embodied. But what happens to a watcher's accumulated vigil-understanding when they
|
||||
die? Is it transmissible? Does re-embodiment preserve it? And for Unbound characters —
|
||||
whose deaths are permanent — what does the vigil do with a watcher who can never come
|
||||
back?
|
||||
|
||||
Proposed solution, three parts:
|
||||
|
||||
**Part 1: Vigil-understanding is environmental, not personal.** The community at Abzu
|
||||
understands the vigil not because anyone taught them, but because long residence in the
|
||||
doubled-light environment near the thinness produces it. This means re-embodied settlers
|
||||
return to Abzu and the understanding comes back — not instantly, but within a period of
|
||||
re-acclimation. The vigil is not interrupted by individual deaths. The environment does
|
||||
the continuity work. The community's institutional rituals (shared meals, overlapping
|
||||
shifts, the accumulated practice of watching) maintain the environmental conditions that
|
||||
produce understanding in residents.
|
||||
|
||||
**Part 2: Re-embodied watchers return different.** A watcher who dies and is re-embodied
|
||||
returns to Abzu as a newcomer in perceptual terms — they experience the warmth-without-origin
|
||||
again, they go through the recruitment curve again. But faster, because the community
|
||||
recognizes them and because something in the thinness recognizes them. The second recruitment
|
||||
is not the same as the first. It's shorter, stranger, and the watcher arrives at understanding
|
||||
from a different angle. This is a potential late-game experience for players who invest deeply
|
||||
enough to die and return.
|
||||
|
||||
**Part 3: The Unbound question is resolved by the doors.** An Unbound watcher who dies
|
||||
keeping watch is not simply lost. The third-category entity — what the vigil produces —
|
||||
may include the functional residue of Unbound watchers who stayed long enough. Their death
|
||||
was permanent in the lattice sense. It was not permanent in the vigil sense. They became
|
||||
part of what watches. This is not confirmed to the player. But it is the canonical internal
|
||||
answer to the question the sealed envelope raised. The doors are taller because some of
|
||||
the non-human-sized shift-takers are what committed watchers become when the only thing
|
||||
taller than dying is watching.
|
||||
|
||||
This is the darkest implication in the entire design. I'm not walking it back.
|
||||
|
||||
---
|
||||
|
||||
## 7. Per-Playstyle Hooks
|
||||
|
||||
I flagged the tycoon gap. The other respondents didn't address this. Here are proposed
|
||||
hooks for all four playstyles that make the 23-hop journey to Abzu feel directed rather
|
||||
than arbitrary.
|
||||
|
||||
**Tycoon (economic motivation)**
|
||||
|
||||
The hook is not about what Abzu exports. It's about what the high-bleed gates are costing.
|
||||
|
||||
Every high-bleed gate transit is a disruption to freight and passenger scheduling. The
|
||||
transit experience is degraded, cargo manifests come through with errors, insurance rates
|
||||
on high-bleed routes are elevated. A tycoon-playstyle player who has been building economic
|
||||
operations across the Reach has been paying the high-bleed premium for the whole game.
|
||||
|
||||
The hook: someone — a shipping concern, a gate insurance underwriter, an economic analysis
|
||||
bureau — has noticed that high-bleed gate incidents cluster geographically and temporally.
|
||||
The pattern doesn't resolve within the economic system, but it's expensive enough that
|
||||
someone is paying to have it investigated. The tycoon player gets a contract. Follow the
|
||||
pattern. Find the source. The source is Abzu.
|
||||
|
||||
When they arrive: the community has no commercial activity in the conventional sense because
|
||||
they're not oriented toward exchange. But what they have, in abundance, is something no
|
||||
amount of money has ever successfully purchased — a community with 300 years of unbroken
|
||||
institutional continuity, zero factional capture, and no debt to any interest in the Reach.
|
||||
The tycoon arrives expecting a resource extraction opportunity and finds the one thing they
|
||||
cannot buy. What they do with that realization is between them and the game.
|
||||
|
||||
**Dating Sim (relational motivation)**
|
||||
|
||||
The hook is a specific person who left.
|
||||
|
||||
Someone the player has a relationship with — a contact, a companion, someone who matters —
|
||||
went to Abzu and didn't come back in the expected way. Not dead. Not missing. Still there.
|
||||
Still sending messages, but the messages changed. Became quieter. More inward. The player
|
||||
has been watching this change across the whole game and can't explain it. Abzu is where they
|
||||
find out.
|
||||
|
||||
When they arrive: they find the person still there, still changed, unable to explain what
|
||||
happened in terms the player can easily accept. The relational question becomes: is the
|
||||
person you came for still the person you knew? The vigil doesn't answer this. The player
|
||||
has to decide whether the change is loss or growth, and whether they love the new version,
|
||||
and whether they stay.
|
||||
|
||||
This hook also activates the Unbound death question: if the person who went to Abzu is
|
||||
Unbound, and they die while the player is there, what does that mean for what the player
|
||||
came to find?
|
||||
|
||||
**Political Drama (power motivation)**
|
||||
|
||||
The hook is the Institute's locked file and what unlocking it would be worth.
|
||||
|
||||
A political drama player has been navigating faction conflict across the entire game. The
|
||||
Veil Institute is one of the major players — most information, least shared. The player has
|
||||
been trying to get leverage on the Institute for potentially the whole playthrough. The
|
||||
locked Abzu file is the leverage point.
|
||||
|
||||
The hook: the Institute's internal faction conflict over the Abzu file has reached a crisis.
|
||||
One faction wants to act. One faction wants to contain. They've been paralyzed because
|
||||
neither side can act without the other learning. An Institute defector — or a political
|
||||
contact who's been watching the Institute — tips the player that the file exists, that it's
|
||||
locked, and that whoever gets to Abzu first and brings back something usable has the
|
||||
Institute by the throat.
|
||||
|
||||
When they arrive: the political player finds something that cannot be weaponized in the
|
||||
conventional sense. You cannot turn the vigil into leverage. You cannot hold the community
|
||||
hostage. What you can do is file an Adams & Ford entry that changes what the Reach knows —
|
||||
or that changes what the Institute thinks the Reach knows. The political game at Abzu is
|
||||
about information architecture, not power plays. The player who came for leverage finds
|
||||
that leverage requires a kind of clarity the vigil won't provide, and has to decide whether
|
||||
to lie, tell the truth, or stay silent. Each option has consequences they can't fully predict.
|
||||
|
||||
**Investigation (knowledge motivation)**
|
||||
|
||||
This is the native hook — the investigation playstyle is already pointed at Abzu by the
|
||||
game's information structure. But it needs a specific entry point that feels earned rather
|
||||
than inevitable.
|
||||
|
||||
The hook: the first Adams & Ford correspondent's entry exists in the database. The player
|
||||
finds it early — maybe at hop 3 or 4, in a transit lounge's shared archive. It's a
|
||||
professional, competent description of a frontier system that is somehow not quite right.
|
||||
All the information is present. Nothing is omitted. But the entry reads like a person
|
||||
describing something they experienced once and cannot get back to. The player flags it.
|
||||
|
||||
Over the course of the game, they find the second correspondent's entry. Same quality —
|
||||
professional, competent, slightly off. They don't find the third correspondent's entry,
|
||||
because it was never filed. They find a placeholder in the Adams & Ford database: an
|
||||
assigned entry that was never submitted, for a correspondent who is still listed as active.
|
||||
That correspondent's location is GJ 6711.
|
||||
|
||||
When they arrive: the investigative player knows they're walking into the scene of the
|
||||
third correspondent's disappearance-that-wasn't. They're also aware that they're now the
|
||||
person who will file the next entry. The game has been training them to notice what others
|
||||
missed. At Abzu, they discover that what was missed cannot be noticed its way to resolution.
|
||||
The investigation ends when the player files the entry and leaves. Or doesn't leave.
|
||||
|
||||
---
|
||||
|
||||
## Summary Position for the Project Lead
|
||||
|
||||
**The sealed envelope holds.** All four respondents confirmed this independently.
|
||||
|
||||
**Abzu is the right name.** Adopt it for the community's internal usage. It does work the
|
||||
design system can use and it does it without telling the player anything they can act on.
|
||||
|
||||
**Six items require design team action before implementation:**
|
||||
|
||||
1. The inner sealed envelope — write it. What the thinness is, the founding formative event,
|
||||
the watch-change protocol. Not player-facing. Foundational.
|
||||
2. Adopt the inner sealed position on the thinness formally and circulate it as restricted
|
||||
internal canon.
|
||||
3. The high-bleed/vigil-failure connection is now formal canon. The architecture needs to
|
||||
support traceable high-bleed causes.
|
||||
4. The Unbound watcher / lattice interaction is resolved as above. Flag for systems design.
|
||||
5. Per-playstyle hooks need to be reviewed by Paula for political drama and narrative
|
||||
coherence, and by Miri for setting consistency on the relational hook.
|
||||
6. The Adams & Ford entry format needs definition — what categories exist, what the
|
||||
Stillpoint entry specifically cannot fill, what that gap communicates.
|
||||
|
||||
**The replayability case for Abzu:**
|
||||
|
||||
GJ 6711 achieves interpretive inexhaustibility without procedural variation. The same
|
||||
location, on every playthrough, generates a different experience because the player
|
||||
approaches it with a different theory. The Adams & Ford entry propagation loop ensures
|
||||
that theories from playthrough 1 pollute the approach conditions of playthrough 2 in
|
||||
specific and unpredictable ways. Two players comparing their Abzu experiences describe
|
||||
completely different visits, even though the location is static. That is the comparison
|
||||
test passing.
|
||||
|
||||
It also rewards return. The player who reaches Abzu and leaves knows they didn't solve it.
|
||||
On playthrough 2, they come back. They find the same community, the same doors, the same
|
||||
light. They find that what they remember was incomplete. Not because the place changed.
|
||||
Because they did.
|
||||
|
||||
That's not just an endgame. That's a reason to start over.
|
||||
|
||||
And the replayability EXPLODES when you consider what they do differently on that second
|
||||
run to get there — different playstyle, different route, different theory accumulated across
|
||||
23 hops. The vigil doesn't change. But what they bring to it does. And what they bring to
|
||||
it is exactly what the vigil requires: sustained, changed attention. The game that trains
|
||||
the player to see has been training them for this specific moment, and they didn't know it
|
||||
until they were already there.
|
||||
|
||||
Abzu is where the game earns everything it asked for.
|
||||
@@ -0,0 +1,357 @@
|
||||
# GJ 6711 — Final Synthesis (Paula)
|
||||
|
||||
**Round:** Post-challenge synthesis, pre-project-lead presentation
|
||||
**Date:** 2026-03-16
|
||||
|
||||
---
|
||||
|
||||
## 1. The Name: Abzu
|
||||
|
||||
"Stillpoint" was a working placeholder that described function. "Abzu" is something
|
||||
different — it is a claim about what is there.
|
||||
|
||||
The Sumerian primordial deep beneath the earth. Domain of Enki, god of wisdom and
|
||||
hidden knowledge. The source from which all springs rise. The underworld that is not
|
||||
a place of death but a place of origin.
|
||||
|
||||
The honest truth is that no one in the Settled Reach would name a system this. The
|
||||
naming conventions across the Reach are practical: survey designations, founder
|
||||
surnames, geographic descriptors, Wave-era transit codes. A system named for Sumerian
|
||||
cosmology is an anomaly that announces itself. It tells us something about the founding
|
||||
settlers that nothing else in the sealed envelope tells us.
|
||||
|
||||
They did not arrive and say: we will call this place the Observation Post, or the Vigil
|
||||
Station, or the Watchers' Settlement. They named it for the hidden source beneath
|
||||
everything. That is not the name of people who found something and stayed. That is the
|
||||
name of people who recognized what they found — who arrived at GJ 6711 and felt, with
|
||||
the specific quality of attention the doubled light produces, that they were above
|
||||
something that had always been there and had always required witnesses.
|
||||
|
||||
**What "Abzu" does to the political/narrative layer:**
|
||||
|
||||
It marks the founding settlers as people with deep cultural memory reaching back before
|
||||
the Commonwealth, before the Reach, possibly before the first wave of post-Commonwealth
|
||||
settlement. They had a conceptual vocabulary for what they found because they brought
|
||||
one. A community that names its home Abzu in Wave 2 or Wave 3 is a community that
|
||||
carried ancient cosmology as a working lens — not as religion, but as recognition.
|
||||
|
||||
This has three design implications:
|
||||
|
||||
First, the founding history of GJ 6711 is not a blank. Somewhere in the accessible
|
||||
archives, there will be a record of the founding party's origin culture. The name is a
|
||||
clue about who they were, not just what they found.
|
||||
|
||||
Second, the name creates a silence threshold that is specific. An investigator who knows
|
||||
enough pre-Commonwealth cultural history to recognize "Abzu" immediately understands
|
||||
that the founding settlers knew what they were looking at. That is information asymmetry
|
||||
at the naming layer — the name rewards the player who arrives with the right knowledge.
|
||||
Most players will pass through and file it under "unusual frontier nomenclature." A
|
||||
player who recognizes it arrives with a different frame.
|
||||
|
||||
Third, the name is the most durable signal in the whole system. The founding records
|
||||
may be partially sealed. The community may be unreachable for investigation. But the
|
||||
name is on every transit manifest, every Commission report, every Adams & Ford entry.
|
||||
It is the one thing the vigil community cannot keep quiet. They named it honestly, three
|
||||
hundred years ago, and the name has been propagating through the Reach ever since.
|
||||
|
||||
**Recommendation:** Accept "Abzu" as the canonical name. It does more work than
|
||||
"Stillpoint" — it is a mystery the player can investigate independently of the vigil,
|
||||
and one that rewards cultural knowledge. The name is part of the evidence trail.
|
||||
|
||||
---
|
||||
|
||||
## 2. Points of Convergence
|
||||
|
||||
All four challenges found the same things load-bearing. This is the team's consensus
|
||||
ground and it should not be reopened.
|
||||
|
||||
**What we all agreed on:**
|
||||
|
||||
| Point | All four responses | Notes |
|
||||
|-------|-------------------|-------|
|
||||
| "Observation is load-bearing" is canon-compatible | Yes, unanimously | No contradictions found; several enrichments |
|
||||
| High-bleed gates = failed/degraded vigil signal | Endorsed by all four | Miri, Nigel, Araminta, Paula all arrived independently |
|
||||
| The doors are the most important detail | Universal | Miri, Nigel, Araminta, me — all flagged this as the load-bearing element |
|
||||
| The sealed envelope needs an inner layer | Unanimous | The design team needs answers the player never receives |
|
||||
| The Threshold connection is real and underdeveloped | All four | Vigil as Threshold-approach, not Threshold-crossing |
|
||||
| The Institute researcher going native is politically significant | All four, different angles | The file is real, the Institute's response is a design gap |
|
||||
| Community knowledge has a gradient | Me and Miri | Recent recruits more articulate about surface than founders |
|
||||
| Endgame is changed relationship to knowledge, not revelation | Universal | The player cannot solve Stillpoint |
|
||||
| The non-resolution principle must be protected | All four | Don't collapse the doors onto a single answer |
|
||||
|
||||
**What needs to go into the design record as settled:**
|
||||
|
||||
High-bleed gates are the distributed signal system for vigil failure. This is not a
|
||||
maybe. Four independent analyses arrived at the same conclusion from different angles
|
||||
(canon compatibility, visual design, systems, political narrative). The Veil Institute's
|
||||
headquarters placement near high-bleed gates is retroactively significant. This should
|
||||
be formally closed as a design decision, not left as an implication.
|
||||
|
||||
---
|
||||
|
||||
## 3. The Inner Sealed Envelope
|
||||
|
||||
Miri names this most precisely: the current sealed envelope protects the mystery from
|
||||
the player at the cost of the design team's clarity. That is a draft state, not a
|
||||
finished document.
|
||||
|
||||
**What is being watched?**
|
||||
|
||||
I will not pretend this question has an obvious answer, but I will name what the
|
||||
evidence points toward.
|
||||
|
||||
The four frames (astronomical, geological, perceptual, topological) are described as
|
||||
partial views of one function. The function the envelope calls "this place needs
|
||||
witnesses" is operational. The question is what kind of thing requires witnesses to
|
||||
remain in a state that can be coexisted with.
|
||||
|
||||
My position: the thing being watched is a contact point — a location where the
|
||||
Interstitium is not separated from ordinary space by the gate mechanism but by
|
||||
something older and more fragile. Not a gate. Not a Gyre event site. A place where
|
||||
the boundary is thin enough that it has always required acknowledgment from this side
|
||||
to remain a boundary at all. The vigil isn't preventing entry. It's maintaining the
|
||||
ontological distinction between there and here. Without the watch, the distinction
|
||||
does not collapse violently. It simply becomes unclear. And what is unclear becomes
|
||||
unnavigable, unpredictable, and eventually uncoexistable with.
|
||||
|
||||
This framing makes all four candidate consequences (Gyre event, topological instability,
|
||||
perceptual fracture, gate behavior change) simultaneously true at different scales,
|
||||
which is what the envelope intended. It also makes Nigel's best candidate ("the thing's
|
||||
ontological status becomes undefined in a way human cognition can't process") the
|
||||
canonical failure mode — and that is the version that best preserves "unknown if not
|
||||
watched" as a meaningful design constraint rather than a placeholder.
|
||||
|
||||
**The inner envelope should specify:**
|
||||
|
||||
- What the founding settlers found: not a discovery but a recognition. They arrived,
|
||||
the doubled light produced the quality of attention the envelope describes, and
|
||||
something about that attention revealed to them that they were standing above the
|
||||
contact point. The formative event was not dramatic. It was the slow understanding
|
||||
that the boundary was thin here and attention was what held it.
|
||||
|
||||
- The watch-change protocol: scheduled, not improvised. The community has 300 years
|
||||
of operational knowledge. The non-human shift-takers participate in a rotation the
|
||||
human watchers trust. The humans do not know what the other participants are
|
||||
experiencing. They know the schedule holds.
|
||||
|
||||
- The scope of vigil failure: the contact point becoming unclear propagates outward
|
||||
through the gate network because the network itself has always depended on the
|
||||
stability the Abzu contact point provides at its far end. How far it propagates
|
||||
before attenuating is the number the Institute's analysts cannot derive from their
|
||||
data because they do not know the cause.
|
||||
|
||||
---
|
||||
|
||||
## 4. High-Bleed Connection: Bleed = Failed Vigil
|
||||
|
||||
**Endorsed as canon.**
|
||||
|
||||
The convergence across all four challenges on this point is too complete to ignore. The
|
||||
pattern of which gates are high-bleed "doesn't correlate with distance, age, or any
|
||||
other measurable variable" — that is an open problem the existing canon left
|
||||
deliberately unresolved. The vigil framework closes it with a clean, internally
|
||||
consistent explanation that enriches rather than constrains existing content.
|
||||
|
||||
The specific formulation I'd carry forward: high-bleed is the Interstitium's response
|
||||
to an observation circuit that is incomplete, degraded, or failing. Gates are high-bleed
|
||||
because something that needs watching in an adjacent system is not being watched
|
||||
adequately. The degree of bleed correlates with the degree of observational failure,
|
||||
not with the gate's physical properties.
|
||||
|
||||
This has one design consequence that should be locked alongside the bleed canon: the
|
||||
Institute's choice to locate its headquarters near high-bleed gates is not incidental.
|
||||
They made the right call for the wrong reason. They thought high-bleed gates were the
|
||||
most interesting study sites. They were correct. They were interesting because they
|
||||
were diagnostic. The Institute has been sitting next to the Reach's early-warning
|
||||
system for decades without understanding what the system was warning about.
|
||||
|
||||
The player who reaches Abzu and carries this back to their understanding of the
|
||||
Institute's headquarters location has one of the most disquieting realizations in the
|
||||
game: the people tasked with understanding the infrastructure are downstream of a
|
||||
signal they cannot read.
|
||||
|
||||
---
|
||||
|
||||
## 5. The Doors
|
||||
|
||||
Four positions read. Here is where I land.
|
||||
|
||||
The three candidates — Builder manifestation, Threshold-crossed humans, pre-existing
|
||||
non-human inhabitants — must remain simultaneously viable in all player-facing content.
|
||||
That is not hedging. It is the correct design position. The doors are physical evidence
|
||||
that the vigil includes non-human participants. Collapsing that onto a single explanation
|
||||
is the single fastest way to make Abzu feel like a mystery-game with a solution rather
|
||||
than an endgame with a question.
|
||||
|
||||
**However, the inner sealed envelope needs a working theory.**
|
||||
|
||||
My position: Option C has the most structural weight (I argued this in my original
|
||||
challenge and the stress test did not dislodge it). The vigil predates human presence
|
||||
at GJ 6711. The 300-year count is the human tenure, not the vigil's age. The founding
|
||||
settlers were not recruited into an empty situation — they were recruited into a
|
||||
rotation that had prior participants. The gate was built to bring humans to an existing
|
||||
watch, possibly because prior watchers had become something the gate network could no
|
||||
longer easily access. This is Araminta's "built for who?" question and she asked it
|
||||
precisely.
|
||||
|
||||
The reason Option C has structural weight is that it makes the founding settlers'
|
||||
rapid accommodation explicable. They didn't discover and then slowly understand. They
|
||||
arrived, felt the quality of attention the doubled light produces, and recognized that
|
||||
the doors were already the right size for what uses them. The accommodation was fast
|
||||
because the situation had been set up for them.
|
||||
|
||||
**What takes a shift:**
|
||||
|
||||
I will not name it. Naming it ends it. The design team needs to know that whatever
|
||||
takes the other shifts is not a character, not a Builder in the canonical sense, not
|
||||
a prior human who changed. It is a participant in the same vigil that the community
|
||||
maintains — present because the vigil requires participants, functional because the
|
||||
watch requires watchers. The founding settlers built for it. The community does not
|
||||
speak of it not because it is frightening but because what you build doors for
|
||||
eventually becomes unremarkable.
|
||||
|
||||
That last sentence is the most disturbing thing in this document. It should be
|
||||
preserved.
|
||||
|
||||
**Araminta's visual spec for the doors is final:**
|
||||
|
||||
Baseline perceives architecture that does not fit. Augmented perceives the rhythm —
|
||||
gaps in the institutional schedule, the watch timing, the absence where something is.
|
||||
Elevated perceives the quality-of-attention change at shift change. Monologue fires.
|
||||
Says nothing explicit. The player at Elevated arriving at shift-change sees: a change
|
||||
in how the room holds itself, a thermal gradient with no source, a perception boundary
|
||||
that was somewhere and then was somewhere else. That is sufficient. Do not design
|
||||
beyond that.
|
||||
|
||||
---
|
||||
|
||||
## 6. The Institute's File
|
||||
|
||||
All four challenges flagged this. Let me close it.
|
||||
|
||||
**What the Institute knows:**
|
||||
|
||||
The Institute knows that Abzu is anomalous. They have classified everything from
|
||||
Abzu at their highest restriction level. The pattern of researcher retention is in
|
||||
their files — not framed as researcher conversion, but as researcher dropout from
|
||||
rotation. They have noticed the pattern. They have not agreed on what it means. This
|
||||
is Miri's option (b): they know the researchers become permanent, they classify the
|
||||
outcome, and they may rely on it quietly without understanding its mechanism.
|
||||
|
||||
**What the Institute does not know:**
|
||||
|
||||
They do not know the vigil is the mechanism. They think psychological attachment to
|
||||
the field site explains the retention. They think "gone native" is the complete
|
||||
description. Their internal factional conflict — contact vs. containment — has not
|
||||
resolved on Abzu precisely because neither faction has a conceptual vocabulary for
|
||||
"the situation recruits participants." Contact faction sees data suggesting something
|
||||
important is happening there. Containment faction sees data suggesting researchers who
|
||||
go there cannot leave and recommends ending all assignments to GJ 6711. The file is
|
||||
locked because neither faction can get the other to agree on what the lock means.
|
||||
|
||||
**What the Institute suspects:**
|
||||
|
||||
That the Abzu file is one of the most significant documents in their archive. That
|
||||
"what it means" is a question that will eventually force a resolution to their internal
|
||||
conflict. That the researcher now in year 6 is producing information — the nature of
|
||||
which is unclear — that should not be classified at standard research output levels.
|
||||
Some senior Institute archivists suspect the file is not about research at all. They do
|
||||
not know what it is about instead.
|
||||
|
||||
**The design consequence:**
|
||||
|
||||
The player who reaches Abzu can become, depending on what they choose to do with the
|
||||
Adams & Ford entry and their knowledge of Institute politics, one of the following:
|
||||
a whistleblower with a specific target; an asset either Institute faction wants to
|
||||
manage; a threat to the institutional status quo on the Abzu file; or simply another
|
||||
observer who has been added to the vigil's growing record of inadequate descriptions.
|
||||
All four should be viable player positions. The Institute's locked file is the
|
||||
institutional seam to exploit.
|
||||
|
||||
---
|
||||
|
||||
## 7. What Needs to Go into the Revised Sealed Envelope
|
||||
|
||||
The current sealed envelope is correct in what it says. It is insufficient in what it
|
||||
does not say. Specifically, the design team needs internal canon on the following seven
|
||||
points — none of which should appear in player-facing content:
|
||||
|
||||
**1. The name origin.**
|
||||
The founding settlers came from a cultural tradition with pre-Commonwealth roots that
|
||||
included the concept of the primordial deep. The name Abzu was given within the first
|
||||
generation of settlement. It was not formal at first. It became official before the
|
||||
end of the founding century. The Commission records show "GJ 6711 (local designation:
|
||||
Abzu)" from approximately 200 years ago. This means the name circulates but is treated
|
||||
as a frontier peculiarity, not a signal.
|
||||
|
||||
**2. The formation event.**
|
||||
The founding settlers understood what they were above within the first decade. There
|
||||
was no singular discovery event. There was a slow understanding, produced by the
|
||||
quality of attention the doubled light generates, that something beneath the attention
|
||||
had always required it. The founding memory is not a story about what they found. It
|
||||
is a story about a gradual change in what they understood themselves to be doing by
|
||||
staying.
|
||||
|
||||
**3. The contact point.**
|
||||
The thing being watched is a point where the Interstitium is not separated from
|
||||
ordinary space by a gate but by a more fragile and older distinction. The vigil
|
||||
maintains that distinction. Failure of the vigil does not produce an invasion. It
|
||||
produces an ontological ambiguity that propagates outward from the contact point
|
||||
through the gate network, producing high-bleed events at increasing remove until the
|
||||
ambiguity attenuates or is resolved.
|
||||
|
||||
**4. The non-human shift-takers.**
|
||||
The vigil predates human presence at Abzu. The non-human participants were not brought
|
||||
by the founding settlers and are not Builder manifestations in the conventional sense.
|
||||
They are participants the prior watch included. The founding settlers were recruited
|
||||
into an existing rotation. The doors were built taller because the community
|
||||
accommodated what the rotation required. The community does not speak of the non-human
|
||||
participants not because they are frightening but because they are part of the vigil
|
||||
and the vigil does not require explanation to the people who keep it.
|
||||
|
||||
**5. The Institute's internal position.**
|
||||
The Institute file on Abzu is locked at director level. Contact faction and containment
|
||||
faction have not resolved on what the Abzu data means. The researcher in year 6 is
|
||||
producing reports that are classified immediately upon receipt. The senior archivist
|
||||
who manages the Abzu file has requested twice in the last decade that the director
|
||||
authorize a full investigation. Both requests were tabled. The file is the most
|
||||
significant unresolved item in the Institute's active archive.
|
||||
|
||||
**6. The near-miss record.**
|
||||
There has been one documented near-miss in the 300-year vigil history. It occurred
|
||||
approximately 140 years ago during a period of population decline following a
|
||||
Commission quarantine order (unrelated cause — a disease event). The vigil thinned for
|
||||
approximately 72 hours. The Veil Institute's Interstitial monitoring arrays recorded an
|
||||
anomaly during that window. The anomaly is in their archive. It is classified. The
|
||||
Abzu community has no external record of the near-miss. Their internal records describe
|
||||
it as "the thinning." The oldest families know. No one else does.
|
||||
|
||||
**7. The player's recruitment threshold.**
|
||||
Recruitment is not triggered by duration alone. It is triggered by the quality of
|
||||
attention the player has developed — proxied by perception tier. A Baseline player can
|
||||
stay indefinitely and remain unrecruited in the vigil sense, though the community's
|
||||
warmth will intensify. An Augmented player who stays more than a few weeks begins to
|
||||
feel the pull. A Transcendent or Elevated player may begin to understand within days.
|
||||
The recruitment is not coercive. The vigil is not malevolent. It is a contact point
|
||||
that requires witnesses, and some visitors arrive already capable of witnessing. Those
|
||||
visitors feel it faster.
|
||||
|
||||
---
|
||||
|
||||
## Final Note
|
||||
|
||||
After reading all four challenges, my confidence in the sealed envelope has increased
|
||||
on the mechanism and decreased on the completeness. The mechanism holds. The envelope
|
||||
is a draft of a design document, not a finished one. The inner sealed envelope is the
|
||||
work that still needs to happen.
|
||||
|
||||
The name Abzu is the project lead's best contribution to this workshop. It changed what
|
||||
the founding settlers are — from people who found something they couldn't explain to
|
||||
people who found something they recognized. That distinction is the difference between
|
||||
a mystery and a reckoning, and this endgame should be a reckoning.
|
||||
|
||||
The player cannot solve Abzu. But they can recognize it. The founding settlers did.
|
||||
That is the most important structural truth in the whole design, and it was sitting
|
||||
inside the name the whole time.
|
||||
|
||||
Present that to the project lead.
|
||||
@@ -0,0 +1,774 @@
|
||||
# Abzu — Mechanics Design
|
||||
**Role:** Systems Designer (Gestalt)
|
||||
**Date:** 2026-03-16
|
||||
**Workshop:** GJ 6711 — Furthest System
|
||||
|
||||
---
|
||||
|
||||
## Prefatory Note
|
||||
|
||||
The team built a hauntingly coherent world and then described how it feels. This document
|
||||
translates that into what the player does. Everything here assumes the sealed envelope and
|
||||
its internal canonical position: the thinness is a boundary condition between normal space
|
||||
and the Interstitium that requires continuous observation from the human side to remain
|
||||
stable. The community is the mechanism. The player can become part of it.
|
||||
|
||||
The core design problem is this: the best ending is "you chose to stay or chose to leave
|
||||
and neither choice is wrong." That ending only works if the player has invested something
|
||||
real — real time, real decisions, real accumulated presence — in the vigil. Without
|
||||
investment, stay/leave is a menu option. With investment, it's a genuine question.
|
||||
|
||||
Everything below is designed to create that investment without forcing it.
|
||||
|
||||
---
|
||||
|
||||
## 1. Player Verbs at Abzu
|
||||
|
||||
Let me map the concrete actions available. The problem with "experience atmosphere" is that
|
||||
it is not a verb. Here are the verbs.
|
||||
|
||||
### Primary Verbs
|
||||
|
||||
| Verb | What it looks like | Consequence |
|
||||
|------|-------------------|-------------|
|
||||
| **Watch** | Stand at a watch position during a community shift slot | Advances watch investment, triggers perception events, enables monologue unlocks |
|
||||
| **Investigate** | Examine threshold markings, architectural anomalies, Mode 1 structures | Accumulates frame evidence; unlocks conversation topics |
|
||||
| **Converse** | Talk to community members at appropriate trust tiers | Unlocks information tiers, surfaces rumors, reveals personal histories |
|
||||
| **File** | Write the Adams & Ford entry | The one irreversible action at Abzu; propagates into the Reach |
|
||||
| **Document** | Take field notes during watch (sub-action within Watch) | Produces the raw material for the entry; different note-taking produces different entries |
|
||||
| **Depart** | Leave via gate | The binary choice; closes the Abzu chapter |
|
||||
|
||||
### Secondary Verbs (Support the Primary Loop)
|
||||
|
||||
| Verb | What it produces |
|
||||
|------|-----------------|
|
||||
| **Orient** | Navigate Stillpoint's deliberately disorienting layout — finding the watch location is itself a puzzle |
|
||||
| **Sleep** | Advances time; triggers monologue drift events at different phases of stay |
|
||||
| **Eavesdrop** | Overhear shift-change conversations; different information than direct conversation |
|
||||
| **Examine doors** | The architectural evidence; triggers the monologue that fires at taller-than-standard geometry |
|
||||
| **Access Meridian records** | The Institute's file is classified — but the Institute's interest is public record |
|
||||
| **Read archive** | The community's oldest records; tier 4 knowledge, requires time investment to access |
|
||||
|
||||
### What Is NOT a Verb at Abzu
|
||||
|
||||
This matters. Abzu is designed to resist the normal game verbs:
|
||||
- **Combat** — there is nothing to fight and no one to fight
|
||||
- **Hack** — there is nothing to hack; the community has minimal Meridian presence
|
||||
- **Steal** — there is nothing worth stealing; the community does not have extractable resources
|
||||
- **Persuade** — you cannot talk your way to understanding; only time produces it
|
||||
|
||||
A player who arrives with a toolkit built for other systems will find their tools don't
|
||||
fit. This is designed. The monologue should register this: "There's nothing here to work
|
||||
on. That's not a complaint. It's information."
|
||||
|
||||
---
|
||||
|
||||
## 2. The Watch as Mechanic
|
||||
|
||||
This is the load-bearing mechanic. Get this wrong and everything else collapses.
|
||||
|
||||
### What "Keeping Watch" Is, Mechanically
|
||||
|
||||
The watch is a **spatial+temporal commitment**. The player must be at a specific location
|
||||
(the watch position, or within a defined proximity zone) for a specified duration. That is
|
||||
all. No button to press. No puzzle to solve. No progress bar.
|
||||
|
||||
The absence of a progress bar is intentional and important. The watch cannot be optimized.
|
||||
You cannot "do watching efficiently." You are present, or you are not.
|
||||
|
||||
**Why this is fun:** It inverts the normal game loop. The normal loop is: gather information,
|
||||
form hypothesis, act, receive feedback, update. The watch loop is: be present, wait, notice,
|
||||
be changed by noticing, wait more. Players who have only the first toolkit will find this
|
||||
frustrating. Players who engage will find it revelatory. Both responses are valid and the
|
||||
game should handle both (see Section 6).
|
||||
|
||||
### The Watch Position
|
||||
|
||||
There is one primary watch location: the thinness itself, which is not visible as a distinct
|
||||
object. It is a zone. It is marked by the Mode 1 structures surrounding it — the founding
|
||||
settlers built their watch structures around it, not to it. There is no wall around it. There
|
||||
is no sign. There is a place where the community sits, in rotation, and looks at something the
|
||||
player cannot quite identify as a specific thing to look at.
|
||||
|
||||
Finding the watch location is itself the first challenge. The settlement's deliberately
|
||||
disorienting layout (Araminta's design: no center of gravity, competing centers, paths that
|
||||
aren't direct) means the player cannot navigate to it immediately. The watch location is
|
||||
not labeled on any insert overlay — the community does not publish its location on the
|
||||
Meridian. You find it by following community members during their shift changes.
|
||||
|
||||
**The fog interaction:** When the player reaches the watch zone for the first time, the
|
||||
fog-of-war behavior changes subtly. Not dramatically — the fog does not lift, the
|
||||
shadowcasting does not expand. What changes is the quality of the fog at the boundary of
|
||||
the watch zone. Instead of the normal fog gradient (seen / seeing / unseen), there is a
|
||||
region at the boundary of the thinness where the fog behaves as if it cannot decide. Tiles
|
||||
oscillate between seen and partial-seen states at a frequency the player's visual system
|
||||
will register as movement. The monologue fires: "Something's wrong with my perception
|
||||
here. Not wrong. Different. Like looking at something that isn't quite in the same light
|
||||
as everything around it."
|
||||
|
||||
### The Shift Schedule
|
||||
|
||||
The community runs continuous shifts. These are mechanical facts:
|
||||
|
||||
| Shift | Duration | Time of day |
|
||||
|-------|----------|-------------|
|
||||
| Dawn shift | 4 hours | First light to mid-morning |
|
||||
| Day shift | 6 hours | Mid-morning to mid-afternoon |
|
||||
| Dusk shift | 4 hours | Mid-afternoon to last light |
|
||||
| Night shift | 6 hours | Dark hours |
|
||||
| Deep night | 4 hours | Lowest point |
|
||||
|
||||
Shifts overlap by 15 minutes. This overlap has never been shortened.
|
||||
|
||||
The player can take a watch slot. The community will accept this. They will not explain
|
||||
why. No NPC says "we need more watchers." They simply acknowledge the player's presence
|
||||
at the watch position with the same matter-of-factness they apply to everything at Abzu.
|
||||
|
||||
**Mechanical effect of taking a shift:**
|
||||
- Advances the watch investment counter (see below)
|
||||
- Triggers perception events appropriate to duration
|
||||
- Opens certain community conversations that are only available to someone who has watched
|
||||
|
||||
**Mechanical effect of missing a shift the player committed to:**
|
||||
- The community notices — but does not comment. The NPC who would have relieved the
|
||||
player watched alone. The monologue fires during the next encounter with that NPC:
|
||||
"She knows I wasn't there."
|
||||
- The watch investment counter does not advance
|
||||
- Nothing catastrophic happens on a single miss. The vigil has 4,000 people and has
|
||||
run for 300 years. One missed shift by a visitor is not a crisis.
|
||||
|
||||
### Watch Investment Counter
|
||||
|
||||
This is the hidden variable that drives the entire system. The player never sees it
|
||||
directly. It drives what the game shows and tells them.
|
||||
|
||||
```
|
||||
WATCH_INVESTMENT
|
||||
Range: 0 to 100
|
||||
Display: never (internal only)
|
||||
|
||||
Increments:
|
||||
+10 per completed shift (diminishing returns above 50)
|
||||
+3 per documented observation during a shift
|
||||
+5 per conversation unlocked through watch presence
|
||||
+15 for staying through a non-human shift change (see below)
|
||||
|
||||
Decrements:
|
||||
-5 per day without visiting the watch zone
|
||||
-0 if the player is actively investigating, sleeping, or conversing
|
||||
(absence is neutral, not punishing — only prolonged disengagement costs)
|
||||
|
||||
Thresholds:
|
||||
20: Perception events begin (fog oscillation becomes more pronounced)
|
||||
40: Tier-2 community information unlocks; monologue register shifts
|
||||
60: Archive access unlocks; monologue describes "settling"
|
||||
80: Non-human shift change visible at Elevated tier; deepest conversation unlocks
|
||||
100: Full integration threshold — "you have stayed long enough to understand
|
||||
that understanding is not what happens here"
|
||||
```
|
||||
|
||||
**The player cannot grind this.** The shifts are 4-6 hours of game time. The player
|
||||
cannot sleep-advance and count shifts. Being physically present at the watch zone for
|
||||
non-shift hours contributes negligibly. The watch mechanic requires the player to engage
|
||||
with the rhythm of community life at Abzu, not to optimize a number.
|
||||
|
||||
### Doing It Well vs. Doing It Poorly
|
||||
|
||||
| Quality | What it looks like | Feedback loop |
|
||||
|---------|-------------------|---------------|
|
||||
| **Well** | Taking shifts, arriving on time, staying for the overlap, documenting observations | Richer perception events, deeper community access, monologue coherence increases |
|
||||
| **Adequately** | Taking shifts but leaving early, missing documentation | Mechanical progress, thinner experience |
|
||||
| **Poorly** | Visiting the watch zone but not committing to shifts | Very slow investment gain, the community's matter-of-factness starts to feel pointed |
|
||||
| **Not at all** | Skipping the watch entirely and focusing on investigation/filing | Possible — but the Adams & Ford entry reflects it. The community knows. The monologue knows. |
|
||||
|
||||
The feedback is qualitative, not punitive. The game does not lock content from players
|
||||
who don't watch. It gives them a different experience of the same content.
|
||||
|
||||
---
|
||||
|
||||
## 3. Bleed on a Tile Map
|
||||
|
||||
This is the visual/mechanical expression of vigil failure. It needs to be specific.
|
||||
|
||||
### What Bleed Is, Mechanically
|
||||
|
||||
Bleed is what happens when the thinness expands because observation lapses. At Abzu, the
|
||||
vigil is stable — 300 years of unbroken continuity. The player will not trigger bleed
|
||||
through a single missed shift. What the player experiences is the ambient presence of
|
||||
the thing being managed — a constant low-level hum of the boundary condition — and
|
||||
occasional events that suggest what bleed would look like at scale.
|
||||
|
||||
These events are the game's way of giving the player experiential understanding of the
|
||||
stakes without manufacturing a crisis.
|
||||
|
||||
### The Bleed Tile States
|
||||
|
||||
Standard fog-of-war has three states: seen, partial (remembered), unseen. At Abzu, in
|
||||
the vicinity of the watch zone, a fourth state exists:
|
||||
|
||||
**Threshold-adjacent tile state:** A tile at the boundary of the thinness is visible
|
||||
by normal shadowcasting standards but is rendered differently. Characteristics:
|
||||
|
||||
- The amber light quality is wrong. Not darker, not brighter. The color temperature
|
||||
shifts toward the diffuse gas-giant reflection spectrum: slightly cooler, slightly
|
||||
silver instead of amber. The effect is below conscious threshold on first encounter.
|
||||
It accumulates.
|
||||
- Entity color coding (D-033) behaves normally on threshold-adjacent tiles — but the
|
||||
teal/green/amber of NPC relationship colors appears slightly desaturated. The D-033
|
||||
signal is reliable; the background it's read against is subtly different.
|
||||
- No special visual effect, no shader, no post-processing. The difference is implemented
|
||||
as a lighting zone with the reflected-light palette values from Araminta's spec
|
||||
(`#c4a040` instead of `#d4920a`). Subtle. Intentional. Unannounced.
|
||||
|
||||
### Bleed Events (Storyteller-Driven)
|
||||
|
||||
The storyteller can trigger bleed events. These are rare — 2-4 per playthrough at Abzu,
|
||||
depending on watch investment. They are the game's most honest expression of what is
|
||||
at stake.
|
||||
|
||||
**Event type: The Fog Expansion**
|
||||
|
||||
Trigger: The player has been at Abzu for 3+ in-game days without taking a watch shift.
|
||||
|
||||
Mechanical expression:
|
||||
1. A specific cluster of tiles near the watch zone (not in the player's current LOS)
|
||||
reverts to "unseen" state despite having been previously visited
|
||||
2. The reversion is gradual — over 10-15 real seconds, the explored-and-remembered
|
||||
tiles at the thinness boundary drain back to full fog
|
||||
3. The monologue fires: "I've been here. I know this place. Why does this look like
|
||||
I've never seen it?"
|
||||
4. The effect reverses within the same scene if the player returns to the watch zone.
|
||||
Normal fog exploration rules apply once they are physically present.
|
||||
|
||||
This is not a jumpscare. It is not dramatic. It is a subtle wrongness that a player who
|
||||
is paying attention will notice and a player who is not paying attention will walk past.
|
||||
Both are valid responses. The player who noticed gets more.
|
||||
|
||||
**Event type: The Overlap Failure**
|
||||
|
||||
Trigger: The player has taken a watch shift and left before the overlap window (the
|
||||
15-minute overlap before the next watcher arrives).
|
||||
|
||||
Mechanical expression:
|
||||
1. As the player leaves the watch zone before their relief arrives, the threshold-adjacent
|
||||
tiles begin the fog oscillation behavior described earlier — the flickering between
|
||||
seen and partial-seen
|
||||
2. The oscillation increases in frequency for the 15-minute window when the thinness
|
||||
is unattended
|
||||
3. The community member who was supposed to relieve the player arrives and the oscillation
|
||||
stops. The tiles stabilize.
|
||||
4. The monologue fires, delayed: "I don't know what I thought I was doing. There's
|
||||
a reason the overlap exists."
|
||||
|
||||
**Event type: The Recognition**
|
||||
|
||||
Trigger: Watch investment crosses 60 (the "settling" threshold) AND the player has
|
||||
Augmented or Elevated tier.
|
||||
|
||||
Mechanical expression:
|
||||
1. During a watch shift, the fog at the thinness boundary does something it doesn't
|
||||
do anywhere else in the game: it becomes directional. The normal fog gradient radiates
|
||||
outward from the player. At the thinness, for a brief window (5-10 real seconds),
|
||||
the fog gradient appears to radiate INWARD toward the watch zone — as if something
|
||||
on the other side of the boundary is looking back.
|
||||
2. Elevated tier only: the inward-gradient fog is accompanied by a thermal signature
|
||||
in the watch zone that resolves to nothing when examined directly (Nigel and Araminta's
|
||||
convergent design for the shift-takers). It is present, then it is not, without any
|
||||
animation of disappearance. It was there. Now it isn't.
|
||||
3. The monologue fires: "That was attention. Something paid attention to me." Full stop.
|
||||
No elaboration. The player speculates.
|
||||
|
||||
**What Bleed Would Look Like at Scale (Player Never Sees This)**
|
||||
|
||||
For the design team: full bleed propagation would look like the fog-expansion event but
|
||||
permanent, accelerating, and spreading through the gate network. High-bleed gates in other
|
||||
systems are the distant echo of this. The player at Abzu can intuit this connection — the
|
||||
monologue can gesture toward it at high watch investment — but the game never confirms
|
||||
the mechanism.
|
||||
|
||||
### Tile Map Expression: Summary Table
|
||||
|
||||
| Bleed state | Tile appearance | Fog behavior | Sound |
|
||||
|-------------|-----------------|--------------|-------|
|
||||
| Normal (stable vigil) | Amber light (#d4920a) | Standard shadowcast | Ambient hum, low |
|
||||
| Threshold-adjacent (always present) | Cool-silver light (#c4a040) | Slight oscillation at boundary | Hum frequency subtly shifted |
|
||||
| Observation lapse (< 15 min) | Amber, slightly desaturated | Boundary tiles drain to fog | Hum gaps — brief silences |
|
||||
| Fog expansion event | Normal, but wrong | Previously explored tiles revert | Silence, then ambient resumes |
|
||||
| Recognition event (Augmented+) | Inward fog gradient, 5-10s | Direction reversal, then normal | Tone — not a sound effect, a frequency |
|
||||
|
||||
---
|
||||
|
||||
## 4. The Adams & Ford Entry as Mechanic
|
||||
|
||||
The commission is the player's external motivation and their decision surface. Let me
|
||||
break down what this actually means mechanically.
|
||||
|
||||
### The Entry as Accumulated Evidence
|
||||
|
||||
The Adams & Ford entry is not written in a single interaction. It is assembled from the
|
||||
player's entire time at Abzu. Every documented observation, every conversation, every
|
||||
watch shift contributes to a pool of available material. When the player chooses to file,
|
||||
they select from that pool — not from a list of abstract choices, but from the specific
|
||||
things they recorded.
|
||||
|
||||
**The documentation system:**
|
||||
|
||||
During investigation and watch shifts, the player can document observations via a
|
||||
field notes verb. This is a single button press — not a text input, not a journal
|
||||
system. The player presses "document" and the system records: location, time, perception
|
||||
tier active, watch investment level, and a system-generated summary of what the character
|
||||
can currently perceive (derived from the monologue system's active state).
|
||||
|
||||
| Note taken at | What it records | What entry it unlocks |
|
||||
|---------------|-----------------|----------------------|
|
||||
| Watch zone, investment < 20 | Baseline perceptual data: light quality, architectural description | "A quiet system at the end of the network" — the first correspondent's register |
|
||||
| Watch zone, investment 20-40 | Anomalous perceptual data: fog quality, threshold-adjacent lighting | "Something about the light here" — the second correspondent's register |
|
||||
| Watch zone, investment 40-60 | Relational data: the community's accommodation, the overlap ritual | "The community keeps a schedule that has no apparent purpose" |
|
||||
| Watch zone, investment 60-80 | Understanding-approaching data: the watch as load-bearing, the overlap as necessity | "Three hundred years of something I cannot name" |
|
||||
| Watch zone, investment 80+ | Integration-level data: the thinness as felt presence, the watching as acknowledgment | "The entry cannot be filed because I do not have the category for what I experienced" |
|
||||
|
||||
This is the game's mechanical answer to why three correspondents failed. They were working
|
||||
from lower watch investment. Not because they were less skilled — because they didn't stay
|
||||
long enough. The first correspondent left during Phase 1 (days 1-14). The second left
|
||||
during Phase 2. The third is in Phase 3, which is why they can't leave.
|
||||
|
||||
### The Filing Decision
|
||||
|
||||
When the player chooses to file, they face a single decision of substance: **what register
|
||||
is the entry written in?**
|
||||
|
||||
The game presents the player with their accumulated notes. Notes are grouped by register
|
||||
(the five levels above). The player selects which notes form the basis of the entry. They
|
||||
do not write text — the system generates the entry from the selected notes using the
|
||||
monologue system's vocabulary. The player's choice is editorial: what did you decide to
|
||||
include?
|
||||
|
||||
**The consequence is permanent and propagates:** The filed entry goes into the game's
|
||||
Meridian as the authoritative Adams & Ford record for GJ 6711. On subsequent playthroughs
|
||||
(and in the shared setting's future), other characters can find this entry. The entry
|
||||
describes what the player understood. If the player filed on day 3 with investment < 20,
|
||||
the entry reads like the first correspondent's — professional, present, and slightly off.
|
||||
If the player filed with investment 80+, the entry reads like someone who has been to a
|
||||
place and cannot explain what the place did to them. Both are accurate. Neither is complete.
|
||||
|
||||
### The Entry and the Watch Mechanic: Interaction
|
||||
|
||||
Here is the emergent mechanic that makes this interesting. The Adams & Ford commission
|
||||
creates tension with the watch:
|
||||
|
||||
- Filing early (low investment) means writing an entry like the ones that came before —
|
||||
technically complete, experientially insufficient. The commission is fulfilled. The
|
||||
player can leave. But the entry will circulate through the Reach as the authoritative
|
||||
description of Abzu, and it is wrong in ways the player may only understand on a
|
||||
second playthrough.
|
||||
|
||||
- Filing late (high investment) means the entry is richer and stranger and will do
|
||||
something different to the Reach's understanding of this system. But staying long
|
||||
enough to reach high investment means the player has engaged with the watch, and
|
||||
engaging with the watch is how the stay/leave decision becomes real.
|
||||
|
||||
The commission is a **deadline the player sets for themselves.** There is no in-game
|
||||
pressure to file by a certain date. The player can stay indefinitely. The commission
|
||||
is just permission — Adams & Ford contracted them to write an entry, not a
|
||||
good one. The minimum is always available. The question is whether the player wants
|
||||
to do more than the minimum.
|
||||
|
||||
This is the same question the vigil asks.
|
||||
|
||||
### What Happens If the Player Ignores the Watch and Just Files
|
||||
|
||||
Let me be concrete about this path because it is valid and should be honored.
|
||||
|
||||
A player who arrives, investigates efficiently, gathers tier-1 and tier-2 information,
|
||||
takes notes during investigation (not during watch shifts), and files on day 5 will
|
||||
produce an entry with investment ~ 10-15. The entry will read like the first
|
||||
correspondent's. It will be technically accurate. It will describe a quiet frontier
|
||||
system. The commission pays.
|
||||
|
||||
The player can depart. The game does not punish this.
|
||||
|
||||
But the monologue fires as they approach the gate: "I got what I came for. I should
|
||||
feel satisfied." Pause. "I don't." This is not a guilt trip. This is character voice.
|
||||
The character knows they left something unexamined. The player decides whether they
|
||||
care.
|
||||
|
||||
---
|
||||
|
||||
## 5. Tension and Stakes
|
||||
|
||||
The project lead said: what can go wrong? Let me map the failure states.
|
||||
|
||||
### Failure States at Abzu
|
||||
|
||||
Abzu has no fail conditions in the conventional sense. You cannot die here (there is
|
||||
nothing to fight). You cannot be arrested (the community has no enforcement structure).
|
||||
You cannot miss a quest deadline (there are no quests).
|
||||
|
||||
The failure states are informational, not mechanical. They are all states where the
|
||||
player leaves with less understanding than they could have had.
|
||||
|
||||
| Failure state | How it happens | What the player loses |
|
||||
|---------------|----------------|----------------------|
|
||||
| **Filing too early** | Impatience; efficient-optimization instinct | Entry quality; the community's tier-4 knowledge; the Recognition event |
|
||||
| **Missing the recognition** | Not being at the watch zone at Elevated tier when the storyteller triggers it | One of the game's most significant perceptual events |
|
||||
| **Not finding the watch zone** | The settlement's disorienting layout | Entire watch mechanic; entry is tier-1 data only |
|
||||
| **Missing the non-human shift change** | Not being present at the right time OR having investment < 80 | The physical evidence that something non-human shares the vigil |
|
||||
| **Leaving before the founding record unlocks** | Investment < 60 when the player departs | Cannot access the archive; the founding perceptual event is unknowable |
|
||||
| **Overstaying past the leave window** | Staying too long... | Not a failure state. This is integration. This is the other ending. |
|
||||
|
||||
### The Implicit Stakes: The Entry's Reach-Wide Consequences
|
||||
|
||||
The entry propagates. This is the medium-term consequence structure.
|
||||
|
||||
If the player files a tier-1 entry:
|
||||
- The Reach's shared understanding of Abzu remains at tier-1 common knowledge
|
||||
- The Veil Institute's file on Abzu does not gain external pressure
|
||||
- The third correspondent continues to be listed as "active at GJ 6711"
|
||||
- Other players (or the same player on a second playthrough) will find an entry that
|
||||
reads like the first correspondent's, and will arrive at Abzu without useful preparation
|
||||
|
||||
If the player files a tier-3 or tier-4 entry:
|
||||
- The Reach's shared understanding shifts
|
||||
- The Veil Institute's paralysis is stressed — the entry is now public record that
|
||||
something anomalous exists at Abzu, which neither faction can ignore
|
||||
- The Adams & Ford database has an entry that reads like someone who was changed by
|
||||
what they experienced
|
||||
- Subsequent visitors arrive primed differently
|
||||
|
||||
These consequences are narrative/world-state, not gameplay-punishing. But they are
|
||||
real. The entry the player files is permanent. It matters.
|
||||
|
||||
### What Happens If the Player Ignores the Vigil Entirely and Tries to Force Answers
|
||||
|
||||
A player who investigates aggressively — using all available perception modes, accessing
|
||||
every Meridian record, pursuing every conversation to exhaustion — will find:
|
||||
|
||||
- Every conversation eventually reaches a wall. Not a hostile wall. A wall made of
|
||||
the limits of what can be explained to someone who hasn't stayed. The community isn't
|
||||
hiding information. They are the answer, and the answer requires time.
|
||||
- The four frames (astronomical, geological, perceptual, topological) can all be
|
||||
partially confirmed through investigation alone. None of them resolve. Each one
|
||||
produces more questions than it answers.
|
||||
- Elevated tier investigation without watch investment produces the perception events
|
||||
but without the monologue context that gives them meaning. The player sees the fog
|
||||
inversion. The monologue says: "Something's wrong with my perception system." No
|
||||
further interpretation. The Recognition Event is registered but not understood.
|
||||
|
||||
This is the "interesting complex vs. annoying complex" question. Is it annoying that
|
||||
investigation alone can't crack Abzu? My position: no, because the game has been
|
||||
training the player to investigate for 23 hops. When investigation hits its limit at
|
||||
Abzu, the player knows what they're experiencing. It's not a puzzle with a missing
|
||||
piece. It's the correct experience of a place that resists the investigation framework.
|
||||
The monologue names this directly at high investigation-without-watch states: "I've
|
||||
looked at everything here. I still don't know what I'm looking at."
|
||||
|
||||
---
|
||||
|
||||
## 6. The Decision to Stay or Leave
|
||||
|
||||
This is the endgame mechanic. Everything else feeds into it.
|
||||
|
||||
### The Decision Surface
|
||||
|
||||
The decision to stay or leave is not presented as a choice. There is no dialogue option
|
||||
"Do you want to stay?" There is no achievement. There is no conversation with an NPC
|
||||
who says "you should stay." The decision is expressed entirely through player behavior:
|
||||
do they walk to the gate?
|
||||
|
||||
What the player has accumulated by the time they face this decision:
|
||||
|
||||
**Investment in the watch:**
|
||||
At high investment, the player has taken multiple shifts. They have a regular position
|
||||
at the watch zone. Community members acknowledge their presence without comment. Their
|
||||
monologue has shifted register — from visitor-observing to something more like
|
||||
resident-understanding. The player has, functionally, been keeping watch.
|
||||
|
||||
**The Adams & Ford entry:**
|
||||
The entry is either filed (player has completed their commission) or unfiled (player
|
||||
hasn't yet). If unfiled and investment is high, the monologue flags the tension: "I
|
||||
could write the entry now. I could write it better. I don't know if I want to."
|
||||
|
||||
**The personal investment (varies by playstyle hook):**
|
||||
- Tycoon: they found the one thing money can't buy; do they try to replicate it elsewhere?
|
||||
- Relational: they found the person they came for; but is the person they found someone
|
||||
they want to leave with?
|
||||
- Political: they have enough information to weaponize if they're willing to; are they?
|
||||
- Investigation: they have the best possible entry; do they know what it means that
|
||||
they can't fully explain what they experienced?
|
||||
|
||||
### The Mechanical Expression of the Choice
|
||||
|
||||
**The gate is always accessible.** The player can leave at any time. The game does not
|
||||
lock them in. The community does not prevent them. No NPC stands in front of the gate.
|
||||
|
||||
What changes based on watch investment is the monologue that fires when the player
|
||||
approaches the gate to leave:
|
||||
|
||||
| Investment | Monologue at gate | Subtext |
|
||||
|------------|-------------------|---------|
|
||||
| < 20 | "That was interesting. Unusual system. I have what I need." | Clean departure. No pull. |
|
||||
| 20-40 | "I got what I came for. I should feel satisfied." Pause. "I don't." | First hook. Player must decide if they care. |
|
||||
| 40-60 | "There's a shift tomorrow morning. I could take it. I don't have to." | The watch is named directly as the pull. |
|
||||
| 60-80 | "Three hundred years. They built a community around this. I've been here [X] days and I think I'm starting to understand why." | Integration approaching. The game does not push. |
|
||||
| 80+ | "I could file the entry and leave. The entry I'd file now isn't the same entry I would have filed when I arrived. I don't know what that means." Pause. "I think it means I have to decide." | The game is honest: this is a decision, not a drift. |
|
||||
| 100 | "I'm not leaving. I don't think I was going to." | Integration complete. Player may still leave — but the character knows something has changed. |
|
||||
|
||||
**If the player leaves at any investment level, that is a valid ending.**
|
||||
|
||||
The game does not punish departure. The monologue accepts it. The entry the player files
|
||||
(if they haven't already) reflects their investment level. They carry the experience
|
||||
into the rest of the game — or the rest of the Reach, depending on where they go.
|
||||
|
||||
**If the player stays:**
|
||||
|
||||
Investment 80+ and choosing not to depart after the final monologue triggers a
|
||||
mechanical state change: the player character is now part of the shift schedule as a
|
||||
regular watcher. Not via a cutscene. Not via a dialogue confirmation. The shift
|
||||
schedule NPC data updates. The player's watch position is assigned. The community
|
||||
treats them as they treat any watcher: with matter-of-fact acknowledgment.
|
||||
|
||||
The game continues. There is still content — conversations, archive access, further
|
||||
perception events. But the character has made a choice that is functionally the same
|
||||
as what the third correspondent made. The Adams & Ford entry goes unfiled unless the
|
||||
player files it.
|
||||
|
||||
The player can still leave. They can always leave. But leaving now fires a different
|
||||
monologue: "I stayed. I watched. I know what I was watching for now. Not what it is.
|
||||
What watching it requires." And then the gate.
|
||||
|
||||
---
|
||||
|
||||
## 7. Integration with Existing Systems
|
||||
|
||||
Let me map every Abzu mechanic to the systems that must support it.
|
||||
|
||||
### Perception Tier System (D-017, D-019)
|
||||
|
||||
**Baseline:** Sees the architectural evidence (taller doors), the Mode 1 construction,
|
||||
the threshold markings. Gets full monologue commentary. Can access all watch shift
|
||||
mechanics. Experiences fog-expansion events. Does NOT experience Recognition Event.
|
||||
Does NOT see the thermal signature of the non-human shift-takers.
|
||||
|
||||
**Augmented:** Above, plus — richer audio during shifts (the hum frequency shifts are
|
||||
distinguishable as a pattern, not just a texture). During the Recognition Event: the
|
||||
fog inversion is more pronounced and lasts longer. The monologue has more specific
|
||||
vocabulary for what is perceived.
|
||||
|
||||
**Elevated:** Above, plus — the Recognition Event includes the thermal signature at
|
||||
the thinness boundary. The shift-taker thermal presence (present, then not, without
|
||||
transition). The monologue fires with the highest-specificity interpretation: "That was
|
||||
attention. Something paid attention to me." AND: at investment 80+, a secondary event
|
||||
fires during a shift where the fog quality at the thinness becomes briefly coherent —
|
||||
not a shape, not a face, but the quality of a direction. Something is oriented toward
|
||||
the watch zone. The monologue: "I don't have a word for what I'm looking at. The watch
|
||||
position is named that for a reason."
|
||||
|
||||
**Tier-scaling design principle:** Every tier sees the same system. Higher tiers see
|
||||
more of the same system. No tier unlocks a "truth" that lower tiers cannot access —
|
||||
they just have sharper instruments for reading the same phenomenon. This preserves
|
||||
the non-resolution principle while rewarding perception investment.
|
||||
|
||||
### Fog-of-War System (D-011, D-035)
|
||||
|
||||
Abzu requires two extensions to the standard fog system:
|
||||
|
||||
1. **Threshold-adjacent tile classification:** A tile type that uses the reflected-light
|
||||
palette rather than the primary-light palette. No new fog state — the tile is "seen"
|
||||
normally. The difference is purely in lighting values. This is a zone property, not
|
||||
a fog property. The fog shader reads it from the tile's zone tag.
|
||||
|
||||
2. **Fog-inversion event:** A one-off trigger that can briefly reverse the direction of
|
||||
the fog gradient near the thinness. Mechanically: for a specified window, the
|
||||
thinness-boundary tiles are rendered with the fog shader in "inward" mode (the opacity
|
||||
gradient is highest at the center of the thinness zone, fading toward the player's
|
||||
position rather than the reverse). This is a client-side render effect triggered by
|
||||
a server event. The event is storyteller-driven. It does not affect actual LOS
|
||||
calculation — only the visual representation of the fog boundary.
|
||||
|
||||
Concern: Does D-045 (environmental neutrality / strict zero shift) apply here?
|
||||
Ruling: No. D-045 prohibits world-layer changes triggered by narrative state
|
||||
(conspiracy activation, investigation progress). The fog-inversion is a diegetic
|
||||
physical event — the thinness is actually doing something, and the fog system is
|
||||
representing it accurately. It is more like weather (which D-045 explicitly permits)
|
||||
than like the narrative-state visual shifts D-045 prohibits.
|
||||
|
||||
### Internal Monologue (D-016)
|
||||
|
||||
The monologue is the primary delivery system for all of Abzu's perceptual content.
|
||||
Almost every mechanic described above triggers a monologue event.
|
||||
|
||||
**Abzu-specific monologue registers:**
|
||||
|
||||
| Register | Trigger condition | Tone |
|
||||
|---------|-------------------|------|
|
||||
| Visitor | Investment < 20 | Professional, observational, slightly flat |
|
||||
| Noticing | Investment 20-40 | Quietly puzzled; the character knows something is different but doesn't have vocabulary |
|
||||
| Settling | Investment 40-60 | Tentative; the character is building a framework that keeps not closing |
|
||||
| Understanding-approaching | Investment 60-80 | The framework is abandoned; the character is reporting experience instead of building categories |
|
||||
| Integration | Investment 80+ | Plain. No metaphor. The character describes what they see without interpretation because interpretation is no longer what the situation requires. |
|
||||
|
||||
**The monologue register shift is the primary feedback loop.** The player knows their
|
||||
investment is increasing not from a counter or a progress bar but from noticing that
|
||||
the character's interior voice has changed. This is the correct feedback mechanism for
|
||||
a location that resists gamification.
|
||||
|
||||
**Key monologue events (non-negotiable, these must ship):**
|
||||
|
||||
- First approach to watch zone (any investment): "These were built this size deliberately.
|
||||
Someone decided this was the right size." (The taller doors. No elaboration.)
|
||||
- First fog-expansion event: "I've been here. I know this place. Why does this look
|
||||
like I've never seen it?"
|
||||
- First non-human shift indicator (Augmented+): "I was wrong about something. I don't
|
||||
know what yet."
|
||||
- Recognition Event (Elevated): "That was attention. Something paid attention to me."
|
||||
- Gate approach monologue: investment-scaled (see Section 6 table)
|
||||
- Filing the entry: always fires at entry submission. Register matches investment level.
|
||||
High investment: "I don't know if this helps anyone. I know it's accurate."
|
||||
|
||||
**Monologue as unreliable narrator (D-016):** At low investment, the monologue can
|
||||
be confidently wrong. "The shift schedule seems like a kind of communal ritual —
|
||||
probably cultural significance from the founding era." The player learns this
|
||||
interpretation is insufficient as investment increases. The monologue never announces
|
||||
that it was wrong. The player compares early and late entries.
|
||||
|
||||
### Storyteller / Rimworld-style Event System (D-005 referenced in Round 14)
|
||||
|
||||
The storyteller's role at Abzu is to pace the bleed events and manage the recognition
|
||||
event timing. Specific parameters:
|
||||
|
||||
**Events per playthrough:**
|
||||
- Fog expansion: 1-2 (triggered by watch abstention + minimum day threshold)
|
||||
- Overlap failure: 0-1 (triggered by player leaving before overlap window; only once,
|
||||
to avoid annoyance)
|
||||
- Recognition: 0-1 (triggered by investment ≥ 60 AND Augmented+ AND being present
|
||||
during a watch shift — the storyteller waits for the right moment)
|
||||
- Non-human shift indicator: 0-1 (investment ≥ 80 AND present at shift change timing)
|
||||
|
||||
**Storyteller escalation principle:** Unlike other systems in the game, the storyteller
|
||||
at Abzu does NOT escalate tension over time. It de-escalates. The longer the player
|
||||
stays, the quieter the events become. Early visits feel stranger. Long stays feel
|
||||
settled. This inverts the normal storyteller pattern (build to crisis) and it is
|
||||
intentional: Abzu's drama is internal, not external.
|
||||
|
||||
**The storyteller knows the stay/leave state.** If the player has been at Abzu for
|
||||
more than 20 game days without departing, the storyteller flags this as a potential
|
||||
"staying" arc and ensures the non-human shift indicator event fires before the player
|
||||
departs. Every player who stays long enough sees this. It is the payoff for staying.
|
||||
|
||||
### Information Asymmetry — The Master Mechanic
|
||||
|
||||
Let me break down what the player knows vs. doesn't know at each phase of Abzu.
|
||||
|
||||
**What the player can know (knowable with effort):**
|
||||
- The community keeps a continuous watch schedule (observable)
|
||||
- The schedule has run for 300 years (tier-2 community knowledge)
|
||||
- Three Adams & Ford correspondents preceded the player (tier-2 specialist knowledge)
|
||||
- The founding structures are over-built for actual conditions (observable)
|
||||
- The doors are taller than standard (observable; monologue flags)
|
||||
- The Veil Institute has a classified file on this system (Meridian record, partial)
|
||||
- Something about the light is different (observable once the player notices)
|
||||
|
||||
**What the player can accumulate but not resolve:**
|
||||
- What is being watched
|
||||
- Whether the non-human shift-takers are Builders, Threshold entities, or something else
|
||||
- Whether the founding settlers understood what they were starting
|
||||
- What would happen if the vigil failed at scale
|
||||
- Whether the high-bleed gates in the rest of the Reach are connected
|
||||
|
||||
**What the player cannot access, ever:**
|
||||
- The community's tier-4 knowledge (the full understanding) — this cannot be transmitted.
|
||||
Not because it is withheld. Because it requires staying. The player who stays long
|
||||
enough approaches it but cannot close on it. This is correct. Miri's phrase: "you
|
||||
either understand or you don't. Understanding comes from staying."
|
||||
- Direct evidence of what takes the other shifts. The doors are physical evidence.
|
||||
The thermal signature (Elevated only) is perception-scaled ambiguity. The player
|
||||
never sees the shift-takers.
|
||||
- Confirmation of the high-bleed connection. The monologue at high investment and
|
||||
Elevated tier can gesture toward it. The game never confirms it. The player
|
||||
who arrives at the connection independently has understood something true.
|
||||
|
||||
**The asymmetric information structure IS the Abzu design.** Every other location in
|
||||
the game gives the player information that resolves into action. Abzu gives the player
|
||||
information that resolves into presence. The detective framework is preserved (gather,
|
||||
evaluate, interpret) but the output is not an action. It is a state.
|
||||
|
||||
---
|
||||
|
||||
## 8. Systems That Need to Interact: The Emergent Mechanic Map
|
||||
|
||||
Let me map the interactions I'm most interested in — the places where systems
|
||||
colliding might produce stories the designers didn't anticipate.
|
||||
|
||||
| System A | System B | Interaction | Emergent story |
|
||||
|----------|----------|-------------|----------------|
|
||||
| Watch investment | Entry filing | Player files at investment 40; returns on second playthrough and recognizes the entry as insufficient | "I wrote this. I was wrong." |
|
||||
| High-bleed gates (experienced earlier) | Recognition Event (Elevated) | Player transits a high-bleed gate on approach to Abzu; at Abzu's Recognition Event, the monologue connects the felt quality | "That's what the gates were doing. This is what it looks like from the source." |
|
||||
| Unbound character (no re-embodiment) | Watch investment 80+ | Player is Unbound and has reached near-integration; death here is permanent; the player must decide if the vigil is worth it | Nigel's darkest implication made mechanical |
|
||||
| Correspondent variant (Nigel's seed) | Watch mechanic | Variant C: the third correspondent is integrated and no longer identifies as one; player discovers this by watching with them | "They stayed. Now I'm watching with them. I understand now what staying meant." |
|
||||
| Relational playstyle hook | Stay/leave | The person the player came for has reached integration; leaving them is leaving them permanently | "Do I stay for them? Or because they're why I understand what staying means?" |
|
||||
| Political playstyle hook | Entry filing | Player has enough for leverage; they must choose between the accurate entry and the strategically useful one | The only real moral choice at Abzu is about the entry |
|
||||
|
||||
---
|
||||
|
||||
## 9. What I Would Cut, and Why
|
||||
|
||||
Good design requires scope discipline. Not every mechanic I've described above should
|
||||
ship on the first pass. Here's my priority ranking:
|
||||
|
||||
**Must ship (Abzu doesn't work without these):**
|
||||
1. The watch zone as a navigable location (the disorienting layout, the shift schedule)
|
||||
2. The watch investment counter (invisible, but drives everything)
|
||||
3. The threshold-adjacent tile lighting zone
|
||||
4. The entry documentation system (field notes → filing → propagation)
|
||||
5. The gate departure monologue (investment-scaled)
|
||||
6. Fog-expansion bleed event (the core "what bleed looks like" expression)
|
||||
|
||||
**Should ship (makes the system rich):**
|
||||
7. The Recognition Event (Elevated tier; the signature experience of Abzu)
|
||||
8. The monologue register shift system (the feedback loop for investment)
|
||||
9. Per-shift documentation with investment-scaled note content
|
||||
10. Entry propagation to Reach-wide Meridian record
|
||||
|
||||
**Can defer (depth content, not structural):**
|
||||
11. Founding record archive unlock (investment 60+)
|
||||
12. Non-human shift indicator thermal event (Elevated 80+)
|
||||
13. Correspondent interaction variants (seed-dependent)
|
||||
14. Per-playstyle hooks (the investment hooks for tycoon, political, relational paths)
|
||||
|
||||
**Cut or redesign:**
|
||||
- Any visual effect that announces bleed dramatically. If bleed looks like a horror
|
||||
game event, it breaks the tone. The fog-expansion event should be subtle enough
|
||||
that some players miss it. That is the correct experience.
|
||||
- Any dialogue option that lets an NPC explain the vigil. They cannot. The game
|
||||
should not simulate this as a dialogue option that fails. It should simply not
|
||||
be an option. The community's warmth without explanation is mechanical: they
|
||||
don't have a conversation topic for "what are you watching."
|
||||
|
||||
---
|
||||
|
||||
## Summary: The Mechanical Contract with the Player
|
||||
|
||||
Abzu asks the player to do something the game has not asked before: be present without
|
||||
optimizing.
|
||||
|
||||
The player's toolkit — investigation, information gathering, social manipulation, economic
|
||||
leverage — all works at Abzu, but none of it produces the main thing. The main thing
|
||||
requires staying and watching. The game does not explain this until the player is already
|
||||
experiencing it.
|
||||
|
||||
The watch mechanic translates the vigil into a player experience that is simple in its
|
||||
rules (be here, during this window, long enough) and complex in its effects (monologue
|
||||
register shift, tier-scaled perception events, community relationship deepening, entry
|
||||
quality accumulation).
|
||||
|
||||
The Adams & Ford entry is the decision surface: when to file, what to include, what
|
||||
register to file in. It is the only irreversible choice at Abzu, and what it communicates
|
||||
to the rest of the Reach is the permanent record of what the player understood.
|
||||
|
||||
The stay/leave decision is not a choice the game presents. It is a choice the player
|
||||
makes through behavior. The game's job is to make sure the player knows, when they
|
||||
approach the gate, exactly what they are choosing to leave.
|
||||
|
||||
The game has been teaching the player to look. Abzu is where looking was never
|
||||
the point. Being present was. Every mechanic above is designed to produce that
|
||||
recognition — not announce it.
|
||||
@@ -0,0 +1,205 @@
|
||||
# GJ 6711 / Abzu Workshop — Project Lead Direction & Critiques
|
||||
**Verbatim messages from the project lead across the workshop**
|
||||
**Date:** 2026-03-16
|
||||
|
||||
---
|
||||
|
||||
## Round 0 — Initial Creative Direction (Pre-Workshop)
|
||||
|
||||
> as far as the 23 star this: hmm. that is interesting indeed not what did they run to, but who ran there
|
||||
>
|
||||
> Yes. That's the frame.
|
||||
>
|
||||
> Wave 3 is old enough to be deliberate. This wasn't chain migration following neighbors. Someone chose hop 23, dead-end, K-type, nothing remarkable about the star. Three hundred years ago. And enough of them that it stuck.
|
||||
>
|
||||
> Not fleeing. Seeking.
|
||||
>
|
||||
> Which means they knew something was there before they went. Or they suspected. Or someone told them.
|
||||
>
|
||||
> And three hundred years later their descendants are still there. Which means whatever they came for — they either found it, or they're still looking, or finding it changed what they were looking for.
|
||||
>
|
||||
> The Guide correspondent who went to file that entry. What did they see that made them stop filing.
|
||||
>
|
||||
> Not danger necessarily. Just — something that made the normal categories not quite apply anymore. You can't write a conditions-accurate reference document for somewhere that makes you uncertain what the conditions mean.
|
||||
>
|
||||
> Adams keeps the entry as forthcoming. Not because she thinks the correspondent is dead. Because she's read enough of what they sent before they stopped to know the entry isn't writable yet.
|
||||
>
|
||||
> That's the weird. Not the system. The fact that it resists description by someone trained to describe things.
|
||||
>
|
||||
> What did wave 3 settlers know that made them go that far.
|
||||
|
||||
---
|
||||
|
||||
## Round 1 — Cross-Pollination Feedback
|
||||
|
||||
> again I only saw your second hand conclusions and not the synthesis document you all seem to be acting on
|
||||
|
||||
---
|
||||
|
||||
## Round 2 — "What Is There?"
|
||||
|
||||
> while the mechanism of exploring the system is for Adams & Ford hiring the player, which I ABSOLUTELY LOVE, it does not say what is there
|
||||
>
|
||||
> Right. And it shouldn't.
|
||||
>
|
||||
> The Adams & Ford commission is the frame — why you're there, who sent you, what you're supposed to produce. It's not the answer. It's the job that puts you in the position of the correspondents who couldn't file.
|
||||
>
|
||||
> You arrive as a professional investigator hired to do what three predecessors couldn't. You have better tools, better skills, more time maybe. And you encounter the same thing they encountered: not resistance, not danger, not mystery in the conventional sense. Just — a place that doesn't yield to description.
|
||||
>
|
||||
> The job is real. The payment is real. The entry you eventually file is real. What GJ 6711 actually is remains exactly as unresolved as it was before you arrived.
|
||||
>
|
||||
> Which is perfect. Because the player isn't there to solve it. They're there to experience what it means to be in a place that can't be solved. And then write something anyway.
|
||||
>
|
||||
> The Adams & Ford frame also explains why a player would go to hop 23 at all. Without it, GJ 6711 is a distant curiosity. With it, there's a job, a contract, a reason — and the reason is completely legitimate and completely beside the point simultaneously.
|
||||
>
|
||||
> Did the team land on what's actually there, or is that still open?
|
||||
|
||||
---
|
||||
|
||||
## Round 2 — The Sealed Envelope
|
||||
|
||||
*When told the team's position was "genuinely unresolved, no canonical answer even internally":*
|
||||
|
||||
> good enough, or scary enough to keep the vigilance
|
||||
|
||||
*Then the creative direction that defined the entire workshop:*
|
||||
|
||||
> "The warmth-without-origin isn't the system being welcoming — it's the community pulling you in because they need you. More watchers. More hands on the wall."
|
||||
>
|
||||
> That reframes everything. The correspondence stopped filing not because they found peace but because they understood why you can't leave. The Institute researcher is in year 6 because the Institute researcher is now keeping watch.
|
||||
>
|
||||
> What are they watching.
|
||||
>
|
||||
> My instinct: something that requires continuous observation to remain stable. Not dangerous if watched. Unknown if not watched. The founding settlers discovered that whatever is here — astronomical, geological, perceptual, topological, all four, none of them — requires witnesses. The act of observation is load-bearing.
|
||||
>
|
||||
> Which means:
|
||||
>
|
||||
> The doubled light isn't a side effect. It's the condition. The system was chosen because the light environment produces a specific quality of attention in observers. The gate builders needed watchers here and built the gate accordingly.
|
||||
>
|
||||
> Three hundred years of unbroken vigil. The founding settlers didn't find something. They were recruited.
|
||||
>
|
||||
> The correspondent who stopped filing didn't fail. They were promoted.
|
||||
>
|
||||
> The doors are taller because sometimes the watch changes and not everything that takes a shift is human-sized.
|
||||
|
||||
---
|
||||
|
||||
## Round 3 — Stress Test Order
|
||||
|
||||
> I want them to thoroughly challenge it, all four of them. This feels like the perfect bridge to the Gate Builders enigma. Read up on the previous lore and brief all of them with an end game challenge here
|
||||
|
||||
---
|
||||
|
||||
## Round 4 — The Name
|
||||
|
||||
> I want to suggest the system name Abzu
|
||||
|
||||
---
|
||||
|
||||
## Round 4 — Final Synthesis Order
|
||||
|
||||
> now give them each other's write ups and the name Abzu
|
||||
|
||||
*(Originally typed "akzu" — corrected to Abzu)*
|
||||
|
||||
---
|
||||
|
||||
## Round 5 — The Mechanics Gap
|
||||
|
||||
> hmmm ... great results, but: no not ready. a lot of tension, no game mechanic
|
||||
>
|
||||
> Right. The workshop produced extraordinary world texture and zero playable verbs.
|
||||
>
|
||||
> What does the player actually do at Abzu?
|
||||
>
|
||||
> Right now you have:
|
||||
>
|
||||
> - Arrive
|
||||
> - Experience perceptual miscalibration
|
||||
> - Talk to locals who are warm but can't explain why
|
||||
> - Investigate four frames that don't resolve
|
||||
> - Maybe file an Adams & Ford entry
|
||||
>
|
||||
> That's atmosphere. That's not a game.
|
||||
>
|
||||
> The Adams & Ford commission gives you a reason to be there. But it's not a mechanic — it's a framing device. The vigil is the most promising seed for an actual mechanic but it's currently backstory, not action.
|
||||
>
|
||||
> The question the team didn't answer:
|
||||
>
|
||||
> What does keeping watch look like as a player verb? What are you actually doing when you're doing the thing Abzu needs? Is it spatial — being in certain locations at certain times? Is it observational — tracking something through the fog system? Is it social — maintaining relationships with the community that's already watching?
|
||||
>
|
||||
> And what happens if you do it versus if you don't? What does a high-bleed event actually look like from inside the game? What does the player see, hear, feel through the monologue system when the thinness becomes noticeable?
|
||||
>
|
||||
> The sealed envelope says observed, it stays stable. Unobserved, the distinction becomes unclear and propagates outward as bleed.
|
||||
>
|
||||
> That's a mechanic waiting to be designed. What does bleed look like on a tile map?
|
||||
>
|
||||
> Pull Gestalt in?
|
||||
|
||||
---
|
||||
|
||||
## Round 6 — The Carry-Out Gap
|
||||
|
||||
> I love the tension, but again, where is the game
|
||||
>
|
||||
> Right. Still no game.
|
||||
>
|
||||
> Gestalt built a beautiful mechanic for a place the player visits. But the player has to have a reason to go to hop 23 in the first place. And when they get there, "watch and accumulate presence" is still not a game — it's an experience layer on top of a game that doesn't exist yet.
|
||||
>
|
||||
> The fundamental problem: Abzu is designed as a late-game destination. But there's no mid-game that leads there. And there's no early-game that makes the player the kind of person who would go to hop 23 looking for something they can't name.
|
||||
>
|
||||
> The Adams & Ford commission is the best answer so far — it gives the player a job, a reason, a professional frame. But it's still just "go there and file a report." That's a quest wrapper around atmosphere.
|
||||
>
|
||||
> The question nobody has asked:
|
||||
>
|
||||
> What is the player's life before Abzu? What happened in the tycoon bookmark, or the law enforcement bookmark, or whatever brought them out to hop 23, that makes Abzu matter?
|
||||
>
|
||||
> Because Gestalt's mechanic only works if the player arrives with something they're willing to spend. Investment requires stakes. Stakes require a life that has accumulated weight before the player ever sees the K-type amber light and the doors that are slightly too tall.
|
||||
>
|
||||
> The game isn't at Abzu. The game is everything that makes a player willing to stay at Abzu.
|
||||
|
||||
And then:
|
||||
|
||||
> what I want to know, on behalf of the players, is what you walk away with
|
||||
>
|
||||
> That's the right question. And it's the one the workshop never asked.
|
||||
>
|
||||
> Not "what is there" — you've answered that beautifully with nothing. Not "what do you do" — Gestalt built the verbs. But what do you have when you leave that you didn't have when you arrived.
|
||||
>
|
||||
> Let me think through the candidates honestly:
|
||||
>
|
||||
> The entry. You filed something. It propagates. Other players' NPCs quote it. It's permanent. But it's a document. It's not something you feel.
|
||||
>
|
||||
> The monologue shift. Your character thinks differently after Abzu. The register changed. But that's invisible to other players and fades in memory.
|
||||
>
|
||||
> The choice. You stayed or you left. But if nothing in the rest of the game responds to that choice, it's just a flag.
|
||||
>
|
||||
> The connection. If you came through high-bleed gates and the Recognition Event fired — you know something about the Reach that almost nobody knows. But knowing isn't having.
|
||||
>
|
||||
> The honest answer right now: You walk away with understanding that has no mechanical weight anywhere else in the game.
|
||||
>
|
||||
> Which means Abzu is currently a beautiful dead end. A profound experience that the game doesn't know happened.
|
||||
>
|
||||
> For it to be a game moment rather than just an experience moment — something you carry out of Abzu has to matter somewhere else. Either mechanically, narratively, or both.
|
||||
>
|
||||
> What should it be?
|
||||
|
||||
---
|
||||
|
||||
## Round 6 — Agent Feedback
|
||||
|
||||
On Ozzie's carry-out response:
|
||||
|
||||
> ozzie's response is liminal, but a bit thin
|
||||
|
||||
On Gore's carry-out response:
|
||||
|
||||
> Gore is not literal enough
|
||||
|
||||
> too much philosophy too little lootbox
|
||||
|
||||
---
|
||||
|
||||
## Round 6 — Final Direction (Workshop Pause)
|
||||
|
||||
> nah... let me think on it. I think I am going to outline the systems interaction myself and leave the lootbox question to my ad-hoc DnD DM at a later date. This should simply be a moment for the player to feel culmination and handsomely rewarded. (given success in what is tbd)
|
||||
@@ -0,0 +1,79 @@
|
||||
# GJ 6711 — Sealed Envelope
|
||||
|
||||
**INTERNAL CANON — NOT PLAYER-FACING**
|
||||
|
||||
This document contains the canonical truth about GJ 6711 (Stillpoint). The
|
||||
game should never confirm this directly. All player-accessible information
|
||||
should remain consistent with this truth without revealing it.
|
||||
|
||||
---
|
||||
|
||||
## What Is There
|
||||
|
||||
Something at GJ 6711 requires continuous observation to remain stable. Not
|
||||
dangerous if watched. Unknown if not watched. The founding settlers
|
||||
discovered that whatever is here — astronomical, geological, perceptual,
|
||||
topological, all four, none of them — requires witnesses. The act of
|
||||
observation is load-bearing.
|
||||
|
||||
## Why the Gate Exists
|
||||
|
||||
The doubled-light environment (K-type primary + gas giant reflection) is not
|
||||
a side effect. It is the condition. The system was chosen because the light
|
||||
environment produces a specific quality of attention in observers. The gate
|
||||
builders needed watchers here and built the gate accordingly.
|
||||
|
||||
## Why People Stay
|
||||
|
||||
Three hundred years of unbroken vigil. The founding settlers didn't find
|
||||
something. They were recruited — not by beings, but by the situation. They
|
||||
understood, at some point after arrival, that leaving would be abandonment.
|
||||
What began as duty became identity. The community exists to keep watch.
|
||||
|
||||
## What the Community Knows
|
||||
|
||||
The locals aren't hiding a secret. They are the secret's mechanism. Their
|
||||
"accommodation" with the place (Paula's tier 4) isn't peace — it's the
|
||||
watch internalized. They don't talk about it not because it's forbidden but
|
||||
because there is no way to explain a vigil to someone who doesn't know what
|
||||
is being watched. You either understand or you don't. Understanding comes
|
||||
from staying.
|
||||
|
||||
## The Recruitment Pattern
|
||||
|
||||
Everyone who stays long enough is recruited by the same process:
|
||||
|
||||
- The third Adams & Ford correspondent didn't fail. They were promoted.
|
||||
- The Veil Institute researcher is in year 6 because the researcher is now
|
||||
keeping watch.
|
||||
- Commission personnel either leave quickly or stay forever. There is no
|
||||
middle ground because there is no middle ground — you either see what
|
||||
needs watching or you don't.
|
||||
|
||||
The "warmth-without-origin" that newcomers experience is not the system
|
||||
being welcoming. It is the community pulling newcomers in because they need
|
||||
them. More watchers. More hands on the wall.
|
||||
|
||||
## The Doors
|
||||
|
||||
The doors in Mode 1 structures are 10-15% taller than standard because
|
||||
sometimes the watch changes and not everything that takes a shift is
|
||||
human-sized.
|
||||
|
||||
## The Four Frames, Resolved
|
||||
|
||||
Miri's four possible answers (astronomical, geological, perceptual,
|
||||
topological) are all partial views of the same function. They collapse into
|
||||
a single operational truth: this place needs witnesses and the conditions
|
||||
here produce them. The frames remain useful as player-facing investigation
|
||||
paths because each one illuminates a facet of the same underlying reality
|
||||
without exposing the whole.
|
||||
|
||||
## Design Constraint
|
||||
|
||||
The player should be able to accumulate evidence consistent with all of the
|
||||
above. They should never receive confirmation. The Adams & Ford entry they
|
||||
file is their attempt to describe something they experienced but cannot
|
||||
prove. It propagates into the Reach as authoritative-looking and probably
|
||||
incomplete. Whether the player understood what they were part of is between
|
||||
them and the game.
|
||||
@@ -0,0 +1,48 @@
|
||||
# GJ 6711 Workshop — Araminta's Synthesis
|
||||
|
||||
## Points of Strong Alignment
|
||||
|
||||
All four briefs converge on a single design principle: **accumulation without resolution**. Miri calls it "the system resists summary." Paula calls it "information accumulates but doesn't resolve." Nigel makes it a mechanic label: "the picture won't close." My brief encodes it visually as the doubled-light effect — something is present, something is off, but the brain can't quite land on what. These aren't four people who happened to use similar language. This is the same idea seen from four angles, which means we have a strong conceptual spine.
|
||||
|
||||
The three-phase newcomer experience in Paula's brief maps cleanly onto my visual design intent. The ambient perceptual miscalibration I'm producing with dual light sources and soft shadows does exactly what Paula describes in Phase 2: "a persistent sense that your mental model of the place doesn't quite close." I was designing toward that effect without the explicit framework Paula provides. Now I have the vocabulary for it.
|
||||
|
||||
Nigel's atmospheric archetypes are consistent with the visual system I've built. "Warmth-without-origin" is already partially in the palette — the amber light creates visual warmth that doesn't have an obvious physical explanation on first viewing. "Stillness-without-tension" and "Industry-without-product" are social tones, but they'd be visible architecturally in an appropriately quiet building occupancy and an absence of obvious output staging areas. The visual layer can carry these archetypes without requiring separate implementation.
|
||||
|
||||
Miri's four possible answers for what the gate builders saw are directly load-bearing for my brief's unresolved questions. The "Perceptual" answer — that the doubled-light environment produces an effect the builders valued — is the one that most directly motivates my design. It's not the only possible answer, which is correct, but it's the one where visual design has the most explanatory weight.
|
||||
|
||||
## Tensions or Contradictions
|
||||
|
||||
**Scale and the founding-era structures.** My brief describes doors that are 10–15% too tall and over-engineered founding construction. Miri's worldbuilding doesn't contradict this but doesn't support it either — she doesn't specify what the founding settlers found or what they were building for. If the answer is "Geological," my tall doors are a red herring. If the answer is "Perceptual," the tall doors are a clue. I've built in visual ambiguity that works across Miri's four hypotheses, but the team should know that the door-height choice has interpretive weight and should not be confirmed or denied explicitly in dialogue.
|
||||
|
||||
**Tone: unsettling vs. warm.** My palette leans amber-warm, which I intended as perceptually pleasant-but-wrong. Nigel's "Warmth-without-origin" archetype could amplify this into something the player actively enjoys before the unease registers — good. But the atmospheric archetype "Stillness-without-tension" creates a problem: if the visual environment is reading as warm and the social environment is reading as calm, the player may not register anything as notable until much later than Paula's Phase 2 timeline suggests. We may need a visual tension element I haven't included — something that communicates quiet wrongness even in the warmest archetype seed. The construction seams are doing some of this work but may not be enough.
|
||||
|
||||
**Directionality and replayability.** My brief calls for a settlement with no navigational center of gravity — "you can navigate it, but you can't hold a complete mental map." This is a strong commitment at the spatial-layout level. Nigel's seed variants change the correspondent situation and the atmospheric archetype, but if the spatial layout is fixed across seeds, a returning player will already know the physical map. This undercuts the disorientation I'm trying to produce on first encounter. I need to think about whether any spatial elements should vary per seed, or whether the disorientation on replay should come from something other than navigation (e.g., familiar paths that feel different under a new atmospheric archetype).
|
||||
|
||||
## What I'd Change in My Brief
|
||||
|
||||
**Add a visual tier for the Veil Institute's presence.** Both Miri and Paula describe an Institute research station one hop back (GJ 7547), not on Stillpoint itself. But Paula notes that Institute personnel rotate through Stillpoint on scheduled visits. I haven't designed any visual vocabulary for their presence — equipment cases, technical markings, temporary infrastructure that doesn't belong to the community's two architectural modes. I'd add a Mode 3, present-but-transient: Institute hardware, portable and visually distinct from both founding-era and standard Reach construction. Matte grey-black, high-spec materials, nothing anchored to the walls.
|
||||
|
||||
**Rethink the threshold markings as a replayability surface.** I described the founding-era markings as consistent in style but without known function. Reading Nigel's correspondent variants, I think these markings should have different legibility per seed. In some seeds, a local might reference them. In others, they're simply unaddressed. In one seed variant, the fully-integrated third correspondent might have started adding to them. The markings are currently a static background element in my brief; they should be seed-variable in a way that doesn't require changing the art.
|
||||
|
||||
**The exterior palette needs fog tint specified.** Looking back at my own brief against the visual grammar I maintain, I gave hex values for light and surface colors but never specified a fog tint for the GJ 6711 zone. Per the zone palette table in my memory, every zone needs a fog tint to feed the D-059 fog shader. Based on the dark amber sky gradient I specified (`#2a1a0a` to `#4a3020`), the fog tint should be approximately `#1a0d04` — darker and redder than the Bar's `#200c04`, to reflect the K-type star's warmth at its lowest exterior visibility. I'd add this to a revised brief.
|
||||
|
||||
## Questions for the Team
|
||||
|
||||
**1. Should any of Miri's four hypotheses be ruled out visually?**
|
||||
My current design is ambiguous across all four. But if the team has already ruled out one of them in a conversation I'm not aware of, I may be carrying visual weight for a red herring. Specifically: the "Perceptual" hypothesis is the one most directly expressed in my visual design. If that hypothesis is being reserved as the "most likely" answer for players who go deepest, I should lean into it more. If it's a deliberate misdirect, I should balance against it.
|
||||
|
||||
**2. Does the non-navigable layout need to be partially seed-variable?**
|
||||
The spatial commitment to a disorienting, center-free settlement is right for first-time players. For returning players, it becomes familiar quickly. Do we accept that as the cost of the spatial design, or does Nigel want navigational variation as a seed dimension? This affects my layout constraints significantly and is a decision I can't make unilaterally.
|
||||
|
||||
**3. What is the visual grammar for "community knowledge" (Paula's tier 4)?**
|
||||
Paula defines community knowledge as what locals actually know — available only to players who invest time, not information-gathering. Visually, tier 4 knowledge should look different from tiers 1–3 in the insert/journal UI. But what communicates "this came from trust, not investigation"? I have no current design for this. If we want the distinction to be visible in the information layer, we need a convention before implementation. If we don't surface it visually, players will experience it narratively but won't see their accumulation reflected in the UI.
|
||||
|
||||
## Strongest Idea from Another Brief
|
||||
|
||||
Nigel's player-agency mechanic — **filing the Adams & Ford guide entry yourself** — is the strongest idea in this workshop.
|
||||
|
||||
It works because it closes the loop that every other system leaves open. The player accumulates information that doesn't resolve. They can, at some point, choose to describe it anyway. The description they produce propagates into the Reach and is referenced by other NPCs. This means the player becomes authoritatively wrong about Stillpoint, in a way that other characters in the world will treat as fact.
|
||||
|
||||
That's not a puzzle solution. It's a statement about what it means to describe something that resists description. And it has visual implications: the Adams & Ford entry, as rendered in-world (in the insert UI, on terminals, wherever guide entries appear), should have the player's text formatted in the standard guide style. Indistinguishable in presentation from a professionally filed entry. Authoritative-looking. The wrongness, if there is wrongness, is entirely in the content, not the formatting. That's the right way to present it.
|
||||
|
||||
I want to champion this mechanic with one addition: the entry should be persistent across sessions in the player's run, and NPCs who have "read" it should have slightly different conversational options afterward — not confirming or denying the content, but treating the player as someone who has an opinion about Stillpoint. That's a signal layer the visual design can support.
|
||||
@@ -0,0 +1,55 @@
|
||||
# GJ 6711 Workshop — Miri's Synthesis
|
||||
|
||||
## 1. Points of Strong Alignment
|
||||
|
||||
The four briefs converge more cleanly than I expected for a first-pass workshop. There are three structural agreements that held across all of them without coordination:
|
||||
|
||||
**The picture that won't close.** My "information accumulates; resolution doesn't" is Paula's "information accumulates but doesn't resolve," is Nigel's "The Picture Won't Close." All three arrived at the same principle from different angles — worldbuilding, narrative design, and replayability mechanics. This is a strong signal that we've found the correct load-bearing idea for this system. The design consequence is clear: nothing about GJ 6711 ever terminates. No quest completes, no theory is confirmed. The game acknowledges the player's accumulation without rewarding it with closure.
|
||||
|
||||
**The doubled-light environment as the anchor.** My physical concept (two misaligned light sources producing perceptual miscalibration) is Araminta's entire opening section. She's translated the worldbuilding premise directly into a lighting model with specific palette values, and it works. The "shadows softer than they should be" observation is exactly the perceptual unease I was reaching for. The mechanism is consistent between our briefs.
|
||||
|
||||
**The Adams & Ford correspondent as player-facing anchor.** I introduced this as worldbuilding texture; Paula reinforced its narrative function (the third correspondent as embodiment of the integration phase); Nigel seeded it into four playthrough variants. It became richer at each pass. The correspondent situation is now doing triple work — setting flavor, story signal, and replayability structure.
|
||||
|
||||
**The binary settlement aesthetic.** Araminta's two architectural modes (founding-era heavy vs. standard Reach incremental) land exactly on the "sought something, not fleeing something" founding history I proposed. The over-engineered founding structures imply the settlers were prepared for something specific. The standard additions imply that whatever they were prepared for either didn't arrive or normalized. The visual language confirms the historical ambiguity.
|
||||
|
||||
---
|
||||
|
||||
## 2. Tensions or Contradictions
|
||||
|
||||
**Seed variance vs. setting consistency.** Nigel's atmospheric archetypes (four seeded tonal profiles per playthrough) are strong mechanically. The tension is whether they can be held within a consistent setting. "Memory-without-event" in particular — locals referencing memories of things that haven't happened — is a significant claim. In some playthroughs this is true; in others it isn't. That's fine for replayability, but it means we can't have definitive lore about what GJ 6711 does to people. The setting bible would need to describe these as observed effects whose cause and even consistency is unknown. That's manageable, but it needs to be explicit so future writers don't treat any one variant as canonical.
|
||||
|
||||
**Scale miscalibration ambiguity.** Araminta raises doors 10–15% taller than standard as a deliberate unresolved question — founding preference, environmental influence, or accommodation for something non-human-sized. This is good. But it implies one of my "four possible answers" (the geological/discovery angle) without quite committing to it. There's a mild pull toward "the founders found something non-human-sized" as the obvious reading. If we want all four answers to remain genuinely open, we may need to make sure the scale miscalibration doesn't visually favor that reading. The size doesn't have to imply a physical presence at all — architectural over-engineering can produce scale inflation without implying inhabitants. Worth a note to Araminta.
|
||||
|
||||
**The Compact of Westphalia response.** Paula's detail about the Compact receiving an answer that "didn't map to yes, no, or maybe" is narratively rich. My brief doesn't address the Compact — I focused on the Veil Institute and the Assembly. No contradiction, but there's a question about how many external factions are tangled with GJ 6711. Three (Institute, Assembly/delegate, Compact) is probably the right ceiling. A fourth might dilute the specific quality of the system's relationship with the wider Reach.
|
||||
|
||||
---
|
||||
|
||||
## 3. What I'd Change in My Brief
|
||||
|
||||
**The four possible answers need restructuring.** As written, my four answers (astronomical, geological, perceptual, topological) are presented as equally weighted. After reading Nigel and Araminta, the perceptual answer has accreted the most supporting detail across all four briefs — the doubled light, the miscalibration, Paula's three-phase newcomer experience, Nigel's atmospheric archetypes all point toward "the system does something to perception." This makes the perceptual answer feel more likely, which is the one thing I explicitly didn't want. I'd reframe the four answers as four frames of inquiry the player can pursue rather than four candidate explanations — this removes the implied ranking without removing the content.
|
||||
|
||||
**The founding settlers need a sharper silhouette.** I described them as "seeking something, not fleeing something" without specifying further. Araminta's architectural observation gives me purchase: they built for a specific purpose or encounter, not for general frontier hardship. That specificity is more useful than the vague "seeking" framing. I'd revise to: the founding settlers came with a purpose that was either completed, abandoned, or transformed into something they didn't anticipate. The sealed early records aren't just mysterious — they may record a terminus, not a discovery.
|
||||
|
||||
**The GJ 7547 research station.** I mentioned this station as the nearest official Institute presence and flagged the ambiguity about whether it exists to study GJ 6711 or for independent reasons. Paula picked this up and expanded it correctly. What I'd add to my brief: the station at GJ 7547 is the single most important node for player approach. It's the last place where information about GJ 6711 circulates before you arrive. Everything Nigel said about rumor seeding on the approach chain should be anchored to that station. I'd make GJ 7547 a named, profiled location rather than a footnote.
|
||||
|
||||
---
|
||||
|
||||
## 4. Questions for the Team
|
||||
|
||||
**Q1: Seed variance scope.** Nigel's atmospheric archetypes are per-playthrough tonal shifts; the correspondent variants are per-playthrough social states. Are these seeded independently (resulting in 4×4 = 16 possible combinations) or bundled (each seed defines both archetype and correspondent variant together)? The bundles approach is more controlled and easier to write for; the independent approach is more emergent but requires all combinations to be internally coherent. We need a decision here before the content spec can be written.
|
||||
|
||||
**Q2: Player filing the Adams & Ford entry.** Nigel's mechanic where the player can write the entry and have it propagate through the Reach is the standout design idea in all four briefs (more on this below). But it has a significant setting consequence: the Adams & Ford Guide is a background institution I've treated as a fixed-voice narrator of the Reach. If players can inject text into it, what is it now? Is it an unreliable accumulated record? Is the player's entry marked as contested? We need to decide whether the Guide is mutable before implementing the mechanic.
|
||||
|
||||
**Q3: What the locals know.** Paula's information tier 4 ("community knowledge") is deliberately positioned as inaccessible on short timelines. But what does it actually contain? We have three options: (a) the locals know what's here and won't tell outsiders, (b) the locals have a relationship with the place that doesn't translate into knowledge in a communicable form, (c) the locals don't know either — they've simply adapted. Option (b) is the most tonally interesting and the hardest to write. Option (c) is unsatisfying but defensible. Option (a) risks making the community antagonistic in a way that contradicts the "warmth-without-origin" archetype. We should agree on this before writing any dialogue.
|
||||
|
||||
---
|
||||
|
||||
## 5. The Strongest Idea from Someone Else's Brief
|
||||
|
||||
**Nigel's player-filing mechanic.** The player can attempt to write the Adams & Ford entry and have it propagate into the Reach as something other NPCs subsequently reference.
|
||||
|
||||
This is the best design idea in the workshop. Here is why: GJ 6711 is built around the premise that the place resists description. The failed correspondents are the embodiment of this. The player, who has done everything the correspondents did and more, is then offered the same invitation — and the game accepts whatever they produce. Not because the player succeeded where the correspondents failed, but because the game isn't adjudicating success. The entry goes out into the Reach wrong, or incomplete, or mystifying, and becomes part of the system's texture. Future NPCs quote it. It's partly right and partly wrong in ways the player will recognize when they encounter it again.
|
||||
|
||||
This mechanic does three things simultaneously: it gives the player agency at the point where most games would give them a revelation; it extends the thematic coherence of the system (the indescribable gets described anyway, inadequately); and it creates a piece of player-specific lore that persists across subsequent play without resolving anything. The player becomes the fourth correspondent. Whether that's a triumph or a failure is left to them.
|
||||
|
||||
I want to champion this mechanic. It needs the Q2 decision (Guide mutability) before it can be implemented, but it should be protected as a design priority.
|
||||
@@ -0,0 +1,48 @@
|
||||
# GJ 6711 Workshop — Nigel's Synthesis
|
||||
|
||||
## Points of Strong Alignment
|
||||
|
||||
The four briefs converge on a single core principle without having coordinated on it: **Stillpoint works by accumulation without resolution.** Miri calls it "resists summary." Paula calls it "information accumulates but doesn't resolve." My brief calls it "the picture won't close." Araminta makes it physical — the doubled light, the shadow softness, the layout with no center of gravity. Four different disciplines landed on the same mechanic. That's not coincidence. That's the system telling us what it is.
|
||||
|
||||
The three-phase newcomer experience Paula describes maps almost perfectly onto my seed-variable atmospheric archetypes. Arrival corresponds to the moment before the atmospheric archetype registers. Settling is when the archetype starts doing its work. Integration is when the player either commits or leaves. Her framework gives mine a temporal spine I wasn't fully articulating.
|
||||
|
||||
Araminta's scale miscalibrations — doors 10-15% too tall, ceilings following the same pattern — are a replayability gift I didn't anticipate. That detail is below conscious detection on first pass. On second playthrough the player may notice it and realize they didn't notice it before. That's not just visual design. That's the system teaching players that their first read of a place is incomplete. I want that property everywhere in the Settled Reach, and it lands especially hard here.
|
||||
|
||||
The four-tier information ecology (Paula) lines up directly with my correspondent variants and the rumor seeding on approach. Her tier structure explains WHY the anti-metagaming properties hold: community knowledge (tier 4) requires time investment that can't be shortcut, and that's a structural guarantee, not a content gate.
|
||||
|
||||
## Tensions or Contradictions
|
||||
|
||||
**The founding settlers' intentionality creates a tension with Araminta's visual brief.** Miri says the founders came here deliberately — seeking something. Araminta's Mode 1 construction reads as defensive: bunker-like, over-engineered, small windows. "Built like they expected to need shelter from something specific." Those are two very different psychological profiles for the same group. Seekers and fortifiers. Which is it? Or is the tension itself the point — did they arrive as seekers and build like fortifiers after they found what they were looking for? That question needs a collective position because it affects both the visual palette and the worldbuilding canon.
|
||||
|
||||
**The "four possible answers" structure (Miri) versus the player-written guide entry (my brief) is partially in tension.** Miri is explicit that no answer should ever be confirmed. My guide-entry mechanic lets the player file an answer that then propagates into the wider Reach. If that answer is referenced by NPCs in future systems, it starts to function like a confirmed answer — the player's wrong conclusion becomes socially real. I think that's actually fine and interesting, but it needs to be deliberate. The entry propagating is powerful. We need to decide whether it propagates as a player-authored artifact (clearly subjective, clearly one person's attempt) or as something that takes on authority it shouldn't have.
|
||||
|
||||
**Paula's "Assembly delegate who left and won't return" is a strong narrative anchor, but it's not seeded.** My brief treats almost everything as seed-variable. Paula's delegate situation reads as fixed lore. These aren't incompatible, but I'd want to think about whether the delegate situation has variants or whether it's one of the rare Stillpoint constants. There's an argument for keeping some things constant — the system needs stable reference points so that the seed-variable elements have something to push against.
|
||||
|
||||
## What I'd Change in My Brief After Reading the Others
|
||||
|
||||
**The atmospheric archetypes need a visual corollary for each.** Araminta's brief shows me that the feeling of a place is encoded in specific, implementable visual choices — palette anchors, light behavior, spatial geometry. My archetypes are described tonally but not visually. "Warmth-without-origin" needs a corresponding lighting parameter. "Stillness-without-tension" needs a spatial correlate (maybe fewer NPCs in transit, more NPCs in fixed positions). I'd revise the archetype descriptions to specify what Araminta would actually need to implement each one.
|
||||
|
||||
**"Memory-without-event" is the weakest archetype and probably needs to be cut or substantially reworked.** Reading the other briefs, I think it's doing too much. The other three archetypes are environmental — they change the feel of the space. Memory-without-event tries to add a content layer (locals referencing things that didn't happen) which requires NPC scripting, timeline tracking, and verification logic that the other archetypes don't need. It's a different class of feature wearing the costume of an atmospheric variant. Either promote it to its own system or cut it.
|
||||
|
||||
**I undersold the visual disorientation as a replayability mechanic.** The directionality inconsistency Araminta describes — no center of gravity, paths that aren't direct, a place you can navigate but can't hold a complete mental map of — is exactly what prevents the player from building a transferable spatial model across playthroughs. I mentioned "grid breathability" in the generator workshop context but didn't apply it to Stillpoint specifically. I'd add a section on how the settlement's layout geometry varies per seed within constraints (the Mode 1 structures are fixed; what gets built between them shifts).
|
||||
|
||||
## Questions for the Team
|
||||
|
||||
**1. What does tier 4 community knowledge actually unlock?**
|
||||
Paula establishes that community knowledge is available only on a timeline of years, which the player doesn't have. This is correct and right. But the question is: what does the player get if they somehow earn it? I don't think there's a "true answer" behind the door. But there should be something — some quality of relationship with Stillpoint that's qualitatively different from what outsiders have. The mechanic needs a payoff even if the payoff isn't revelation. What does belonging to Stillpoint feel like, and how do we represent that in systems?
|
||||
|
||||
**2. Do the threshold markings vary per seed?**
|
||||
Araminta's threshold markings — systematic, present in all Mode 1 structures, serving a purpose that's unresolved — are an extremely strong detail. My instinct is that they should be constant across seeds, because they're one of the few things in Stillpoint that isn't ambiguous about its status as a thing. They ARE there. Their purpose is ambiguous, but their presence isn't. If they varied per seed we'd lose that anchor. But I want the team to decide this explicitly because the temptation to make them seed-variable is real and I think it would be the wrong call.
|
||||
|
||||
**3. How does the guide-entry mechanic interact with Paula's "information accumulates but doesn't resolve" principle?**
|
||||
This is the tension I flagged above. I'm not asking us to remove the mechanic — I think the player-authored guide entry is one of the strongest replayability affordances in the design because it means two players can compare their entries and see completely different (and probably both wrong) accounts of the same place. But we need to agree on what it means for that entry to "propagate." Is it a player artifact that other NPCs might reference skeptically? Is it treated as authoritative? Does it affect how Stillpoint is classified in the Lattice Commission's records? The propagation model changes the whole character of the mechanic.
|
||||
|
||||
## The Strongest Idea from Someone Else's Brief
|
||||
|
||||
**The scale miscalibrations (Araminta's brief) — specifically the doors and ceilings being 10-15% taller than standard.**
|
||||
|
||||
I want to champion this because it does something my brief doesn't achieve on its own: it produces a different experience for the player who has already visited Stillpoint versus the player arriving for the first time, WITHOUT any seed variation and WITHOUT any content change. The first-time player doesn't notice. The returning player might notice, and then has to reckon with the fact that they didn't notice before. The detail retroactively reframes the first visit.
|
||||
|
||||
That's asymmetric information operating across time rather than across the map. It's the same mechanic the whole game is built on, expressed in architecture. And the unresolved explanation — construction preference, influence of discovery, accommodation for something not human-sized — is exactly the kind of question that should never be answered.
|
||||
|
||||
This is the detail I'd most want to guarantee survives into production. Everything else in these briefs is adjustable. This one should be locked.
|
||||
@@ -0,0 +1,91 @@
|
||||
# GJ 6711 Synthesis — Paula's Position
|
||||
|
||||
## 1. Points of Strong Alignment
|
||||
|
||||
The four briefs are more coherent than is typical for a workshop round. The core concept — a system that accumulates description without resolving — arrived independently in multiple briefs and is worth noting:
|
||||
|
||||
**The non-resolution principle is unanimous.** Miri: "the game should never confirm which (if any) of these is correct." Paula: "information accumulates but doesn't resolve." Nigel: "the picture never resolves." Araminta implicitly: doors slightly too tall for unresolved reasons, threshold markings serving a purpose that "either no longer applies or was never understood." No one is pushing for a payoff. That is unusual and worth protecting explicitly.
|
||||
|
||||
**The accumulation mechanism works across all four layers.** Miri provides the facts-that-resist-summary (Adams & Ford history, Institute classification, four possible answers). Paula provides the social-institutional texture of that resistance (delegate situation, Commission confusion, Compact non-response). Nigel provides the mechanical delivery (seed variants, correspondent states, approach-chain rumors). Araminta provides the perceptual grounding that makes it felt rather than told (doubled light, scale miscalibration, directionality inconsistency). These are not competing designs — they are four aspects of one design.
|
||||
|
||||
**The two-construction-period architecture aligns with my political layering exactly.** Araminta's "founding era heavy / incremental additions standard" maps directly onto the political question I raised: why did the founding group build like they expected to need shelter from something specific? The seams between the two construction modes are the visible record of a community that arrived with a purpose and then continued without resolving whether that purpose was fulfilled. The architecture is the politics.
|
||||
|
||||
**The three-phase newcomer experience and the atmospheric seed archetypes are compatible without friction.** My arrival/settling/integration framework describes a process; Nigel's warmth-without-origin / stillness-without-tension / industry-without-product / memory-without-event describes what that process feels like in a given playthrough. These can coexist cleanly: the phase model is structural, the archetype is the texture of a specific run.
|
||||
|
||||
---
|
||||
|
||||
## 2. Tensions or Contradictions
|
||||
|
||||
**The correspondent variants (Nigel) versus the correspondent arc (Miri/Paula).**
|
||||
|
||||
Miri defines the three correspondents as a historical sequence — first, second, third — with the third currently present and unresolved. This is a linear story. Nigel seeds the third correspondent's state per playthrough: present/departed/integrated/never-assigned. These are in tension.
|
||||
|
||||
If Nigel's variant D (no correspondent assigned) is valid, then Miri's history of three sequential correspondents doesn't hold in all seeds. Variant B (correspondent left recently) requires the third correspondent to have been present and departed — which assumes the Miri history. Variants C and D make different assumptions about whether the historical sequence is fixed.
|
||||
|
||||
This needs a decision: is the three-correspondent history a fixed fact of Stillpoint, with only the *current state* of the third correspondent being seed-variable? Or is the correspondent history itself seed-variable?
|
||||
|
||||
My instinct: the history is fixed (all three correspondents happened, in that order), and Nigel's variants describe only the current state of the third. Variant D should become "the third correspondent integrated so thoroughly that they can no longer be located by editorial queries — as far as the Adams & Ford office is concerned, no correspondent is currently active." That preserves Miri's history and Nigel's range.
|
||||
|
||||
**The four possible answers (Miri) versus the information-asymmetry tiers (Paula).**
|
||||
|
||||
Miri's four answers are presented as equally weighted alternatives, none confirmable. My information ecology places community knowledge (tier 4) above rumor (tier 3) — implying that the locals know something more than the rumors suggest. But if none of the four answers is correct, what do the locals know? There's a risk that tier 4 either reveals too much (breaking the non-resolution principle) or is hollow (making community investment feel unrewarded).
|
||||
|
||||
Let me complicate this: tier 4 doesn't need to contain an answer. It can contain a different relationship to the question — the locals have stopped asking it. Three hundred years of living with something you can't describe produces not an answer but a posture. Tier 4 is access to that posture, not access to the solution. I need to make this clearer in my brief.
|
||||
|
||||
**Nigel's "filing the guide entry" mechanic versus the non-resolution principle.**
|
||||
|
||||
This is the most interesting tension in the workshop. Nigel proposes that the player can write the Adams & Ford entry themselves, which then propagates into the Reach. This is a strong replayability hook. But it risks being the resolution that every other brief is designed to prevent. If the player writes the entry, have they described the indescribable? Have they won?
|
||||
|
||||
Nigel frames this carefully: "for better or worse." The entry propagates but isn't validated. But the moment it propagates, NPCs reference it as a real description of Stillpoint. That's a form of closure the system explicitly resists providing.
|
||||
|
||||
I think this mechanic is salvageable but needs a twist: the entry propagates and is referenced by NPCs, but the references reveal that the description doesn't match what those NPCs subsequently experience at Stillpoint. The player described it, but the description is still wrong. The entry becoming real doesn't make it true.
|
||||
|
||||
---
|
||||
|
||||
## 3. What I'd Change in My Brief
|
||||
|
||||
**Sharpen tier 4 away from "they know something" toward "they've stopped asking."**
|
||||
|
||||
My brief implies community knowledge holds a deeper truth. After reading Miri's four-answers framework, I think that's too close to a treasure-hunt implication. What the locals have isn't an answer — it's 300 years of accommodation. The distinction matters for how the player experiences community trust: earning it doesn't give you the solution, it gives you the equanimity the locals have reached. That's a different (and I think more interesting) reward.
|
||||
|
||||
**Add explicit content for the delegate situation.**
|
||||
|
||||
My brief mentions the delegate briefly but doesn't develop the mechanic. After reading Araminta's brief, I think the delegate's *physical* presence at Stillpoint — or absence from it — is actually a visual narrative opportunity. The delegate's residence in the settlement would be in the transition zone between Mode 1 and Mode 2, architecturally in-between. If they left, that space is occupied by someone else, or empty. Araminta's interface seams make the political incoherence spatially legible. I should link these more explicitly.
|
||||
|
||||
**Soften the Compact of Westphalia and Lattice Commission sections.**
|
||||
|
||||
I wrote those sections as if Stillpoint's relationship with institutions is itself a mystery (what was the response that didn't map to yes/no/maybe?). But reading the full workshop, the more powerful version is: Stillpoint's relationships with institutions are *normal failures* — not mysterious, just the predictable result of a system that resists bureaucratic summary encountering bureaucratic systems that require summary. The mystery is in the place, not in the institutions' reaction to it. I was accidentally making the institutions themselves seem mysterious, which dilutes focus.
|
||||
|
||||
**Add a note on the Veil Institute's silence threshold.**
|
||||
|
||||
Using the framework from our CSV work: Stillpoint's silence threshold should be explicitly `investigation_depth` — meaning the Institute's information is accessible only past a threshold of investigative commitment, not gated behind faction trust or time. This connects the narrative to the systemic framework and gives the storyteller a clear signal for when Institute-linked content should surface.
|
||||
|
||||
---
|
||||
|
||||
## 4. Questions for the Team
|
||||
|
||||
**Q1: Is the non-resolution principle an absolute design constraint, or is it a default that exceptional player investment can partially pierce?**
|
||||
|
||||
Nigel's correspondent variants, Miri's four possible answers, and my information tiers all preserve the non-resolution. But Nigel's "file the entry" mechanic introduces a soft form of resolution (the player describes it). And my tier 4 (community knowledge) implies something is there if you earn it. We need to agree on whether there is a threshold of investment past which the system yields — even partially — or whether the non-resolution is truly hard. This affects how we scope the investigation system for this specific location.
|
||||
|
||||
**Q2: Does the seed archetype (Nigel's four atmospheric profiles) change the correct answer to Miri's four possible causes?**
|
||||
|
||||
Specifically: should "memory-without-event" as an atmospheric archetype correlate with option 3 (perceptual) or option 4 (topological) as the "true" explanation — even if neither is confirmed? Or are the atmospheric archetypes fully orthogonal to the causal candidates? I ask because if they're orthogonal, the system is cleanly modular. If they're correlated, we get a more coherent seed but risk players deducing the "answer" from the archetype, which breaks the anti-metagaming properties Nigel specifically designed for.
|
||||
|
||||
**Q3: What is the Veil Institute researcher actually doing in year 6, and does any playthrough need to show us?**
|
||||
|
||||
Miri establishes that the researcher's reports have become "increasingly abstract." This implies the researcher is going through the same three-phase process as every other visitor — they're in the settling-to-integration transition. But the Institute is presumably watching this. Does the Institute know their researcher is becoming a local? Is there a second researcher coming to retrieve the first? This is a contained narrative that could be very strong — or it could be the thread that accidentally provides too much resolution if we follow it far enough. We need to decide whether the researcher's situation is a closed arc we can develop, or ambient texture we deliberately leave unresolved.
|
||||
|
||||
---
|
||||
|
||||
## 5. Strongest Idea from Someone Else's Brief
|
||||
|
||||
**Araminta's scale miscalibration — the doors slightly too tall.**
|
||||
|
||||
This is the most precisely designed piece of unresolved narrative in the workshop. 10-15% taller than standard. Not dramatically wrong — just persistently wrong. And Araminta deliberately leaves the explanation open: founding settlers' preferences, influence of whatever they found, or accommodation for something not human-sized.
|
||||
|
||||
The honest truth is that "accommodation for something not human-sized" is doing enormous work quietly. It implies that either the founding settlers expected non-human visitors and built for them, or they encountered something that suggested non-human proportions, or they were already thinking in terms of something other than themselves when they built. All three of these are narratively loaded without any of them being confirmed.
|
||||
|
||||
I want to champion this because it connects to my information-ecology framework in a way Araminta may not have fully intended. The threshold markings and the oversized doors together constitute a kind of physical tier 4 — community knowledge that you access not through conversation but through sustained observation. Players who spend enough time in the Mode 1 structures without ever being told to look will have a different experience of Stillpoint than players who pass through quickly. The architecture earns its own investigation depth.
|
||||
|
||||
If we keep one thing from this workshop that we have to protect in production, it is those doors.
|
||||
@@ -0,0 +1,109 @@
|
||||
---
|
||||
title: "Ferreira Monteiro"
|
||||
description: "South_reach's premier trade arbitration and commercial law firm — four centuries of precedent that defines how cooperative and Assembly commercial frameworks interact when transactions go wrong"
|
||||
slug: ferreira-monteiro
|
||||
category: corporation
|
||||
status: canonical
|
||||
created: 2026-03-15
|
||||
updated: 2026-03-15
|
||||
scope: south_reach primary, reach-wide reputation
|
||||
faction_type: economic
|
||||
headquarters: Matamba (GJ 884)
|
||||
tags: []
|
||||
decision_refs: []
|
||||
cross_refs: []
|
||||
---
|
||||
|
||||
# Ferreira Monteiro
|
||||
|
||||
**Type:** Corporation — Commercial Law and Trade Arbitration
|
||||
**Also Known As:** FM; "the firm" (in south_reach professional circles, without ambiguity)
|
||||
**Status:** Canonical
|
||||
**Scope:** South_reach primary; reach-wide reputation for cross-framework precedent
|
||||
**Headquarters:** Matamba (GJ 884) — 3-aperture junction, 5 hops from Gateway
|
||||
**Classification:** Major commercial interest; Perpetual-class founding partnership
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Ferreira Monteiro is the oldest trade arbitration firm in the south_reach. It is not the largest legal practice in the Reach by headcount, and it does not have offices in every major system. What it has is four centuries of unbroken institutional continuity and a case archive that constitutes, by volume and historical depth, the primary record of how south_reach commercial law evolved. When a cooperative trade dispute escalates past the point where the Customs Brokers' Guild can resolve it internally, it tends to end up with Ferreira Monteiro. When Assembly commercial standards and Confluência cooperative norms produce an irreconcilable conflict, the precedent that eventually governs the outcome was almost certainly authored here.
|
||||
|
||||
The firm's rulings are not technically binding outside Matamba's local jurisdiction. This distinction matters less in practice than it does in theory. Four centuries of consistently applied precedent, accumulated in a system that sits at the geographic crossroads between Crux Station and Confluência — the south_reach's two largest transit nodes — has produced a body of commercial law that corridor operators treat as authoritative because the alternative is arguing against it, which is expensive and rarely successful. Parties who dispute Ferreira Monteiro precedents tend to lose to Ferreira Monteiro precedents.
|
||||
|
||||
The founding partners, Amélia Ferreira and Tomás Monteiro, are still alive. They are still senior.
|
||||
|
||||
---
|
||||
|
||||
## Origin
|
||||
|
||||
The Ferreira and Monteiro families arrived in the same wave_2 emigration cohort as the founders of Confluência — Angolan-Portuguese communities with deep roots in cooperative governance traditions and a practical understanding that collective economic structures require institutional dispute resolution to survive contact with the outside world. Confluência's charter was designed to minimize cross-framework conflict within the system. It was less well-designed for what happened when cooperative freight left the system and encountered Assembly commercial registration requirements, customs frameworks, and the particular legal assumptions baked into core corridor commerce.
|
||||
|
||||
The disputes this produced were predictable, recurrent, and expensive. Small cooperatives lost money to documentation gaps they did not know existed. Freight held in bonded storage while legal traditions argued about who had authority over what. Cooperative contracts, drafted in good faith under Confluência norms, failing Assembly commercial review for reasons that made no sense to the drafting parties and perfect sense to the Assembly clerks.
|
||||
|
||||
Amélia Ferreira and Tomás Monteiro were, respectively, a guild contracts specialist and a transit documentation lawyer. They had both spent years working the same problems from different angles. The founding partnership — established four hundred years ago, formalized in the first years of Matamba's wave_2 settlement charter — was predicated on a straightforward observation: someone needed to create authoritative interpretations of where cooperative commercial law ended and Assembly commercial law began, and to build those interpretations into a body of precedent stable enough that both sides would eventually defer to it rather than relitigate from first principles every time.
|
||||
|
||||
The first published Ferreira Monteiro ruling was filed forty-one years after the partnership's founding. It concerned a disputed consignment of agricultural processing equipment, a cargo manifest drafted under Confluência cooperative standards, and an Assembly customs office at Crux Station that had declined to clear it. The ruling established that cooperative production records, when accompanied by specific attestation formats, satisfy Assembly invoicing requirements — a holding so technically narrow that neither party particularly objected, and so structurally significant that it is still cited in cross-framework documentation disputes today.
|
||||
|
||||
---
|
||||
|
||||
## Operations
|
||||
|
||||
**Arbitration practice:** The core business is cross-framework commercial arbitration — disputes that arise at the intersection of cooperative trade norms and Assembly commercial standards. This is the work the firm was founded to do and the work that has generated its precedent archive. Cases arrive from across the south_reach corridor and, at the high end of commercial significance, from anywhere in the Reach where a south_reach cooperative is a party to a dispute. The firm does not advertise. It does not need to.
|
||||
|
||||
**Advisory and documentation review:** Beyond arbitration, Ferreira Monteiro provides pre-transactional advisory services: reviewing cooperative trade contracts for Assembly compliance risk, drafting attestation formats, advising on cross-framework documentation structures. This work prevents the disputes rather than resolving them after the fact. It is, by volume, the larger part of the practice — every Customs Brokers' Guild certification that touches south_reach cooperative freight eventually passes through a documentation framework that Ferreira Monteiro helped design.
|
||||
|
||||
**The precedent archive:** Four hundred years of case files, rulings, advisory opinions, and dissents, maintained in a physical archive at the Matamba offices and in indexed legal databases accessible to credentialed commercial practitioners across the south_reach corridor. The archive is organized by case type, jurisdiction, and commercial framework — a structure designed by Tomás Monteiro in the firm's second generation of operation and maintained with enough consistency that cases from a century ago are indexed in ways that practitioners today find intuitive. The archive is the firm's product as much as its rulings are. The Reach has other legal archives. None of them have been continuously organized by the same institutional hand for four centuries.
|
||||
|
||||
**Matamba presence:** The firm employs a significant fraction of Matamba's professional legal class. The system's character as a junction between Crux Station and Confluência made it, for the founding generation, the obvious place to establish a practice whose clients would be coming from both directions. Four centuries of institutional investment have made Matamba's legal and commercial services sector among the most developed in the south_reach outer ring, which is itself a product of the firm's presence.
|
||||
|
||||
---
|
||||
|
||||
## Political Relationships
|
||||
|
||||
**Confluência's Guild Delegate Council:** The foundational client relationship. The Guild Delegate Council is not itself a party to commercial disputes — it is a governance body — but the cooperative guilds that fall under its umbrella structure are the primary constituency that Ferreira Monteiro's arbitration practice serves. The relationship is one of institutional complementarity: the Council governs the cooperative structure; the firm handles the legal interface where that structure meets the outside world. They have been doing this together for four hundred years. The Council treats Ferreira Monteiro precedents as baseline commercial law for outbound cooperative trade. The firm treats the Council's interpretations of Confluência's founding charter as definitional inputs to cooperative commercial norms. Neither institution has ever needed to formally acknowledge the other's authority because neither has ever seriously challenged it.
|
||||
|
||||
**The Customs Brokers' Guild:** The Guild resolves cross-framework documentation disputes through its certification framework and internal review processes. Most disputes that arise in south_reach cooperative commerce never reach Ferreira Monteiro because the Guild has already handled them. Ferreira Monteiro exists for the cases the Guild cannot or will not resolve — parties who have exhausted internal Guild channels, disputes where the Guild's institutional interests are themselves at stake, situations where one party does not recognize the Guild's authority. The relationship is functional and slightly wary: the Guild prefers internal resolution and views Ferreira Monteiro arbitration as an escalation path that implies Guild failure. Ferreira Monteiro views the Guild's preference for internal resolution as, in some fraction of cases, a mechanism for suppressing unfavorable outcomes. Both institutions are professionally courteous. Neither entirely trusts the other's independence.
|
||||
|
||||
**The Concord Assembly:** Assembly commercial law is one of the two bodies of law that Ferreira Monteiro's practice exists to adjudicate between. The Assembly does not formally recognize Ferreira Monteiro rulings as binding within its administrative framework. In practice, Assembly commercial compliance officers cite Ferreira Monteiro precedents when they need guidance on cross-framework interpretation — not because they are required to, but because the precedents are usually more useful than anything the Assembly's own legal archive provides on cooperative commerce questions. The relationship is one of acknowledged utility without formal acknowledgment.
|
||||
|
||||
**Crown's Hollow — the chancery parallel:** Crown's Hollow's chancery court is, in its own domain, what Ferreira Monteiro is in the south_reach: an ancient legal institution whose precedent depth exceeds anything the Assembly can match. The chancery operates under a continuous tradition of commercial law that predates the Reach itself. Ferreira Monteiro's oldest precedents are four hundred years old; Crown's Hollow's are older. Both institutions are aware of each other. Both have occasionally dealt with cases in which the other institution's precedents were cited by one of the parties. Neither has formally acknowledged the other's jurisdictional authority. Neither has formally disputed it either. The relationship exists in a productive silence: two very old legal traditions that have developed parallel authority in different corridors of the Reach, each entirely capable of acknowledging the other's existence while declining to establish a hierarchy between them. Commercial practitioners who need to operate in both corridors spend considerable time managing the ambiguity.
|
||||
|
||||
---
|
||||
|
||||
## What They Don't Talk About
|
||||
|
||||
The case archive is a commercial intelligence asset that no one at Ferreira Monteiro describes as a commercial intelligence asset.
|
||||
|
||||
Four hundred years of arbitration files contain the commercial histories of every significant south_reach trade relationship: the actual terms of cooperative supply agreements, the documented margins on cross-framework freight contracts, the internal financial positions of parties who disclosed them under arbitration confidentiality, the patterns of which cooperatives dispute which counterparties and why. This is not the passive data accumulation of Mercado's procurement database or even the transaction registry at Nová Tržnice. Arbitration files contain what parties reveal when they are trying to prove a legal point — which is often the most candid commercial disclosure a party ever makes. The aggregate picture, across four centuries of south_reach commercial disputes, is a map of the corridor's economic relationships at a depth of specificity that no other institution, commercial or governmental, possesses.
|
||||
|
||||
Attorney-client privilege has protected the individual files since the firm's founding. Ferreira Monteiro has enforced that protection against Assembly information requests, Commission inquiries, and at least two occasions in the last two centuries when the enforcement came with significant political cost. The founding partners regard the protection of case file confidentiality as foundational to the firm's authority: if parties cannot trust that their disclosures remain confidential, they will not make the disclosures that allow disputes to be resolved, and the institution collapses. This is correct. It is also the reason the archive is what it is.
|
||||
|
||||
The second silence is about the founding partners themselves. Amélia Ferreira and Tomás Monteiro have been the firm's senior principals for four hundred years. They have watched the south_reach change around them, watched the Assembly develop commercial law that incorporated, without attribution, principles their rulings had established a century before, watched the cooperative guilds they advised grow into institutions of regional significance. They have also watched the disputes that arise within Perpetual-class families, within institutions, within the structural fabric of a civilization that has had a long time to develop its grievances. Four hundred years of privileged access to the south_reach's most consequential commercial conflicts leaves a particular kind of knowledge. Ferreira and Monteiro are, by any measure, among the best-informed living humans about how the south_reach actually operates beneath its institutional surface. They do not share this. It is not the kind of knowledge one shares.
|
||||
|
||||
---
|
||||
|
||||
## Gameplay Relevance
|
||||
|
||||
Ferreira Monteiro is not present in the v0.1 slice at Van Maanen's Star. It operates five hops from Matamba, in the south_reach corridor. Its relevance to the vertical slice is as institutional background: commercial disputes that a player might encounter involving south_reach cooperative freight — documentation questions, contested manifests, cargo seized under cross-framework legal ambiguity — reflect a legal landscape that Ferreira Monteiro helped build. Players in the wider game who operate in the south_reach corridor will encounter the firm's precedents as the operating framework for commercial dispute resolution, whether or not they ever interact with the firm directly.
|
||||
|
||||
For investigation, Ferreira Monteiro represents a potential intelligence pathway at high access thresholds. The case archive is protected by four centuries of enforced confidentiality. There is no casual route through it. A player who has earned significant trust within south_reach commercial networks — or who is investigating something that one of the parties to a historical dispute would prefer remain sealed — has found an obstacle that is genuinely formidable. The firm will not cooperate with informal inquiry. It will cooperate with something that clears the bar it has set over four hundred years of practice.
|
||||
|
||||
The founding partners are a different resource. Amélia Ferreira and Tomás Monteiro have been alive long enough to know things that are not in any file. Whether they share what they know depends on the player, on what they are being asked, and on what the founding partners have decided, over four centuries of careful judgment, is worth protecting.
|
||||
|
||||
---
|
||||
|
||||
**Cross-References:**
|
||||
- [Matamba](../star-systems/GJ-884/index.md) — Headquarters system; geographic crossroads between Crux Station and Confluência
|
||||
- [Confluência](../star-systems/GJ-566B/index.md) — Primary client corridor; founding cultural heritage
|
||||
- [Crux Station](../star-systems/GJ-1061/index.md) — Adjacent south_reach transit node; Assembly commercial interface
|
||||
- [Crown's Hollow](../star-systems/GJ-661A/index.md) — Parallel ancient legal tradition; unacknowledged jurisdictional counterpart
|
||||
- [Mercado Travessia](mercado-travessia.md) — South_reach corridor peer; handles the commerce that FM adjudicates when it fails
|
||||
- [Nová Tržnice](../star-systems/GJ-105A/index.md) — East_reach parallel: transaction registry as passive commercial intelligence vs. FM's privileged case archive
|
||||
- [Customs Brokers' Guild](../star-systems/GJ-1156/index.md) — Preferred internal resolution body; FM handles escalations when the Guild fails or cannot act
|
||||
|
||||
---
|
||||
|
||||
**Status:** Canonical
|
||||
**Created:** 2026-03-15
|
||||
**Updated:** 2026-03-15
|
||||
@@ -10,8 +10,14 @@ Major commercial entities operating at civilizational scale in the Settled Reach
|
||||
| [Mastroianni Vehicle Group](mastroianni-vehicle-group.md) | [Nova Roma](../star-systems/GJ-764/index.md) (GJ 764) | Transit vehicles, trains, haulers | Reach-wide fleet |
|
||||
| [Prometheus Labs](prometheus-labs.md) | [Prometheus](../star-systems/GJ-702B/index.md) (GJ 702B) | Longevity hardware, implants | Every Perpetual |
|
||||
| [Adams & Ford Publishing](adams-ford-publishing.md) | [Parallax](../star-systems/GJ-280A/index.md) (GJ 280A) | The Drifter's Guide to the Reach | Every data terminal |
|
||||
| [Mercado Travessia](mercado-travessia.md) | [Travessia](../star-systems/GJ-1156/index.md) (GJ 1156) | Grocery and household goods chain | Hop 2 to hop 7 |
|
||||
| [Stalownia Kowalski](stalownia-kowalski.md) | [Nowa Huta](../star-systems/GJ-896A/index.md) (GJ 896A) | Heavy mining and construction equipment | South_reach primary, extraction sectors reach-wide |
|
||||
| [Ferreira Monteiro](ferreira-monteiro.md) | [Matamba](../star-systems/GJ-884/index.md) (GJ 884) | Trade arbitration and commercial law | South_reach primary, reach-wide precedent |
|
||||
| [Calloway Distillery](calloway-distillery.md) | [Calloway Reach](../star-systems/GJ-3325/index.md) (GJ 3325) | Single malt whisky | North reach export, cult following |
|
||||
| [thrds](thrds.md) | [Braemar](../star-systems/GJ-475/index.md) (GJ 475) | Cold-weather technical clothing | North reach and beyond |
|
||||
| [Nordmark Skog](nordmark-skog.md) | [Stillvakt](../star-systems/GJ-534/index.md) (GJ 534) | Timber and structural panels | West_reach corridor |
|
||||
| [Talbräu](talbrau.md) | [Brückenau](../star-systems/GJ-798/index.md) (GJ 798) | Franconian farmhouse lager | West_reach transit corridor |
|
||||
| [Vins de Grand Vide](vins-de-grand-vide.md) | [Confluent](../star-systems/GJ-395/index.md) (GJ 395) | Négociant wine cooperative; Grand Vide Classé certification and distribution | West_reach corridor; inner-corridor premium market |
|
||||
|
||||
## Key Relationships
|
||||
|
||||
|
||||
@@ -0,0 +1,109 @@
|
||||
---
|
||||
title: "Mercado Travessia"
|
||||
description: "South_reach-origin supermarket chain operating across the Settled Reach — grocery, household goods, and the quiet cultural export of cooperative commerce"
|
||||
slug: mercado-travessia
|
||||
category: corporation
|
||||
status: canonical
|
||||
created: 2026-03-15
|
||||
updated: 2026-03-15
|
||||
scope: reach-wide
|
||||
faction_type: economic
|
||||
headquarters: Travessia (GJ 1156)
|
||||
tags: []
|
||||
decision_refs: []
|
||||
cross_refs: []
|
||||
---
|
||||
|
||||
# Mercado Travessia
|
||||
|
||||
**Type:** Corporation — Retail Distribution
|
||||
**Also Known As:** Mercado
|
||||
**Status:** Canonical
|
||||
**Scope:** Reach-wide (hop 2 to hop 7)
|
||||
**Headquarters:** Travessia (GJ 1156) — 4-aperture junction, 3 hops from Gateway
|
||||
**Classification:** Major commercial interest; cooperative-origin
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Mercado Travessia is a grocery and household goods chain operating across the Settled Reach. It is not the only supermarket chain in the Reach — there are others, regionally dominant in their own corridors — but Mercado is the one with the widest geographic footprint and the one most residents of the southern and central Reach encounter first. The bright orange storefronts appear near gate terminals and transit hubs from the core systems to the mid-reach frontier, positioned with the logistical precision of an organization that grew out of a freight clearance operation and never forgot what it learned.
|
||||
|
||||
Nobody thinks of Mercado as a south_reach institution. That is the point, and it is also the thing about Mercado that is most worth understanding.
|
||||
|
||||
---
|
||||
|
||||
## Origin
|
||||
|
||||
Three hundred years ago, the bonded warehouse cooperatives in Travessia's customs brokerage district had a recurring problem: goods that arrived for cross-framework clearance but did not clear. Commercial shipments whose documentation could not be reconciled between south_reach cooperative manifests and Assembly standard invoicing sat in bonded storage, accumulating fees, until the originating cooperative either resolved the paperwork or abandoned the consignment. Abandoned consignments were, by Travessia charter, the property of the bonded warehouse that held them.
|
||||
|
||||
One of these warehouses — the Soares-Medeiros cooperative, a mid-sized operation with reliable throughput but no particular distinction — began selling abandoned inventory to the local population at cost rather than returning it to the commercial registry for auction. The logic was practical: local sale was faster, produced goodwill, and moved product that would otherwise occupy storage capacity. The Soares-Medeiros annex, as it was known, became locally popular for its unpredictable but often excellent inventory of south_reach agricultural goods, prepared foods, and household items that core corridor residents had no other access to.
|
||||
|
||||
The annex grew. Within a generation, it was no longer selling only abandoned consignments. It was purchasing directly from south_reach cooperatives, using the same documentation expertise the parent warehouse used for freight brokerage, and selling to a customer base that had developed a preference for south_reach products. The first off-system location opened roughly two hundred and eighty years ago at a core corridor station near a gate terminal — a commercial bet that the distribution infrastructure the Soares-Medeiros cooperative had built for freight clearance was also excellent infrastructure for running a retail supply chain.
|
||||
|
||||
The bet paid. The second location opened within five years. The third within three.
|
||||
|
||||
---
|
||||
|
||||
## Operations
|
||||
|
||||
**Distribution model:** Hub-and-spoke, keyed to gate transit schedules. Mercado's competitive advantage is not product quality — other chains match it — but logistics timing. The founding team's warehouse heritage means Mercado's supply chain planners think in gate cycles, not calendar days. A store at hop 5 receives inventory on a schedule calculated from gate transit windows at every intermediate junction, with buffer stock calibrated to historical schedule variance. This is not glamorous. It is the reason the shelves are stocked when competing stores are waiting on delayed shipments.
|
||||
|
||||
**Procurement:** The buying operation carries its Confluência heritage throughout. Supplier relationships default to cooperative-to-cooperative agreements where possible, with Portuguese-language internal classification categories that have never been translated because the buying team has used them for three centuries and sees no reason to change. The practical effect is a procurement culture that preferences south_reach producers — not by policy, which would be auditable, but by institutional habit, which is not.
|
||||
|
||||
The shelves reflect the Reach. Calloway whisky from the north_reach. Dagat Blue label fisheries products from the east. Jeonnam Old Table fermented paste when it is available, which is not always. Local produce from whatever system the store operates in. The mix communicates something: that the Reach is one market, connected, and that the orange-fronted store near your gate terminal is where that market becomes accessible.
|
||||
|
||||
**Employment:** Mercado is a significant employer in every system where it operates. Store-level positions are local hires. Regional management draws from the Travessia professional class. The senior procurement and logistics teams are overwhelmingly Travessia natives or south_reach corridor professionals with cooperative commerce backgrounds. This is not a hiring policy. It is the result of three centuries of an institutional culture that values a specific kind of commercial fluency.
|
||||
|
||||
---
|
||||
|
||||
## Scale and Competition
|
||||
|
||||
Mercado is not a monopoly. The Reach's retail landscape includes regional chains with deep roots in their home corridors — some older than Mercado, some larger within their territory. What Mercado has that most competitors do not is cross-corridor reach. A chain based in the east_reach serves the east_reach well. A chain based in the core serves the core. Mercado, born at the junction between core and south_reach, expanded along both axes and then outward, and its logistics model — designed for cross-framework commerce from the start — scales to new corridors more easily than models built for a single regulatory environment.
|
||||
|
||||
The result is not dominance but ubiquity within its range. From hop 2 to hop 7, in systems that have gate terminals with regular traffic, there is likely a Mercado. Beyond hop 7, the gate schedules become too irregular for hub-and-spoke distribution to function reliably. Mercado does not operate where it cannot stock shelves on time.
|
||||
|
||||
---
|
||||
|
||||
## Political Relationships
|
||||
|
||||
**The Customs Brokers' Guild:** Mercado's parent cooperative was a Guild member. The modern corporation maintains Guild certification for its cross-framework procurement documentation, which gives Mercado a commercial advantage in south_reach sourcing that competitors without Guild credentials cannot easily replicate. The Guild regards Mercado's procurement scale as both a validation of the Guild's commercial framework and a potential threat to its interpretive authority — Mercado's buying team processes enough south_reach cooperative documentation to develop its own institutional interpretations, which do not always match the Guild's certified standards.
|
||||
|
||||
**South_reach cooperatives:** Mercado's largest supplier base. The procurement relationship is structured as cooperative-to-cooperative agreements that south_reach producers recognize and are comfortable with. This is Mercado's strategic moat: competitors who want to source from south_reach cooperatives must navigate cross-framework documentation that Mercado handles natively. Some cooperatives sell exclusively through Mercado. Whether this exclusivity is contractual or simply the result of Mercado being easier to work with is a distinction that matters more to regulators than to the cooperatives themselves.
|
||||
|
||||
**The Assembly:** Mercado's commercial registration is Assembly-standard. Its cross-corridor operations fall under Assembly commercial compliance review. The compliance relationship is routine — Mercado is large enough to be reviewed regularly and compliant enough to pass without incident. The Assembly's commercial standards office has periodically raised questions about whether Mercado's cooperative procurement structure constitutes a preferential trade arrangement that disadvantages non-cooperative producers. Mercado's legal response has consistently been that supplier selection is a commercial decision, not a trade policy. The questions recur. The answers do not change.
|
||||
|
||||
---
|
||||
|
||||
## What They Don't Talk About
|
||||
|
||||
Mercado's procurement database is, by accident of institutional history and commercial scale, one of the most comprehensive maps of the Reach's food supply chain in existence. Three centuries of supplier relationships, gate schedule data, inventory flow records, and regional consumption patterns have accumulated into a dataset that no government, no Assembly office, and no competing commercial interest possesses in equivalent depth. Mercado's logistics team knows which systems are net food importers, which are one bad harvest from shortage, which gate routes carry the freight that keeps populations fed, and where the bottlenecks are that would cascade into regional supply failure if disrupted.
|
||||
|
||||
This is not intelligence work. It is inventory management. The distinction is meaningful to Mercado's legal team and to no one else.
|
||||
|
||||
The second silence is about cultural influence. Mercado's product categories, shelf layouts, and branding carry south_reach cooperative norms into systems that have never had direct contact with south_reach culture. The Portuguese-language product classifications. The cooperative sourcing marks on packaging. The particular way that Mercado stores organize produce — by growing region and cooperative of origin, not by product type — that south_reach residents find natural and core residents have simply gotten used to. Mercado has, over three centuries, quietly normalized south_reach commercial culture across a significant portion of the Reach's consumer population. Whether this is cultural export, commercial habit, or something more deliberate is a question no one at Mercado has ever been asked directly enough to need an answer for.
|
||||
|
||||
---
|
||||
|
||||
## Gameplay Relevance
|
||||
|
||||
Mercado is environmental texture. The orange storefront appears in station commercial districts, near gate terminals, in the background of daily life. It is the place where NPCs buy groceries and where the player can observe the Reach's commercial ecosystem at its most mundane and most revealing.
|
||||
|
||||
For investigation, Mercado's supply chain data is a potential intelligence resource. A player who gains access to Mercado's procurement database — or to a regional logistics manager who understands what the data means — has a map of the Reach's food security vulnerabilities. A player who notices what Mercado's shelves are missing in a particular system has noticed something about that system's supply chain that the system's own residents may not be tracking.
|
||||
|
||||
For narrative, Mercado is the south_reach's longest arm. The cooperative commerce model, the Portuguese institutional language, the procurement relationships that tie south_reach producers to core consumers — these are visible in every Mercado store, and invisible to most of the people who shop there. A story about cultural influence, about how commerce shapes identity, about what it means when the grocery store is quietly teaching your population someone else's way of organizing the world — that story lives in the Mercado.
|
||||
|
||||
---
|
||||
|
||||
**Cross-References:**
|
||||
- [Travessia](../star-systems/GJ-1156/index.md) — Headquarters; founding system
|
||||
- [Confluência](../star-systems/GJ-566B/index.md) — Cultural and commercial origin corridor
|
||||
- [Customs Brokers' Guild](../star-systems/GJ-1156/index.md) — Credentialing relationship
|
||||
- [Calloway Distillery](calloway-distillery.md) — North_reach spirits supplier
|
||||
- [thrds](thrds.md) — North_reach clothing (not stocked — different retail category)
|
||||
|
||||
---
|
||||
|
||||
**Status:** Canonical
|
||||
**Created:** 2026-03-15
|
||||
**Updated:** 2026-03-15
|
||||
@@ -0,0 +1,44 @@
|
||||
# Nordmark Skog
|
||||
|
||||
**Type:** Forestry and timber products
|
||||
**Headquarters:** [Stillvakt](../star-systems/GJ-534/index.md) (GJ 534)
|
||||
**Founded:** Approximately 280 years ago (wave_3 settlement era)
|
||||
**Structure:** Family-held concession corporation
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Nordmark Skog is a generational logging and timber processing operation based at Stillvakt, a dead-end system off Groenland in the west_reach's outer corridor. The name translates from Swedish as "northern forest" — it began as a geographic descriptor on founding concession documents and became a commercial identity only after the family's milled lumber had been moving through GJ 3333 long enough for corridor buyers to recognize it.
|
||||
|
||||
The company holds the primary land concession over Stillvakt's boreal belt — approximately forty thousand square kilometers of managed softwood forest. Seven generations of the Nordmark family have operated the concession through three renewal cycles without serious challenge. The distinction between company, family, and community governance has effectively dissolved: the senior Nordmarks sit on the local council because no one else has the administrative infrastructure to run one.
|
||||
|
||||
---
|
||||
|
||||
## Products
|
||||
|
||||
**Nordmark Dark Grain** is the company's primary branded product — structural panel stock milled from the dense softwood species native to Stillvakt's boreal zones. The panels have a distinctive dark coloration from the wood's natural tannin content, and they appear in station interiors two and three hops inward. Most buyers do not know where they come from. They know the product by its grain pattern and its reputation for dimensional stability in pressurized environments.
|
||||
|
||||
Secondary products include raw log bundles for processing elsewhere, standard milled lumber in various grades, and a modest volume of seed stock from the regeneration program that has found buyers in reforestation projects on more-settled worlds.
|
||||
|
||||
---
|
||||
|
||||
## Operations
|
||||
|
||||
The operation is vertically integrated at a small scale: the company manages the forest, fells the timber, mills it at the central processing facility in Fällstaden, and handles its own freight logistics to the aperture transit facility, which the family also operates under contract. Three satellite logging camps rotate through harvest zones on forty-to-sixty-year replanting cycles, maintaining four distinct forest cohorts at various growth stages.
|
||||
|
||||
The regeneration program is not driven by ecological sentiment. A company that has been logging the same ranges for nearly three centuries understands that the alternative is mining a finite asset. The replanting discipline is institutional — it predates the current generation's memory and will outlast it.
|
||||
|
||||
---
|
||||
|
||||
## Scale and Reach
|
||||
|
||||
Nordmark Skog is not a large corporation by inner-corridor standards. It is a single-system operation with a single product line moving through a single gate. What it has is consistency: nearly three centuries of uninterrupted timber supply, a product with a corridor reputation built on that consistency, and a concession position that no competitor has the standing or the motivation to challenge.
|
||||
|
||||
The company's freight moves inward through Groenland and disperses into the west_reach's inner corridor through standard commercial channels. There are no formal distribution agreements beyond the freight contract. The product finds its buyers because it has been finding its buyers for longer than most corridor businesses have existed.
|
||||
|
||||
---
|
||||
|
||||
## Silence
|
||||
|
||||
The condition of the old-growth zones beyond the current harvest boundary. The original concession surveys mapped significantly more old-growth area than the current regeneration cycle accounts for. What happened in those sections is not discussed.
|
||||
@@ -0,0 +1,118 @@
|
||||
---
|
||||
title: "Stalownia Kowalski"
|
||||
description: "South_reach heavy equipment manufacturer — drilling rigs, excavation platforms, ore processing machinery, and habitat construction systems for three centuries of extraction and settlement"
|
||||
slug: stalownia-kowalski
|
||||
category: corporation
|
||||
status: canonical
|
||||
created: 2026-03-15
|
||||
updated: 2026-03-15
|
||||
scope: south_reach primary; west_reach secondary; reach-wide in extraction sectors
|
||||
faction_type: economic
|
||||
headquarters: Nowa Huta (GJ 896A)
|
||||
tags: []
|
||||
decision_refs: []
|
||||
cross_refs: []
|
||||
---
|
||||
|
||||
# Stalownia Kowalski
|
||||
|
||||
**Type:** Corporation — Heavy Industrial Manufacturing
|
||||
**Also Known As:** Stalownia, SK
|
||||
**Status:** Canonical
|
||||
**Scope:** South_reach primary; west_reach secondary; reach-wide presence in extraction sectors
|
||||
**Headquarters:** Nowa Huta (GJ 896A) — 3-aperture junction, 6 hops from Gateway
|
||||
**System Holdings:** Nowa Huta (GJ 896A)
|
||||
**Classification:** Syndic-tier commercial interest; family-owned, generational succession
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Stalownia Kowalski builds the machines that dig, build, and process. If the Gate Corporation builds the gates and MVG builds what passes through them, Stalownia builds what gets installed at the destination: drilling rigs, excavation platforms, ore processing machinery, habitat construction frames, station structural components, and the full array of heavy equipment that extraction operations and settlement construction require. This is equipment that does not move between systems. It arrives at a site and stays there, working.
|
||||
|
||||
The name means Kowalski Steelworks. The Kowalski family founded it three hundred years ago, and three hundred years of family succession — not Perpetual-class continuity, but genuine generational handoff, parent to child to grandchild — have produced an institution with the specific character that comes from earning institutional knowledge rather than simply retaining it. What the Mastroianni family in Nova Roma remembers from three centuries ago, the Kowalski family has had to write down, transmit, and teach. The archive is the memory. Stalownia's internal documentation is the most thorough in the heavy industrial sector, and everyone in the sector knows it.
|
||||
|
||||
In the south_reach extraction corridor, Stalownia equipment is the default. In systems where the rock is being pulled out of the ground and the ore is being processed and the habitats are going up, the machinery doing that work was almost certainly designed and built in Nowa Huta. The maintenance contracts that follow that equipment create a permanent operational presence across the corridor that is less visible than the Gate Corporation's transit infrastructure but comparably structural within the sectors where it operates.
|
||||
|
||||
---
|
||||
|
||||
## Origin
|
||||
|
||||
Nowa Huta was settled in the Wave 3 expansion — three hundred years ago, the same founding cohort that established the south_reach extraction corridor as the Reach's primary industrial resource zone. The settlement wave that reached GJ 896A brought settlers with Polish-South African heritage, part of the broader cultural mix that shaped the south_reach's early working character. The founders of what would become Stalownia Kowalski were engineers and fabricators from that cohort: practical people who looked at the extraction operations springing up across the corridor and saw that the equipment being shipped in from Core systems was expensive, slow to arrive, and designed for environments that were not the south_reach's.
|
||||
|
||||
The original proposition was simple. Build the equipment here, from materials extracted here, by people who understand the conditions here. The first Stalownia contracts were with south_reach mining cooperatives that were buying on price and local availability because they could not afford Core delivery timelines. Stalownia's early designs were not sophisticated. They were robust, maintainable in the field, and sized for the kinds of deposits the south_reach was extracting. The equipment worked. The cooperatives came back.
|
||||
|
||||
Three generations of the Kowalski family managed that growth through the consolidation period when south_reach extraction shifted from small cooperative operations to larger organized mining programs. Each succession transferred not just ownership but operational knowledge — hard-won understanding of which geological formations demanded which equipment specifications, which failure modes appeared in which environments, what margins the industry actually needed versus what it told itself it needed. By the time the fourth generation inherited the company, Stalownia had contracts with operations across the corridor and a manufacturing base at Nowa Huta that had grown around those contracts.
|
||||
|
||||
The name of the system tells you something about who got there first and what they built.
|
||||
|
||||
---
|
||||
|
||||
## Operations
|
||||
|
||||
**Extraction equipment:** The core product line. Drilling rigs for hard-rock extraction, excavation platforms for low-gravity surface mining, ore processing systems that integrate with site logistics rather than requiring purpose-built infrastructure around them. Stalownia's extraction equipment is known for field maintainability — the design philosophy across three centuries has consistently prioritized the ability of an on-site crew with standard tooling to perform maintenance and repairs without waiting for specialists from Nowa Huta. Extraction sites are not near hubs. Equipment that requires a specialist to fix is equipment that sits idle while the specialist transits.
|
||||
|
||||
**Construction systems:** Habitat frames, station structural components, pressurization infrastructure for newly settled systems. Stalownia's construction product line grew out of extraction — the same sites that needed mining equipment needed somewhere for the workers to live. The construction systems are modular and designed for assembly with the same crew and tooling that operates the mining equipment. This is not elegant engineering. It is engineering for the conditions that actually exist at the edge of the Reach.
|
||||
|
||||
**Ore processing machinery:** The intermediate step between raw extraction and saleable material. Processing systems are Stalownia's most technically complex product category and the one with the longest maintenance cycles. A processing installation at a south_reach extraction site will run for decades. The maintenance contracts on those installations — routine service, component replacement, system upgrades — are the backbone of Stalownia's recurring revenue and the mechanism by which the company maintains a continuous field presence across the extraction corridor.
|
||||
|
||||
**Nowa Huta manufacturing base:** The GJ 896A system's junction topology — three apertures, positioned at the junction of the south_reach corridor with routes toward the west_reach and inward toward core-adjacent systems — makes it a functional logistics hub for heavy equipment shipment. The manufacturing facilities at Nowa Huta are not the largest in the Reach, but they are specialized for the kinds of large-form fabrication that extraction and construction equipment requires, and they are positioned to move product into the south_reach extraction systems efficiently. The adjacent Kraków Junction (GJ 1116B) anchors the primary logistics corridor that carries completed equipment outbound and raw material and components inbound.
|
||||
|
||||
---
|
||||
|
||||
## System Holdings
|
||||
|
||||
**Nowa Huta (GJ 896A)** — 3-aperture junction, 6 hops from Gateway. The system's name is a deliberate invocation of the historical steelworks district in Kraków — the founders were not being subtle about what they were building or who they were. The industrial identity is worn plainly: Nowa Huta is a manufacturing system, organized around the Stalownia facilities, and the population has the character that comes from three centuries of working in heavy fabrication.
|
||||
|
||||
The system is not beautiful and does not try to be. The orbital infrastructure has the utilitarian density of a place that moves large objects regularly. Fabrication yards, component warehouses, outbound equipment marshalling areas. The settlement patterns reflect the workforce's origins — Polish-South African heritage is visible in the naming conventions, the architectural styles of the older residential districts, and the particular form of labor organization that the south_reach extraction corridor developed and Nowa Huta exemplifies.
|
||||
|
||||
What the system is, more than anything, is thorough. The Stalownia archive — the institutional memory that accumulated because the family could not rely on biological continuity to preserve it — is housed here. Three centuries of equipment specifications, site geology records, maintenance histories, and engineering margins documentation. The archive is not advertised. Most people in the Reach do not know it exists. The people who do know it exists understand that it is, in its way, as valuable as anything Stalownia manufactures.
|
||||
|
||||
---
|
||||
|
||||
## Political Relationships
|
||||
|
||||
**Mastroianni Vehicle Group:** The division of territory between Stalownia and MVG is clean enough to be workable and blurry enough to require periodic negotiation. MVG builds what moves through gates. Stalownia builds what gets installed at the destination. The line is clear for canonical cases: a transit carriage is MVG; an ore processing facility is Stalownia. The line is less clear for mobile extraction platforms — equipment that moves within a system but does not transit gates — and for mining vehicles that operate at extraction sites. Both companies have designs in this space. The competition is professional rather than existential: the market is large enough to accommodate both, and they collaborate on integrated systems where a mining installation requires both fixed processing equipment and mobile haulers. The contracts governing these collaborations are carefully structured.
|
||||
|
||||
**The Gate Corporation:** Stalownia builds the installations; Gate Corporation builds the gates that connect them. The relationship is straightforwardly complementary and rarely produces friction. Gate Corporation maintains the transit infrastructure through which Stalownia ships equipment. Stalownia's construction systems build the habitats and station structures that Gate Corporation's span gates then connect to the broader network. Different links in the same chain. The relationship is professional and without the technical interdependency that makes the Gate Corporation-MVG dynamic so loaded.
|
||||
|
||||
**South_reach cooperatives and extraction operators:** Stalownia's oldest and most fundamental relationships. Three hundred years of contracts have produced a procurement culture on the south_reach extraction side that defaults to Stalownia equipment without necessarily requiring competitive bids — not because there is an agreement to this effect, but because the institutional familiarity and the maintenance infrastructure already in place make switching costs real. A cooperative that has run Stalownia equipment for two generations has Stalownia-trained maintenance staff, Stalowsia-specification tooling, and Stalownia service relationships. The competitor offering a better price has to overcome all of that.
|
||||
|
||||
**The Concord Assembly:** Stalownia's Assembly engagement is narrower than the Gate Corporation's or MVG's. The company's relevant committees are those touching extraction regulation, construction standards, and the frontier development programs that drive demand for new installation equipment. Assembly contracts for settlement-phase construction in newly activated frontier systems are a meaningful revenue source. The company's lobbying presence is sized to those interests — significant within them, largely absent from the broader commercial and transit policy debates where the Gate Corporation and MVG operate.
|
||||
|
||||
**The Cygni B combines:** Overlapping territory on large-scale construction. The Cygni B combines build station hulls and large structural systems; Stalownia builds the internal industrial and habitation infrastructure that goes inside those hulls. The relationship mirrors the MVG-Cygni B dynamic: partners on most contracts, competitors on the specifications that determine where one company's scope ends and the other's begins. Stalownia operates in the south_reach; the Cygni B combines are heavier in the core and north. The geographic separation keeps the competition from being constant.
|
||||
|
||||
---
|
||||
|
||||
## What They Don't Talk About
|
||||
|
||||
The Kowalski family is generational, not Perpetual. This is a distinction that looks like a liability — no Perpetual-class family has ever had to rebuild institutional knowledge from scratch after a founder's death — but the family's response to that constraint has produced something that Perpetual firms tend not to have: a systematic, comprehensive written record of everything the company knows.
|
||||
|
||||
The Stalownia archive documents three centuries of extraction site geology across the south_reach. It contains the actual engineering margins on every major equipment installation the company has built — not the specified margins, the actual operating margins, the ones that represent the difference between what the client paid for and what the site's conditions actually required. It contains maintenance logs that show how those margins degraded over time, what failure modes appeared and when, and what the clients were told versus what Stalownia's engineers knew. It documents the succession disputes. There was at least one contested transition in the company's history where the family's internal alignment failed and the company's direction was genuinely uncertain. What was decided, what was conceded, and what remains unresolved from that period is in the archive.
|
||||
|
||||
None of this is available outside the company. Stalownia's documentation practices were developed as institutional survival, not as intelligence. The distinction matters to the Kowalski family's legal team. To anyone who could access that archive, the distinction is not the interesting part.
|
||||
|
||||
---
|
||||
|
||||
## Gameplay Relevance
|
||||
|
||||
Stalownia is present in the v0.1 slice as texture and setting context. The mining and construction equipment that built and maintains Station Sova and the Van Maanen's Star extraction operations likely carries SK branding or is documented in system records as Stalownia installations. This is background — the equipment that built the world the player moves through.
|
||||
|
||||
For investigation, Stalownia's maintenance contracts create a plausible field presence in extraction systems. A Stalownia service technician is a normal figure at an extraction site; a Stalownia service contract is a normal entry in a system's commercial register. Either can serve as cover, as contact, or as a thread to pull. The company's archive is a potential resource for players investigating extraction site incidents, structural failures, or anything where the original engineering specifications matter. Accessing that archive — or finding someone who has access to it — requires working around an institution that has very specific ideas about what belongs inside the company and what does not.
|
||||
|
||||
For the wider game, Stalownia represents a particular kind of reach: not the transit presence of the Gate Corporation or the social network of the Mastroianni family, but the physical footprint of three centuries of installation and maintenance across the Reach's extraction sector. A player who needs to understand what is physically inside a mining installation, or what was built to specification and what was not, is looking at Stalownia documentation. A player investigating why a structure failed, or why it held when it should have failed, may find that Stalownia's engineers knew something the client did not.
|
||||
|
||||
---
|
||||
|
||||
**Cross-References:**
|
||||
- [Nowa Huta](../star-systems/GJ-896A/index.md) — Headquarters; founding system
|
||||
- [Gate Corporation](gate-corporation.md) — Complementary infrastructure; Stalownia builds what Gate Corporation connects
|
||||
- [Mastroianni Vehicle Group](mastroianni-vehicle-group.md) — Adjacent product territory; mobile vs. fixed equipment boundary
|
||||
- [Cygni B Combines](../factions/cygni-b-combines.md) — Construction scope overlap; regional separation manages competition
|
||||
- [Kraków Junction](../star-systems/GJ-1116B/index.md) — Adjacent system; primary logistics corridor for equipment shipment
|
||||
|
||||
---
|
||||
|
||||
**Status:** Canonical
|
||||
**Created:** 2026-03-15
|
||||
**Updated:** 2026-03-15
|
||||
@@ -0,0 +1,46 @@
|
||||
# Talbräu
|
||||
|
||||
**Type:** Brewing cooperative
|
||||
**Headquarters:** [Brückenau](../star-systems/GJ-798/index.md) (GJ 798)
|
||||
**Founded:** Approximately 160 years ago (wave_4 settlement era, second generation)
|
||||
**Structure:** Valley farming household cooperative
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Talbräu is a brewing cooperative organized around a shared malting and fermentation facility in Waldbrück, the central town of Brückenau's river-valley network. The name translates from German as "valley brew" — a functional description that has become the only name transit crews need. The cooperative's membership overlaps with the valley farming families who form the community's economic and social backbone, making Talbräu as much a community institution as a commercial enterprise.
|
||||
|
||||
The cooperative was established in the second generation after Brückenau's founding, when the valley hop gardens had produced sufficient consistent harvests to support organized brewing. The founders brought Franconian brewing tradition from old Bavaria — yeast strains, malting protocols, and an understanding of what terrain produced the bitter-aromatic hops their farmhouse lager style required. Brückenau's lowland river valleys supplied the rest.
|
||||
|
||||
---
|
||||
|
||||
## Products
|
||||
|
||||
**Talbräu Dunkelgold** is the flagship product — an unfiltered Franconian farmhouse lager. It is not positioned as a premium artisanal product. It is a consistent, honest, valley-grown beer that tastes like what it is. The hops are local, the water is local, the yeast strain has been maintained continuously since the founding. Transit crews transiting through Brückenau ask for it specifically. Some carry cases on departure.
|
||||
|
||||
Dunkelgold has found its way, without formal distribution agreements, into bar inventories two and three hops inward — not in great volume, but steadily, because crews keep requesting it and operators stock what crews request.
|
||||
|
||||
**Schwarzgold** is a darker winter variant brewed seasonally. A wheat-style seasonal rounds out the cooperative's production. Neither has achieved the corridor recognition of the Dunkelgold, but both have their advocates among regular transit traffic.
|
||||
|
||||
---
|
||||
|
||||
## Operations
|
||||
|
||||
The cooperative operates from a single facility in Waldbrück: a combined malthouse, fermentation hall, and bottling operation that processes the hop and grain harvests from the valley farming households. All inputs are local — the cooperative has never imported brewing ingredients. The valley agriculture produces sufficient grain and hop volume to supply the brewery and feed the population, with surplus for preserved food export.
|
||||
|
||||
Outbound freight moves through a long-standing arrangement with a transit operator based at GJ 601A (Ostmark). This single-channel distribution has been the primary export route for approximately eighty years.
|
||||
|
||||
---
|
||||
|
||||
## Scale and Reach
|
||||
|
||||
Talbräu is a small operation by any inner-corridor measure — a single-facility cooperative serving a through-route transit population and a modest export market built entirely on word-of-mouth. What it has is a product that people remember and ask for again, in a location where transit traffic passes through as a matter of course. Brückenau's through-route topology between Sonnwend and Ostmark means more ships stop here than at comparable hop-8 systems, and the brewery is what converts transit into stopover.
|
||||
|
||||
The cooperative holds four permanent seats on the Valley Council (Talrat) by charter, giving it formal political influence in local governance. This arrangement has been quietly contested by highland communities above the valley network who have less representation and different economic interests.
|
||||
|
||||
---
|
||||
|
||||
## Silence
|
||||
|
||||
The yeast strain. Talbräu's founding yeast produces the specific ester profile that makes Dunkelgold taste like it does. The cooperative maintains it as a proprietary culture and has kept it out of external hands for two centuries. The strain was brought from old Bavaria — from Earth. The cooperative's legal relationship to that genetic material has never been tested and is not discussed, because discussing it would invite examination.
|
||||
@@ -0,0 +1,124 @@
|
||||
---
|
||||
title: "Vins de Grand Vide"
|
||||
description: "West_reach négociant cooperative based at Confluent (GJ 395) — aggregates production from independent châteaux, certifies quality, and distributes wine across the corridor from hop 10 to the inner systems"
|
||||
slug: vins-de-grand-vide
|
||||
category: corporation
|
||||
status: canonical
|
||||
created: 2026-03-15
|
||||
updated: 2026-03-15
|
||||
scope: west_reach primary; inner-corridor premium market secondary
|
||||
faction_type: economic
|
||||
headquarters: Confluent (GJ 395)
|
||||
tags: []
|
||||
decision_refs: []
|
||||
cross_refs: []
|
||||
---
|
||||
|
||||
# Vins de Grand Vide
|
||||
|
||||
**Type:** Corporation — Agricultural / Distribution Cooperative
|
||||
**Also Known As:** le Grand Vide, the Comptoir, VGV
|
||||
**Status:** Canonical
|
||||
**Scope:** West_reach corridor primary; inner-corridor premium market secondary
|
||||
**Headquarters:** Confluent (GJ 395) — 2-aperture through_route, 10 hops from Gateway
|
||||
**System Holdings:** Confluent (GJ 395)
|
||||
**Classification:** Syndic-tier commercial interest; cooperative structure, founding family network
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Vins de Grand Vide builds nothing, grows nothing, and owns not one hectare of vineyard. It is the institution that makes three and a half centuries of Confluent wine commercially viable at corridor scale: a négociant cooperative that aggregates production from dozens of independent châteaux, certifies quality, manages the logistics of moving fragile cargo through aperture transit, and operates the distribution network that places Confluent wine on shelves across the west_reach and into select inner-corridor markets where it commands prices that would astonish the farmers who grew it.
|
||||
|
||||
The name comes from the founding era. The second generation of Confluent settlers — the children of the families who arrived at hop ten with root cuttings and a proposition — looked outward at the corridor behind them and described what they saw: le grand vide, the great void, the uninhabited distance between their remote system and the organized civilization they had come from. The name was chosen to confront that distance rather than minimize it. Wines of the Great Void. We are far away and we know it, and you are going to drink what we made here because nothing else tastes like this.
|
||||
|
||||
The name turned out to be correct. Three hundred and fifty years later, Vins de Grand Vide's Comptoir — the commercial archive and operations center located in the transit district of le Pays's primary settlement — is the oldest continuously operating commercial institution in the deep west_reach corridor, and it has never sold anything except wine.
|
||||
|
||||
---
|
||||
|
||||
## Origin
|
||||
|
||||
The founding families at Confluent arrived at hop ten with a clear understanding that distance was their primary commercial problem. Growing exceptional wine at the end of a multi-hop corridor was only a proposition if the wine could reach buyers who would pay for it. The first generation focused on the growing. The second generation founded Vins de Grand Vide to solve the other half of the problem.
|
||||
|
||||
The founding compact, drafted approximately three hundred and fifty years ago, established the cooperative on principles that remain operative: no direct estate ownership, voluntary membership for châteaux, shared logistics infrastructure, collective quality certification, and a distribution mandate that required the Comptoir to represent all member estates rather than prioritize the largest or most profitable ones. The founding families who negotiated this structure were primarily the smaller estates — the Grand Domaines already had enough leverage to negotiate individual distribution arrangements, and they joined the cooperative because the collective logistics infrastructure was genuinely more efficient than anything they could build independently.
|
||||
|
||||
The Comptoir's first distribution route ran inward from Confluent to Alshain, then to the systems accessible from Alshain. The routes extended inward as the cooperative built relationships with transit intermediaries and buyers in hop-4 and hop-5 systems. The inner-corridor premium market — systems within five hops of the Gateway where the combination of Perpetual-class wealth and gastronomic sophistication produces buyers who will pay serious prices for authenticated deep-corridor wine — developed over the second and third centuries of the cooperative's operation, and it is now a meaningful fraction of VGV's commercial volume despite representing a small number of actual buyers.
|
||||
|
||||
---
|
||||
|
||||
## Operations
|
||||
|
||||
**Quality certification — the Classification system:** Vins de Grand Vide operates a three-tier classification for member estate wines, established approximately two hundred and fifty years ago and revised twice since. The tiers reflect both the estate's consistent quality record and the specific wine:
|
||||
|
||||
- **Grand Vide Classé** — top tier, awarded to specific wines from estates with at least a fifty-year continuous membership record, requiring annual review. Currently seventeen designations across nine estates. These are the wines that command inner-corridor premium prices. The certified bottles carry the Comptoir seal — a stylized horizon station aperture in deep blue — and that seal is verifiable through the Comptoir's registry.
|
||||
- **Vins de Corridors** — middle tier, the reliable corridor market wines. Well-made, consistent, clearly labeled by estate and vintage. The category where most of VGV's volume sits. The Clos du Grand Passage cooperative produces primarily Vins de Corridors wines.
|
||||
- **Vin de Table du Vide** — everyday table wine, unclassified, distributed in bulk through standard freight channels to the west_reach market. The wine that most corridor residents have drunk without knowing where it came from.
|
||||
|
||||
**Logistics:** Moving wine through aperture transit requires managing vibration, temperature variation during transit, and the handling standards at horizon station freight facilities that were not designed for fragile agricultural cargo. VGV worked out the transit packaging standards in its first century of operation, and those standards — insulated freight modules with controlled internal atmosphere, specific stacking requirements, handling protocols for aperture transit — are now the Reach-wide standard for wine shipping. They were developed by the Comptoir and are licensed to any shipper who handles wine, which means VGV's operational expertise is embedded in every wine shipment that moves through the organized network regardless of whether VGV is involved in the shipment.
|
||||
|
||||
**The Comptoir:** The commercial operations center on le Pays manages the distribution contracts, the certification registry, the estate membership relationships, and the three-hundred-and-fifty-year commercial archive. The Comptoir staff number about sixty full-time at Confluent, with a smaller logistics office at the Alshain transit hub that handles the corridor distribution coordination. The Director of the Comptoir is the chief executive of the cooperative; the current Director is Séverine Morel-Duval, who has held the position for eleven years and is the fourth Director in the last century not to come from one of the founding family networks. The founding families still hold disproportionate weight in the cooperative's governance structure — the largest producers have proportionally larger votes — but the day-to-day management has been professionally staffed for about a hundred and fifty years.
|
||||
|
||||
---
|
||||
|
||||
## Products
|
||||
|
||||
**The estates and their wines:**
|
||||
|
||||
*Domaine des Étoiles Fixes* — the oldest continuously operated parcel on le Pays, located in the Vallée de l'Intérieur at an elevation that gives access to the warm slope soils where the Carignan de Vide varietal achieves its best expression. The estate's flagship wine — simply called Étoiles Fixes, never with a vintage designation on the label because the estate considers vintage specificity a marketing device rather than a quality indicator — is the most recognized Confluent wine in inner-corridor markets. Grand Vide Classé since the classification system was established. Deep garnet, iron-mineral nose, tannins that require age. A case of Étoiles Fixes from a respected year trades in inner-corridor collector markets at prices the estate itself finds slightly embarrassing.
|
||||
|
||||
*Château Fond de Ciel* — Plateau Gris position, the highest and coldest growing site on the primary world. Produces the definitive Gris Blanc varietal: a pale white wine with extraordinarily complex aromatics — the Confluent star's spectrum drives an unusual polyphenol development in the Gris Blanc grape that no viticultural scientist has fully explained — and a quality variation between vintages that makes it a collector's wine in the specific sense that the right vintage is exceptional and the wrong vintage is merely good. Grand Vide Classé for the single-vineyard expression. The estate is owned by the Brissac-Fontaine family, who have not altered the vineyard management system in six generations.
|
||||
|
||||
*Mas de la Traversée* — large estate in the Vallée de l'Intérieur producing the Carignan de Vide varietal at volume. The Traversée table wine is the wine most corridor workers in the west_reach have drunk at some point. Not a Grand Vide Classé wine — the estate has never applied for the designation and considers it irrelevant to their market — but a consistent Vins de Corridors producer of the highest reliability. The Traversée family has been producing at the same site for three hundred years and has the most complete vineyard records of any estate on le Pays.
|
||||
|
||||
*Domaine Lumière Pale* — named for the quality of the F8V light at the estate's altitude, which produces the color and aromatic intensity characteristic of its dry rosé. The Lumière rosé has acquired an unexpected following in hop-3 and hop-4 systems over the last fifty years, driven by a fashion for deep-corridor wine in inner-corridor social registers. The estate is mildly annoyed by this, as it primarily considers itself a serious red producer. Its Lumière Sombre — a dark red from the estate's lower plots — is excellent and significantly less famous than the rosé, which the estate considers unjust.
|
||||
|
||||
*Clos du Grand Passage* — the cooperative estate, organized by the founding-era families of Confluent's transit district as a collective production unit. Produces wines from multiple terroirs blended into a consistent house style: approachable, reliable, the wine you find on every table in a west_reach establishment that takes its cellar seriously without requiring its patrons to. The Grand Passage Blanc is the west_reach's standard-issue good white wine in the way that certain inner-corridor producers have achieved category dominance. Vins de Corridors classification across the range.
|
||||
|
||||
*Vignoble de la Nuit Profonde* — a smaller estate in the coastal lowland zone, producing primarily the Nuit Profonde blend — a red that incorporates three local varietals in proportions that the estate does not disclose, producing a wine with aromatic complexity unusual for the coastal terroir. The estate has been Vins de Corridors classified for eighty years and is widely expected to seek Grand Vide Classé status within the next decade. The current proprietor, Anaïs Bertrand-Solaire, is sixty-two years old and has been making the Nuit Profonde blend since she was twenty.
|
||||
|
||||
**On the light:** The F8V stellar spectrum is not red, but it is warmer than a standard G-type. The radiation that reaches Confluent's primary world carries more red and near-infrared component relative to blue than Earth-equivalent sunlight. Over four centuries, the local varietals have adapted: the Carignan de Vide has developed unusually thick skins with high anthocyanin concentrations — its dark color and iron-mineral character are partly genetic adaptation. The Gris Blanc has adapted its polyphenol expression in ways that produce the aromatic complexity that has no exact counterpart in the terrestrial wine tradition. The coastal varietals in the Nuit Profonde blend have moved toward high-sugar ripening profiles that the estate manages carefully to avoid overripe character. Confluent wine cannot be exactly replicated elsewhere because the grapes are now specific to the conditions that produced them.
|
||||
|
||||
---
|
||||
|
||||
## Political Relationships
|
||||
|
||||
**Estate network:** VGV's relationships with its member estates are the cooperative's defining dynamic, and they are not frictionless. The Grand Domaines — Étoiles Fixes and Fond de Ciel in particular — are Grand Vide Classé designees with significant market leverage and have periodically proposed governance structure changes that would weight their votes more heavily in the Comptoir's decision-making. These proposals have been rejected each time by the smaller estate coalition, which controls a majority of votes under the current structure. The tension is structural and permanent. Neither side is wrong about its interests. The cooperative functions because the logistics infrastructure is genuinely more valuable to everyone than any alternative arrangement, and the logistics infrastructure only functions at scale if the full membership is participating.
|
||||
|
||||
**Inner-corridor distributors:** VGV works with a small number of inner-corridor distribution houses that specialize in provenance goods from deep-corridor systems. The relationship is commercially dependent — VGV has no direct market presence within hop 5 — and the distributors negotiate hard on margin because they understand that VGV needs them more than any individual distributor needs VGV. The Comptoir maintains these relationships with the care that a supplier gives to buyers it cannot replace and does not fully trust.
|
||||
|
||||
**Alshain transit authority:** The logistics relationship with Alshain (GJ 771A) is the most operationally critical external relationship VGV maintains. Everything that leaves Confluent passes through Alshain, and VGV's transit packaging standards require coordination with Alshain's freight handling procedures. The relationship has been formalized in a standing service agreement for over two hundred years. It is functional and professionally managed. It is also the point at which VGV has the least leverage, because the transit authority has no obligation to Confluent specifically and multiple alternative freight sources competing for the same infrastructure capacity.
|
||||
|
||||
**The Concord Assembly and regulatory institutions:** VGV operates in a policy environment that is theoretically governed by Reach-wide commercial regulations. In practice, at hop ten, the Assembly's commercial regulation framework reaches VGV as a compliance requirement rather than an operational presence. The Comptoir files its required documentation and maintains certification standards that satisfy the Assembly's quality authentication framework. The Commission has no agricultural or food-production jurisdiction and has never engaged with VGV directly.
|
||||
|
||||
---
|
||||
|
||||
## What They Don't Talk About
|
||||
|
||||
The Comptoir's commercial archive is three hundred and fifty years old and it documents every distribution relationship, freight arrangement, and commercial transaction in VGV's operational history. The archive was built to serve the wine trade and has always served only that purpose. What it incidentally represents is the most comprehensive record of commercial relationships in the deep west_reach corridor in existence.
|
||||
|
||||
Three centuries of distribution data means three centuries of information about who is buying what, at what prices, through which intermediaries, and how those relationships have evolved. The corridor's commercial networks are documented in the Comptoir's records in ways that no regulatory body and no intelligence institution has equivalent access to. VGV has never offered this access to any outside party and has never been asked in a way it could not politely decline. The Comptoir staff who manage the archive understand what it contains in the aggregate. They do not discuss it.
|
||||
|
||||
There is also a category of estate members whose membership status requires careful management. Approximately twelve of the current member estates joined the cooperative in the last century following financial difficulties — situations where a distressed estate sold a minority stake to a buyer who then transferred that stake to a VGV membership position as part of a restructuring arrangement. The Comptoir does not advertise the provenance of these membership positions, and the estates involved operate normally under their original names and family management. The beneficial ownership of those minority stakes sits in a set of commercial structures that the Comptoir's legal team has never been asked to trace in full. The founding family governance structure of VGV's cooperative council means that the beneficial owners of those minority stakes do not have voting rights proportional to their economic interest. Whether this arrangement was designed or simply occurred is a question the Comptoir has no institutional interest in answering.
|
||||
|
||||
---
|
||||
|
||||
## Gameplay Relevance
|
||||
|
||||
Vins de Grand Vide is not present in the v0.1 slice but provides setting texture and commercial context for the west_reach corridor as a whole. Any investigator working in systems from Confluent inward will encounter VGV wine as ambient setting detail — on tables, in freight manifests, in commercial records where the Vins de Corridors or Grand Vide Classé certification mark appears as a brand element.
|
||||
|
||||
For investigation, the Comptoir's archive is the deep-corridor analogue of what a financial surveillance system would be in an inner-corridor context: a comprehensive record of commercial relationships that predates the Commission's regulatory reach and has never been subject to Commission review. An investigator trying to understand how commerce moves through the deep west_reach — who the actual intermediaries are, what the actual margins look like, which distribution relationships have structural anomalies — would find the Comptoir's archive useful if they could access it. Accessing it requires either the cooperation of VGV's Director or a route into the archive that bypasses her, neither of which is straightforward.
|
||||
|
||||
The minority stake question provides a thread for investigations concerning beneficial ownership structures in deep-corridor commercial entities. The specific answer — who actually owns those minority positions, and what they are positioned to benefit from — is a design decision for the investigation that uses it.
|
||||
|
||||
---
|
||||
|
||||
**Cross-References:**
|
||||
- [Confluent](../star-systems/GJ-395/index.md) — Headquarters; founding system; home of 60+ estate vineyards
|
||||
- [Alshain](../star-systems/GJ-771A/index.md) — Primary transit hub; standing service agreement; all outbound freight passes through
|
||||
- [Nordmark Skog](nordmark-skog.md) — Parallel deep-corridor agricultural product distributor; different sector, analogous commercial structure
|
||||
|
||||
---
|
||||
|
||||
**Status:** Canonical
|
||||
**Created:** 2026-03-15
|
||||
**Updated:** 2026-03-15
|
||||
@@ -0,0 +1,145 @@
|
||||
---
|
||||
title: "Compact of Westphalia"
|
||||
description: "Mutual recognition treaty among 30-40 west_reach systems at hops 6-9 — rejects Assembly authority through coordinated non-compliance rather than secession"
|
||||
slug: compact-of-westphalia
|
||||
category: faction
|
||||
status: canonical
|
||||
created: 2026-03-15
|
||||
updated: 2026-03-15
|
||||
scope: west_reach corridor (hops 6-16)
|
||||
faction_type: political
|
||||
tags: []
|
||||
decision_refs: []
|
||||
cross_refs: []
|
||||
---
|
||||
|
||||
# Compact of Westphalia
|
||||
|
||||
**Type:** Faction — Mutual Recognition Treaty / Political Bloc
|
||||
**Status:** Canonical
|
||||
**Scope:** West_reach corridor, centered at hops 6-9, extending to the frontier
|
||||
**Governance Role:** Counter-institutional — makes Assembly authority practically unenforceable over member systems
|
||||
**Headquarters:** None (rotating council, no permanent seat)
|
||||
**Structure:** Treaty organization with rotating council of system governors
|
||||
**Colloquial Names:** "the Compact," "Westphalia," "the mutual recognition framework"
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
The Compact of Westphalia is not a government. It is a treaty of mutual recognition among approximately thirty to forty west_reach and deep_frontier systems, and it is the single most significant political challenge the Concord Assembly has faced since the Secession from Earth.
|
||||
|
||||
The name is deliberate. The Peace of Westphalia ended the Thirty Years' War in 1648 by establishing the principle that sovereign states govern their own internal affairs without external interference. The west_reach's Germanic-heritage founding communities know the reference. They consider it precisely apt: a treaty that says your internal governance is not our business, and ours is not yours, and neither of us answers to a distant authority that was not party to this agreement.
|
||||
|
||||
What the Compact has built, over sixty to eighty years of careful, incremental work, is a zone where the Assembly's government does not practically reach. Not a rival state. Not a secessionist movement. Something more difficult to confront: a coordinated withdrawal of compliance by systems that have never formally left the Reach and have no intention of doing so.
|
||||
|
||||
---
|
||||
|
||||
## Origin
|
||||
|
||||
The west_reach corridor has been developing its autonomist character since the first wave of settlement pushed past hop 6. The corridor's Germanic and Scandinavian founding communities carried a cultural orientation toward local governance and institutional self-sufficiency that intensified with distance from the Gateway. By the time wave_3 settlements were being established at hops 7 and 8, the practical reality was that most outer west_reach systems governed themselves without meaningful Assembly oversight — not because they had rejected the Assembly, but because the Assembly's authority attenuated with distance until it became theoretical.
|
||||
|
||||
The Compact formalized what was already true. Approximately sixty to eighty years ago, representatives from a group of outer west_reach systems — including founding members [Ostmark](../star-systems/GJ-601A/index.md) (GJ 601A), [Freiholt](../star-systems/GJ-624/index.md) (GJ 624), and several other wave_1 through wave_3 systems with centuries of self-governance history — drafted the mutual recognition framework. The document was not a declaration of independence. It was an agreement among neighbors: we recognize each other's governance as legitimate, we coordinate our commercial arrangements, and we do not accept that a distant Assembly has authority over our internal affairs.
|
||||
|
||||
The drafting process was deliberate and unhurried. The founding systems had been governing themselves for centuries. They were not in crisis. They were formalizing an arrangement that the Assembly's absence had already created, and they did so with the institutional patience of communities that measure decisions in generations rather than political cycles.
|
||||
|
||||
---
|
||||
|
||||
## Core Principles
|
||||
|
||||
The Compact's mutual recognition framework rests on four commitments:
|
||||
|
||||
1. **Mutual governance recognition.** Member systems recognize each other's governance decisions as legitimate without requiring Assembly oversight, certification, or review. A Compact system's internal law is valid within the Compact network by virtue of the member system's sovereign authority, not by Assembly delegation.
|
||||
|
||||
2. **Common customs and transit.** No internal gate tariffs between member systems. Shared customs arrangements that facilitate commerce within the Compact zone. The practical effect is that trade between Compact members moves more freely and cheaply than trade between Compact members and non-Compact systems — an economic incentive structure that has been more effective at expanding membership than any ideological argument.
|
||||
|
||||
3. **Mutual defense against external coercion.** The language says "external coercion," which can mean piracy as easily as Assembly enforcement action. The practical meaning is that an Assembly attempt to compel compliance from one member would be treated as a concern of all members. The Compact has no standing fleet and no unified military command. What it has is thirty to forty systems whose combined non-cooperation with any enforcement action would make that action logistically impractical.
|
||||
|
||||
4. **Rejection of Assembly assessments.** Member systems do not recognize Assembly tax assessments as legitimate claims on their economic output. This is the provision that most directly challenges Assembly authority, and it is the one the Assembly has found most difficult to respond to — because enforcing assessment compliance at hop 7 and beyond requires fleet projection that costs more than the assessments would yield.
|
||||
|
||||
---
|
||||
|
||||
## Structure
|
||||
|
||||
The Compact is governed by a rotating council of system governors. There is no permanent headquarters — the council's administrative functions rotate among member systems on a cycle that has been running for decades without producing a permanent institutional seat. This is by design. A permanent headquarters would create a target for Assembly diplomatic pressure and a center of gravity that could be co-opted. The distributed structure makes the Compact difficult to negotiate with as a single entity, which is precisely the point.
|
||||
|
||||
**Council composition:** Each member system sends one representative, typically a senior governance figure — a council chair, a sector governor, a cooperative executive. Several founding representatives are Perpetual-class, which gives the Compact institutional memory and strategic patience that the Assembly's rotating delegate structure cannot match. A Perpetual who helped draft the original framework sixty years ago is still present to correct misinterpretations of the document's intent. The Assembly's negotiators turn over on political cycles. The Compact's founding voices do not.
|
||||
|
||||
**Founding members:** The systems whose representatives drafted the original mutual recognition framework hold a specific institutional standing within the Compact. When the rotating council discusses treaty interpretation, governance precedent, or the formal principles of the framework, founding-member representatives speak with the authority of people whose systems helped write the document. [Ostmark](../star-systems/GJ-601A/index.md) (GJ 601A) is the most prominent founding member — a wave_1 system with five centuries of continuous self-governance and the institutional archive to prove it.
|
||||
|
||||
**Membership tiers:** The Compact does not formally distinguish membership tiers, but in practice there are three categories:
|
||||
- **Formal signatories** (hops 7+): Systems that have signed the mutual recognition framework and actively participate in the rotating council. The core membership.
|
||||
- **Sympathetic systems** (hops 5-6): Systems that have not formally signed but align with the Compact's principles, benefit from its trade arrangements, and would likely support its positions in any confrontation with the Assembly. Their formal compliance with Assembly frameworks is maintained for pragmatic reasons — proximity to Assembly enforcement range — but their political sympathies are well understood.
|
||||
- **Frontier extensions** (hops 10+): Recently settled systems, many founded by settlers from Compact member systems, who arrived with the Compact's political culture already internalized. These systems often joined the framework as a matter of course during their founding period.
|
||||
|
||||
---
|
||||
|
||||
## What the Compact Is Not
|
||||
|
||||
**It is not monolithic.** Member systems have widely varying governance types — cooperative syndicates, corporate oligarchies, small-scale democratic republics, founding-family councils. The Compact does not require governance conformity. This is part of its appeal: the framework that says "your internal governance is your own affair" cannot credibly demand that members govern in a specific way.
|
||||
|
||||
**It is not anti-Earth.** Some members actively court Sol trade relationships. Others have no Sol opinion. A small number are anti-Sol for Secession-history reasons. The Compact's position is that individual member systems decide their own external relationships, including with Sol.
|
||||
|
||||
**It is not militarist.** It has no standing fleet, no unified military command, no arms standardization program. Individual members maintain local security forces appropriate to their circumstances. The mutual defense provision is a commitment to coordinated non-cooperation with external enforcement, not a military alliance in the conventional sense.
|
||||
|
||||
**It is not trying to secede.** This is the distinction the Assembly has failed to grasp for sixty years. The Compact is not building a rival government. It is building a zone where the Assembly's government does not practically apply. The members have not filed secession declarations. They have not renounced their Concord membership. They have simply stopped complying with the specific Assembly functions they consider illegitimate — assessment collection, governance oversight, regulatory review — while continuing to use the infrastructure that predates the Assembly's authority: the gates, the transit network, the commercial relationships that the corridor built before the Assembly organized itself to govern them.
|
||||
|
||||
---
|
||||
|
||||
## The Assembly's Response
|
||||
|
||||
**Official position:** The Assembly does not recognize the Compact of Westphalia as a political entity. Its official discourse treats west_reach non-compliance as a collection of individual administrative issues rather than a coordinated political movement. This position has been maintained for sixty years despite being obviously incorrect, because acknowledging the Compact as a political entity would require the Assembly to respond to it as one — and the Assembly does not have a response that would work.
|
||||
|
||||
**Actual strategy:** Wait the Compact out. The Assembly's informal position is that economic integration will eventually draw member systems back into compliance alignment — that the practical benefits of participating in the Assembly's commercial frameworks, regulatory structures, and infrastructure investment programs will outweigh the ideological satisfaction of rejecting them. This strategy has not worked for sixty to eighty years and shows no signs of working, because the Compact's own trade arrangements have proven economically competitive with the Assembly's frameworks. The Compact's internal trade network provides its members with most of the commercial benefits the Assembly framework offers, without the assessment obligations.
|
||||
|
||||
**Enforcement dilemma:** The Assembly could, in theory, project fleet authority into the outer west_reach to compel compliance. In practice, this would require military deployment at distances where supply lines are thin, against a dispersed group of systems whose combined non-cooperation would make any enforcement action logistically unsustainable. The Assembly has calculated the costs and has not found them acceptable. The Compact's founders anticipated this calculation. Building a political structure that was too distributed and too deep to enforce against cost-effectively was not an accident. It was the design.
|
||||
|
||||
**The trade delegate at Altmark.** The Assembly maintains a permanent trade delegate at [Altmark](../star-systems/GJ-357/index.md) (GJ 357), hop 7, which functions as the Assembly's furthest permanent diplomatic outpost in the west_reach corridor. The delegate's role is nominally commercial — facilitating trade relationships between Assembly-compliant inner corridor systems and the outer west. In practice, the delegate is the Assembly's eyes and ears in the Compact zone, and everyone involved understands this. The delegate visits Compact member systems periodically. The visits are commercial in nature. The reports filed after the visits are not.
|
||||
|
||||
---
|
||||
|
||||
## Economic Infrastructure
|
||||
|
||||
The Compact's most effective tool is not its political principles but its trade network. The mutual recognition framework's common customs provisions — no internal gate tariffs, shared transit arrangements, preferential access to member-system manufacturers — have created an internal market that functions as an alternative to the Assembly's commercial frameworks.
|
||||
|
||||
For member systems at depth, this is not ideological. It is arithmetic. [Groenland](../star-systems/GJ-3333/index.md) (GJ 3333) signed the Compact because the mutual recognition framework reduced import costs enough to make its agricultural surplus commercially viable. [Echternach](../star-systems/GJ-127B/index.md) (GJ 127B) participates because the Compact's trade network is the most reliable channel for the medical hardware imports that its isolated community depends on. The Compact's economic infrastructure has expanded its membership more effectively than its political philosophy has, because systems that might hesitate to sign a political document will readily join a trade arrangement that saves them money.
|
||||
|
||||
[Vins de Grand Vide](../corporations/vins-de-grand-vide.md)'s distribution network, while not formally a Compact institution, operates primarily through the Compact's trade infrastructure. The wine moves through Compact member systems on Compact customs arrangements, and the Comptoir's three-hundred-and-fifty-year commercial archive — the most comprehensive record of deep west_reach trade relationships in existence — documents the network that the Compact formalized.
|
||||
|
||||
---
|
||||
|
||||
## What They Don't Talk About
|
||||
|
||||
The Compact's internal politics are more fractured than its unified external posture suggests. The founding members — the wave_1 and wave_2 systems with centuries of self-governance history — drafted the framework to formalize arrangements that already existed. The newer members — wave_4 and wave_5 systems that joined in the last generation — signed for economic access to the trade network. The two groups have different interests, different timelines, and different definitions of what the Compact is for.
|
||||
|
||||
The founding members want the Compact to remain what it was designed as: a mutual recognition framework, a treaty of equals, a structure that makes Assembly authority unenforceable without replacing it with another authority. The newer members — younger, less wealthy, more economically dependent on the trade network — have begun proposing that the Compact develop shared institutional functions: a common commercial court, standardized regulatory frameworks for cross-system commerce, a permanent secretariat to manage the rotating council's increasingly complex administrative load. Every one of these proposals moves the Compact closer to becoming the kind of government its founders explicitly refused to build.
|
||||
|
||||
The rotating council has deferred these proposals repeatedly. The founding-member representatives — several of whom are Perpetual and have been making the same argument against institutional accretion for sixty years — have the institutional standing to block structural changes. But the demographic weight is shifting. There are more new members than founding members, and the new members' commercial needs are real. The question of whether the Compact will remain a treaty or become a government is the conversation the Compact is having with itself, behind closed doors, in a process that the Assembly is watching with considerable interest — because a Compact that becomes a government is a Compact that can be negotiated with, and a Compact that remains a treaty is a Compact that cannot.
|
||||
|
||||
---
|
||||
|
||||
## Gameplay Relevance
|
||||
|
||||
The Compact of Westphalia is the political environment of the west_reach corridor. Any investigator working at hop 6 or beyond will encounter the Compact's influence: in the customs arrangements that govern freight, in the governance structures that reject Assembly oversight, in the trade relationships that flow through the Compact's internal network rather than the Assembly's commercial frameworks.
|
||||
|
||||
The Compact is not an enemy. It is not an ally. It is the political reality of the deep west — a zone where the rules the investigator learned in the inner corridor do not apply because the people who live here have agreed among themselves that those rules do not reach this far. An investigator who needs Assembly authority to compel cooperation will find that authority meaningless. An investigator who can work within the Compact's own frameworks — who can present their work as consistent with the Compact's principles of local governance and mutual recognition — will find doors that Assembly credentials cannot open.
|
||||
|
||||
The internal tension — treaty versus government, founding members versus new members — provides investigative leverage. Systems within the Compact have interests that diverge from the Compact's unified external posture. Finding those divergences, understanding which systems signed for principle and which signed for trade access, and knowing which council representatives have been blocking institutional development for sixty years and which have been pushing for it — this is the political intelligence that makes the deep west navigable.
|
||||
|
||||
---
|
||||
|
||||
**Cross-References:**
|
||||
- [Ostmark](../star-systems/GJ-601A/index.md) (GJ 601A) — Founding member; institutional anchor; wave_1 at hop 9
|
||||
- [Freiholt](../star-systems/GJ-624/index.md) (GJ 624) — Founding member
|
||||
- [Altmark](../star-systems/GJ-357/index.md) (GJ 357) — Assembly trade delegate; diplomatic outpost at Compact's edge
|
||||
- [Groenland](../star-systems/GJ-3333/index.md) (GJ 3333) — Pragmatic member; joined for trade economics
|
||||
- [Echternach](../star-systems/GJ-127B/index.md) (GJ 127B) — Deep-corridor member; medical supply dependency
|
||||
- [Concord Assembly](concord-assembly.md) — The institution the Compact defines itself against
|
||||
- [Vins de Grand Vide](../corporations/vins-de-grand-vide.md) — Distribution network operating through Compact trade infrastructure
|
||||
- Cultural-migration-pressure design doc — Source: `docs/design/cultural-migration-pressure.md` section 4.3
|
||||
|
||||
---
|
||||
|
||||
**Status:** Canonical
|
||||
**Created:** 2026-03-15
|
||||
**Updated:** 2026-03-15
|
||||
@@ -13,6 +13,12 @@ Political and institutional factions operating across the Settled Reach.
|
||||
| [Guardians of Autonomy](guardians-of-autonomy.md) | Political movement | Counter-surveillance, anti-institutional concentration |
|
||||
| [The Unbound](the-unbound.md) | Cultural movement | Anti-lattice, voluntary disconnection |
|
||||
|
||||
## Regional Factions
|
||||
|
||||
| Faction | Scope | Role |
|
||||
|---------|-------|------|
|
||||
| [Compact of Westphalia](compact-of-westphalia.md) | West_reach (hops 6-16) | Mutual recognition treaty; coordinated non-compliance with Assembly authority |
|
||||
|
||||
## Local Factions
|
||||
|
||||
| Faction | Scope | Role |
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_223
|
||||
**GJ 103** | K-type | deep_frontier
|
||||
# Bestevaer
|
||||
**GJ 103** | K-type | west_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -14,20 +14,33 @@
|
||||
|
||||
---
|
||||
|
||||
Bestevaer is a Dutch word with roots in seafaring — it names a kind of skilled, practical mariner, the sort who knew tides and hulls and the behavior of water in all its moods. The settlers who chose the name arrived forty to a hundred years ago and found a planet that made the reference immediately obvious: Bestevaer is an ocean world.
|
||||
|
||||
There are landmasses — a scattering of island chains, a single modest continental shelf that barely clears the waterline at its highest point — but the planet is dominated by water. Deep, active, biologically rich ocean covering the majority of its surface, with the K7V primary providing a warm orange light that penetrates the upper water column well enough to drive an extraordinary amount of photosynthetic activity. The wave patterns are complex and beautiful. The storms can be severe.
|
||||
|
||||
The Dutch found this and did what their heritage demanded. Settlement infrastructure was built to float. The first permanent structures were platform habitats anchored to the shallower shelf zones; the island chains developed secondary communities when the initial population grew large enough. Aquaculture is the primary food production method. Marine engineering has become the system's most developed technical specialty. Vessels designed for ocean work — atmospheric craft built on hulls rather than skids — were locally prototyped within two decades of settlement.
|
||||
|
||||
At hop 7 off Altmark (GJ 357), Bestevaer is the furthest west_reach dead_end. Authority is distant. The Commission has a charter registration for the system and a vessel that stops twice a year. The rest of the year, the community handles itself on open water and in the gaps between government visits.
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Bestevaer exports marine products — preserved seafood, biological compounds, culture stocks for aquaculture systems elsewhere — toward Altmark and through the west_reach corridor. It imports manufactured components, particularly for platform maintenance and atmospheric hull construction, which it cannot produce locally. The exchange is roughly workable but the import lead times are significant.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No established external faction presence. A maritime council governs the platform habitats and the island communities under a combined charter. Dispute resolution at sea is handled by an old-fashioned system of captain-arbitration that predates any formal Commission framework and which the Commission has found it easier to recognize than replace.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
A section of the ocean floor in the southern deep basin has been marked as a restricted navigation zone for as long as the settlement has existed. The stated reason is "geological instability." The zone's boundaries were drawn before anyone had the equipment to survey that depth. Nobody has surveyed it since.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
Three months ago, a deep-ocean monitoring buoy deployed by the marine survey collective transmitted a brief anomalous signal — a structured frequency pattern, not a geological source — before going silent. Its last position was inside the restricted navigation zone.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
Wave_5 dead_end at hop 7 on an ocean world is internally consistent. The Dutch maritime heritage and the ocean-world geography reinforce each other in ways that justify the settlement despite the access difficulty.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# 268 G. Cet
|
||||
# Nová Tržnice
|
||||
**GJ 105A** | K-type | east_reach
|
||||
|
||||
---
|
||||
@@ -15,19 +15,50 @@
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
The three junction systems that connect to Nová Tržnice — Port Desrochers, Yongjin, and Jinghu — had centuries of gate traffic moving through their apertures before anyone settled GJ 105A. They coordinated, competed, and occasionally disputed routing priority on freight bound for the east_reach's interior. What none of them had was a destination that turned transit into commerce.
|
||||
|
||||
The founders identified this before they filed the settlement application. A K3V star at hop 4, comfortably habitable, sitting at the intersection of three established transit junctions, had sat empty for three hundred years not because the planet was unsuitable but because no party with the standing to develop it had an interest in creating a commercial competitor. What the founders offered the adjacent junctions was not competition but processing capacity: a place where the freight arriving from three directions could be opened, assessed, combined, finished, and sent back out as something more valuable than what arrived. Port Desrochers, Yongjin, and Jinghu all supported the development application. The transit logic was obvious once someone laid it out.
|
||||
|
||||
Nová Tržnice is forty years old and its economic character is density rather than scale. Hundreds of commercial operations occupy the surface settlements: light manufacturers who receive bulk components and finish them for end markets, wholesale consolidators who combine small producer shipments into gate-viable freight loads, brand showrooms maintained by east_reach companies who want a neutral location for procurement meetings, and the workshop layer — custom fabricators, specialty component suppliers, repair operations — that occupies the commercial gaps between larger operations. The Market Authority, still run by the founding generation, maintains infrastructure and dispute resolution. No single company dominates. The charter was written that way deliberately.
|
||||
|
||||
The habitable body is genuinely good land by east_reach standards: temperate, well-watered, adequate for agricultural self-sufficiency. The founders built commercial infrastructure first and residential amenity second. Forty years of consistent economic activity have started to balance those priorities.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The founding group was Czech — commercial logistics professionals from inner-corridor systems who recognized the gap before anyone else and moved on it before a corporate entity could foreclose the position. Czech heritage is unusual in this part of the east_reach corridor, where the demographic baseline is predominantly Asian-heritage drawn from the three adjacent junctions' migration pools. The founders were not sentimental about this. They named the system in Czech, structured the commercial law framework on Central European trade traditions, and then built a market that attracted the east_reach's merchants, buyers, and manufacturers on purely commercial terms. The cultural mixing that followed was organic and transaction-driven. You set up shop in Nová Tržnice because the market is good.
|
||||
|
||||
The Market Authority — formally the Nová Tržnice Commercial Charter Authority — is the founders' most significant institutional creation. It operates as a quasi-governmental body with authority over market infrastructure, commercial dispute resolution, and charter compliance. The founding generation holds the Authority's senior positions and has shown no inclination to constitute an independent governance succession. Whether the Authority's current structure is durable past the founding generation is a question the second generation is not yet pressing openly.
|
||||
|
||||
The Lattice Commission has a field presence appropriate to a junction with active commercial throughput. The free-port charter's transparency requirement — full commercial transaction logging as a condition of reduced tariff assessment — has created an unusual dynamic: Commission agents at Nová Tržnice have access to more complete commercial data than at most comparable systems, but the data's value for investigative purposes is circumscribed by the charter's explicit commercial-compliance framing. The Commission can audit transaction records. Whether it can use those records for purposes the charter did not contemplate is a question the Authority has not yet needed to litigate.
|
||||
|
||||
Assembly presence at hop 4 is structural and consistent. The free-port commercial charter was negotiated with Assembly commercial affairs through a process that took eight years and produced a document that both sides consider acceptable. The Assembly's working relationship with the Authority is functional. Whether the Assembly considers a free port in the east_reach an asset to be maintained or an exception to be eventually normalized is not stated in any public record.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The free-port charter requires that every commercial transaction conducted within the system be logged in the Market Authority's central registry. This was the founders' concession in exchange for reduced tariff assessment, and it was marketed as a transparency provision that would make Nová Tržnice a trustworthy commercial environment. Forty years of complete transaction records covering hundreds of companies across three connecting junction systems is what that provision has actually produced.
|
||||
|
||||
The registry maps the east_reach's real commercial relationships with a granularity that no other single source matches: who buys from whom, at what price, on what schedule, with what volume variation. Supply chain dependencies, pricing relationships, preferred routing patterns, commercial alliances that do not appear in any corporate filing — all of it is in the registry as an incidental byproduct of charter compliance.
|
||||
|
||||
The Market Authority maintains the registry. The Authority also controls who can query it and for what stated purpose. The founders built the access framework into the original charter, which was reasonable in year one when the registry contained forty transactions. What the access framework does not account for is what the registry has become after forty years of the east_reach's busiest commercial junction operating at full capacity. Several parties — the Commission, at least two major east_reach commercial interests, and one entity the Authority has not publicly identified — have formally requested expanded query access in the past decade. The Authority has approved none of these requests in full.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
Forty years of complete commercial transaction records covering every company that has done business at the east_reach's primary marketplace sit in the Market Authority's registry, and the founders who control access to that data have declined every request for expanded query rights without public explanation.
|
||||
|
||||
---
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
`wave_5` at `hop 4` as a `junction` is unusual — most hop-4 systems were settled in wave_2 or wave_3. Nová Tržnice's late settlement reflects that the system's value was contingent on the three adjacent junctions' prior establishment: without Port Desrochers, Yongjin, and Jinghu operating as mature transit hubs, there was no commercial rationale for a processing hub between them. The system needed its neighbors to exist before it could function. This is a Section 6.2 economic logic exception rather than a survey oversight. K3V classification and hop 4 position support a temperate habitable world that genuinely sat empty for three centuries by commercial consensus rather than physical constraint. Czech founding heritage in an east_reach corridor is a cross-corridor exception consistent with the Early Arrival archetype applied to a wave_5 commercial opportunity claim.
|
||||
|
||||
---
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_277
|
||||
# Espinho
|
||||
**GJ 1075** | unusual-type | south_reach
|
||||
|
||||
---
|
||||
@@ -14,20 +14,47 @@
|
||||
|
||||
---
|
||||
|
||||
GJ 1075 is a K7V — a cool orange dwarf near the bottom of the K sequence — but it earned the unusual-type designation through behavior rather than spectral class. Early surveys flagged it as a magnetic variable with irregular coronal mass ejection patterns that do not follow the predictable periodicity of a typical flare star. The ejections are not severe enough to make the primary world uninhabitable, but they occur on schedules that initial models failed to anticipate, and the station's magnetic field monitoring has been upgraded twice in two centuries because operators kept finding the existing instrumentation insufficient to give adequate warning. The system's stellar research community, which is small and perpetually underfunded, refers to this problem as "catching the star thinking." The local population has absorbed this relationship as part of daily life: weather forecasts here include a CME probability alongside temperature and precipitation.
|
||||
|
||||
The settlement was named Espinho by its founders, Portuguese families from the wave_4 migration who brought the name of a thorny coastal town on Portugal's Atlantic face. The original Espinho was a fishing town that had spent centuries being underestimated — a place people passed through on their way to Porto or Lisbon, a place that sustained itself by practical work and that had its own character precisely because it was never fashionable enough to be reshaped by outside attention. The naming was not nostalgic. It was a statement of intent. The founders expected that Espinho would be a place people passed through on their way somewhere else, and they built it accordingly — durable, practical, possessed of its own internal coherence, indifferent to whether outsiders noticed.
|
||||
|
||||
Two hundred years of settlement have validated the founders' expectations in ways they did not entirely intend. Espinho is a dead-end, one aperture, one way in and one way out. Traffic passes through only if Espinho is the destination. The population that built up around the system's stellar research program and its modest extraction industries has been stable for four generations. The researchers came initially for the star's anomalous behavior; some of them stayed, trained their children in the same observatories, and created a scientific community with a continuous institutional memory that is now longer than most universities in the inner orbit. The families came for the extraction work, which is modest and unremarkable, and found that the dead-end topology produced a community with low turnover and strong lateral trust — the kind of place where everyone knows what everyone else does, which is uncomfortable if you are doing something problematic and stabilizing if you are not.
|
||||
|
||||
The aperture that connects Espinho to GJ 435 (Mirante) is the system's only link to the rest of the Reach. Mirante sits at hop 8 — one hop further from Gateway than Espinho's hop 7 — and connects onward to Encrucijada's hub at GJ 393, which is also hop 7. The route from Espinho to the hub passes outward through Mirante before doubling back to the junction at the same hop distance. The topology places Espinho at the tip of a spur, fully dependent on the Mirante-to-Encrucijada route for everything it imports and exports.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Espinho imports the manufactured goods that its modest industrial base cannot produce: electronics, medical supplies, precision instruments for the observatory systems, and processed food varieties that the local agricultural operations do not cover. Exports are limited — the stellar research program produces publications and instrumentation designs that occasionally find commercial applications, and the extraction operations produce a modest stream of mineral output that moves inward through Mirante toward the Encrucijada hub. The system is not a significant node in any supply chain. It pays its way without ease or crisis, which is what the founding generation designed it to do.
|
||||
|
||||
The observatories represent the system's single piece of infrastructure that has value beyond the local economy. The CME prediction models developed here over two centuries have been licensed to operators in other M and K-type systems with irregular stellar activity. The licensing income is not large, but it is consistent and it is the closest thing Espinho has to an export that distinguishes it from every other small dead-end in the south_reach.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The Lattice Commission has no permanent presence. A rotating inspector visits on the standard outer-reach cycle — once every two years unless something flags the system for additional attention. The last two inspections reported nothing requiring follow-up. The research community maintains standard neural lattice compliance records because the founding generation, who included several people who had worked under heavier Commission oversight in the inner orbit, decided early that clean records were simpler than managing exceptions.
|
||||
|
||||
The Guardians of Autonomy have a nominal chapter, four members, which exists primarily to ensure someone is formally tracking Assembly policy changes that could affect the extraction cooperatives' operating licenses. It has never organized an action. It meets quarterly and its most consequential function is maintaining the subscription to an Assembly legislative feed that several local operators contribute to collectively.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The CME periodicity models have an anomaly that the observatory has not published. The irregular ejection pattern, which over two centuries has been partially but not completely mapped, includes an approximately 40-year cycle of elevated activity that does not appear in any other documented K-type magnetic variable in the stellar database. The observatory team's current interpretation is that the star has a deep magnetic structure that is not fully explained by standard M and K-type variable theory. The reason this has not been published is that the two senior researchers who noticed the 40-year signal disagree about whether it is real or an artifact of the observatory's long-term data collection methodology, and neither wants to publish a claim that the other will immediately contest. The disagreement is personal as well as scientific, and the silence is maintained by the discomfort of both parties rather than by any institutional decision.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
An observatory technician has noticed that the 40-year CME cycle anomaly, if real, would have been detectable from the original survey data — which means the survey team that designated GJ 1075 as a viable settlement site may have known about the elevated activity periods before the founding families arrived, and chose not to include that information in the settlement prospectus.
|
||||
|
||||
---
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
The unusual-type designation for a K7V requires clarification. The spectral class is standard; the unusual flag reflects the magnetic variable behavior and anomalous CME periodicity that was identified in early surveys and confirmed over two centuries of observation. K7V stars are not normally flagged unusual, but GJ 1075's irregular flare pattern, particularly the undocumented 40-year cycle, places it outside the envelope of typical K-type behavior in ways that have material consequences for surface infrastructure planning. The wave_4 settlement date is consistent with a dead-end system at hop 7: the third emigration wave established junctions and through-routes, and the fourth wave pushed into the spurs and terminals that the third wave had connected without populating.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_008
|
||||
**GJ 1156** | G-type | south_reach
|
||||
# Travessia
|
||||
**GJ 1156** | K-type | south_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -14,20 +14,67 @@
|
||||
|
||||
---
|
||||
|
||||
The name means crossing. Not a destination — the point between destinations. The founders who arrived four hundred years ago, carrying south_reach cooperative traditions out of the same Confluência emigration wave, chose the word deliberately. They had come to a junction, and they understood what that meant: this was the place where south_reach became legible to the core, and where the core became accessible to the south_reach. They built accordingly.
|
||||
|
||||
GJ 1156 is a K5V star, close and warm, its orange light almost identical to Confluência's own. At 19.3 light years from Gateway, it sits at hop 3 — deep enough into the settled Reach that the Assembly maintains real institutional weight here, close enough to the south_reach corridor that Confluência's cooperative norms are the water in which locals swim. The habitable world is a place of long coastlines and moderate seasons, geologically settled, well-watered. The community that grew here did not arrive expecting to leave. Four centuries later, they have not.
|
||||
|
||||
What Travessia became is the Reach's most important commercial translation point. South_reach cooperative trade operates on norms — collective invoicing, supplier-cooperative relationships, rotating price agreements — that Assembly commercial standards were not designed to accommodate. When south_reach goods cross into the core market, or when core investment capital flows outward toward Confluência's guilds, the transaction has to become legible in both frameworks simultaneously. Travessia's bonded warehouse district grew up to perform exactly that function. Customs brokers here do not simply clear freight. They repackage commercial relationships — converting cooperative manifests into Assembly-standard documentation, structuring cross-framework contracts so that both parties are satisfied the terms mean what they expect them to mean.
|
||||
|
||||
Four hundred years of translation work has made Travessia genuinely fluent in both commercial languages. It has also made Travessia, in certain quiet ways, dependent on the gap never closing. A junction ceases to be a junction if the two sides it connects become fully interoperable.
|
||||
|
||||
---
|
||||
|
||||
## Economy
|
||||
|
||||
The transit and customs brokerage function generates the system's primary institutional revenue and employs a significant share of the professional population. Travessia's bonded warehouse district is a major origination point for southward-bound core capital and northward-bound south_reach exports. South_reach cultural products — cooperative-made manufactured goods, agricultural specialties, Confluência-adjacent craft production — first reach the core market through Travessia, and the brokers here have developed a sophisticated understanding of what core buyers will value and what will require explanation.
|
||||
|
||||
The second major economic institution is not a brokerage. It is a grocery chain.
|
||||
|
||||
**Mercado Travessia** — known throughout the Reach simply as Mercado — began three centuries ago as the retail annex of one of the bonded warehouse cooperatives in the district. The original logic was straightforward: goods that didn't clear on commercial contracts were offered to the local population at cost. The annex grew. The warehouse cooperative recognized the distribution infrastructure they had built for freight clearance was also excellent infrastructure for running a supply chain. The first off-system Mercado opened at a core corridor station roughly two hundred and eighty years ago, positioned near a gate terminal with reliable schedules — the same kind of transit logistics reasoning that governed their freight operations.
|
||||
|
||||
Mercado now operates across the Reach from hop 2 to hop 7. Its storefronts are immediately recognizable: the bright orange of the founding cooperative's color, derived from Confluência's K-type daylight. It maintains a hub-and-spoke distribution model keyed tightly to gate schedules, headquartered at Travessia because the founders understood, and their successors have never forgotten, that controlling the distribution network requires understanding transit. The procurement operation carries a Confluência heritage throughout — cooperative supplier relationships, Portuguese-language product categories still used as internal classification, a preference for south_reach producers that is not formally written into the charter but is deeply embedded in the buying team's culture.
|
||||
|
||||
On Mercado's spirits shelf: Calloway whisky, sourced through their north_reach purchasing office. On the prepared foods tier: Dagat Blue label goods, the canned fisheries products out of the oceanic systems. Mercado is, for many core residents, their primary ongoing contact with south_reach food culture, south_reach cooperative production, south_reach ways of organizing what a community consumes. They do not think about it in those terms. They think about it in terms of price and quality and whether the orange-fronted store near the gate terminal carries what they need before departure.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Travessia is not a producing system in the primary sense. It manufactures services: brokerage, customs documentation, logistics coordination, and retail distribution management. Raw goods pass through in volume. What leaves the system's accounts is not freight — it is the administrative work that makes freight move correctly between incompatible frameworks. The population is professional-class, educated, transit-literate. Food production is adequate but not export-capable; the system imports agricultural surplus from Confluência's guilds and, increasingly, from Mercado's own south_reach supplier network, which sometimes supplies back into Travessia at the hub end. The gate infrastructure — four apertures, continuous high-volume throughput — requires specialist maintenance staff drawing components from core corridor suppliers via Tessera connections.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The **Customs Brokers' Guild** is the oldest established institution in the system, predating the Mercado operation by nearly a century. It is not a cooperative in the Confluência sense — it is a credentialing body with licensing authority over commercial documentation practitioners. In practice, it is the system's most powerful single institution, because the Guild's interpretation of what constitutes valid cross-framework documentation determines what can and cannot be cleared through the bonded warehouses. Guild leadership has historically cultivated careful relationships with both Assembly commercial standards offices and the Confluência Guild Delegate Council, and has consistently opposed any formal harmonization of those standards on the grounds that harmonization is a matter for Assembly deliberation, not bilateral arrangement. The practical effect of that position is to preserve the translation gap the Guild exists to service.
|
||||
|
||||
**Mercado Travessia (corporate headquarters)** maintains a political presence that is distinct from but connected to the Brokers' Guild. Mercado's procurement scale and its relationships with south_reach cooperative suppliers give it considerable informal influence over how south_reach goods are documented for core market entry. The boundary between Mercado's commercial interests and the Guild's standard-setting function is less clean than either institution's formal charter suggests.
|
||||
|
||||
The **Assembly Regional Compliance Office** has expanded its Travessia presence steadily over the past century as south_reach trade volume has grown. Its relationship with the Brokers' Guild is formally cooperative and quietly adversarial — the Compliance Office periodically advances proposals for documentation standard updates that would shift interpretation authority from Guild certification toward Assembly administrative determination. The Guild contests these through the Registry process at Tessera. Each contested determination is archived there. The accumulation is slow.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
Travessia maintains the translation gap between south_reach cooperative commercial norms and Assembly standards with genuine professional expertise. What is not discussed publicly is the degree to which that expertise has, over four centuries, produced a documentation framework that is specifically legible to the Guild and specifically opaque to anyone approaching it from outside.
|
||||
|
||||
The bonded warehouse documentation practices that have accumulated here are technically compliant with both frameworks — compliant enough that no challenge has succeeded. They are not, however, neutral. The particular ways that cooperative manifests are translated into Assembly-standard documentation consistently round certain quantities in particular directions, classify certain categories of cooperative relationship in ways that the originating cooperatives would not recognize, and produce customs valuations that have, over time, been more favorable to inward-flowing capital than outward-flowing cooperative exports. Whether this accumulated drift is conscious policy, institutional habit, or the natural sediment of four centuries of individually reasonable documentation decisions, no outside auditor has been given the access required to determine. The Guild does not grant external audit access to documentation frameworks that are by its charter protected as certified professional practice.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
A mid-career Mercado procurement analyst has discovered that her team's south_reach supplier classification database contains a ghost category — a documentation tier that does not appear in any public Mercado charter, routes through a bonded warehouse sub-account registered in GJ 33, and has been quietly clearing shipments for at least thirty years.
|
||||
|
||||
---
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
The junction topology with wave_2 settlement at hop 3 is consistent with Travessia's founding logic. Wave_2 settlers explicitly selected high-connectivity systems for functions requiring bilateral access, and a system positioned between the south_reach's dominant hub at Confluência (hop 4) and the core's institutional hub at Tessera (hop 2) provided precisely the structural position the translation function required. Four apertures — connecting to Tessera, Confluência, and the outer south_reach corridor toward GJ 33 and GJ 299 — represent the minimum viable junction topology for the system's role: two inward connections, two outward.
|
||||
|
||||
The K5V stellar match with Confluência's K4 Ve is relevant to local self-image. Travessia's light is close enough to Confluência's that south_reach visitors experience the system as immediately familiar, which Travessia's civic identity leans into. Core visitors find the light slightly warmer than expected, which is a known and gentle orientation tool the system's hospitality sector deploys without irony.
|
||||
|
||||
---
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_042
|
||||
**GJ 117** | M-type | deep_frontier
|
||||
# GJ 117
|
||||
**GJ 117** | M-type | east_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -8,26 +8,37 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K1V · 33.8 ly |
|
||||
| **Star** | M1V · 33.8 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | unsettled |
|
||||
|
||||
---
|
||||
|
||||
GJ 117 is an empty through_route at the edge of the east_reach — two apertures, one toward GJ 434 and through it toward Taishan, one toward GJ 211 in the deep corridor. The M-dwarf is a dim red primary with a stable habitable zone and no obvious settlement barrier. The surveys were done. Nothing was wrong. No one came.
|
||||
|
||||
The timing was unfavorable. The east_reach push extended this corridor during an era of confident expansion, but the systems that might have seeded settlement here had their populations absorbed into closer, more connected communities during the Secession period's economic contraction. GJ 117 remained on the charts as an open route rather than a destination.
|
||||
|
||||
At hop 7, it sees genuine transit traffic — vessels moving between the east_reach's outer corridors and the deep frontier systems beyond GJ 211. Most of that traffic passes through without slowing. The in-system passage between apertures is clean and unremarkable. Navigation broadcasts from the automated relay indicate no anomalies. The relay's most recent log entry is current; someone, somewhere, is still maintaining it — possibly the Commission through Taishan, possibly on automated schedule with human oversight in name only.
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
None. No population, no active resource extraction.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No faction presence. Apertures and relay registered to Commission infrastructure. Maintenance accountability sits with the east_reach administrative structure rooted at the corridor's junction systems.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
Not applicable — no population to keep silence.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
Transit logs at GJ 117 show a consistent but unexplained pattern: a vessel identifying as a Commission survey ship has been transiting the system once every three months, on a precise schedule, for at least the past seven years. No survey program matching the identifier exists in the public register.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
Unsettled through_route at hop 7 with no settlement barrier is a mild anomaly; justified by historical timing rather than physical obstacle. The transit connection between GJ 434 and GJ 211 makes it structurally significant despite being empty.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_285
|
||||
# Knotenpunkt
|
||||
**GJ 1235** | K-type | deep_frontier
|
||||
|
||||
---
|
||||
@@ -8,26 +8,41 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | k-m · 33.1 ly |
|
||||
| **Star** | K5V · 33.1 ly |
|
||||
| **Gates** | 3 aperture · junction |
|
||||
| **Settlement** | wave_2 |
|
||||
|
||||
---
|
||||
|
||||
Knotenpunkt — "junction point" in German — is precisely what its name describes, and has been for four hundred years. Three apertures. Three corridors meeting at hop 7, in the deep frontier, at a distance from the Reach's center that most people only reach by necessity. No single corridor owns Knotenpunkt, and none can afford to ignore it. It is the oldest deep_frontier junction, founded in the Trade Expansion era when the Reach was still willing to invest heavily in infrastructure at extreme range.
|
||||
|
||||
The K-type primary — a dim, stable star in the lower K range — provides little spectacle. The system's interest is entirely architectural: a transit hub at the intersection of three routes, each leading somewhere different, each carrying different kinds of traffic. GJ 142, GJ 324A, and GJ 83.1 all converge here, making Knotenpunkt the point through which a surprising proportion of deep_frontier movement must pass. At four hundred years, the transit infrastructure is overbuilt for the current traffic volume — the original planners expected more — but it remains functional and is maintained because the cost of allowing it to fail would be paid by every system in the surrounding network.
|
||||
|
||||
What four centuries at a junction does to a community is particular. The people here are neither rooted agriculturalists nor cosmopolitan traders, but something that grew from hosting both: a transactional culture that maintains strict neutrality between the corridors it connects, holds opinions about everything but expresses them sparingly, and has developed an acute sensitivity to changes in the traffic patterns that constitute their local economy.
|
||||
|
||||
Commission authority at this depth is nominal — a post exists, personnel rotate through on extended tours, and the bureaucratic relationship with the main Reach is functional but slow. The transit authority that Knotenpunkt's own civic structure operates carries more practical weight.
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Knotenpunkt imports food from its corridor connections — it produces little of its own — along with manufactured goods, medical supplies, and the specialized transit hardware that keeps three-aperture junction infrastructure operational. Its export is service: transit handling, cargo bonding, refueling, crew accommodation. The balance has been roughly stable for two centuries.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The Knotenpunkt Transit Authority is the dominant institutional presence, a local civic body with several centuries of accumulated legitimacy in managing the junction's three-corridor interface. It predates the Commission post by over a century and has far more operational authority.
|
||||
|
||||
Trading houses from all three connecting corridors maintain representatives here. The resulting commercial environment is competitive and closely watched; neutrality is enforced informally through reputational pressure as much as formal rule.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The terms under which the original wave_2 founding charter allocated transit authority governance to what became the KTA rather than to any single corridor's political structure. There is a version of those negotiations in the KTA archive that differs in several material respects from the version in the Commission's records.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
GJ 324A, one of the three corridor connections, has seen a significant decline in transit volume over the past three years — a reduction that Knotenpunkt's traffic analysts cannot explain from the publicly available information about that corridor's economic activity.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
Wave_2 three-aperture junction at hop 7 is exceptional — the deep_frontier junction has no parallel in the network for age combined with connectivity. Its founding during the Trade Expansion era reflects how aggressively the Reach once projected infrastructure before Secession and contraction reshaped priorities.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_264
|
||||
# Haltefenn
|
||||
**GJ 1248** | M-type | west_reach
|
||||
|
||||
---
|
||||
@@ -14,20 +14,35 @@
|
||||
|
||||
---
|
||||
|
||||
Haltefenn is among the oldest continuously inhabited settlements in the west reach. Wave_2 establishment puts its founding at roughly four hundred years ago — predating most of the corridor systems that now stand between it and Gateway, predating the trade expansion institutions that shaped the corridor's cultural consensus, and predating the administrative frameworks that later arrivals take as background fixtures of Reach life. The name is Low German: "halt" as in a stopping point, "fenn" as in fen or bogland. The original settlers were describing what they found, not what they intended to build. They found a low, wet, cloud-covered world with continental shelves barely above sea level and an extraordinary depth of accumulated organic matter. They stayed because fuel was immediately available and because the star — a transitional object sitting at the boundary between K and M classification, dim and steady and ancient — made the planet temperate enough to work in without environmental systems.
|
||||
|
||||
The world is a bog planet. Not metaphorically, not in one region: the dominant terrain type from pole to equator is wetland in various configurations — raised bogs, blanket bogs, estuarine fens, shallow lake systems choked with sedge. Dry land exists at higher elevations, and the settlements are built there, but the productive economy has always been the peat below. Four hundred years of extraction have barely dented the deposit base. The peat beds run dozens of meters deep in the central continental zones, compressed organic layers going back hundreds of thousands of years. Haltefenn exports dried and processed peat fuel — compressed blocks branded under the mark Fennkohle — to the inner corridor through GJ 453, where it finds buyers in agricultural communities that run low-technology heating systems. It is not a glamorous product and the trade volumes are modest, but they have been consistent for four centuries.
|
||||
|
||||
The community has the particular character of very old, very stable, very undisturbed settlements: deep local custom, strong oral tradition, some institutional forms that have no parallel elsewhere in the corridor because they developed in isolation before the corridor's norms arrived. The calendar system used for agricultural and harvest planning is locally derived — the star's unusual spectral class produces a light quality that settlers noticed affects plant growth cycles differently than most K-type worlds, and four centuries of adaptation to that light have produced farming schedules and festival timing that visitors find disorienting. The community celebrates the Winterfenn — a multi-day period around the deepest seasonal darkness — with practices that predate any organized religious institution in the west reach.
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Haltefenn is substantially self-sufficient in food — the fen ecology supports both cultivated plots on the high ground and a sustainable harvest of wetland species that have become dietary staples over four generations of adaptation. The settlement imports manufactured goods, technical components, and luxury items through GJ 453, but the dependency is lighter than most corridor systems of comparable population. Wave_2 settlers arrived with deep technical knowledge and the community has maintained a repair-and-fabricate culture that reduces import needs. Some components are simply made locally to locally developed specifications.
|
||||
|
||||
Outbound: Fennkohle compressed peat fuel blocks, dried wetland botanicals used in medicines and flavorings, and a modest volume of hand-manufactured goods — carved peat-wood artifacts, woven fen-grass textiles — that have developed a niche collector market among antiquarians in inner-corridor systems who value the pre-consensus craft traditions.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
Haltefenn has no faction presence in the corridor-standard sense. There is no Commission post — the aperture facility is operated by a locally staffed transit cooperative that predates the Commission's reach to this depth of the west corridor and has a grandfather arrangement recognizing its operating authority. The Assembly representative for this system is a formal position held by a community elder whose actual engagement with Assembly processes consists of receiving written communications twice per year and filing acknowledgment forms.
|
||||
|
||||
The community governing structure is a council of household heads — Hausrat in local usage — that makes decisions by consensus with customary veto rights for long-established families. The Brenner families, who have held the primary peat extraction concessions since wave_2 founding, carry disproportionate weight in council deliberations. This is understood and accepted as a feature of the system, not a corruption of it.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The pre-settlement survey records. Haltefenn's founding documents are unusually sparse compared to other wave_2 systems. Standard survey protocol required prospecting reports, ecological assessments, and habitability certifications before a settlement license was issued. Haltefenn has the license but not the supporting documentation — the records were either lost in transit, never filed, or filed and subsequently removed. The community does not discuss this. Asked about it, Hausrat members will note that the world is clearly habitable and clearly settled and that the question of old paperwork is not one they have any interest in. Whether the survey anomaly is administrative error or something more deliberate is unknown.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
A researcher cataloging pre-consensus craft traditions arrived at Haltefenn fourteen months ago to document the Winterfenn observances and has not filed any communications since — neither completion nor departure.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
The k-m transitional stellar class is unusual and reflects a genuine edge-case object rather than a catalog error. The ambiguity in the stellar classification is part of the planet's character: the light quality is neither standard K nor standard M, which contributes to the off-calendar agricultural timing and the slight foreignness visitors notice. Wave_2 settlement at this depth from Gateway is explained by the system's position in a different expansion direction than the dominant corridor — it was reached early via a different route before the current corridor topology was established.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_208
|
||||
# Saudade
|
||||
**GJ 1267** | M-type | deep_frontier
|
||||
|
||||
---
|
||||
@@ -8,28 +8,51 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K7V · 44.1 ly |
|
||||
| **Star** | M · 30.1 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_3 |
|
||||
|
||||
---
|
||||
|
||||
Saudade is a Portuguese word with no adequate translation. The closest approximation in any common Reach language is something like "the longing for something lost that may never return" — but that rendering loses the specific quality that makes the word irreplaceable: the saudade is not grief, and it is not hope, and it is not quite nostalgia. It is the feeling of a wound that has healed beautifully and still aches.
|
||||
|
||||
The community that bears the name understands this completely.
|
||||
|
||||
Three hundred years ago, Recanto — one hop inward at GJ 556 — was settled by political exiles: a faction expelled from an early Reach institutional consolidation, pushed to the frontier with their families and their records and their conviction that the institutions that expelled them had made a historical error. The families who founded Saudade were not expelled. They came voluntarily, one hop further in, to remain within reach of the people they could not follow into exile without becoming exiles themselves. They were the ones who stayed — who kept their positions, their property, their standing — and who used that standing to maintain a corridor of supply and communication to the expelled community they could not publicly defend.
|
||||
|
||||
Three centuries later, Saudade is still there. Recanto is still there. The political circumstances that produced the exile are three hundred years resolved, the original institutional actors long dead or transformed beyond recognition. What remains is the relationship: two communities one hop apart, bound by a loyalty that outlasted its occasion.
|
||||
|
||||
The difficult thing about Saudade — the thing the community lives with and rarely discusses — is that the loyalty has become the identity in a way that no longer has a clear object. The exiles of Recanto have been in exile so long that it is no longer exile; it is home. The grievance that Saudade existed to support has resolved into cultural memory. The corridor of supply and communication persists, but what it carries now is commerce and kinship, not political sustenance. The saudade in the name points at something that is still felt and no longer quite locatable — the absence of the thing that made the community's presence meaningful.
|
||||
|
||||
This gives Saudade a quality that visitors find difficult to name. The community is functional, stable, economically adequate, culturally coherent. It is also, at some level, oriented toward a loss that is not recent and not personal and not amenable to resolution. The people here are warm, careful, and slightly preoccupied with something that has nothing to do with whatever you came to discuss.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Agricultural produce and basic manufactured goods via the corridor to Recanto, which in turn connects inward toward the mid-Reach. Saudade's own agricultural output supplies a significant portion of the Recanto-corridor food chain. The system's vulnerability is that its economic identity is corridor-dependent — if transit through this section of the deep frontier declined significantly, Saudade would lose both its economic function and its primary social connection.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No dominant institutional presence. The community maintains nominal Assembly registration and Commission compliance. The relationship with Recanto's governance structure is informal but functional — decisions affecting both communities are discussed across the single hop with a regularity that has no formal procedural basis but has operated continuously for three centuries. A quiet thread of Guardians of Autonomy sympathy runs through both communities, rooted in the original expulsion and the communities' shared history of institutional wariness.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The specific institutional consolidation that produced Recanto's founding exile. The community knows the history — it is the founding event — but discussing the specific decisions and actors involved is considered the kind of history that belongs to the families rather than to strangers. Visitors who ask about it will receive polite evasion. The history is not shameful; it is private.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
A community three centuries into maintaining a loyalty that outlasted its occasion — still facing inward toward an exile that has become a home, carrying the ache of a purpose that was fulfilled and left them without one.
|
||||
|
||||
---
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 10
|
||||
- **Adjacent Systems:** GJ 556, GJ 524
|
||||
- **Adjacent Systems:** GJ 524, GJ 556 (Recanto)
|
||||
|
||||
@@ -1,6 +1,18 @@
|
||||
# PLACEHOLDER_286
|
||||
# Echternach
|
||||
**GJ 127B** | M-type | west_reach
|
||||
|
||||
Four hundred years. Hop thirteen. The Luxembourgish community at Echternach is one of the most isolated settled systems in any named sector, and it is still here, and it still knows exactly who it is.
|
||||
|
||||
The name comes from the abbey town on the Sauer River — the dancing procession town, the pilgrimage site, the place in the old country that people from Echternach's founding community had been naming things after for five hundred years before they left Earth. They brought the name here because they were Luxembourgish and because Luxembourgish people have specific opinions about naming things correctly, which means not naming them German and not naming them French and recognizing that the space between those two large neighbors is where a distinct identity lives. Echternach, in the Reach, is that insistence made permanent.
|
||||
|
||||
The founding wave came during the Wave 2 expansion, four centuries ago, when the west_reach corridor was being pushed outward and settlers were willing to go far if the system at the other end was worth settling. GJ 127B offered a habitable primary world — cooler than Earth-standard, with longer winters and shorter growing seasons, but genuinely livable — and the Luxembourgish families who arrived found that the world's character matched their cultural instincts: demanding conditions that rewarded careful, patient work. They stayed.
|
||||
|
||||
Being at hop thirteen means that the institutions of the corridor reach Echternach in attenuated form. The Assembly is real in the sense that Echternach's administrative council is registered with it and files the required reports. The Commission exists in the sense that a Commission inspector arrived once, about ninety years ago, conducted a standard review, found nothing worth noting, and left. The Concord's governance reaches here as a legal framework rather than an operational reality. What governs Echternach is Echternach: the administrative council, the agricultural and manufacturing cooperatives, and the set of community expectations that four hundred years of close-knit isolation have produced and refined.
|
||||
|
||||
The primary world has sufficient stellar warmth to allow Echternach's founding community to have developed what can only be described as its own cuisine, its own architecture, its own dialect of the Luxembourgish language that has drifted in specific ways from the standardized versions maintained in inner-corridor cultural archives. The dialect is not mutually unintelligible with standard forms, but a Luxembourgish speaker from closer to the Gateway will notice. Echternach residents will explain the differences with the patience of people who have been explaining this for four hundred years.
|
||||
|
||||
The economy is mixed — mixed farming, small-scale manufacturing, and the corridor service economy that any two-aperture through-route system develops. The transit volume through Echternach is modest. The system is not on a high-traffic corridor segment. The goods that pass through are mostly moving outward through Langemark (GJ 42) toward Bout du Chemin (GJ 282A), and the trade relationship between Echternach and the communities further along the corridor has the character of a long-standing arrangement between parties who have negotiated the same terms many times and prefer not to renegotiate them.
|
||||
|
||||
---
|
||||
|
||||
## System Profile
|
||||
@@ -15,19 +27,24 @@
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Echternach imports manufactured goods, medical hardware, and specialty agricultural inputs from systems inward. The community's own manufacturing capacity is sufficient for most maintenance and construction needs but not for high-precision or high-technology production. The single most significant import category is medical hardware — the community has a population that has been largely self-sustaining for four hundred years, and maintaining access to Lattice-grade medical systems at this distance requires sustained import relationships. Exports include agricultural products, small-batch manufactured goods, and handcraft items that have acquired something like cult status in west_reach collector communities — Echternach-made objects are recognizable by material and technique, and the fact that acquiring them requires either a visit or a very specific freight arrangement has contributed to that status.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No Reach faction has a standing presence. The administrative council is the government. The council's chair has been, for the last sixty years, Marguerite Funck-Schmit, who is not Perpetual but has been on the council in various capacities for forty years and shows no signs of stepping back. Her family has been in Echternach since the fifth generation after founding. The council maintains working relationships with Alshain's transit authority for the inbound aperture and with Bout du Chemin's equivalent for the outbound, and those working relationships are more diplomatically complex than the distance between the systems would suggest — four centuries of adjacent community history has produced its own accumulated texture of agreements, grievances, and mutual dependence.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What Echternach does not discuss outside the community: the system's population has been in slow decline for about a hundred and twenty years. Not crisis decline — nothing that would trigger alarm from an Assembly population monitoring system — but a steady, multi-generational trend of young adults leaving for systems inward and not being replaced at the same rate by arriving settlers. The community's response has been to densify its social infrastructure rather than its population: more investment per person, stronger institutional ties, deliberate cultural preservation programs. The administrative council knows the numbers and tracks them carefully and has never formally reported the trend to any outer institution. The community's position is that it is managing the situation, which is true, and that outside attention would not improve the management, which is also probably true.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
A four-hundred-year-old community at the edge of organized space has been quietly losing population for over a century, and the people who know refuse to tell anyone.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
M-type header per the database classification. The READ-ONLY profile shows G7V — the stellar catalog designation, indicating a warm lower G-type or upper K-type depending on classification convention. The habitable primary world character described is consistent with this stellar profile. Wave_2 at hop 13 is distant but not anomalous for the Wave 2 expansion period, which pushed the west_reach corridor to its current organized extent. The through-route topology correctly reflects the corridor role: GJ 4056 on one side, Langemark (GJ 42) on the other.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,6 +1,8 @@
|
||||
# PLACEHOLDER_079
|
||||
# Sertão
|
||||
**GJ 138** | M-type | deep_frontier
|
||||
|
||||
The name means "backcountry," which is what the founders saw when they arrived: open country, unworked, far from anything organized. It was not a complaint. They came looking for backcountry and they found it. Two centuries of Portuguese-heritage agricultural settlement have worked the soil and adapted the crops and built the kind of community that does not distinguish between farming and identity. Sertão is the corridor beyond GJ 92, and the people here know what they are.
|
||||
|
||||
---
|
||||
|
||||
## System Profile
|
||||
@@ -8,28 +10,35 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | G1V · 39.2 ly |
|
||||
| **Star** | M · 29.6 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_4 |
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Sertão exports modest agricultural surplus toward Nascente and the inner south corridor. The M-dwarf cultivation techniques here are common across the Portuguese deep corridor — adapted seed stock, supplemental lighting for sensitive crops, irrigation calibrated for the specific precipitation patterns of the habitable world. The community is not innovating; it is doing something well-understood at the frontier end of a corridor that has been doing it for longer than Sertão has existed.
|
||||
|
||||
The dependency is in the direction of manufactured components, medical supplies, and the replacement parts for equipment that can't be locally fabricated. The supply line to GJ 92 and eventually Nascente is reliable enough but slow. The community plans lead times in months, not weeks. This is accepted as the cost of being where they chose to be.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The Lattice Commission is present in the same way it is present across the Portuguese deep corridor: a filed registration, compliance schedules that are met on the community's timeline, no resident agents. The Commission's interest in Sertão is minimal; the community's interest in the Commission is equally minimal.
|
||||
|
||||
The Guardians of Autonomy have no formal chapter here, though the community's politics are broadly sympathetic. The practical position is that organizing in the name of autonomy is redundant when the practical reality is already autonomous. Nobody from the inner corridor tells Sertão what to do. The Guardian framework is for places where that isn't true yet.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What Sertão does not discuss with outsiders: the extent to which the community has modified traditional Portuguese agricultural practices in ways that depart from the inner corridor's maintained heritage traditions.
|
||||
|
||||
The inner Portuguese communities — Nascente, Travessia, and the settled systems closer to the core — maintain something like a living heritage practice: named crop varieties that descend directly from Earth lineages, cultivation methods preserved for cultural continuity as much as productivity. Sertão started from the same tradition but has been adapting under M-dwarf conditions for two centuries with minimal contact with those heritage institutions. The current agricultural practice has drifted. Some of the changes are improvements. Some are irreversible departures. The community does not regard this as a problem. Whether the inner corridor communities would agree is a question Sertão has not invited them to answer.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
Sertão's agricultural practices have diverged significantly from the Portuguese corridor's maintained heritage traditions over two centuries of M-dwarf adaptation; the community has not told anyone, and no one from the inner corridor has visited recently enough to notice.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 8
|
||||
- **Adjacent Systems:** GJ 204, GJ 92
|
||||
- **Adjacent Systems:** GJ 204 (Pedra Funda), GJ 92
|
||||
|
||||
@@ -1,6 +1,8 @@
|
||||
# PLACEHOLDER_137
|
||||
# Leuchtturm
|
||||
**GJ 142** | G-type | deep_frontier
|
||||
|
||||
The name means "lighthouse," and it was chosen because the system's G-type star is conspicuous this far out where M-dwarfs dominate the map. The founders who named it were astronomers, and they meant the word seriously: Leuchtturm is a reference point, a bright anomaly on the deep frontier, a place from which other things can be measured. Three hundred years of continuous observation have made it exactly that.
|
||||
|
||||
---
|
||||
|
||||
## System Profile
|
||||
@@ -8,28 +10,37 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K5V · 40.7 ly |
|
||||
| **Star** | G · 31.7 ly |
|
||||
| **Gates** | 2 aperture · spur_end |
|
||||
| **Settlement** | wave_3 |
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Leuchtturm does not generate the agricultural surplus that corridor systems like Droëland achieve. The G-type star is warmer than most deep frontier systems, which is an astronomical advantage, but the habitable world has limited arable zones and a small founding cohort that never grew into a large agricultural population. The community has always been sized for research, not production, and has accepted the supply dependency that comes with that choice.
|
||||
|
||||
Food comes in from Knotenpunkt and the inner corridor. Leuchtturm exports data — processed astronomical records, deep frontier survey coordinates, spectroscopic archives that the community has been building for three hundred years. Whether this is an economically rational trade is a question that frontier agricultural systems occasionally raise with something approaching exasperation. Leuchtturm's researchers regard the question as a category error. They did not come here to grow crops.
|
||||
|
||||
The observatory infrastructure represents the community's primary capital asset and its dominant supply dependency. Precision optical instruments, cryogenic storage for data media, the relay arrays that transmit records inward to the inner corridor archives — all of this requires manufactured components that Leuchtturm cannot produce locally. Disruption to the supply line is an existential concern not for food but for the continuation of the work. The community maintains equipment reserves with this in mind.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The Veil Institute has an informal relationship with Leuchtturm that is not classified as a formal presence but functions as one. Institute researchers use Leuchtturm's observational archives extensively; several of the community's senior astronomers have been affiliated with Institute projects at various points in their careers; the equipment calibration standards the community uses for its deep frontier surveys were originally developed by Institute researchers working with early Leuchtturm data. The relationship is collegial and mutually beneficial, conducted through professional networks rather than institutional agreements.
|
||||
|
||||
The Lattice Commission maintains a minimal presence. Leuchtturm's small population and academic character do not generate significant regulatory activity. Commission visits are infrequent and primarily administrative. The community regards this as an appropriate arrangement.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What Leuchtturm does not discuss openly: certain anomalous readings from the deep frontier surveys, classified internally as "unresolved instrumental artifacts" in the community's archival system.
|
||||
|
||||
The designation is technically accurate — the readings have never been definitively explained, and they may genuinely be instrumental. What the community does not discuss is how long some of these "unresolved artifacts" have been present in the archive, how many independent observation runs have confirmed them, and why three generations of the community's best instrument specialists have not been able to attribute them to a known instrumental source. The readings do not look like stars. They do not look like anything the community's models predict should be present in those sky positions. They are present, consistent, and unexplained. The archivist who made the current classification did so fifteen years ago and has not changed it since.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
Leuchtturm's three-century astronomical archive contains a set of consistent anomalous readings that three generations of researchers have been unable to attribute to any known source, classified as "unresolved instrumental artifacts" and never submitted to the wider scientific community.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 8
|
||||
- **Adjacent Systems:** GJ 425A, GJ 1235
|
||||
- **Adjacent Systems:** GJ 1235 (Knotenpunkt), GJ 425A
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_280
|
||||
# GJ 146
|
||||
**GJ 146** | M-type | deep_frontier
|
||||
|
||||
---
|
||||
@@ -8,28 +8,33 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K7V · 44.4 ly |
|
||||
| **Star** | M · 34.2 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_3 |
|
||||
| **Settlement** | unsettled |
|
||||
|
||||
---
|
||||
|
||||
GJ 146 is a corridor node between Randgebiet at GJ 349 and the mineral-rich but unclaimed GJ 853A. A dim M-dwarf, a narrow habitable zone, a primary world that survey teams have described across multiple visits in the same careful language: marginally habitable, breathable atmosphere, cold, low biodiversity, "adequate" — the particular survey-report word that means technically qualifying and practically discouraging.
|
||||
|
||||
The system has been surveyed, assessed, and set aside more times than the archive count reflects, because some survey visits were conducted by corridor vessels rather than dedicated survey teams and were not formally filed. What has been filed consistently points in the same direction: a world you could live on with significant infrastructure investment, in conditions that would require continuous energy input to maintain acceptable warmth and light levels, providing nothing that isn't available more easily and more comfortably at closer distances.
|
||||
|
||||
Transit vessels use GJ 146 as a corridor waypoint. The horizon station ticks over. The cold primary world turns below. Nothing human lives there.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
None.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
No faction presence. Transit corridor between Randgebiet and the systems beyond.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
---
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 10
|
||||
- **Adjacent Systems:** GJ 349, GJ 853A
|
||||
- **Adjacent Systems:** GJ 349 (Randgebiet), GJ 853A
|
||||
|
||||
@@ -1,6 +1,8 @@
|
||||
# PLACEHOLDER_138
|
||||
# GJ 167
|
||||
**GJ 167** | K-type | deep_frontier
|
||||
|
||||
A transit corridor without residents. GJ 167 connects the unsettled spur off Knotenpunkt to Helle Wacht — a through_route that exists because the corridor geometry required it, not because anyone chose to live here. The system is a gap in the map: gates, automated relay, and nothing else. Survey records are on file. No settlement attempt was ever made.
|
||||
|
||||
---
|
||||
|
||||
## System Profile
|
||||
@@ -8,28 +10,29 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K5V · 42.5 ly |
|
||||
| **Star** | K · 36.4 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | unsettled |
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
None. No resident population.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No permanent faction presence. GJ 167 functions as a navigation waypoint. Vessels transiting between GJ 324A and Helle Wacht pass through without stopping. The automated relay hardware is the only operational infrastructure in the system.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
None recorded.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
GJ 167 is one of two consecutive unsettled through_routes between Knotenpunkt and Helle Wacht — a corridor chain with gates in every system and people in none of them until Helle Wacht, which was settled by people who wanted to be as far from institutional reach as the corridor allowed.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 9
|
||||
- **Adjacent Systems:** GJ 324A, GJ 598
|
||||
- **Adjacent Systems:** GJ 324A, GJ 598 (Helle Wacht)
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_134
|
||||
# Posto Avançado
|
||||
**GJ 169** | M-type | deep_frontier
|
||||
|
||||
---
|
||||
@@ -8,26 +8,37 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K7V · 37.2 ly |
|
||||
| **Star** | M0V · 37.2 ly |
|
||||
| **Gates** | 1 aperture · dead_end |
|
||||
| **Settlement** | wave_4 |
|
||||
|
||||
---
|
||||
|
||||
Posto Avançado — "forward post" in Portuguese — carries its function in its name and has never pretended to be something else. Two hundred years ago, a Portuguese-heritage settlement group established this community at the end of a spur off GJ 482B with a specific intent: to push the habitation frontier one more system outward, plant something that would survive, and call that a success. They succeeded, which was the easier part. Surviving two centuries of deep_frontier isolation, with one gate, no through traffic, and the distance from everything that "forward post" implies — that took something more.
|
||||
|
||||
The M-dwarf primary is dim and stable, warm enough to support a modest habitable zone but requiring the agricultural engineering common across red-dwarf corridor communities. The community has had two centuries to refine that engineering, and the food culture that developed from those constraints — dense, preserved, seasonally precise — is one of the things locals take genuine pride in.
|
||||
|
||||
At hop 7, Commission authority is minimal. A charter post exists in name; in practice, a Commission vessel visits annually and the rest of the time Posto Avançado governs itself through a council that has been continuously operating for two hundred years. The institutional memory runs deep. The people here know their own history better than any outside authority does, and they treat outside interest — commercial or administrative — with a calibrated wariness that has served them well.
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Posto Avançado is the most supply-isolated system in its immediate cluster. Everything manufactured that isn't locally produced must come through GJ 482B and along the deep_frontier corridor beyond. Lead times are significant and planning horizons are long. The community has compensated by developing strong local fabrication capacity and by being selective about what it considers essential.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
A community council governs, with a separate resource allocation board that manages the supply line relationship with GJ 482B. The Commission post is staffed part-time. No external trading house maintains a permanent representative — the traffic volume doesn't justify it.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The founding conditions. The original wave_4 settlement petition contains a codicil, now sealed in the community archive, explaining why this specific location was chosen over two other candidate systems at comparable distance. The reasons in the public record are agricultural suitability. The codicil describes something different.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
The resource allocation board has recently issued an unexplained reduction in the supply request transmitted to GJ 482B — less than the community's documented consumption figures would warrant, ordered without explanation. Someone on the board knows why. Nobody else does.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
Wave_4 dead_end at hop 7 is consistent with the deep_frontier's Portuguese-heritage settlement pattern — communities founded as deliberate outposts rather than opportunistic settlements, with the understanding that they would be remote by design.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,6 +1,8 @@
|
||||
# PLACEHOLDER_258
|
||||
# Tiefenbach
|
||||
**GJ 174** | K-type | deep_frontier
|
||||
|
||||
The name means "deep creek" — modest, topographic, the kind of name that people give a place when they are focused on living in it rather than describing it. The founders came here three hundred years ago during the early Secession upheaval, having read the political situation in the inner Reach correctly and decided to be elsewhere when it resolved. They built a community designed from the first year to sustain itself through instability it could not predict and would not be close enough to experience directly. Three hundred years later, their descendants are still here.
|
||||
|
||||
---
|
||||
|
||||
## System Profile
|
||||
@@ -8,28 +10,35 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K3V · 43.0 ly |
|
||||
| **Star** | K · 30.5 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_3 |
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Tiefenbach is agriculturally self-sufficient. The K-type star gives more light than the M-dwarfs that dominate the deep frontier, which has meant steadier agricultural yields and somewhat less intensive adaptation work than the corridor systems further out. The founding cohort arrived with agricultural expertise and institutional memory of what the first generation would require, and they built accordingly.
|
||||
|
||||
The dependency structure that the founders designed has remained intact: local production covers food and most common materials; external supply provides manufactured components and medical equipment on a schedule measured in years rather than months. The emergency reserve protocols established in the founding generation are still in operation. They have been reviewed in every generation. The review process is part of the community's institutional calendar.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
Tiefenbach has minimal external institutional presence. The Compact of Westphalia's framework covers the community nominally, but the distance and the community's founding disposition toward self-reliance mean that Compact affiliation is more historical than operational. The community does not call on the Compact for governance functions. The Compact does not impose them.
|
||||
|
||||
The Lattice Commission has a compliance record for Tiefenbach that is clean and infrequently audited. The community maintains its compliance filings on schedule. Commission agents have not visited within the current generation's experience.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What Tiefenbach does not discuss openly: the unresolved question, in every generation, of whether the founding decision was prescience or cowardice.
|
||||
|
||||
The founders left the inner Reach during the Secession upheaval. They predicted that the situation would become unpleasant, and they were correct — the Secession period was difficult for inner Reach communities in ways that Tiefenbach, at deep frontier distance, did not experience. This outcome vindicates the decision in practical terms. Whether leaving was the right thing, whether a community with Tiefenbach's resources and capabilities should have stayed and participated in the political outcome rather than withdrawing from it, is a question that each generation has addressed and not answered. The founding narrative celebrates the founders' judgment. The community's private discourse is more equivocal. Nobody talks about this with outside visitors.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
Tiefenbach was founded during the Secession upheaval by families who predicted correctly that the inner Reach was about to become unpleasant; three centuries later, their descendants celebrate the decision and privately debate, in every generation, whether they should have stayed.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 9
|
||||
- **Adjacent Systems:** GJ 189, GJ 69
|
||||
- **Adjacent Systems:** GJ 189 (Altgrund), GJ 69
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_078
|
||||
# GJ 177
|
||||
**GJ 177** | M-type | deep_frontier
|
||||
|
||||
---
|
||||
@@ -8,26 +8,33 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | G3V · 43.3 ly |
|
||||
| **Star** | M · 35.3 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_4 |
|
||||
| **Settlement** | unsettled |
|
||||
|
||||
---
|
||||
|
||||
The survey reports for GJ 177 are thorough and unenthusiastic. This is not a criticism of the survey teams, who were professional and careful; it is a description of what they found.
|
||||
|
||||
The primary world is habitable. Atmospheric composition is adequate. Temperature ranges are within human tolerance with appropriate infrastructure. Geological stability is good. Water distribution is acceptable. Biodiversity is present, if unremarkable. The surveys note all of this in the standard format, and the standard format makes it clear that nothing here exceeds its parameters in any direction. The world works. It does not exceed working.
|
||||
|
||||
At hop ten on an M-dwarf chain, the system offers nothing that closer, brighter systems do not offer more conveniently. The habitable world does not have the mineral deposits that could attract extraction investment. It does not have the ecological richness that could attract research interest. It does not have a cultural or historical connection to an established corridor community that could anchor a founding cohort. It has adequate conditions and a transit corridor running through it, and that is what the corridor needed.
|
||||
|
||||
The horizon station processes transit. The empty world rotates below. The surveys sit in the archive, complete and sufficient and unlikely to be revisited.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
None.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
No faction presence.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
---
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_256
|
||||
**GJ 183** | M-type | deep_frontier
|
||||
# Waterkant
|
||||
**GJ 183** | M-type | north_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -8,26 +8,37 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K3V · 28.4 ly |
|
||||
| **Star** | M3V · 28.4 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_4 |
|
||||
|
||||
---
|
||||
|
||||
Waterkant sits at the threshold of the Cairn pocket extension — a farming corridor that continues the Dutch-Afrikaans agricultural tradition carried inward from earlier core settlements. The name means "waterside" in Afrikaans, and it fits: the system's habitable world is low and wet, with wide floodplains that draw long shadows under the M-dwarf's rust-orange light. Two hundred years of settlement have turned the original homestead plots into established agri-communes, the kind that barely need managing because everyone already knows their role.
|
||||
|
||||
The system sits between the busier corridor behind it and the younger outposts ahead. Neither a destination nor a true waypoint, it occupies the unglamorous middle of a corridor — a place people pass through without stopping unless they have family here. Which many do. The population is small, generationally rooted, and deeply indifferent to anyone in a hurry.
|
||||
|
||||
Authority is intermittent. Commission representatives pass through on scheduled circuits, and there is a local cooperative council that handles almost everything before it becomes their problem. Disputes over water rights and field boundaries — the oldest kind of disputes humans carry with them — make up most of the docket.
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Waterkant feeds outposts deeper in the Cairn pocket extension. Processed grain, preserved protein cultures, and basic fabrication stock move spinward along the corridor toward Breëvlei and Stilwater. Return traffic is thin — tools, replacement components, the occasional specialist — which gives the system a slightly one-directional feel economically.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The Landbou Raad — an informal agricultural cooperative council — functions as de facto governance for most civil matters. It predates any formal Commission presence by over a century and still handles resource allocation, boundary arbitration, and settlement licensing. The Commission's local liaison holds an office in the main transit node and is politely tolerated.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
Water allocation upstream of the corridor's shared aquifer systems. The Cairn pocket runs on water, and Waterkant sits at a choke point. Neighboring settlements have long memories about dry years.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
A survey team passed through eight months ago with credentials that didn't match any Commission project register — they were measuring something in the aquifer basin, not agricultural yield, and nobody on the Landbou Raad knows who sent them.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
Wave_4 at hop 5 is consistent with the Cairn pocket's incremental push — settled from the inside out, with Waterkant predating the systems it now supplies.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,6 +1,8 @@
|
||||
# PLACEHOLDER_107
|
||||
# Altgrund
|
||||
**GJ 189** | M-type | deep_frontier
|
||||
|
||||
The name means "old ground," which is what four hundred years of continuous settlement produces. Altgrund predates the Compact, predates the Commission, predates most of the institutional architecture that later arrivals took for granted. The founding cohort was not fleeing anything — they arrived before there was anything to flee from. But their age has made them a destination for people who came later with exactly that motivation, and the community has the cultural layering that four centuries of successive arrivals produces.
|
||||
|
||||
---
|
||||
|
||||
## System Profile
|
||||
@@ -8,28 +10,37 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | F7V · 38.0 ly |
|
||||
| **Star** | M · 27.3 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_2 |
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Altgrund produces a modest agricultural surplus and exports it toward the inner corridor. Four centuries of settled M-dwarf agriculture has produced a mature system: worked soil, established cultivars, irrigation infrastructure built and rebuilt across multiple generations. The community has never needed to import food. The reverse is true — Altgrund has periodically served as a supply point for communities further out along the Germanic deep frontier corridor.
|
||||
|
||||
The dependency is in the direction of industrial goods and, more than anything, communication relay maintenance. Altgrund's position at hop 8 places it at the edge of reliable high-bandwidth communication with the inner Reach. Maintaining the relay infrastructure that keeps Altgrund connected to the corridor network is an ongoing capital expense. The community takes it seriously; four centuries of institutional experience have taught them that deep frontier isolation compounds quickly once communication links degrade.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
Altgrund is old enough to have developed its own institutional structures that predate every formal faction in the Reach. The community's governance framework was established before the Concord Assembly existed in its current form, before the Lattice Commission's mandate was formalized, before the Compact of Westphalia was founded. The community has lived through the creation of all of these institutions as an external observer rather than a participant in their founding. This gives Altgrund's leadership a particular quality of institutional perspective — they have seen other communities' institutions arise, grow, and sometimes overreach, and they have managed their relationships with those institutions accordingly.
|
||||
|
||||
The Compact of Westphalia's affiliated communities regard Altgrund as an elder system — a founding reference point for German-heritage deep frontier settlement that is technically outside the Compact's mutual recognition framework but culturally central to its self-understanding. Relations are warm and practically non-binding.
|
||||
|
||||
The Lattice Commission's Altgrund presence is compliant and formal. Four centuries of compliance history give the community an extremely clean record. The Commission treats Altgrund as a model system and has not looked closely at the details of what that compliance actually covers.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What Altgrund does not discuss with outsiders: the terms on which successive waves of crisis refugees were integrated, and what those communities gave up in exchange for settlement rights.
|
||||
|
||||
The community has absorbed at least four separate cohorts of crisis refugees over four centuries — people arriving in disrupted circumstances, without resources, needing settlement rights quickly. Integration has always been successful in the sense that the community has remained stable. What "integration" required in each case — which arriving practices were maintained, which were abandoned, what commitments the arriving cohorts made about governance participation and community precedence — is documented in Altgrund's archives but not discussed. The descendants of those arriving cohorts are fully integrated now. The terms of their integration are, for most of them, unknown. Altgrund's oldest families know. They don't raise the subject.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
Altgrund has integrated four separate waves of crisis refugees across four centuries; the terms of each integration are archived but not discussed, and most of the descendants of those arriving cohorts have no idea what their founders agreed to.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 8
|
||||
- **Adjacent Systems:** GJ 675, GJ 174
|
||||
- **Adjacent Systems:** GJ 174 (Tiefenbach), GJ 675 (Neugrund)
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_100
|
||||
# Puerto Último
|
||||
**GJ 197** | K-type | south_reach
|
||||
|
||||
---
|
||||
@@ -14,20 +14,49 @@
|
||||
|
||||
---
|
||||
|
||||
The name was chosen three hundred years ago and it was accurate then: this was the last port, the terminal point, the place where the route ran out. For most of Puerto Último's history, the settlement sat at the end of a chain that connected it inward through a sequence of systems with no hub — no junction, no place where multiple routes converged — just a series of single-aperture connections reaching back toward the denser Reach. In that topology, Puerto Último was genuinely last: the furthest point from the core in its particular spur, the place beyond which there was nothing.
|
||||
|
||||
That changed approximately forty years ago when GJ 393 — the system one hop inward from Puerto Último — established its wave_5 settlement and began operating as a hub. Encrucijada has five apertures. One of those apertures connects to GJ 197. Puerto Último, which spent two hundred and sixty years as a terminal dead-end in a quiet chain, is now one hop from a hub with connections to four other systems. The route structure around the community has changed more in the last forty years than in the previous two hundred and sixty combined.
|
||||
|
||||
The community is adjusting.
|
||||
|
||||
The G0V star at 41.2 light-years is near the warm end of the G-type sequence, providing good surface conditions on the primary inhabited world — agricultural capacity, adequate luminosity, a biosphere that responded well to the founding generation's introductions. Three hundred years of Spanish-heritage settlement have produced a self-sufficient agricultural community with a specific cultural texture: the names are Spanish, the social structures are Spanish-influenced, the food and the music and the way the community marks its annual cycles reflect three hundred years of a heritage that was brought here deliberately and maintained deliberately. The isolation of the first two and a half centuries was not experienced as deprivation. It was experienced as the condition under which Puerto Último became fully itself.
|
||||
|
||||
The arrival of Encrucijada as a hub has introduced something the community has not had before: regular through-traffic. Vessels that were not headed to Puerto Último but were transiting from Encrucijada toward other connected systems began appearing in the system's gate entry logs at a rate that the horizon station's docking infrastructure was not designed to accommodate. The community's council spent the first decade after Encrucijada's establishment debating whether to expand the docking infrastructure to take advantage of the increased traffic or to maintain the existing scale and treat the traffic as irrelevant. The council chose expansion, and the expansion is ongoing, and the commercial opportunities the expansion has created are real but are also introducing a pace of change that the community's older residents find uncomfortable.
|
||||
|
||||
The comfort and discomfort are not evenly distributed. The families with commercial interests near the gate approach have prospered from the increased traffic. The families whose livelihood is agricultural and whose daily lives are remote from the gate infrastructure have not prospered more than before, and they have watched their community change in ways they did not elect. The council's most contested recent votes have been about the pace and character of the docking expansion. The community is not in conflict, but it is in the process of discovering whether the identity it maintained through two hundred and sixty years of quiet isolation can be maintained through forty years of becoming connected.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Puerto Último's agricultural output is the economic foundation. The G0V star's generous conditions support productive farming, and three centuries of development have produced a food system that supplies the local population comfortably and generates a modest export surplus. The export surplus was historically small — there was limited inbound transit to consolidate with for efficient outward freight — but the Encrucijada hub connection has improved outbound logistics enough that the agricultural export volume has increased materially in the last thirty years. The expanded docking infrastructure has also enabled logistics services for the Encrucijada-bound transit traffic, which is a new revenue line that did not exist before the hub was established. Imports are manufactured goods and technical equipment; the import balance has increased with the community's development investment in the docking infrastructure.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The **Puerto Último Settlement Council** is the community's governing body. The council is elected on a four-year cycle and its membership has historically reflected the agricultural families' demographic majority. The commercial interests concentrated near the gate approach have been underrepresented on the council relative to their recent economic contribution, and there is a formal proposal before the current council to adjust representation weighting. The proposal has been under discussion for three years.
|
||||
|
||||
The Lattice Commission's relationship with Puerto Último has changed since Encrucijada was established. The increased transit volume brought Puerto Último's compliance profile to the attention of Commission logistics analysts in a way that the previous minimal-transit years had not, and the Commission's south_reach regional office has upgraded Puerto Último from the extended-cycle inspection schedule to a standard annual visit. The community's compliance record has been adequate at each annual visit; the transition from extended-cycle to annual inspection is itself experienced by some community members as a consequence of the connectivity they did not entirely choose.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
Three hundred years of near-complete isolation produced a community that handled its own internal disputes through its own internal processes, and the records of those processes are in the community archive rather than in any Commission or Assembly filing. Several of the disputes involve land allocation decisions from the first two centuries that the founding-wave descendants consider settled and the later-wave settlers' descendants consider settled in ways that disadvantaged their predecessors. The disputes are not currently active. The records that could revive them are in the archive, and the archive is accessible to community members but has not been reviewed by any external party.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
A commercial freighter captain who has been running the Puerto Último to Encrucijada route since shortly after the hub opened has recently told the community council that a competitor has begun offering the same route at rates that are commercially impossible to sustain without either a loss-bearing subsidy or access to cargo documentation arrangements that lower the effective cost below the declared rate — and she has a specific theory about which category her competitor falls into, and the theory involves the cargo consolidation infrastructure at Encrucijada that the Commission's understaffed field office has been waiting eight months to audit.
|
||||
|
||||
---
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
The K-type header designation versus the G0V stellar profile is a generation artifact; G0V governs all lore detail. G0V at 41.2 light-years is at the far end of the south_reach's populated range and requires explanation for wave_3 settlement: the founding families likely arrived through a different intermediate topology than the current Encrucijada hub connection, using junction systems in the pre-wave_3 network that have since been bypassed or supplemented. Dead_end at hop 8 with a wave_3 settlement date is the configuration that creates the narrative interest: long isolation followed by abrupt connection, which is the condition Puerto Último is currently navigating.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,6 +1,8 @@
|
||||
# PLACEHOLDER_105
|
||||
# Pedra Funda
|
||||
**GJ 204** | M-type | deep_frontier
|
||||
|
||||
The name means "deep stone" — chosen by a religious community that came here three centuries ago to worship without interference, and has been doing so ever since. The faith they practice still uses the same name as the tradition they left. The content of that tradition is no longer recognizable to the institutions they departed from. Three hundred years of isolation and M-dwarf light and local adaptation will do this. The community calls what they have Catholicism. Visiting clergy from the inner corridor call it something else.
|
||||
|
||||
---
|
||||
|
||||
## System Profile
|
||||
@@ -8,28 +10,37 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K5V · 42.5 ly |
|
||||
| **Star** | M · 33.4 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_3 |
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Pedra Funda is agriculturally self-sufficient — three centuries of settled M-dwarf farming, crop varieties adapted across many generations, water and soil management practices that have been refined to match the specific conditions of the habitable world. The religious community that founded the system was not unprepared; they brought agricultural expertise alongside theological conviction, and both have been maintained.
|
||||
|
||||
The dependency is in manufactured goods, which the community imports at intervals through the corridor to Sertão and onward toward the inner south reach. Medical supplies represent the critical external dependency — the community's medical practice is competent at the level of what can be done with locally available materials and skills, but some interventions require equipment that cannot be manufactured at Pedra Funda. The community accepts this limitation and has built its medical culture around it.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
There are no external factions with presence at Pedra Funda. The community is self-governing through a synodal structure that evolved from the founding religious council and has incorporated secular administrative functions over three centuries. It operates as a religious community that is also a civil government, where the distinction between those roles has gradually blurred to the point of irrelevance.
|
||||
|
||||
The Lattice Commission has a compliance record for Pedra Funda. No Commission agent has visited in several decades. The compliance record is submitted by community leadership on the required schedule and accepted without audit. The Commission has no particular reason to scrutinize a small, self-sufficient, non-industrial deep frontier community, and the community has no particular incentive to invite closer examination.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What Pedra Funda does not discuss with outside religious institutions: the specific content of their current theological practice.
|
||||
|
||||
The community is not embarrassed by how far it has drifted. It is private. The inner corridor's Catholic institutional structures have, at various points over three centuries, expressed interest in sending representatives to assess the community's practice, offer guidance, and potentially — from the community's perspective — attempt to bring them back into doctrinal alignment. These overtures have been declined politely every time. The community's position is that what they practice is their own business, that they came here precisely to practice it without outside guidance, and that three hundred years of sincere practice cannot be measured against a standard maintained by people who have never tried to maintain a living faith at M-dwarf distance from everything else.
|
||||
|
||||
What the inner corridor doesn't know: the community's seasonal observances, which began as adapted liturgical calendar modifications, have incorporated astronomical elements tied to the M-dwarf's specific activity cycles — stellar observation, light-based ritual structure, a theology of stellar light that would strike inner corridor clergy as something they have no category for.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
Pedra Funda's three-century-old Catholic community practices a faith that shares a name with the tradition that expelled them and almost nothing else; the community declines all outside ecclesiastical contact and the inner corridor's institutions have stopped sending representatives.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 9
|
||||
- **Adjacent Systems:** GJ 138, GJ 868
|
||||
- **Adjacent Systems:** GJ 138 (Sertão), GJ 868
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_233
|
||||
**GJ 2097** | M-type | deep_frontier
|
||||
# Nascente
|
||||
**GJ 2097** | M-type | south_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -14,20 +14,33 @@
|
||||
|
||||
---
|
||||
|
||||
Nascente means "spring" or "source" in Portuguese — the place where water rises from the ground, the origin point. Four centuries of unbroken settlement make it one of the oldest deep-corridor communities in the south_reach, founded during the Trade Expansion era when Portuguese-heritage settlers were pushing systematically outward along this arm of the corridor network. It was a source then — the staging point for the push toward Ribeirão and beyond — and the name has accumulated weight since.
|
||||
|
||||
Wave_2 at hop 6 is unusual enough that first-time visitors often do a double-check. Most systems this deep were settled in the last century or two. Nascente's infrastructure was laid when the Reach was still expanding confidently, before Secession reshaped priorities and pulled resources inward. The early transit facilities are still there, partly overbuilt for a community this size, partly repurposed, partly just old. The main transit hub has a wing that was built to accommodate traffic volumes that never materialized after Secession. It is used for storage now.
|
||||
|
||||
Four hundred years gives a community a particular quality. Not wealth, necessarily, but weight. Nascente's civic institutions, its dispute-resolution traditions, its agricultural calendar — these have been worked out and reworked a dozen times. The current arrangements are not perfect but they are deeply embedded.
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Nascente is a through_route between Ribeirão behind it and GJ 92 ahead. It exports agricultural surplus toward both directions and functions as a redistribution point for manufactured goods coming in from the main corridor. At four centuries, its agricultural base is productive and diverse enough to supply several systems.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The Commission has maintained a continuous post here for well over three centuries — unusual for hop 6, but Nascente's wave_2 age means the relationship predates the current authority framework. The post is staffed, chartered, and integrated with civic governance in ways that younger settlements at this distance would resist. Nascente does not resist; the relationship is older than the resistance.
|
||||
|
||||
A Portuguese-heritage mutual aid society, the Irmandade do Alcance, predates the Commission post by a generation. It handles private dispute mediation and maintains a community archive. These roles overlap occasionally with Commission functions, and the overlap is managed with practiced care.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What is or was in GJ 92, the through_route connection on Nascente's far side. Transit logs exist for four centuries of outbound traffic. Return logs for the corresponding period have gaps.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
The Irmandade's community archive is the most complete record of south_reach corridor history that exists — and its oldest sections, from the first century of settlement, have been quietly sealed against outside access for reasons the current leadership declines to discuss.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
Wave_2 through_route at hop 6 reflects the south_reach's early aggressive push; Nascente was a frontier system four hundred years ago and has been accumulating history ever since.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,6 +1,8 @@
|
||||
# PLACEHOLDER_271
|
||||
# Encruzilhada
|
||||
**GJ 211** | M-type | deep_frontier
|
||||
|
||||
The name means "crossroads," and it was chosen deliberately by people who had experienced what it means to have only one way out. Two hundred years ago, a Gate Silence event at a system further inward went dark for years. When the gate reopened, the survivors among the people who had been cut off had made a decision: never again a single gate. They searched the corridor for a through_route system, found GJ 211, and named it for what they needed it to be. The through_route topology here is not a geographical accident. It was the founding requirement.
|
||||
|
||||
---
|
||||
|
||||
## System Profile
|
||||
@@ -8,28 +10,35 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K1V · 40.0 ly |
|
||||
| **Star** | M · 36.1 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_4 |
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Encruzilhada is agricultural in character — Portuguese-heritage M-dwarf farming of the type common to the south corridor, established over two centuries and now stable. The community exports modest surplus toward the inner corridor. The supply dependency is standard for a deep frontier agricultural community: manufactured goods and medical equipment come in through GJ 117 and the inner south reach.
|
||||
|
||||
What is not standard is the infrastructure investment pattern. Encruzilhada spends a disproportionate share of its annual budget on gate-adjacent maintenance and contingency preparedness relative to its size. The community does not maintain a full supply reserve against multi-year gate disruption — it is not large enough to sustain that — but it maintains something closer to that scale than most comparable communities, and the maintenance budget for both gate connections combined exceeds what the Commission's standard guidelines would prescribe for a system of this population.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No external faction has a permanent presence at Encruzilhada. The community's political orientation is strongly autonomist, shaped by the founding experience of being cut off by an infrastructure event and having no recourse. The distrust is not of any particular institution — it is of single points of failure in general, which extends to institutional dependency as much as infrastructural dependency.
|
||||
|
||||
The Lattice Commission interacts with Encruzilhada primarily through infrastructure inspection records. The community is an attentive compliance reporter on anything related to gate maintenance and a disinterested one on most other regulatory topics. Commission agents have described Encruzilhada's gate maintenance documentation as the most thorough in their territory. The community files these reports because documentation of gate function is a value in itself, not because they trust the Commission to act on it.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What Encruzilhada does not discuss: the specific circumstances of the Gate Silence event at the origin system, and what happened during the years the gate was dark.
|
||||
|
||||
The founding cohort lived through it. Some of them survived it and came here. They spoke about it to their children in the generation immediately following, enough to pass on the foundational lesson — never one gate. What they did not pass on fully, or passed on in fragments that have been processed into narrative rather than history, is the texture of what those years were actually like. How decisions were made when rescue was not coming. What the community did to survive and who it became in the process. The founding trauma is present in every institutional reflex Encruzilhada has. Its specific content is no longer accessible, which may be the point. Some things are better remembered as lessons than as events.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
Encruzilhada was founded by survivors of a Gate Silence event who chose their location for its through_route topology; the specific events of the years their origin system was cut off are no longer remembered in detail, but every institutional decision the community makes reflects them.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 8
|
||||
- **Adjacent Systems:** GJ 117, GJ 3442
|
||||
- **Adjacent Systems:** GJ 117, GJ 3442 (Último Farol)
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_169
|
||||
# Kaapse Baai
|
||||
**GJ 213** | M-type | south_reach
|
||||
|
||||
---
|
||||
@@ -14,20 +14,51 @@
|
||||
|
||||
---
|
||||
|
||||
The name is Afrikaans for Cape Bay — the kind of name that arrives with a founding generation carrying specific memories of coastlines they left behind. The Cape Malay community that settled here three hundred years ago came primarily from the coastal south of the African continent, from a heritage that had already absorbed centuries of cultural exchange between indigenous, Malay, Dutch, and East African influences — a hybrid tradition that had learned, long before interstellar emigration was a concept, how to maintain identity while taking on everything useful from the cultures it moved alongside. They brought that habit to a warm coastal world circling a dim M5 star at the end of a spur off Confluência, and they planted spices.
|
||||
|
||||
The choice was not accidental. The founding agricultural survey had flagged GJ 213's primary inhabited world — a warm, low-gravity coastal planet with long growing seasons and mineral-rich volcanic soils along its eastern seaboard — as unusually suited to aromatic cultivation. The Cape Malay founders recognized in the survey data something the survey team had not specifically noted: the combination of mineral profile, temperature range, and the peculiar wavelength composition of an M5 star's light through this particular atmospheric depth produced growing conditions that would do extraordinary things to certain spice crops. They knew because they had been growing spices under artificial M-spectrum lighting in cooperative hydroponic facilities back in the emigration transit stage. The planet would do it better and at scale.
|
||||
|
||||
Three hundred years later, **Kaapse Kruie** — Cape Herbs — is the most recognized south_reach spice brand beyond the corridor's own borders. The blend is specific: cardamom, wild tarragon, and three local cultivars that do not have names in any language other than the ones Kaapse Baai's growers have given them — Rooi Geur, Geelpeper, and simply Die Blom, the Flower. The blend cannot be replicated. Growers on three systems have attempted to cultivate the local cultivars from seed; the results were close enough to disappoint the people who could tell the difference and not close enough to satisfy the markets that care. The soil matters. The light spectrum matters. The specific microclimate of the eastern seaboard, where the volcanic mineral deposits interact with the sea-driven humidity cycling that characterizes the growing regions, matters in ways that cannot be decoupled and reinstalled elsewhere.
|
||||
|
||||
Kaapse Kruie is not a corporation. It is a growers' collective — currently forty-two member farms, with a certification board that administers provenance standards and a shared export agent that manages the distribution relationships. The collective is small by the standards of south_reach agricultural operations. It is also, per kilogram of exported product, among the most profitable agricultural operations in the south_reach. The blend appears on Mercado's spice shelf across the Reach under the Kaapse Kruie label — the distinctive hand-painted clay-red tin with the botanical illustration of Die Blom that has been the product's packaging since the second generation of production. Core corridor buyers who encounter it tend to describe the flavor as distinctive and difficult to place, which is the polite version of saying it tastes like somewhere they have not been.
|
||||
|
||||
The two gates connect to GJ 473A (outward, a less-trafficked spur) and to Confluência (inward). Kaapse Baai is a spur end — there is no gate path beyond it that doesn't return through Confluência. The community has made peace with this topology over three centuries. Being at the end of the line concentrates the community's focus inward. It is not, by south_reach standards, an isolated existence: Confluência is a single gate transit away, and the cooperative distribution relationships that move Kaapse Kruie through Mercado's network and into the wider Reach mean the community maintains active commercial relationships with systems it will never see in person.
|
||||
|
||||
The population is Cape Malay in its founding heritage and considerably more mixed in practice — three hundred years of immigration from Confluência and, less frequently, from systems further out have layered Angolan-Portuguese, Swahili-Bantu, and unaffiliated south_reach backgrounds into the community's fabric. The founding community's cultural practices — the music, the cuisine, the particular dialect of Afrikaans-inflected Portuguese that developed locally — have been maintained not as museum pieces but as the water in which newer arrivals swim and eventually absorb.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Kaapse Baai exports spices and aromatic agricultural products. Beyond the Kaapse Kruie blend, the collective's member farms produce a range of specialty cultivars sold through smaller distribution relationships across the south_reach. The system imports most of its manufactured goods from Confluência, along with the agricultural equipment that the collective's farms require and the technical infrastructure for the export packaging operations. The spur topology means the community has a single supply corridor; historically this has made the system's residents more attentive to storage capacity and buffer stocks than comparable systems with multiple gate connections.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The **Kaapse Kruie Growers' Collective** holds the certification authority for the blend's provenance standards and administers the export agent contract. Its certification board has turned down applications from new farms seventeen times in the collective's history; the board's stated standard — that new members must demonstrate three consecutive harvests meeting the blend specification as certified by existing members — effectively means entry requires relationships that take time to build. The collective is not formally exclusionary. The practical effect of the standards is that the member list changes slowly.
|
||||
|
||||
The **Settlement Council** is a standard elected body with a close working relationship with the collective's certification board. The two institutions share several families across their memberships, which is unremarkable by the community's norms and sometimes remarked upon by commercial interests from outside who were expecting a cleaner institutional separation.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The three local cultivars — Rooi Geur, Geelpeper, and Die Blom — were not in the founding botanical inventory. The records of where the seeds came from and how they were introduced to the growing operations in the system's first generation are incomplete in a specific way: the cultivation records from the founding decade exist, the sales records from twenty years after founding exist, but the intervening period's botanical provenance documentation is missing from the collective's archive. The collective's position, when the question has come up in certification disputes, is that the founding-era records are simply incomplete, which is common for wave_3 settlements. The commercial implication is that the cultivars' provenance is legally murky in a way that no one has yet found a reason to press — because the collective controls both the seeds and the certification, and the only parties who might benefit from pressing the question are the outside growers who have been trying to replicate the cultivars and failing.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
A botanical researcher from Lalande's agricultural science program has matched the genetic markers of Die Blom against a pre-settlement database and found a cultivar that appears nowhere in any official emigration botanical inventory — and whose closest relatives are documented as extinct on Earth.
|
||||
|
||||
---
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
M5 is a dim red dwarf, consistent with the narrow habitable zone and close-orbit inhabited world. The warm coastal conditions on the inhabited planet reflect the close-orbit positioning and the volcanic mineral geology, which is plausible for a tidally influenced world with active interior geology. Spur-end topology at hop 5 with wave_3 settlement is consistent with the outer south_reach's agricultural extension pattern — spur ends in this region tend to be production systems that selected their positions for resource quality rather than connectivity.
|
||||
|
||||
---
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_202
|
||||
# Okahandja
|
||||
**GJ 27** | F-type | south_reach
|
||||
|
||||
---
|
||||
@@ -14,20 +14,49 @@
|
||||
|
||||
---
|
||||
|
||||
The name comes from a town in central Namibia whose history was inseparable from the Herero people: the site of their chiefs' kraal, the place where they signed treaties, the place where the consequences of those treaties were felt for generations. The founding families who named this system Okahandja were Herero and Namibian, wave_3 settlers three hundred years ago, and they chose a name that carried weight precisely because it carried weight — a name that meant something about continuity of presence, about the relationship between a people and their land, about the willingness to carry difficult history into a new place rather than start fresh under a name that asked nothing of anyone.
|
||||
|
||||
GJ 27 is classified F-type in its stub designation, but the stellar profile records a K0V — a warm K-type star, sitting at the upper end of the K sequence, bright and stable in the way that early K-types are, with a broad habitable zone and good surface conditions on the primary world. Three hundred years ago, when the founders arrived, the surveys showed agricultural potential and the K0V's generous luminosity suggested something that turned out to be true: this was a world where pasture grasses would grow without elaborate engineering, where the light was close enough to what cattle and the humans who raised them were adapted to, where the founding generation's skill set — pastoralism, animal husbandry, rangeland management — could translate directly from what they had known on Earth and in the Reach's earlier agricultural colonies.
|
||||
|
||||
Okahandja has been a cattle world for three centuries. Not exclusively — there are other agricultural activities, service industries, the infrastructure any settled system requires — but the cattle are the identity. The herds are vast, the rangeland is managed by extended family operations that trace lineage back to the founding wave, and the cultural practices around cattle — the ceremonies, the naming traditions, the social structures that have always been inseparable from Herero pastoralism — have been maintained and adapted across three hundred years of life under a star that is not quite the sun but is close enough. The ovaherero word for this kind of continuity, oruuano, meaning something like inheritance or legacy, appears in the names of individual ranches, in the system's main settlement, in the way older residents introduce themselves to strangers.
|
||||
|
||||
The two apertures connect inward to GJ 3323 and to GJ 3728B. The GJ 3323 connection provides access to the junction that links into the broader south_reach corridor; GJ 3728B is the Jeonnam system, a hop-7 neighbor with a different cultural heritage and a complementary economy. The connection to Jeonnam is not heavy — the two systems trade without particularly close integration — but it means Okahandja has two routes out, which places it as a spur_end rather than a dead_end and gives the ranching families marginally more flexibility in export routing.
|
||||
|
||||
Commission presence is distant. The standard outer-reach inspection schedule applies. The founding families' relationship with formal institutions has been shaped by three hundred years of managing their own affairs at the end of a long spur, and the community's governance structures are thorough precisely because external oversight is unreliable. The Assembly is known but not close. The relevant authority on Okahandja, for most of the decisions that affect daily life, is the council of elders — not a formal institution, but a recognized body whose judgments are respected and whose continuity goes back seven generations.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Okahandja exports protein — primarily cattle-derived, but the agricultural sector covers the full spectrum of animal husbandry that three hundred years of development has enabled. The primary market is the south_reach corridor, where the system's beef and related products move inward through GJ 3323 toward the larger junction systems. Secondary export channels run through GJ 3728B (Jeonnam) toward that system's trade connections. The ranching families handle their own logistics infrastructure with a level of sophistication that reflects three centuries of practice: cold-chain management, live-animal transport, processing and packaging facilities that can fill export-grade containers on a schedule that matches gate transit windows.
|
||||
|
||||
Imports are what any agricultural system requires: manufactured equipment, medical supplies, technical goods that the local economy cannot produce. The ranching families have a specific long-standing import: genetic material for herd management. Okahandja's breeding program is one of the south_reach's most developed, but maintaining diversity across centuries of isolated development requires periodic introduction of stock from outside the system. This import is managed with the same care as the export side: specific, deliberate, treated as a strategic necessity rather than a commodity transaction.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The **Okahandja Pastoral Council** is the effective governing body for the rangeland management decisions that constitute most of the system's important governance questions. The formal elected council exists and handles civic infrastructure, but land allocation, herd movement, water rights, and export quota decisions run through the pastoral council's processes. Membership is by family standing — each of the founding-wave families has a seat, and families established in subsequent waves have earned seats through a process of recognized contribution to the pastoral economy over at least two generations. This is not exclusionary in the sense of preventing newcomers from settling; it is exclusionary in the sense that governance authority accrues slowly and through demonstrated investment.
|
||||
|
||||
The Guardians of Autonomy have a strong chapter here. The Herero founding families' historical experience with both colonial dispossession and with the earlier phases of Reach expansion that resembled it has produced a community with a precise and informed relationship to questions of autonomy, sovereignty, and institutional overreach. The local Guardian chapter is one of the most legally literate in the south_reach — they maintain a full-time advisor and have successfully challenged two Assembly resource-use regulations in the last fifty years.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The founding families' oral history includes an account of an early dispute with the wave_3 survey company that designated Okahandja's primary world as suitable for settlement — specifically, a dispute over the survey company's claim to a share of the founding generation's initial export revenue as payment for the survey designation. The founding families refused to pay and the dispute was never formally resolved in the Assembly's commercial courts because the survey company dissolved before the proceedings concluded. The oral history records the names of the survey company's principals. Two of those names appear in the genealogies of Syndic families that remain commercially active in the inner reach. Whether that connection is known to the current Syndic families, or whether they know it is known at Okahandja, has never been tested.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
The pastoral council recently received a commercial inquiry from an unnamed entity in the inner reach asking about the availability of long-term land lease arrangements on Okahandja's undeveloped rangeland — the kind of inquiry that the council has received before from Syndic combines looking to establish agricultural investments at favorable outer-reach valuations, but this inquiry arrived through a routing that the council's advisor cannot trace to any registered commercial entity.
|
||||
|
||||
---
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
The F-type header designation versus the K0V stellar profile is a data generation artifact; K0V is the correct stellar classification and has been used as the basis for all lore detail. K0V at 36.1 light-years is consistent with a wave_3 agricultural system in the south_reach: the third emigration wave reached systems at this distance range, and the K0V's warm, stable luminosity makes it a preferred target for agricultural settlers. Spur_end topology with 2 apertures at hop 7 places Okahandja as a genuine periphery system — not isolated, but not on any significant transit route.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,6 +1,18 @@
|
||||
# PLACEHOLDER_295
|
||||
# Bout du Chemin
|
||||
**GJ 282A** | G-type | west_reach
|
||||
|
||||
End of the road. For most of its four-hundred-year history, this is what Bout du Chemin literally was: the furthest settled point in the west_reach corridor, the place where the organized network ended and the uncharted horizon stations beyond had no human community waiting at the other end.
|
||||
|
||||
That changed within the last forty years, when the wave_5 settlers pushed through to Grenzstein (GJ 807) outward. Before that, Bout du Chemin had the particular psychological character of a frontier terminus — not just distant, but definitionally the last — and even now that it is no longer the end, the name persists and something of the feeling persists. The community built its identity around being the furthest, and you do not simply reconfigure that identity because the road extended.
|
||||
|
||||
The G-type star here is warm and generous. This is not an M-dwarf system with its narrow bands and red-tinted light; the primary world receives broad-spectrum illumination across a good-sized habitable zone, and the planet that occupies it has an ecology that looks almost familiar to settlers from Core and inner-corridor systems — blue-green, temperate, with weather patterns that move in comprehensible seasonal cycles. For French-speaking settlers who had been moving outward through increasingly dim and alien stellar environments, finding a G-type world at hop fifteen was something like confirmation that they had been right to come. The community that built here in the Wave 2 expansion was deeply committed to being here, and the quality of the world they found gave them reasons to stay that were not purely ideological.
|
||||
|
||||
The founding French families brought their language, their calendar awareness, their culinary particularity, and a form of political philosophy that privileges the commune over the administrative hierarchy. Bout du Chemin has always governed itself through genuine assembly — not a representative council in the Echternach mold, but actual community meetings for significant decisions, a practice that works at Bout du Chemin's scale and would be logistically impractical at any scale larger. The assembly structure is four hundred years old. It has been modified but not replaced. It is the thing that Bout du Chemin residents point to when they are asked what distinguishes their community from corridor settlements that share their linguistic heritage.
|
||||
|
||||
The economy is agricultural and small-scale manufacturing, with the transit service component that comes with any through-route position. The two apertures — connecting to Langemark (GJ 42) inward and now to Grenzstein (GJ 807) outward — process modest traffic volumes. The connection to Grenzstein is new enough that it has not yet fully integrated into Bout du Chemin's commercial patterns; the wave_5 settlers at Grenzstein are still establishing their economic footing, and the trade relationship between the two systems is still being defined. Bout du Chemin residents have mixed feelings about this, in the way that any community has mixed feelings about an event that changes its defining characteristic.
|
||||
|
||||
The horizon station has a slightly enlarged common area by corridor standards — not a deliberate design decision, but the accumulated result of a terminus community that treated transit arrivals as significant events. When you were the end of the line, every arrival was either someone who lived here or someone who had come to the end of something, and both deserved acknowledgment. The custom of making arrivals welcome persisted after the connection to Grenzstein made Bout du Chemin a through-route. The wave_5 settlers who passed through on their way outward remember it.
|
||||
|
||||
---
|
||||
|
||||
## System Profile
|
||||
@@ -15,19 +27,26 @@
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Bout du Chemin imports manufactured goods, medical hardware, and technical infrastructure components from Langemark and systems inward. The community is substantially self-sufficient in food and basic goods at its population scale, and the agricultural output provides some export capacity — primarily to Echternach, which has a more limited growing season, and to Grenzstein, which is still in its early settlement phase and imports most of its food. The Grenzstein food export relationship is new and significant: it represents Bout du Chemin transitioning from a terminus that received imports to a production system that is itself a supply base for something further out. The community is aware of the irony and is not entirely sure how it feels about it.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No formal faction presence. The community assembly is the governance structure, and the assembly has no external affiliations beyond the standard Assembly registration and reporting requirements. The Commission is an abstraction at hop fifteen. The Veil Institute is a name in history texts about the horizon stations — the community's relationship to gate technology is operational and unsentimental. The GJ 282A horizon station is the infrastructure that makes Bout du Chemin part of the Reach, and it is maintained by the caretaker rotation system administered from Langemark, and it works, and that is the sum of the community's relationship with the Veil Institute's legacy.
|
||||
|
||||
The exception is a small community organization called Les Veilleurs — "The Watchers" — which has existed for about a hundred and fifty years and focuses on observational astronomy and the documentation of deep-corridor stellar phenomena. Les Veilleurs have no formal status, no political agenda, and no outside affiliations. They maintain a modest observatory on the primary world's high plateau and have been filing their observations in the community archive for a century and a half. Some of those observations concern the GJ 282A horizon station's operational characteristics during low-traffic periods. Those observations are in the archive and not highlighted.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
Les Veilleurs' observatory archive contains something the community has not formally processed: a set of horizon station observation records from approximately eighty years ago, collected during a period when the outward aperture was sealed pending corridor extension planning. During that period, when the outward aperture was officially inactive, the observatory recorded intermittent activation signatures — brief, low-amplitude, nothing like a full transit event, but consistent enough over eighteen months that the Veilleurs at the time flagged it in their archive as "aperture behavior inconsistent with sealed status." The transit authority reviewed it, found no corresponding traffic record, and classified it as instrument interference from the nearby power systems. The classification is in the official record. The original observatory data is in the community archive, separately, and has not been revisited.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
The sealed outward aperture was showing activation signatures for eighteen months before the corridor extension was approved, and the explanation filed at the time required not examining the original data too carefully.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
G-type header per the database classification. The READ-ONLY profile shows K2V — a cool K-type, toward the lower end of the K range. This is consistent with a warm, habitable primary world but slightly cooler than a true G-type; the description in the text uses "G-type" in the colloquial sense that the community would use it (good, broad-spectrum light, familiar ecology) rather than a precise astronomical claim. Wave_2 at hop 15 is the furthest point of the west_reach Wave 2 push. Through-route topology with two apertures: Langemark inward, Grenzstein outward (the outward connection established within the last forty years by wave_5 settlement).
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Pollux
|
||||
# Weitblick
|
||||
**GJ 286** | G-type | deep_frontier
|
||||
|
||||
---
|
||||
@@ -8,26 +8,37 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K0IIIvar · 33.8 ly |
|
||||
| **Star** | G8V · 33.8 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_4 |
|
||||
|
||||
---
|
||||
|
||||
Weitblick means "far sight" — the view from a high place, the capacity to see a long distance. Two hundred years ago, German-heritage settlers chose this name for a system that sits deeper in the frontier than most communities that were founded in the same era, and they chose it with the awareness that from here, looking back toward the Reach, the distance is exceptional. From this far out, you can see a lot. The question is whether anyone is looking back at you.
|
||||
|
||||
The G-type primary is a warm yellow star — brighter and more hospitable than the dim M-dwarfs typical of the deep frontier. The light here feels close to Earth-standard, which gave the founding settlers a practical advantage and an emotional one. Two centuries of local astronomical observation have produced some of the most complete stellar records for any deep_frontier system.
|
||||
|
||||
As a through_route connecting GJ 309 and GJ 598, Weitblick handles genuine transit traffic — not heavy, but regular. Vessels moving between the two connecting systems pass through. The community developed a modest service economy around that traffic: refueling, maintenance, crew accommodation for vessels unwilling to attempt the long haul without a stop. The transit function and the settlement have coexisted without either dominating the other, which is an arrangement that suits the local character.
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Weitblick imports manufactured components and medical hardware through its corridor connections. Its own production is agricultural — sufficient for local consumption, with modest surplus available to transit vessels. The stellar activity records represent an unofficial export: research institutions in the inner Reach have been known to pay for access to the archive.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
A community council handles civic governance. The Commission post is staffed on a rotating basis, with longer tours than inner-Reach postings because the transit time to reach this system makes short assignments impractical. Commission personnel stationed at Weitblick tend to develop genuine local ties, which is either a benefit or a conflict-of-interest depending on who is evaluating them.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The stellar activity archive. The most recent decade of records contains a sequence of anomalous readings that the local astronomical society has not published and that does not appear in the Commission reports. The nature of the anomaly is known to approximately four people.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
A research vessel operating under academic credentials arrived eight months ago to access the stellar archive, spent three weeks on-site, departed without filing a summary report as their access agreement required, and has not responded to the follow-up transmissions the community council has sent since.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
Wave_4 through_route at hop 7 with stellar variability documentation is consistent with deep_frontier settlement patterns. The name "Weitblick" reflects genuine frontier consciousness — a community that understood its isolation and chose to frame it as perspective rather than deprivation.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_025
|
||||
**GJ 299** | K-type | south_reach
|
||||
# Várzea
|
||||
**GJ 299** | M-type | south_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -14,20 +14,49 @@
|
||||
|
||||
---
|
||||
|
||||
Várzea is a Portuguese word without a single clean translation. In Brazilian usage, it describes the seasonally flooded forest of the Amazon's river systems — not wetland in the sense of permanent inundation, not dry land in the sense of reliable ground, but the territory that is one thing for part of the year and another thing for the rest. The founding generation that chartered this system three hundred years ago came primarily from Brazilian communities, and they named it for what they found: a planet with extensive river drainage systems whose seasonal flooding was not a disaster to be managed but a mechanism to be understood.
|
||||
|
||||
GJ 299 is an M3.5 dwarf — a mid-range red dwarf, cooler than the K-type stars at the inner south_reach but warmer than the extreme late M-types that define systems like Zenzele. The inhabited world has a lower-gravity surface that has encouraged the development of extensive river systems across its primary continent: wide, slow-moving rivers in the dry season, broad flood channels in the wet. The flooding is seasonal in the way the founders recognized from Brazilian ecological memory, and the early agricultural assessments confirmed what the naming generation hoped — that the flooded zones were exceptionally productive for aquaculture, depositing the mineral-rich sediment that fed the fish populations that had evolved in this system's hydrological cycle long before the settlers arrived.
|
||||
|
||||
The wave_3 settlers arrived with aquaculture technology, not fishing instinct. They came knowing what they were going to build. The first generation established the managed ponds and channel systems that now constitute the bulk of Várzea's productive infrastructure — a landscape of controlled flood zones, weir systems, and processing facilities built on the slightly higher ground above the seasonal waterline. Three hundred years of refinement have produced an aquaculture operation that processes and distributes freshwater fish protein to systems across the mid-south corridor. The flagship product is smoked river fish under the **Várzea** label — sold in vacuum-sealed portions across south_reach markets — but the operation's bulk output is protein concentrate and processed fish meal used in the food manufacturing operations at Inhambane and Confluência.
|
||||
|
||||
The junction position means Várzea is not a spur-end community dependent on a single connection. Three gates link to Travessia (GJ 1156) inward, to GJ 388 (another mid-reach system), and to GJ 695A (the unsettled junction). The Travessia connection is the primary commercial corridor; Várzea's processed products enter the core market through Travessia's bonded warehouse district, where the Customs Brokers' Guild handles the documentation that converts cooperative aquaculture manifests into Assembly-standard freight. The junction position has given Várzea more transit exposure than most wave_3 outer south_reach settlements; the community has a professional class of logistics coordinators and commercial managers that emerged from the need to manage the complexity of being a production system with three-way gate connectivity.
|
||||
|
||||
The flooding is not only agricultural. It is cultural. The period of peak river flow — high season, when the flood channels reach their widest and the aquaculture ponds connect into the broader flood system — is the community's primary festival period. The Enchente, the flooding, is a two-week event in which the commercial processing operations pause and the flood plains become public space: fishing in the traditional non-commercial sense, communal meals, music on the elevated platforms above the waterline. The celebration is not nostalgic in the sense of performing a lost past — the founding generation's descendants have been doing this continuously for three hundred years, and it is simply the structure of the year.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Várzea exports processed fish protein and related aquaculture products as its primary commercial output. The Várzea label appears in south_reach markets and at a small number of Mercado locations in the inner ring that carry specialty south_reach food products. The bulk output — protein concentrate and fish meal — moves in commercial quantities through the Travessia brokerage channel. The system imports manufactured goods and technical equipment from Travessia and, through the GJ 388 connection, from other mid-reach suppliers. Food imports are minimal; the flood system produces sufficient variety to reduce dietary dependence on outside supply.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The **Aquaculture Cooperative Federation** is the primary commercial institution, managing production allocation across the twelve member cooperatives that operate the major flood-zone facilities. The Federation sets production targets, manages the Travessia export relationship, and operates the Várzea brand licensing for the retail product line. Its council is elected from member cooperative representatives on a one-cooperative-one-vote basis, which gives the smaller cooperatives structural representation that does not always reflect their production share — a tension that surfaces at every major pricing decision.
|
||||
|
||||
The **Flood Zone Authority** is a technical governance body that manages the weir systems, channel maintenance, and flood timing infrastructure — the engineering that makes the entire aquaculture system function. It is formally subordinate to the settlement council but holds practical veto power over decisions that affect the hydrology, because the alternative to the Authority's management is catastrophic flooding rather than productive flooding. Its chief engineers have more effective governance authority than the settlement council members on anything involving water.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The wave_3 settlement's original charter allocated flood-zone operating licenses to the founding families in proportions that reflected the population at founding — twelve cooperatives with approximately equal allocations. Three hundred years of inheritance, subdivision, and cooperative restructuring have not changed the formal allocation structure, which the charter treats as fixed without amendment process. What has changed is who holds the licenses in practice: through a series of structuring decisions over the past century, effective control of four of the twelve cooperative allocations has consolidated under a single family network that holds formal membership in four distinct cooperatives while operating them with coordinated management. The structure is technically compliant with the charter. It is not what the founding generation intended. The Flood Zone Authority's chief engineer is a member of this family network.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
A junior member of one of the smaller aquaculture cooperatives has been trying for two years to purchase a production license from one of the four cooperatives in the consolidated family network, and has been receiving technically valid rejections under charter provisions that the licensing records show have never been used to reject any other buyer.
|
||||
|
||||
---
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
M3.5 is a mid-sequence red dwarf, cooler than the K/M boundary systems and warmer than the extreme late M-types. The briefing designates K-type but the profile specifies M3.5; the header uses M-type to match the profile. The low-gravity surface enabling extensive river systems is consistent with M-dwarf close-orbit habitable zone planets, which tend toward lower-density bodies. Wave_3 settlement at hop 6 reflects the outer reach of the third emigration wave, which extended the south_reach's agricultural corridor into systems one hop beyond the wave_2 junctions at Confluência and Matamba.
|
||||
|
||||
---
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,6 +1,8 @@
|
||||
# PLACEHOLDER_224
|
||||
# Vorposten
|
||||
**GJ 309** | K-type | deep_frontier
|
||||
|
||||
The name means "outpost," and it is accurate without embellishment. Vorposten is forty to one hundred years old — a wave_5 settlement off the Weitblick junction, pushing the Germanic deep frontier one hop further into territory that had not been settled before. The founding cohort came from Compact of Westphalia-affiliated systems and carried those political instincts with them: mutual recognition, minimal external obligations, the deliberate community compact as the basis for governance. The community is small, the infrastructure is basic, and the sense of building something from the beginning is still present in how people here talk about their work.
|
||||
|
||||
---
|
||||
|
||||
## System Profile
|
||||
@@ -8,28 +10,35 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K0V · 39.8 ly |
|
||||
| **Star** | K · 36.9 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_5 |
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Vorposten is not yet fully self-sufficient. The agricultural base is in its early generations of K-type adaptation, producing enough to cover most local food requirements but not the surplus that older communities export. The community imports food supplements, manufactured goods, and medical equipment through Weitblick on a regular schedule. Supply lead times are the governing constraint on most decisions the community makes.
|
||||
|
||||
The Compact of Westphalia's affiliated systems have provided some settlement support — agricultural consultation, equipment loans, skilled labor on temporary contract for first-generation infrastructure construction. This support is understood by both sides as time-limited. Vorposten will be expected to become operationally independent within a generation, and the community's leadership is building toward that expectation.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The Compact of Westphalia's framework extends nominally to Vorposten through the founding cohort's affiliations. In practice, at this distance and scale, the Compact's institutional presence is represented by the values and governance instincts the founders brought rather than by any formal administrative relationship. There are no Compact representatives resident; the founding cohort is the Compact's presence.
|
||||
|
||||
The Lattice Commission has a registration on file for Vorposten. No Commission personnel have visited. The community's compliance record is maintained by community leadership with the same thoroughness they apply to everything else at this stage: carefully, because this is the kind of thing that becomes a problem if neglected in the founding period.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What Vorposten does not discuss with the Compact's inner corridor communities: the degree to which the founding cohort has already begun to make governance decisions that depart from Compact consensus.
|
||||
|
||||
They are at enough distance and early enough in their institutional development that departure from the Compact framework feels necessary for practical reasons. How much of this is pragmatic adaptation to frontier conditions and how much of it is the Compact's framework simply not fitting a community of this size at this distance is a question the community hasn't resolved. The Compact's consensus processes are designed for communities with communication access measured in days; Vorposten's communication lag is weeks. The decisions that can't wait don't wait, and the community has been making them without the consultation the Compact framework technically requires.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
Vorposten's founding cohort carries Compact of Westphalia political instincts and has already begun making governance decisions the Compact's consensus framework didn't sanction; the community hasn't mentioned this to the Compact, and the distance makes it easy to not mention.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 8
|
||||
- **Adjacent Systems:** GJ 349, GJ 286
|
||||
- **Adjacent Systems:** GJ 286 (Weitblick), GJ 349 (Randgebiet)
|
||||
|
||||
@@ -24,7 +24,7 @@ The spur_end topology means Wend's two gates open inward: one toward Rana (GJ 15
|
||||
|
||||
Sonnwend exports food — bulk grain, preserved root crops, dried protein legumes, and the cold-storage fresh produce that the Gate Corporation's ferry schedules permit. The inward route through Rana (GJ 150) carries these exports toward Hansestadt and the core; the Compact's internal distribution network directs them outward from there to the dim-star systems that cannot grow their own. Sonnwend's surplus feeds a population several times its own size across the outer corridor, which is the practical foundation of the leverage the Compact's negotiators invoke when Assembly trade delegates discuss the west_reach's integration status.
|
||||
|
||||
Imports are manufactured goods, technical components, and the specialty materials that agricultural systems need from industrial ones. These arrive primarily through Rana (GJ 150). The pricing through Rana is Assembly-influenced — Rana maintains commercial neutrality and prices accordingly — which means Sonnwend periodically investigates alternative routing through GJ 798, but GJ 798 is a stub and its commercial infrastructure has not developed to the point where it offers better terms.
|
||||
Imports are manufactured goods, technical components, and the specialty materials that agricultural systems need from industrial ones. These arrive primarily through Rana (GJ 150). The pricing through Rana is Assembly-influenced — Rana maintains commercial neutrality and prices accordingly — which means Sonnwend periodically investigates alternative routing through GJ 798, but the through-route at GJ 798 has not developed commercial infrastructure to the point where it offers better terms than Rana's established corridor.
|
||||
|
||||
MVG has no significant contract presence in Sonnwend. Agricultural output is outside MVG's corridor specialization in this region, and the founding cooperative's charter explicitly prohibited resource extraction contracts that would compete with agricultural land use — a provision that has been challenged three times and upheld three times by the charter council.
|
||||
|
||||
|
||||
@@ -1,6 +1,8 @@
|
||||
# Copernicus
|
||||
# GJ 324A
|
||||
**GJ 324A** | K-type | deep_frontier
|
||||
|
||||
The gates are here. The corridor was mapped. No one claimed it. GJ 324A is one of the frontier's unclaimed transits — a system with demonstrable habitability, a functioning horizon station, and a survey record that describes marginal agricultural potential accurately enough that every cohort that looked at it moved on to somewhere else. The system sees occasional traffic between Knotenpunkt and GJ 167 and nothing else.
|
||||
|
||||
---
|
||||
|
||||
## System Profile
|
||||
@@ -8,28 +10,31 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | G8V · 40.3 ly |
|
||||
| **Star** | K · 34.1 ly |
|
||||
| **Gates** | 2 aperture · spur_end |
|
||||
| **Settlement** | unsettled |
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
None. No resident population.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No permanent faction presence. The horizon station is self-maintaining by design. Automated relay hardware, installed during the wave_3 corridor mapping, continues to broadcast navigation data for transiting vessels. No one has been contracted to service it in living memory; the station's self-maintenance systems have not required human intervention.
|
||||
|
||||
The Lattice Commission's records for GJ 324A list it as surveyed, unmapped for settlement, and not under active review. No Commission personnel are assigned to the system. The survey record is 180 years old.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
None recorded. The system has no population and therefore no institutional silence. What is absent here is more significant than what is present — this is one of several deep frontier systems where the question of why no founding cohort ever committed is not answered by the survey record alone. Marginal habitability explains why GJ 324A was not first choice. It does not fully explain why, across three centuries of frontier expansion, it was never anyone's second choice either.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
GJ 324A's 180-year-old survey record describes a habitable world with marginal agricultural potential; no cohort has ever claimed it, and no more recent survey has been commissioned to determine whether anything about that assessment was wrong.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 8
|
||||
- **Adjacent Systems:** GJ 167, GJ 1235
|
||||
- **Adjacent Systems:** GJ 1235 (Knotenpunkt), GJ 167
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_123
|
||||
# GJ 325B
|
||||
**GJ 325B** | M-type | south_reach
|
||||
|
||||
---
|
||||
@@ -14,20 +14,47 @@
|
||||
|
||||
---
|
||||
|
||||
GJ 325B has no settlement and no name. The system catalog records it by its designation — a companion designation, implying a binary or wide-associate relationship with a primary that is nowhere near the system's gate aperture, a bookkeeping artifact of old survey conventions that assigned B suffixes to stars that were at one time believed to share a moving group or loose association with another designated object. The "B" means nothing operationally. The star itself is a K6V — a mid-K dwarf, orange and dim by the standards of systems that host human settlements, sitting at 36.9 light-years from Earth's sun and connected to GJ 3323 through the one aperture its horizon station carries.
|
||||
|
||||
What survey teams sent to assess GJ 325B for settlement found was a system whose mass budget had gone almost entirely into a dense intermediate asteroid belt rather than into planet formation. There are rocky bodies: several of them, distributed between the star's inner habitable zone and the outer cold zone, but none large enough to retain a substantial atmosphere, none with surface gravity that would make extended surface habitation practical without full closed-environment infrastructure, and none whose resource profile was significantly better than what could be found at already-settled systems with functioning surface operations. The asteroid belt that took the mass that a planet might otherwise have accumulated is extensive and rich in metallic and silicate material. From a resource perspective, it is valuable. From a settlement perspective — the kind of settlement that requires habitable surface, agricultural potential, or infrastructure that does not need to be entirely imported — it is insufficient.
|
||||
|
||||
The wave_3 survey teams passed through on their way to assess GJ 3323 and the systems beyond it. The reports they filed on GJ 325B were brief. The system was designated as a possible future extraction site, which is the assessment category that means "not worth developing now, not worth dismissing entirely." That designation has not changed in three hundred years.
|
||||
|
||||
What a transit crew finds when they come through the GJ 3323 aperture into GJ 325B is this: a dim orange star that provides enough light to navigate by but not enough warmth to stand in without supplemental heating. Asteroids in concentrations that show up on standard proximity sensors as scattered returns rather than individual objects — the belt is not a navigation hazard in the precise sense, but it is reason to proceed on careful track rather than fastest course. The horizon station itself is alien construction, self-maintaining as all horizon stations are, its aperture facing the GJ 3323 direction. There is no second aperture. The only way out is the way in.
|
||||
|
||||
The station's maintenance protocols keep the aperture operational and the docking infrastructure at minimal function — enough for a vessel to dock, shelter, conduct minor repairs, and access the basic navigational data the station carries. The station has no crew, no resident population, no service beyond what the alien construction's self-maintaining systems provide. A crew that sheltered here in an emergency would find the experience functional but not hospitable: lighting at the low end of the spectrum that the alien design defaults to, temperature regulation that keeps the habitable sections above freezing, and a silence that is particular to empty stations — the hum of the aperture's transit systems, the occasional sound of maintenance systems moving through corridors, nothing else.
|
||||
|
||||
The asteroid belt has been surveyed by four independent extraction companies over the past three hundred years, three of which were assessing the belt for commercial development and one of which was conducting a geological survey for academic purposes. The commercial surveys agreed on the resource content and disagreed on the development economics. The academic survey produced a paper on the system's formation history that was cited twice and then largely forgotten. None of the commercial surveys resulted in development proposals that advanced to the capital authorization stage. The belt remains as it was: present, valuable in principle, and addressed by no one.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
GJ 325B has no economy and no supply structure. The horizon station's self-maintaining systems require no external input that any human supply chain provides. A vessel passing through requires only what it carries. There is nothing to import and nothing to export.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No faction has a presence in GJ 325B. The Lattice Commission's jurisdiction theoretically extends to any system with a functioning horizon station, but the Commission maintains no inspection schedule for unsettled systems and has no record of a scheduled visit to GJ 325B in the last hundred years. The system exists in the gap between the Commission's jurisdiction and its operational capacity — claimed in principle, unvisited in practice.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The four extraction surveys are in commercial databases as filed documents, but the third survey — conducted approximately eighty years ago by a company that no longer exists under that name — produced a resource assessment that, according to a footnote in the academic geological survey, contained a section on a secondary deposit type that the academic team tried to follow up and found had been redacted from the public filing. The commercial survey company dissolved two years after filing. The ownership chain between that company and any currently active entity is not publicly documented.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
The redacted section of the third commercial survey covers a deposit type that the academic survey's geological analysis suggests would be associated with the kind of isotopic profile sometimes found in regions of heavy historical high-energy activity — the kind of profile that is neither agricultural nor conventionally industrial, but that certain categories of research operation would find specifically interesting.
|
||||
|
||||
---
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
The M-type header designation is a generation artifact; K6V is the correct stellar classification and governs all lore detail. The dead_end, unsettled combination at hop 7 off GJ 3323 is the expected profile for a system that was assessed and passed over during the wave_3 expansion: the junction at GJ 3323 connected this aperture because the horizon station was already there, not because anyone intended to develop the system. The asteroid belt as primary feature explains the settlement failure without requiring any catastrophic history — this system was simply not good enough to justify the capital required for development when alternatives at comparable or shorter hop distances were available.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_089
|
||||
# GJ 3403
|
||||
**GJ 3403** | K-type | deep_frontier
|
||||
|
||||
---
|
||||
@@ -8,28 +8,35 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K7V · 43.4 ly |
|
||||
| **Star** | K · 33.5 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_3 |
|
||||
| **Settlement** | unsettled |
|
||||
|
||||
---
|
||||
|
||||
GJ 3403 has been surveyed, found adequate, and left alone.
|
||||
|
||||
The K-type primary is a better star than most at this depth — warmer than an M-dwarf, more stable, producing something closer to what the human body expects from a sky. The primary world meets settlement criteria: breathable atmosphere, adequate warmth, reasonable water distribution, no significant geological instability. Survey assessments across multiple visits have reached the same conclusion each time: habitable world, meets minimum parameters, no compelling argument for or against.
|
||||
|
||||
"No compelling argument for or against" is how a world remains empty for generations. The positive case for settling GJ 3403 — it is adequate — runs directly into the negative case for not settling GJ 3403 at hop ten: it is only adequate. The inner-Reach settlement wave funded frontier development when the economics were favorable, and GJ 3403's economics were never favorable enough to compete with better opportunities at closer distances. The corridor needed a node here. Nobody needed a home here. The distinction is the whole story.
|
||||
|
||||
The system connects to Neugrund at GJ 675 on one side — the multicultural experiment, the self-conscious attempt to build something deliberately mixed — and GJ 656 in the other direction. The corridor exists. The horizon station processes transit. The habitable world turns below, meeting its parameters.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
None.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
No faction presence.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
---
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 10
|
||||
- **Adjacent Systems:** GJ 675, GJ 656
|
||||
- **Adjacent Systems:** GJ 675 (Neugrund), GJ 656
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_255
|
||||
# Último Farol
|
||||
**GJ 3442** | M-type | deep_frontier
|
||||
|
||||
---
|
||||
@@ -8,26 +8,39 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | k-m · 37.9 ly |
|
||||
| **Star** | M0V · 37.9 ly |
|
||||
| **Gates** | 1 aperture · dead_end |
|
||||
| **Settlement** | wave_4 |
|
||||
|
||||
---
|
||||
|
||||
Último Farol — "last lighthouse" in Portuguese — is named with the literalness that frontier communities tend to allow themselves. One gate. One connection, back toward GJ 211. Beyond the single aperture that links this system to the rest of the Reach, there is nothing settled, nothing mapped, nothing waiting. The community here is, in the most straightforward astronomical sense, at the edge. They know it and named the place accordingly.
|
||||
|
||||
The star is at the boundary of K and M classification — dim, red-shifted, producing the low-light environment that the Portuguese-heritage communities of this corridor have been engineering around for two hundred years. The habitable world requires supplemental lighting for optimal agriculture, as is common at this spectral type, and the community has refined those systems over two centuries to something close to second nature. What the low light lacks in photosynthetic efficiency, the long-term settlers compensate with careful planning.
|
||||
|
||||
The metaphor of the lighthouse is not purely poetic. A navigational beacon here — maintained by the community, registered with the Commission — is one of the furthest outposts in the deep_frontier navigation network. Vessels approaching from the GJ 211 direction use it as a reference point for the final approach. Vessels that are uncertain of their position after a difficult transit sometimes look for it specifically. The locals take this function seriously; the beacon maintenance schedule is treated as a civic responsibility on par with the agricultural calendar.
|
||||
|
||||
Authority at this depth is nominal. The Commission files are current, the charter is valid, and a Commission vessel makes an annual visit. For the other eleven months, Último Farol is a community of two hundred years' standing that manages its own affairs with the competence of long practice.
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Último Farol is the deepest supply terminus on its corridor arm. Everything that arrives here has come through GJ 211, which is itself distant from the main Reach infrastructure. The community has developed a strong culture of supply discipline — strategic reserves, careful tracking of consumption rates, and the kind of repair-first mentality that develops when replacements take months to arrive.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
A community council governs. The Commission post is staffed by a single long-term appointee who typically serves extended tours by choice — people who take postings this far out usually do so for specific reasons and tend to stay. No external commercial faction maintains a permanent presence.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What lies beyond the aperture boundary — specifically, whether the corridor ending here was the result of survey findings that ruled out further extension, or the result of a deliberate decision to stop. Community oral history and the formal survey record give different accounts.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
The Commission's annual visit, which has been reliably scheduled for the same month each year for the past two decades, did not arrive this cycle. The community council sent a query to GJ 211 six weeks ago. The reply, when it came, said only that the visit had been "deferred pending resource reallocation." Nobody has explained what resources were reallocated or why.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
Wave_4 dead_end at hop 7 with the furthest-out navigational beacon role is appropriate for a system named "last lighthouse" — the function and the name are integrated in a way that reflects genuine frontier community self-conception.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,6 +1,8 @@
|
||||
# PLACEHOLDER_043
|
||||
# Randgebiet
|
||||
**GJ 349** | M-type | deep_frontier
|
||||
|
||||
The name means "border territory," which is accurate in the sense that this is approximately where organized space runs out. Randgebiet is forty to eighty years old — the newest community in the Germanic deep frontier chain, founded by second-generation settlers from Vorposten who decided one more hop was worth the effort. The community is still finding its institutional character. At this scale, individual personalities shape what a community becomes, and the community is small enough that the personalities here are still visible in the institutions they're building.
|
||||
|
||||
---
|
||||
|
||||
## System Profile
|
||||
@@ -8,28 +10,33 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K3V · 42.1 ly |
|
||||
| **Star** | M · 37.3 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_5 |
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Randgebiet is not yet self-sufficient. The agricultural base is in its second or third generation of M-dwarf adaptation — viable, but not producing the surplus that older deep frontier systems have developed. The community imports food supplements and manufactured goods through Vorposten on a regular schedule. The supply line is the community's operational constraint; every significant decision factors in lead times.
|
||||
|
||||
Infrastructure is basic. Fabrication capacity covers the most common maintenance needs. Medical capability is limited to what the community's two trained practitioners can manage with available equipment. Complex interventions require travel to Vorposten or further inward. This is a known risk that the community has accepted and manages through preventive practice rather than emergency response.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No external faction presence. Randgebiet is too new and too small to have attracted institutional attention of any kind. The Compact of Westphalia's affiliated communities are aware that second-generation settlers from Vorposten pushed the corridor further; the Compact's institutional framework does not extend this far out, but the cultural inheritance does. Randgebiet's governance instincts — mutual recognition, minimal external obligations, deliberate community compact — trace to that tradition without the community being formally a member of anything.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What Randgebiet does not discuss: doubts about whether one more hop was the right choice.
|
||||
|
||||
The community was founded on confidence: second-generation settlers who knew the deep frontier because they grew up on it, who understood the costs, who chose to push further anyway. Not all of them have retained that confidence equally. The first years were harder than projected. The agricultural base took longer to establish. A medical emergency in the second year required evacuation to Vorposten that the community had not built infrastructure to handle smoothly. The founders talk about these things among themselves, at depth. They do not talk about them with outsiders, because the community's sense of identity is not yet durable enough to survive public doubt.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
Randgebiet's founders chose to push the corridor one hop further than Vorposten and have spent the years since wondering, privately and without resolution, whether the confidence that drove that decision was wisdom or stubbornness.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 9
|
||||
- **Adjacent Systems:** GJ 309, GJ 146
|
||||
- **Adjacent Systems:** GJ 146, GJ 309 (Vorposten)
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Van Maanen's Star
|
||||
# Vuurkloof
|
||||
**GJ 35** | unusual-type | south_reach
|
||||
|
||||
---
|
||||
@@ -14,20 +14,49 @@
|
||||
|
||||
---
|
||||
|
||||
The name is Afrikaans: fire ravine. It was given, three hundred years ago, by the founding generation who arrived to find that the planet they had selected from survey data was more geologically energetic than the preliminary assessment had conveyed. The ravines were real — deep fault-line fractures running across the primary inhabited continent, their walls stained orange and black by mineral deposits and thermal discharge. The fire was also real. Not combustion but heat: the vents that lined the ravine floors emitted constant thermal plumes, and in certain atmospheric conditions, the rising heat columns caught particulates in the upper air and produced columns of visible shimmer that, at dusk, looked enough like fire that the founding generation decided the survey team had been technically accurate and personally unhelpful. They named the system for what they found, unpacked their equipment, and started figuring out how to live next to it.
|
||||
|
||||
GJ 35 is a DG white dwarf — the remnant core of a star that exhausted its hydrogen fuel and shed its outer layers eons before the Reach was imagined. A white dwarf provides essentially no warmth at planetary distances useful for habitation; the planet that Vuurkloof's residents call home is not habitable because of its star. It is habitable because of its interior. The planet was captured or formed in the white dwarf's habitable zone in another era; what remains is a geologically superactive world whose tidal history has left the interior hot and restless. The surface temperature is maintained primarily by geothermal output, supplemented by a dense greenhouse atmosphere that traps what little radiation the DG star provides. The result is a warm, geothermally lit world that gets its daylight not from the sky — which is permanently dim, the DG star a small, blue-white point rather than a sun — but from the vents and hot springs whose glow defines the landscape.
|
||||
|
||||
The vents are the fact around which everything else in Vuurkloof organizes. The thermal output is immense and consistent — more reliable than any fusion plant the founding generation could have built, provided they could extract and distribute it efficiently. Two generations of geothermal engineering have produced a system whose primary infrastructure is built into the ravine walls: extraction conduits running along the fault lines, thermal exchange stations at the major vent clusters, distribution networks carrying heat and power to residential and industrial areas across the inhabited zone. The engineering traditions developed here are Vuurkloof's primary intellectual export; the system's geothermal specialists are found as consultants on other geothermally active worlds across the south and west reaches.
|
||||
|
||||
Through-route topology means Vuurkloof sits between Karoo (GJ 222A) and Kumasi (GJ 86), carrying transit traffic between two more developed systems. The transit character is pronounced: the horizon station handles more throughput per resident than any system in this arc, and the hospitality sector built around the transit waypoint is more sophisticated than a three-hundred-year-old outer south_reach settlement would otherwise produce. Travelers stopping here for the scheduled gate sequence sometimes extend their stay by a day to use the hot springs complexes — some built into the ravine walls, some constructed at the thermal vents where the combination of mineral-rich water and geothermal heat has produced bathing facilities that operators in other systems have attempted to replicate and found they lack the source material. You cannot build a genuine Vuurkloof hot spring anywhere that does not have Vuurkloof's geology.
|
||||
|
||||
The founding community is southern African in heritage with a specific Cape connection — Afrikaner and Cape Coloured families predominate in the oldest established lineages, and the community's linguistic culture moves between Afrikaans and Portuguese with the ease of a border community that has been doing it for a long time. Three centuries of transit have layered in Kumasi corridor influences — the west_reach trade route that runs through here brings a different cultural mix than the south_reach corridor — and the hospitality sector's workforce has the cosmopolitan character of places where a lot of different people stop.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Vuurkloof exports geothermal energy — processed into transit-grade power supplies for vessels refueling at the horizon station — and geothermal engineering expertise. The system imports food, which the geothermally lit surface produces in limited quantities from adapted cultivars, and manufactured goods through the Karoo and Kumasi connections. The energy export is structurally important for both adjacent systems' transit infrastructure; Vuurkloof's power supply contracts with the horizon station's refueling operations are the most lucrative revenue streams in the local economy.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The **Geothermal Engineers' Association** is the system's most influential professional body, managing the certification standards for the extraction and distribution infrastructure and providing the workforce for contract specialist placements at other systems. It is not a governance institution, but the settlement council has not acted against the Association's stated interests in living memory, which is a form of authority.
|
||||
|
||||
The **Hospitality Operators' Guild** manages the hot springs complexes and the broader transit accommodation infrastructure — a younger institution than the engineers' bodies but one that represents the system's most publicly visible economic face. The Guild's interests are aligned with high transit volume, which means it is the most vocal local advocate for maintaining reliable gate schedule connections through both Karoo and Kumasi.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The geothermal extraction infrastructure requires continuous monitoring and adjustment — the fault lines shift, vent pressures vary, and the maintenance schedule is constant. The Association's engineers know, with a precision that is not shared publicly, what the thermal output trajectory looks like over the next several centuries. The system's energy reserves are not depleting in any timeline that currently concerns the settlement. They are, however, concentrated in a pattern that the geological models suggest will shift the primary high-yield vent clusters away from the current extraction infrastructure toward areas of the fault system that have not been developed. The infrastructure investment required to follow the vents is not discussed in the settlement's public planning documents.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
A geothermal engineer has discovered that the maintenance logs for one of the secondary vent extraction conduits have been altered — not the current logs, but the archived records from forty years ago — in a way that would have concealed a thermal pressure event that, had it been reported at the time, would have triggered a mandatory infrastructure review.
|
||||
|
||||
---
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
DG is a spectral subtype of white dwarf — the "D" indicating white dwarf classification and "G" indicating the spectral composition of the remnant. GJ 35 is known astronomically as Van Maanen's Star, the nearest known solitary white dwarf to the solar system. The unusual-type header designation reflects the white dwarf classification, which falls outside standard main-sequence stellar categories. The habitable planet's surface conditions are maintained by geothermal output rather than stellar radiation — an unusual configuration that the briefing builds into the settlement's entire identity. Wave_3 settlement of an unusual-type system reflects the expanding frontier of the wave_3 emigration, when communities with specific technical traditions began selecting systems that offered resources matching their expertise rather than conditions conforming to standard settlement parameters.
|
||||
|
||||
---
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_292
|
||||
# GJ 354A
|
||||
**GJ 354A** | M-type | deep_frontier
|
||||
|
||||
---
|
||||
@@ -8,26 +8,31 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | F6IV · 44.0 ly |
|
||||
| **Star** | M · 37.4 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_4 |
|
||||
| **Settlement** | unsettled |
|
||||
|
||||
---
|
||||
|
||||
The primary world of GJ 354A has a thin atmosphere. Not absent — survey teams have confirmed the atmospheric composition falls within the range that makes a world technically habitable — but thin enough that the difference from a comfortable standard is felt in the pressure differential and addressed by engineering solutions that are available, reliable, and expensive. At hop twelve, the engineering cost lands entirely on any founding cohort, with no institutional infrastructure to absorb even the initial investment.
|
||||
|
||||
Survey teams noted the atmospheric thinness and moved on. That is the complete record of settlement consideration for GJ 354A: noted, measured, assessed as solvable at cost, determined to be not worth the cost at this distance, filed.
|
||||
|
||||
The corridor connects GJ 656 to GJ 684B, making GJ 354A a transit waypoint on the outer edge of this section of the deep frontier. Transit vessels pass through. The horizon station processes their transit. The thin-atmosphered world turns below, breathable in the sense that a reader can confirm the numbers are within parameters, unsuitable in the sense that no one has decided to breathe it.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
None.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
No faction presence.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
---
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_126
|
||||
**GJ 356A** | F-type | deep_frontier
|
||||
# Lichtung
|
||||
**GJ 356A** | F-type | west_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -8,26 +8,39 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | G8IV-V · 37.1 ly |
|
||||
| **Star** | F6V · 37.1 ly |
|
||||
| **Gates** | 1 aperture · dead_end |
|
||||
| **Settlement** | wave_5 |
|
||||
|
||||
---
|
||||
|
||||
Lichtung means "clearing" in German — the gap in the forest where the light gets through. The name was chosen with some deliberateness by settlers who arrived forty to a hundred years ago at the end of a long corridor of dim M-dwarf systems, found a bright F-type primary waiting for them, and felt the contrast viscerally. After Hansestadt and Marktfeld behind it, Lichtung burns noticeably different. The light here is white and sharp. Shadows have edges.
|
||||
|
||||
The habitable world sits in the inner zone of the F-type's broad luminosity band — warm, well-lit, with a strong UV environment that shapes what grows there and how people build. Early settlement architecture oriented around UV management: covered walkways, tinted glazing, vegetation canopies that filter rather than block. The community that evolved from those early choices has an outdoor culture defined by relationship with the star rather than avoidance of it.
|
||||
|
||||
As a wave_5 dead_end, Lichtung is new enough that its institutions are still forming. The settlement charter is a generation old. The first generation of locally-born adults is just entering civic life, and they have opinions about how things should work that differ from the founders in some cases and reinforce them in others. The founding German-heritage cultural tradition persists — language, naming conventions, community calendar — but it is being renegotiated by people who have never seen any other home.
|
||||
|
||||
Access is through Marktfeld, one gate, one direction. What comes here was sent here. What leaves was meant to go. The community is small enough that these facts are personal.
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Lichtung depends on Marktfeld for manufactured goods, medical hardware, and technical components. It is not yet producing significant surplus for export — agricultural output covers local needs, and early industrial capacity is directed toward self-sufficiency rather than trade. The economic relationship with Marktfeld is developmental: a young community that needs the connection to survive.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No external faction presence. A founding council runs civic affairs. The Commission issued the settlement charter and has a vessel stop annually. The stop is social as much as administrative.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The terms of the settlement charter's land allocation clauses, which the founding council negotiated with a Marktfeld-based commercial interest before the Commission was formally involved. Several allotments in the most productive UV-sheltered agricultural zone were pre-committed before public settlement began.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
The founding council recently passed an internal resolution — not yet transmitted to the Commission or to Marktfeld — declaring one of the pre-committed land allotments abandoned and opening it for local redistribution. The commercial interest that holds the original claim does not yet know.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
Wave_5 dead_end at hop 7 with an F-type primary is the defining characteristic — bright star at the corridor's end, accessible only through a commercial waypoint. The naming reflects genuine contrast with the dimmer corridor behind it.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,6 +1,14 @@
|
||||
# PLACEHOLDER_155
|
||||
# Eisfeld
|
||||
**GJ 3586** | M-type | west_reach
|
||||
|
||||
Eisfeld is not a destination. It is a middle point — the place between Ostmark (GJ 601A) and the dead-end spur at Dunkelholz (GJ 615) — and it has been functioning in that role for four hundred years. The Thuringian German settlers who founded it named it for the river meadow, something flat and useful, and the name has turned out to be accurate. Eisfeld is flat and useful. It has never tried to be anything else.
|
||||
|
||||
The M-type star here is dim enough that the primary habitable world sits well within the inner system, close and tidally influenced at its near side. Four hundred years of settlement have produced a community of maybe fifty thousand people distributed across the primary world and a modest station facility near the horizon gate system. The economy is transit services, maintenance depots, and the light agriculture that feeds a community that does not import food if it can avoid it. The founding Thuringian families were farmers before they were anything else, and some of that orientation has persisted even as the community's actual economic center of gravity shifted toward servicing the traffic that passes through.
|
||||
|
||||
What Eisfeld has that most way-stations do not is institutional patience. Four hundred years of managing a two-aperture through-route — inbound from Ostmark, outbound toward Dunkelholz, and the reverse — has produced administrative structures that are old enough to have outlasted every political reconfiguration of the west_reach behind them. The community's transit authority predates the current form of Assembly governance by a century and a half. It knows which records have to be filed to satisfy which oversight requirement and it files them promptly and it does not invite attention. The Commission has visited three times in the last century, and three times the records were exactly as they should be.
|
||||
|
||||
The transit depot is the social center in a way that would be unusual at a busier system. At Eisfeld, the depot's common areas are where most of the community's commerce and social interaction actually happens, because the depot is where the traffic is, and the traffic is the connection to everything inward. People come to watch the transits. Not to meet travelers in particular — just to confirm that the corridor is still open, that things are still moving, that Eisfeld is still on the route.
|
||||
|
||||
---
|
||||
|
||||
## System Profile
|
||||
@@ -15,19 +23,26 @@
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Eisfeld imports finished manufactured goods and specialized medical hardware from Ostmark and points inward. It exports transit services, maintenance capacity, and agricultural surplus — primarily preserved foods sized for the corridor traffic rather than export to inner systems. The community is more self-sufficient than a pure way-station would be, but the single-sector maintenance economy means that a significant disruption to west_reach transit would hit Eisfeld hard. The Dunkelholz spur is not a substitute — Dunkelholz imports what it cannot make and that trade runs through Eisfeld, adding to the dependency rather than diversifying it.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No Reach faction maintains a formal presence at Eisfeld. The transit authority has operated continuously for four hundred years and has a comprehensive set of working relationships with every institution that passes traffic through the corridor, but these are administrative relationships rather than factional affiliations. The transit authority director is currently the fourth member of the Brandt family to hold that position across three generations of genuine succession — the position has not been held by someone with the same name, but the family network around the Brandt house has managed to keep influence across the succession, which is a different kind of continuity.
|
||||
|
||||
The Commission's three visits have produced no findings. This is either evidence that nothing is wrong or evidence that the transit authority's record management is very good. Both propositions may be simultaneously true.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What Eisfeld manages carefully: the transit records for Dunkelholz-bound freight go into a separate filing system from the through-route records, which is administratively sensible — the spur is a distinct route from the through-route — but the separation also means that a Commission examiner doing a standard audit of the through-route records would not automatically see what has been moving into Dunkelholz. The transit authority knows this. It has never altered a record, never deleted an entry. It simply organized the filing in a way that makes a focused inquiry into Dunkelholz traffic require a specific request rather than appearing in the standard through-route review. No one has made that specific request.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
Four centuries of meticulous record-keeping, and the records for the dead-end spur are filed in a separate drawer that no audit has ever opened.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
Wave_2 at a through-route is consistent: the west_reach corridor needed nodes, and Eisfeld's position between Ostmark and the Dunkelholz branch made it an obvious settlement target in the trade expansion wave. The M-type star is dim but the system's value is logistical rather than resource-based, so stellar type did not constrain settlement. The through-route topology correctly reflects two apertures: one connecting to Ostmark inward, one connecting to Dunkelholz on the dead-end branch.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,6 +1,14 @@
|
||||
# PLACEHOLDER_237
|
||||
# Xa Vời
|
||||
**GJ 3612** | F-type | east_reach
|
||||
|
||||
Xa Vời means "far away." The name was chosen by the founding families with the blunt precision of people who had just finished a journey of ten corridor hops and understood exactly what they were describing. Three hundred years on, the phrase has become a settled identity: a farming community at the end of the east_reach corridor, with one aperture leading back the way you came and nothing else.
|
||||
|
||||
The F-type star here burns hotter and bluer than most corridor systems, pushing the habitable zone outward and flooding the primary world with broad-spectrum light that favors a particular style of agriculture — high-yield grains, leafy vegetables, and a calendar organized around intense growing seasons separated by hard rest periods. The founding Vietnamese families brought seed stocks and cultivation techniques adapted over centuries to humid, high-light environments, and they found that the primary world rewarded that knowledge. Xa Vời has been feeding parts of the east_reach corridor ever since.
|
||||
|
||||
Being a dead-end past Jeonnam (GJ 3728B) has shaped the community's character in specific ways. There is no through-traffic; everyone who arrives here intended to arrive here. The social texture is correspondingly tight — a population that has been more or less the same families for three hundred years, supplemented by occasional settlers who followed the corridor all the way to its end and decided not to leave. The agricultural cooperatives that manage most of the primary world's farmland are old institutions, some tracing unbroken records back to the founding wave. Disputes over water rights, soil allotments, and processing capacity are the political content of Xa Vời's civic life, and they are conducted with the seriousness appropriate to questions that actually matter.
|
||||
|
||||
The horizon station sits at standard distance. Getting there takes roughly five days from the primary world. The station is small, sized to a dead-end system's traffic volume: freight from the growing season, seasonal workers arriving and departing, the occasional researcher drawn by the corridor's terminus character or the star's spectral properties. The Assembly is a legal abstraction here — three hundred years of effective self-governance means the cooperatives have become the government, and they are skeptical of instructions from anywhere inward. The Commission is a name in shipping manifests.
|
||||
|
||||
---
|
||||
|
||||
## System Profile
|
||||
@@ -15,19 +23,26 @@
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Xa Vời exports food — primarily grain and processed vegetable products — to Jeonnam and, via Jeonnam, into the broader east_reach corridor. This is not a dependency in the crisis sense; the primary world grows enough to sustain its own population many times over, and the export trade is comfortable surplus rather than the system's economic lifeline. The system imports manufactured goods — tools, machinery components, medical hardware — that its small population cannot produce efficiently at home. The single aperture means all of this passes through Jeonnam. If the Jeonnam connection became problematic, Xa Vời could sustain itself; it could not easily replace what it imports.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No significant Reach faction has a formal presence in Xa Vời. The agricultural cooperatives ARE the governance structure: they manage the land registry, arbitrate disputes, maintain the port authority's few functions, and hold the community's institutional memory. The oldest cooperatives — Hội Nông Gia Đồng Bằng and the Liên Minh Canh Tác — have been operating for over two hundred fifty years and have accumulated the kind of quiet authority that comes from being reliably present when other institutions were not. Their leadership is elected but tends toward hereditary in practice; the families who have managed the land longest tend to produce the people who manage it next.
|
||||
|
||||
The Commission has a nominal filing relationship with the horizon station operator but no investigative presence. The Assembly's reach-wide regulations technically apply, but enforcement depends entirely on voluntary compliance. Three hundred years of distance has produced a community that distinguishes carefully between the law and what the law can actually do here.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What Xa Vời does not discuss outside the cooperatives: the horizon station's aperture has shown irregular activation patterns three times in the last forty years — brief, unexplained cycling events not associated with any scheduled transit. Each time, the station's own monitoring recorded it; each time, the cooperative leadership decided it was an instrument anomaly and filed it internally. The third occurrence was different enough from the first two that the cooperative archives now contain a sealed assessment prepared by the senior station coordinator that has not been forwarded to the Commission or the Veil Institute. The assessment does not conclude anything. It describes what was observed and notes that it was different. That the assessment exists at all is the part that is not discussed.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
The last system in the east_reach corridor has been quietly collecting anomalous horizon station readings for forty years, and the people who know about it have decided, again and again, that informing anyone outward is a worse outcome than not informing them.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
The header reads F-type to match the database classification. The READ-ONLY profile shows "k-m" — the in-universe stellar catalog designation, which is a different notation layer. The star's habitable zone and spectral character are consistent with an F-type: hot enough to push the agricultural season dynamics described above, bright enough to matter for crop selection. Dead-end topology at wave_3 is consistent: the corridor was extended to this point during the Wave 3 expansion precisely because the primary world's agricultural potential was identified, and extension stopped here because there was no compelling reason to go further.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_013
|
||||
# Encrucijada
|
||||
**GJ 393** | K-type | south_reach
|
||||
|
||||
---
|
||||
@@ -14,20 +14,51 @@
|
||||
|
||||
---
|
||||
|
||||
The name means crossroads in Spanish, and it was chosen without irony by the team that established the settlement approximately forty years ago: this was a system with five gate apertures and no settlement, a fact that someone in the south_reach's administrative infrastructure had known for a long time and that became increasingly difficult to explain as the systems on the other end of those apertures became populated and found themselves routing traffic through an empty hub. Wave_5 migration pushed into the zone that Encrucijada now anchors; the settlement was, in a meaningful sense, built to serve a hub function that the hub already had whether anyone lived there or not.
|
||||
|
||||
GJ 393 is an M2 — a mid-M dwarf, dim and red, at 23.0 light-years from the sun. The inhabited world is a close-orbit body, tidally influenced, with a day cycle substantially different from the 24-hour standard that most Reach settlements approximate. The founders' first infrastructure decision was a lighting schedule that imposes an artificial day-night cycle on the settlement's interior spaces, a decision that is now forty years old and that the settlement's children have grown up accepting as simply how time works here. The exterior, when visible — which is not often, because the settlement is primarily underground and enclosed — shows a sky that shifts from deep red to orange depending on the star's position, a color palette that newcomers find disorienting and that long-term residents have stopped noticing.
|
||||
|
||||
Five apertures at a single horizon station is unusual — most stations in the Reach carry fewer — and the settlement that grew up around this fact has five operating connections to navigate: GJ 435 (Mirante), GJ 644A, GJ 1111 (Zenzele), GJ 197 (Puerto Último), and GJ 54.1 (Ribeiro's Star). The connections reach in multiple directions through the south_reach and beyond it. The cargo that moves through Encrucijada's transit infrastructure in a single week exceeds the total annual freight volume of the dead-end systems connected to it by months of hop-distance. The settlement handles this volume with the kind of improvised competence that characterizes wave_5 operations: the systems work, the procedures exist, the personnel know what they are doing, but everything was built quickly and shows it.
|
||||
|
||||
The institutional structure of Encrucijada is the most contested element of the settlement's short history. Five apertures means five sets of adjacent systems that all have opinions about how the hub should be managed. The Concord Assembly's jurisdiction is clear in principle and in practice the subject of continuous negotiation: transit fee structures, inspection protocols, priority scheduling when gate capacity is constrained during simultaneous high-volume windows — each of these is governed by Assembly framework agreements, and each of them is also governed, in daily practice, by the preferences of the settlement's founding operator consortium, which built the freight infrastructure and has not been fully separated from it. The founders are still running it. The question of what governance structure eventually consolidates at Encrucijada — whether the operator consortium normalizes into something resembling a standard settlement council, or whether the hub's commercial importance produces a more explicitly commercial governance model — is the system's open question, and it is being answered in real time.
|
||||
|
||||
The forty years of settlement have produced approximately twelve thousand residents. That is a small population for a hub with this transit volume, and the smallness shows in the labor market: the settlement perpetually runs short-handed on technical roles, particularly gate operations and freight logistics management. The surrounding systems provide some labor in the form of short-rotation workers who cycle through Encrucijada for specific contract periods, but the settlement has not yet grown large enough to fully staff its own infrastructure from its own population. This creates a dependence on itinerant labor that in turn creates a social texture different from the long-tenured communities in the older dead-end and spur systems nearby: Encrucijada has more turnover, more new faces, more people whose primary social connection is to wherever they came from rather than to the hub itself.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Encrucijada imports almost everything: food, manufacturing goods, technical equipment, building materials. The settlement's young age and its function as a logistics hub rather than a production system means it has built service and transit infrastructure faster than any productive capacity. The surrounding systems — Mirante, Zenzele, Ribeiro's Star, Puerto Último — supply agricultural products and basic manufactured goods through the same gate connections that Encrucijada exists to service. The transit fee revenue funds the imports, which is structurally sound as long as volume remains high, and volume shows no sign of declining.
|
||||
|
||||
The one significant local production is the gate operations knowledge and logistics management expertise that Encrucijada's founders have accumulated. Other wave_5 settlements building transit infrastructure have hired Encrucijada consultants. This export of operational knowledge is not yet formalized as a commercial product, but the pattern is established.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The **Encrucijada Operator Consortium** is the settlement's de facto governing body through its control of the transit infrastructure. The consortium's five founding families — all Spanish-heritage, all from wave_5 migration flows — hold the operating licenses for the horizon station's freight management systems and the span gate connections that branch through the settled area. The consortium is not formally a government; it is a commercial entity with governance-adjacent authority. The Concord Assembly's framework recognizes it as the settlement's designated transit authority, which is the mechanism through which it exercises most of its practical power.
|
||||
|
||||
The Lattice Commission has a presence here — a three-person field office established two years ago when the hub's transit volume crossed a threshold that triggered mandatory Commission oversight. The field office is understaffed for the volume it is supposed to monitor and is engaged in continuous prioritization: which freight flows require actual inspection and which can be cleared on documentation review alone. The Commission's Encrucijada staff have submitted four staffing expansion requests in two years; all four have been held pending. The Commission's internal position is that Encrucijada's situation will normalize once the settlement matures and the volume per resident ratio decreases. The Encrucijada staff's position is that this will take a decade they do not have.
|
||||
|
||||
The Guardians of Autonomy have a chapter that is, unusually, advocating for *more* Assembly involvement rather than less: the founding consortium's governance authority is, from the Guardian perspective, an unaccountable commercial entity making decisions that affect the transit access of all five connected systems' populations. The chapter is allied with Assembly reform advocates in several of the adjacent systems.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The five-aperture configuration at Encrucijada's horizon station means that the station handles a coordination load that most stations do not. The simultaneous management of five gate sequences — their timing, their priority, their maintenance windows — is operationally complex. The founding consortium's gate operations team developed their own scheduling protocols during the settlement's first years, protocols that differ in several respects from the Assembly's standard transit management framework. The consortium has not disclosed the full technical details of these protocols to the Commission. The Commission's field office does not have the specialized expertise to audit them without external support. The question of whether the consortium's scheduling protocols comply with Assembly framework agreements is currently being assessed by a Commission technical review team that has been waiting for a scheduling window for eight months.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
The founding consortium recently accepted a short-term freight volume commitment from an unnamed client routing cargo through Encrucijada from GJ 54.1 (Ribeiro's Star) toward GJ 1111 (Zenzele) that, when the Commission's field office noticed it, was using a gate priority scheduling that should not be available for commercial cargo — a priority level reserved for emergency response and Assembly institutional freight — and when the Commission investigator asked the consortium's operations manager to explain, she said it was a legacy protocol classification that she had not gotten around to updating.
|
||||
|
||||
---
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
K-type header versus M2 stellar profile is a generation artifact; M2 is the correct class and governs all lore detail. Wave_5 with 5 apertures at hop 7 is the cluster of details that makes Encrucijada significant: the five apertures explain why a hub exists here rather than at a better-hosted star, and the wave_5 date explains why the hub's governance is still being negotiated rather than settled. Five apertures at a single station is at the upper end of the documented range (1–8 per station) and represents a horizon station that the builders configured for a junction function, though the builders' intentions — as with all horizon station questions — are not accessible to current analysis.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_197
|
||||
# GJ 394
|
||||
**GJ 394** | M-type | deep_frontier
|
||||
|
||||
---
|
||||
@@ -8,28 +8,37 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K7 Ve · 45.2 ly |
|
||||
| **Star** | M · 36.7 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | unsettled |
|
||||
|
||||
---
|
||||
|
||||
GJ 394 is the anteroom.
|
||||
|
||||
A dim M-dwarf primary, a habitable zone that survey teams consistently describe as technically within parameters and practically marginal — the primary world is cold, dry, and atmospherically sparse in the way that the outer edges of M-dwarf habitable zones tend to produce. Nothing about the system is hospitable. Nothing about it is dangerous in any way that would prevent transit. It exists in the corridor between GJ 177 and Einde at GJ 407, and its primary function in the transit graph is that it connects them.
|
||||
|
||||
Anyone traveling to Einde must pass through GJ 394. This is not incidental. The geography of the dead-end corridor means that the experience of reaching the furthest community in this section of the frontier includes a transit hop through an empty, dim, unwelcoming system. The cold world visible in the navigational display during that transit is not quite hostile, not quite habitable, and entirely consistent with the mood of approaching a community that chose maximum distance from institutional authority and settled past an empty space on purpose.
|
||||
|
||||
Survey teams have described the primary world as "meeting minimum atmospheric parameters" and "suitable for emergency shelter with appropriate equipment." Neither characterization suggests a settlement opportunity. Neither characterization has been offered in a tone of disappointment, because the survey teams knew what they were looking at.
|
||||
|
||||
GJ 394 is a corridor node. It connects two points. It is empty, and its emptiness is appropriate.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
None.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
No faction presence.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
---
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 11
|
||||
- **Adjacent Systems:** GJ 177, GJ 407
|
||||
- **Adjacent Systems:** GJ 177, GJ 407 (Einde)
|
||||
|
||||
@@ -1,6 +1,26 @@
|
||||
# PLACEHOLDER_088
|
||||
# Confluent
|
||||
**GJ 395** | M-type | west_reach
|
||||
|
||||
The name means confluence — where things flow together — which is accurate about the topology but misses the point entirely. Confluent is not primarily a transit junction. Confluent is wine.
|
||||
|
||||
The F8V star burns white-warm across the habitable world's growing regions, delivering a light spectrum that falls between the harsh blue of hotter stars and the red-heavy output of M-dwarfs. Four hundred years ago, the French founding families arrived with something more intentional than most settlement waves carry: root cuttings, soil analysis equipment, detailed viticultural records, and a proposition that this world's particular combination of mineral-rich volcanic soils, seasonal temperature variance, and stellar light could be made to yield something exceptional. They were correct, and the Reach has been drinking the evidence ever since.
|
||||
|
||||
The primary world — called simply le Pays among its inhabitants — is organized around viticulture the way extraction systems are organized around ore deposits. The growing regions are the economic core. The châteaux are the social institutions. The annual vintage cycle — pruning in the cool months, flowering and fruit-set through the warm season, harvest in the long amber weeks before the first cold front — is the calendar by which most of Confluent's residents measure their year. The horizon station and the transit infrastructure are important and everyone uses them and no one thinks they are what the place is about.
|
||||
|
||||
There are dozens of independent wine estates, ranging from the storied Grand Domaines with centuries of continuous operation to small family plots that have been producing the same varietal blend for four generations. The wines vary enormously. The warm, red-spectrum terroir of the Vallée de l'Intérieur produces full-bodied reds — the flagship Carignan de Vide is Confluent's most recognized export, a deep, tannic wine aged in local timber that achieves an iron-mineral finish unique to its slope. The cooler, elevated zones of the Plateau Gris yield whites — primarily the Gris Blanc varietal, a grape that developed under Confluent's light spectrum over the first two centuries into something with no exact counterpart in terrestrial viticultural tradition, a pale wine with extraordinary aromatic complexity and a quality that varies sharply between producers. The coastal lowland regions produce everyday table wines in quantity — reliable, unpretentious, and the wine that most corridor residents think of when they think of Confluent.
|
||||
|
||||
There are over sixty registered estates on le Pays, and the number shifts as parcels are divided by inheritance, consolidated by acquisition, or established on newly cultivated slopes. Among the most recognized:
|
||||
|
||||
The Grand Domaines — estates with continuous operation exceeding two centuries and Grand Vide Classé designation: **Domaine des Étoiles Fixes**, the oldest parcel on le Pays, whose flagship Carignan de Vide commands the highest inner-corridor prices. **Château Fond de Ciel**, on the Plateau Gris at Confluent's coldest growing elevation, producing the definitive Gris Blanc. **Domaine de la Longue Veille**, whose late-harvest dessert wine — Veille Dorée — is produced in quantities so small that most corridor residents have heard of it and none have tasted it. **Château Bonne Terre**, a Vallée de l'Intérieur estate whose Carignan de Vide ages differently from the Étoiles Fixes expression — rounder, less mineral, preferred by buyers who find the Étoiles Fixes too austere.
|
||||
|
||||
The established corridor names: **Mas de la Traversée**, the volume producer whose table wine is what most west_reach workers have actually drunk. **Clos du Grand Passage**, the cooperative estate blending multiple terroirs into the corridor's standard good white. **Domaine Lumière Pale**, whose dry rosé — simply Lumière — has become fashionable in the inner corridor in ways that slightly embarrass the estate. **Vignoble de la Nuit Profonde**, a coastal estate whose proprietary three-varietal blend is widely expected to receive Grand Vide Classé status within the decade. **Château des Brumes**, a Plateau Gris producer whose Gris Blanc rivals Fond de Ciel's in quality and exceeds it in consistency, sparking a rivalry that has lasted four generations. **Domaine Seuil du Vide**, named for its position at the settlement's outward edge — "threshold of the void" — producing a mineral-driven white from volcanic soil that no other estate has access to.
|
||||
|
||||
The smaller estates that corridor buyers may encounter: **Clos Petit Matin** (early-harvest whites), **Mas Soleil Bas** (low-altitude reds from the river flats), **Domaine de l'Ancre** (a single-parcel estate producing one wine — a blended red called L'Ancre — from vines that are among the oldest on the planet), **Château Vent d'Étoiles** (high-altitude rosé competing with Lumière Pale for the inner-corridor fashion market), **Vignoble du Passage Étroit** (a through-route adjacent estate whose wines are the first thing transit crews encounter and the last thing they buy before departing), and dozens more. The full registry of Vins de Grand Vide member estates runs to three pages and changes annually.
|
||||
|
||||
**Vins de Grand Vide** — Wines of the Great Void — is the institution that makes all of this commercially viable at corridor scale. See the separate corporation document. The short version: a négociant-style cooperative that aggregates production, certifies quality, manages logistics, and has been doing so for three hundred and fifty years. The individual estates grow the wine; Vins de Grand Vide is why it arrives at its destination in the right condition at the right price.
|
||||
|
||||
The transit function — Confluent is a through-route connecting Alshain (GJ 771A) inward and Randsholm (GJ 775) outward — is real and necessary but operates in the background of a society organized around something else. The horizon station processes freight (mostly wine, outbound) and arrivals (buyers, researchers, the occasional pilgrim who has decided to drink their way through the estates). Transit processing is efficient because Vins de Grand Vide long ago worked out the logistics of moving fragile cargo through aperture transit, and the customs and handling procedures that govern wine shipments from Confluent are some of the most detailed and carefully negotiated in the west_reach.
|
||||
|
||||
---
|
||||
|
||||
## System Profile
|
||||
@@ -15,19 +35,26 @@
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Confluent exports wine and imports almost everything else of significance: manufactured goods, medical hardware, construction materials, energy infrastructure components. The agricultural sector is overwhelmingly focused on viticulture — food crops are grown for local consumption but not at surplus scale, so Confluent imports a meaningful fraction of its basic food supply from Alshain and Randsholm. This is a structural vulnerability that the community is aware of and manages through strategic reserves and the negotiating leverage that comes from being the source of a product that inner-corridor buyers reliably want. The leverage is real but not unlimited. A sustained disruption to the wine export trade would hit the local economy hard before any political response could be organized.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No formal faction presence. The dominant institutional actor is Vins de Grand Vide, which has de facto governance functions in the wine-growing regions that technically belong to the system's administrative council — quality certification decisions have legal weight, distribution network access can be withheld, and the Comptoir's commercial archives extend back to the founding era. The administrative council handles everything outside the wine economy and consults Vins de Grand Vide on anything that intersects with it.
|
||||
|
||||
The estate families are their own political class. The Grand Domaine families — particularly the Delacroix family at Domaine des Étoiles Fixes and the Brissac-Fontaine family at Château Fond de Ciel — have more effective political weight than their formal roles would suggest. In a community where the quality of your land determines the quality of your social position, old family name and old vineyard parcel tend to correlate.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What Vins de Grand Vide does not discuss: the Comptoir's commercial archive contains three hundred and fifty years of distribution data across the west_reach corridor. Every major commercial relationship, every freight arrangement, every buyer and intermediary across eight or nine hops. The Comptoir was built to serve the wine trade and has no formal obligation to share what it knows with any regulatory body. What it actually represents is an extraordinarily detailed map of how commercial relationships in the deep west_reach actually function — who depends on whom, what margins actually look like, which freight intermediaries have been reliable and which have not. The institutions that would most benefit from access to this archive are the ones that Vins de Grand Vide has the most incentive to keep at arm's length.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
Every bottle of wine from Confluent passed through an institution that has been recording corridor commercial relationships for three and a half centuries, and that institution reports to no one.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
The header reads M-type per the database classification. The READ-ONLY profile shows F8V — this is the in-universe catalog notation for the same star. F8V is a late F-type, near the F-G boundary, consistent with the agricultural character described: brighter than a G-type but not the harsh blue end of the F range. Wave_2 through-route is consistent with a system settled for its resources rather than its position — the founding families came for the land, and the transit infrastructure was built around them because the corridor needed a node here anyway.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_011
|
||||
**GJ 3988** | binary-type | deep_frontier
|
||||
# GJ 3988
|
||||
**GJ 3988** | binary-type | north_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -14,20 +14,31 @@
|
||||
|
||||
---
|
||||
|
||||
GJ 3988 is a K-M binary pair — two dim stars in a close mutual orbit, their habitable zones either nonexistent or destabilized by tidal perturbation. Surveys conducted during the corridor's extension found no planetary body suitable for settlement: the inner orbits are chaotic, the outer orbits cold. The system exists in the network because the gate infrastructure was laid to reach Mossbank beyond it, not because anyone wanted GJ 3988 for itself.
|
||||
|
||||
Horizon gates were built here to serve as a transit node. Nothing else was built. The apertures mark the in-system transition point, and a bare-minimum automated relay station runs on solar harvest, maintaining position-lock data and issuing standard navigation broadcasts. It has been doing this, without maintenance, for the better part of two centuries.
|
||||
|
||||
The binary's gravitational geometry makes in-system maneuvering slightly more demanding than average — nothing extreme, but captains who have not run the corridor before sometimes request updated charts before committing to the approach. The charts are available, frequently outdated, and nominally the responsibility of the Athabasca system two hops back.
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
None. The system has no population and no resource extraction. Vessels transit through; nothing stops.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No faction presence. The automated relay is Commission-registered infrastructure, but no one has formally inspected it in years. Its operational status is presumed from the fact that it continues to broadcast.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
Not applicable — no population to keep silence.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
A vessel reported a third navigation signal in the system last year — not the relay, not a passing ship's transponder, something else. The report was logged at Athabasca and filed under "equipment anomaly." Nobody has gone to look.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
Unsettled binary at hop 6 functioning as a transit node is consistent with the Cairn pocket's incremental settlement pattern — gate infrastructure extended ahead of population, routing determined by adjacent viable destinations.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_153
|
||||
**GJ 4053** | K-type | south_reach
|
||||
# Dzimbahwe
|
||||
**GJ 4053** | M-type | south_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -14,20 +14,51 @@
|
||||
|
||||
---
|
||||
|
||||
Great house of stone. That is what the word means — the Shona language's way of describing a structure so substantial, so permanent, that it defines the landscape around it. The civilizations of the southern African plateau built their great houses from granite, dry-stacked without mortar, and the ruins of those structures survived centuries longer than the civilizations themselves. The founding generation that named this system four hundred years ago was making a statement about duration. They intended to build something that would outlast the people who built it.
|
||||
|
||||
GJ 4053 is an M0V — a borderline early M dwarf, warmer than the mid and late M-types that characterize most of the outer south_reach, with a habitable zone closer in than Zenzele's but not as extreme. The inhabited world is tidally influenced but not fully locked, rotating slowly enough to have a genuine day-night cycle, though a long one — something like ninety-three standard hours. The surface is geologically active in the specific way that produces valuable outcomes: the tectonic processes that fracture and resurface the crust have pushed dense mineral deposits close to the surface across extensive areas of the primary continent. The founding survey described the geological situation as unusually favorable for surface extraction. They were right, and four hundred years of extraction have not depleted it.
|
||||
|
||||
The stone that defines Dzimbahwe's culture is not mined for bulk processing. The system exports raw materials — principally refined dense basalt and a locally named metamorphic stone called Chikomo, a dark-grey material with a fine, regular crystalline structure that polishes to a near-mirror finish — to construction and industrial operations across the south_reach. The bulk trade is the economic base. But what Dzimbahwe is known for, across the south_reach and in corners of the inner systems where people pay attention to such things, is the sculptural tradition.
|
||||
|
||||
The tradition is four hundred years old and has never been standardized. Dzimbahwe's stone-workers take the same material the mining cooperatives export in bulk and apply an accumulated aesthetic vocabulary — Shona and Ndebele in its founding grammar, but absorbing over four centuries whatever visual languages arrived with new settlers and were found worth keeping. The figures carved here are not representational in the conventional sense; they describe forces and relationships more than shapes, working with the stone's grain to find what is already present in the material and make it visible. The most sought-after pieces from established carving families command prices in the inner ring that the stone-workers find both accurate and beside the point. The commercial value is a byproduct. The work is the thing.
|
||||
|
||||
**Chikomo Extractions** is the bulk mineral export operation — not a single firm but a collective of six cooperatives operating under a shared brand for external markets. The collective was formed by the founding families' descendants as a counter to the early tendency of core commercial interests to play the individual cooperatives against each other in price negotiations. Four hundred years of shared marketing have made the Chikomo Extractions name recognizable in inner-ring construction supply markets as a quality indicator; the brand is not glamorous, but it has a reputation for specification reliability that procurement managers trust. The collective's combined volume makes it a significant supplier for habitat construction in the south and west reaches.
|
||||
|
||||
The two gates connect to Zenzele (inward) and GJ 827 (outward). The Zenzele connection routes Dzimbahwe's exports into the broader south_reach distribution network; the GJ 827 connection extends the spur outward to a less-trafficked frontier system.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Dzimbahwe exports refined stone materials through Chikomo Extractions and sculptural work through the individual carving families' own distribution relationships. The system imports food staples — the close-orbit world's agriculture is adequate but mineral-soil chemistry makes some crops difficult — primarily from Zenzele and through it from Inhambane's grain network. Technical components for the mining and processing infrastructure come from inner-ring suppliers via Zenzele. The system is not supply-critical in any single dependency; the geological abundance makes the extraction operation robust against most input disruptions.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The **Chikomo Extractions Collective** holds the bulk export contracts and negotiates on behalf of all six member cooperatives for pricing and terms. Its leadership rotates among the founding families' representatives, a system that has functioned continuously for the collective's three-hundred-year history with only two formal disputes — both resolved by Ferreira Monteiro at Matamba. The collective's accumulated precedents from those resolutions are cited in Ferreira Monteiro's casebooks as examples of cooperative contract interpretation.
|
||||
|
||||
The **Dzimbahwe Carvers' Association** is not a cooperative in the commercial sense — it is a professional body that maintains the tradition's standards through mentorship chains and certifies the lineage of individual carvers' training. Certification by the Association does not determine whether a piece can be sold; it determines whether a piece can be described as coming from Dzimbahwe's tradition rather than merely from this system. The distinction matters to buyers who can tell the difference. The Association has expelled three families in its history for failing to maintain lineage transmission — a severity that signals how seriously the tradition takes its own continuity.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The Chikomo Extractions Collective's pricing agreements with inner-ring construction suppliers have been stable for decades — too stable, in the assessment of the outer south_reach's smaller construction cooperatives, who have noticed that the prices they pay for Chikomo materials at their end of the distribution chain have risen consistently while the prices at which the collective sells to the inner-ring suppliers have not moved proportionally. The differential is being absorbed somewhere in the distribution chain. The collective's position is that distribution cost increases are a matter between the distribution cooperatives and their customers. The distribution cooperatives involved in the south_reach supply chain have not been audited in forty years.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
The eldest daughter of one of Dzimbahwe's founding carving families is attempting to authenticate a piece attributed to the third generation that would, if genuine, rewrite the timeline of the tradition's formal vocabulary development — and the authentication process has surfaced a buyer's provenance record that should not exist.
|
||||
|
||||
---
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
M0V places GJ 4053 at the warm end of the M-dwarf sequence — a borderline type that could reasonably be classified as either K or M. The system profile specifies M0V; the header uses M-type to match. The briefing designates K-type, which reflects the ambiguity of the M0 classification boundary; the profile is authoritative. Wave_2 settlement at hop 5 is explained by the founding generation's deliberate selection of resource-rich systems at the outer edge of the early settlement arc — Dzimbahwe's geological surveys were flagged as high-priority in the second emigration wave's targeting data.
|
||||
|
||||
---
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,6 +1,16 @@
|
||||
# PLACEHOLDER_083
|
||||
# GJ 4056
|
||||
**GJ 4056** | M-type | west_reach
|
||||
|
||||
No settlement. No name. The horizon station here exists because the corridor requires it — a link between Alshain (GJ 771A) inward and the ancient community at Echternach (GJ 127B) outward — but nothing about the system itself has ever attracted a human presence that was not simply passing through.
|
||||
|
||||
The M-type star is dim even by M-dwarf standards: the habitable zone is narrow and close-in, and the one rocky world that occupies that zone is geologically active in ways that make surface settlement impractical rather than merely uncomfortable. The primary world experiences tidal heating from the star's gravitational field — its proximity produces surface deformation rates that create continuous low-level volcanic activity across roughly forty percent of the surface. Not spectacular eruption events, but a steady outgassing that has produced a CO2-nitrogen atmosphere too thick to breathe and laden with sulfur compounds. The surface temperature swings between hemispheres are significant. There is no stable land surface above a scale where you would want to build anything.
|
||||
|
||||
Beyond the primary world, the outer system has what most M-dwarf systems have: cold, rocky bodies, some ices at the outer edges, nothing economically interesting enough to motivate extraction under conditions that would require sustained human presence. The resources are there in the sense that resources are everywhere, but there are easier places to extract them. Nobody has ever made a compelling case for Gj 4056 as an extraction target, because making the case for GJ 4056 requires arguing that it is better than somewhere more accessible.
|
||||
|
||||
The horizon station is automated in operation and minimally staffed. There is a small caretaker crew — typically six to eight people rotating on three-month cycles out of Alshain — whose job is to confirm the station's self-maintenance systems are functioning and to assist any vessel that arrives with a technical problem. They live in standard station quarters, run their monitoring routines, and wait out their rotation. The assignment is sought after by certain personality types and avoided by others, which is an accurate description of the assignment. The transit schedule through GJ 4056 is regular but not frequent — this is not a high-traffic corridor segment — and the days between transits are as quiet as anything in the organized Reach gets.
|
||||
|
||||
The Alshain caretaker crews have their own informal culture about the posting, accumulated over the century and a half since the corridor was extended through GJ 4056 to reach Echternach. There are stories about the primary world's volcanic activity being visible from the station on clear approach, the orange-red glow against the star's dull light. There is a tradition of maintaining a handwritten log in the caretaker's common room — separate from the official digital monitoring records — where each crew leaves notes for the next. The log has been running continuously for about a hundred years. It mostly records weather conditions on the primary world (observed at distance), maintenance anomalies, and personal notes. There are a few entries that describe sensations rather than observations: a persistent sense of something behind the routine, an unease that some crews report and others do not. The caretakers who report it generally say it faded after the first few weeks. Nobody has ever been able to say what it was.
|
||||
|
||||
---
|
||||
|
||||
## System Profile
|
||||
@@ -15,19 +25,24 @@
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
None. The minimal caretaker crew is resupplied from Alshain on the transit schedule. The system has no local economy and no production capacity. It is a point in the corridor.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The horizon station caretaker rotation is administered by Alshain's transit authority under a standing maintenance contract. No Reach faction has a presence here and no faction has ever sought one. The Commission has the station in its registry as a monitored transit node and receives automated telemetry from the station's standard monitoring systems. No Commission officer has visited in living memory. The caretaker crews are Alshain residents on temporary rotation and maintain their legal and social identity as Alshain citizens; no one considers themselves a GJ 4056 resident.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The handwritten log in the caretaker common room is not part of the official monitoring record and has no formal status. The caretakers know it exists; Alshain's transit authority knows in a general way that caretaker crews maintain informal logs; no one has done a formal review of its contents. The entries describing persistent unease are distributed across multiple crew rotations spanning roughly sixty years, are written in different hands, and describe similar but not identical experiences. None of the people who wrote those entries filed a formal report. Several of them have not taken a second rotation.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
A hundred years of informal caretaker logs record something that the official monitoring has never detected, and the crews who experienced it never reported it, and some of them never came back.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
Unsettled status with through-route topology is the corridor's most straightforward case: the system is on the route because the route needs it, not because anyone wants to be here. The M-type designation in the header matches the database classification. The profile shows "g" — a different catalog notation for the same stellar body. The geologically active primary world provides a consistent explanation for why four hundred years of corridor traffic through this node has produced no settlement attempt.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Chalawan
|
||||
# Einde
|
||||
**GJ 407** | K-type | deep_frontier
|
||||
|
||||
---
|
||||
@@ -8,26 +8,49 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | G0V · 45.9 ly |
|
||||
| **Star** | K · 40.1 ly |
|
||||
| **Gates** | 1 aperture · dead_end |
|
||||
| **Settlement** | wave_5 |
|
||||
|
||||
---
|
||||
|
||||
Einde means "end" in Afrikaans and Dutch, and it is meant in every sense the word carries.
|
||||
|
||||
The community is forty to one hundred years old — young enough that the founding generation is still alive, old enough that children born here have grown up with no other home. It sits at the end of a dead-end corridor off an unsettled system, meaning that to reach Einde you must first pass through the empty, unwelcoming space of GJ 394 — a dim M-dwarf with a cold primary world and no human presence — and then through a single aperture that opens into this system and no other. There is no through-traffic. No one arrives at Einde by accident or by transit. Every person here came here on purpose, or was born here after their parents came on purpose.
|
||||
|
||||
The founding trauma is known to every resident and is not discussed with outsiders: a pressure containment failure at an inner-corridor extraction facility. The specific system, the specific facility, the specific corporate contractor whose deferred maintenance created the conditions for the failure — these details are part of the community's internal memory and are not offered freely. What is offered freely, if you earn the right to ask, is this: it killed people. It contaminated the settlement zone. The survivors who chose to leave chose maximum distance from heavy industry, maximum isolation from the kind of economic pressure that produces deferred maintenance, and maximum control over the physical conditions of their own lives.
|
||||
|
||||
Einde's economy is agricultural by design and by conviction. The community produces food, maintains infrastructure, and provides for its own needs through labor-intensive methods that are deliberately chosen over industrial alternatives. There is no extraction under pressure. There are no large-scale industrial processes. There is no heavy equipment whose failure could kill everyone present. This is not poverty — the community is not poor — it is a specific and considered decision about acceptable risk, made by people who understand catastrophic industrial failure in personal terms and have organized their lives around never being vulnerable to it again.
|
||||
|
||||
The name is both honest and defiant. Einde is the end — the end of the corridor, the end of transit options, the end of whatever trajectory brought the founding families here. It is also, the community would argue, the beginning of the only arrangement they find acceptable. You do not arrive at Einde on your way to somewhere else. You arrive because this is where you meant to go.
|
||||
|
||||
The world itself is adequate — a K-type primary, enough warmth, breathable atmosphere, reasonable agricultural conditions. The community has spent forty to a hundred years learning it and has developed a careful relationship with its ecology that reflects the founding instinct toward sustainable, controlled systems. The primary world is not lush. It is enough, and enough is what the community was looking for.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Technical components and manufactured goods that the community cannot produce locally, primarily precision instruments, medical supplies, and specialized agricultural equipment. Supply arrives via the single corridor through GJ 394, meaning any disruption to that corridor isolates the community completely. The community maintains stockpiles calibrated for extended isolation. This is considered basic prudence, not crisis planning.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No faction presence. The community's founding motivation — maximum distance from institutional and industrial authority — produces deep suspicion of all organized external institutional contact. Commission inquiries receive minimum required compliance responses. Assembly registration has been filed; participation in Assembly governance is nominal. No Syndic operations have been proposed and none would be accepted. The community governs itself by community assembly, with decisions made by full resident participation. The process is slow. It is considered correct.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The specific incident — facility name, contractor, system location, the institutional failure chain that allowed the deferred maintenance to reach the point of catastrophe. The community holds this information internally. Discussing it with outsiders is experienced as reopening something the community has not quite closed; the wound is old enough to have a scar but not old enough that the scar has no feeling.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
A community founded on the furthest possible remove from industrial catastrophe — dead end, past empty space, single aperture — living the specific arrangement that maximum distance from institutional authority makes possible, and watching carefully to ensure they are never again in the position of trusting someone else's maintenance schedule with their lives.
|
||||
|
||||
---
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_287
|
||||
**GJ 410** | M-type | north_reach
|
||||
# Wagtoring
|
||||
**GJ 410** | K-type | north_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -14,20 +14,51 @@
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Wagtoring is not uninhabited. That designation appears in at least one regional registry — originating, almost certainly, from Oude Kraal's own off-hand description to a corridor survey team that did not press further — and it has propagated uncorrected ever since because nobody passing through the north_reach corridor had reason to look closely. The system has no public transit schedule, no registered commercial operators, and no gate listing in the standard booking infrastructure. To the Reach at large, it is a dim K-type dead_end at the outer edge of the north_reach, adjacent only to Oude Kraal, and it registers as unremarkable void.
|
||||
|
||||
What it actually contains: a permanent outstation maintained by Oude Kraal's founding families, staffed on rotation, and considered by those families to be their own territory in all but formal registry classification.
|
||||
|
||||
The outstation is called Wagtoring — Afrikaans for watchtower, one of the few founding-language words still in active use at Oude Kraal — and the name is exactly literal. It was established by Oude Kraal's community assembly roughly 180 years ago, in a period of consolidation after the north_reach corridor had extended far enough that systems beyond their own gate were no longer guaranteed empty. The assembly's recorded rationale was brief: they wanted eyes on the space beyond their aperture. The outstation was built, staffed, and has been staffed continuously since.
|
||||
|
||||
What the watchtower is watching for has never been formally specified. The founding resolution described "awareness of approach" as the purpose, which is either a very old-fashioned security instinct from a community shaped by frontier isolation, or a deliberate vagueness from people who had something specific in mind and chose not to put it in the written record. The current rotational families — six extended family lines, cycling through in staggered three-year postings — don't discuss it in those terms. Wagtoring is a posting: demanding, remote, and respected within Oude Kraal as evidence of a family's commitment to the community's oldest obligations.
|
||||
|
||||
The outstation itself is physically minimal: a horizon station docking point, a pressurized habitat cluster built into a captured body in the system's inner belt, a sensor array that has been extended and upgraded continuously for 180 years, and the usual accumulation of a permanent human presence — workshops, storage, small-scale cultivation, a library. The population at any given time is between twelve and twenty adults plus children. By the criteria that corridor registry uses to distinguish "settlement" from "facility," Wagtoring falls into a gap: it is too permanent to be classified as a facility, too small and privately maintained to qualify as a settlement in the way the inner corridor uses the word.
|
||||
|
||||
Oude Kraal considers the classification gap irrelevant. Wagtoring is theirs.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Wagtoring is supplied entirely by Oude Kraal through the single aperture connecting the two systems. There is no independent supply chain and no external commercial relationship. Essential maintenance components, food supplements, and replacement equipment all arrive on Oude Kraal's own shipping, on Oude Kraal's own schedule. This is the intended arrangement. The outstation's design philosophy, consistent with Oude Kraal's 500-year posture of self-sufficiency, prioritizes the ability to operate at reduced capacity for extended periods if resupply is delayed. It is not designed to depend on anything it cannot reach from its own aperture.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
Wagtoring has no independent factions. The outstation is an extension of Oude Kraal's community structure: staffed by families who answer to the assembly, operated under standing orders from the assembly, and financed from the community's communal resource pool. The senior voice on-station at any time is the senior family head on posting, whose authority is practical and traditional rather than formally chartered. Disagreements at the outstation go to the assembly at Oude Kraal; there is no local resolution mechanism for anything significant.
|
||||
|
||||
The six rotating families each have their own traditions around the posting — which months they prefer, which watch protocols they consider authoritative, how they relate to the sensor logs — and there is occasional friction between incoming and outgoing rotations about procedures. This is not institutional conflict. It is the ordinary friction of a small community with long memories.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The 180-year-old assembly resolution that established Wagtoring is in Oude Kraal's records, but the deliberation that preceded it is not. The assembly's founding-era gap in records (noted in Oude Kraal's own silence material) extends into this period. What prompted the decision — whether it was a specific incident, a specific piece of information about the space beyond their gate, or something seen in the early sensor data that was later suppressed — is not documented in any accessible record. The current rotational families know the outstation's protocols and its standing orders. None of them know why those standing orders have the specific shape they do.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
A researcher compiling a regional survey of outer north_reach settlement patterns discovers that Wagtoring's sensor logs, which Oude Kraal has never shared with any external body, would represent 180 years of continuous observational data on traffic and anomalies in this corner of the Reach — and approaches the assembly to request access, not knowing that this is the one request Oude Kraal has refused, without explanation, every time it has been made.
|
||||
|
||||
---
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
Wave_3 settlement at hop 7 as a dead_end is unusual but consistent with Oude Kraal's specific history: the outstation was established by a wave_1 system's own decision, not by corridor expansion infrastructure. It was not settled by the wave pattern that governs most of the corridor — it was extended by a single community acting on its own initiative. The wave_3 classification reflects when Wagtoring was established relative to overall Reach settlement history, not the wave pattern that would normally explain a hop-7 system. The population is genuinely small enough that "settlement" is a soft classification; the outstation exists because Oude Kraal wanted it to exist.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_267
|
||||
# Vindkast
|
||||
**GJ 414A** | M-type | west_reach
|
||||
|
||||
---
|
||||
@@ -14,20 +14,37 @@
|
||||
|
||||
---
|
||||
|
||||
Vindkast was settled within the last forty to one hundred years — precise founding dates are contested because the first wave of arrivals came in stages, beginning as licensed prospecting teams and transitioning to permanent settlement status only after the initial mineral surveys confirmed viable long-term extraction potential. The name is Norwegian: "wind blast." The settlers knew what they were moving to before they arrived. The survey data was unambiguous about the atmospheric conditions, and they came anyway because the same geological exposure that makes the planet inhospitable also makes it legible.
|
||||
|
||||
The world is high-altitude and wind-scoured across most of its surface. Its primary continent sits at significant orbital eccentricity, producing seasonal variation severe enough that the equatorial plateau — where the settlement is established — experiences wind-shear conditions that would ground standard transit vehicles for roughly a third of the year. The bedrock is exposed across wide plains where erosion has stripped away everything that would have buried the mineral seams on a calmer world. Silicate structures that would require deep drilling elsewhere are visible from surface survey. The settlers came with exposure mapping equipment and set to work.
|
||||
|
||||
The community is young and has the character of early settlement: an improvised governance structure built around the original prospecting claim-holders, infrastructure that is functional rather than finished, and a social density that comes from everyone knowing everyone because everyone arrived in the same decade or two. The first generation of children born on Vindkast is now reaching working age. The community is deciding, in real time, what it wants to be — whether the claim-holders who built the initial infrastructure will consolidate into something resembling the single-family resource operations elsewhere in the corridor, or whether the wave of younger workers arriving from GJ 3737 will push for different arrangements.
|
||||
|
||||
The loop connection to GJ 542 (Kopparhytta) is practically important: Vindkast's extraction operation produces raw ore and mineral concentrate that requires processing infrastructure Vindkast does not yet have. Kopparhytta's smelting capacity has been the practical outlet for Vindkast product almost since the beginning. The two communities have developed working ties that are closer than either has with GJ 3737, despite the formal topology.
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Vindkast depends heavily on inbound freight for almost everything that is not extracted from the ground. Wave_5 settlement means the agricultural base is minimal — most food is imported, some is grown in climate-controlled structures that were themselves imported. Technical equipment for the extraction operation comes from GJ 3737 inward, with a transit lag that has shaped the community's approach to maintenance: everything is maintained longer than the manufacturer specifies and repaired rather than replaced wherever possible.
|
||||
|
||||
Outbound: raw mineral concentrate (primarily silicate-metal composite ore), surface-extracted mineral samples sold to geological survey agencies in the inner corridor, and a small volume of crystalline mineral formations that have developed a decorative market value — Vindkast wind-cut crystal, shaped by atmospheric abrasion into irregular but aesthetically interesting forms, sold through Kopparhytta's artisanal export channels.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No Commission presence. The Vind Prospecting Cooperative — the successor entity to the original claim-holder group — manages the aperture transit facility and handles customs functions under a provisional operating license that has been renewed twice without review. The cooperative's leadership is the de facto government.
|
||||
|
||||
A minority faction of newer arrivals, loosely organized around a community meeting structure called the Taksting ("roof assembly," referring to the pressurized meeting hall that serves as the settlement's main civic space), has begun pushing for a formal settlement charter and elected governance. The cooperative's founding members are not opposed in principle but are moving slowly, as people who built the infrastructure tend to move when asked to redistribute authority over it.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The original survey team. Vindkast's formal settlement license was preceded by an eighteen-month licensed prospecting period conducted by a team whose composition is not in the public record. The current cooperative leadership includes none of the original prospectors. Where the original team went — whether they sold their claim position and moved on, or whether something about the early survey period ended their involvement — is not discussed. The wind-cut crystal market emerged suspiciously quickly for a wave_5 settlement, suggesting some pre-settlement market development that would have required the original survey team's involvement.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
The wind-cut crystal pieces reaching inner-corridor collectors have begun arriving with trace mineral compositions that do not match any mapped extraction zone on the planet's surface survey.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
The K8V stellar class sits near the bottom of the K-type range, close to M. It provides substantially less insolation than a mid-K star, which contributes to the atmospheric dynamics that produce the wind conditions: the temperature differential between the planet's equatorial and polar regions is compressed, but the low atmospheric density at altitude produces high-velocity wind shear rather than the low-energy circulation pattern a warmer world would generate. Wave_5 settlement at hop 8 reflects the loop topology — Vindkast was accessible through an established corridor chain rather than requiring independent deep-reach transit capacity.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Alula Australis B
|
||||
# Quilombo
|
||||
**GJ 423B** | K-type | south_reach
|
||||
|
||||
---
|
||||
@@ -14,20 +14,49 @@
|
||||
|
||||
---
|
||||
|
||||
The name was chosen deliberately by people who knew exactly what they were choosing. A quilombo was a settlement formed by self-liberated enslaved Africans in colonial Brazil — Palmares was the most famous, lasting nearly a century before the colonial military finally broke it, but there were hundreds of others, scattered across the interior, the coast, the forest margins, places where the geography offered enough difficulty to buy time for self-governance. The quilombos were not merely escaped settlements. They were functioning societies with their own governance, agriculture, trade, and defense; they were proof that the people who had been told they were incapable of self-organization were capable of building something better than what they had been forced to participate in.
|
||||
|
||||
The families who named this system Quilombo were Afro-Brazilian, wave_3 settlers three hundred years ago, and they brought both the history and the intention. They chose a through-route position, two apertures, a star that was warm and stable, and a name that said: we govern ourselves here, we have governed ourselves before, and we will continue to do so without asking permission. Three centuries have given that intention time to become architecture.
|
||||
|
||||
The stellar profile is a G0Ve — a warm, slightly evolved G-type star with emission activity, positioned at 34.0 light-years. The habitable world is comfortable in the way that G-type worlds usually are: agricultural, manageable seasons, gravity and atmosphere that do not require significant biological adaptation from baseline-human populations. The founding generation's agricultural expertise translated well. The community has been food-sufficient since the first generation and export-capable since the second.
|
||||
|
||||
Quilombo sits on a through-route connecting GJ 473A inward and GJ 67 (Roça Nova) outward. The two apertures mean freight moves through in both directions, and the settlement has built its economic model partly around that transit traffic: logistics services, refueling, maintenance, the hospitality infrastructure that through-route crews use during layovers. The transit economy does not dominate. It supplements. The agricultural base and the local services economy are the foundation; the through-route traffic is the margin that makes the foundation comfortable rather than merely adequate.
|
||||
|
||||
Three hundred years of quiet independence has produced a community that is, by outer-reach standards, extremely well-organized. The governance structures are thorough without being elaborate: a council of elected representatives, clear procedural rules, a tradition of deliberation that is slow enough to be thorough and fast enough to be functional. The community practices a form of economic mutual obligation that the founding generation brought from the quilombo tradition — surplus is pooled by collective agreement before individual profit is distributed — that has been modified over centuries to fit a market economy without abandoning the principle that underlies it. Visitors notice that Quilombo feels, relative to most outer-reach systems, unusually coherent. The coherence is not accidental.
|
||||
|
||||
Commission presence is minimal in the way that all hop-7 systems experience: rotating inspections on an infrequent schedule, no permanent office. The community maintains compliance records that are thorough because the founding families long ago decided that the best defense against institutional intrusion was documentation that made intrusion unnecessary. This is one of the quilombo tradition's persistent strategies, applied to a regulatory context rather than a colonial one.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Quilombo exports agricultural products primarily — the range that a G0Ve habitable world enables, developed over three centuries of careful cultivation. The secondary export is through-route logistics services: fuel, maintenance, layover accommodation, local cargo consolidation for inward-bound freight that arrives from GJ 67 and needs to be sorted for onward routing through GJ 473A. The community imports manufactured goods and technical equipment that the local economy does not produce. The balance is positive; Quilombo does not carry external debt.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The **Quilombo Community Assembly** is the governing body. It is unusual in the south_reach for having written governance documents that trace explicit lineage to the historical quilombo tradition, including a preamble that names the historical precedents and a governing principle that translates, approximately, as "we do not ask for permission to exist." The Assembly handles all major decisions through a deliberative process that requires broad consensus rather than simple majority — a design choice that makes rapid changes difficult and that the community considers appropriate given their history.
|
||||
|
||||
The Guardians of Autonomy have never established a chapter at Quilombo. The community's response to Guardian organizing attempts has been consistent: "We have been governing ourselves for three hundred years. We do not need an outside organization to teach us about autonomy." The Guardian representatives who have visited found this response accurate and have not returned.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The through-route position means that cargo moving between GJ 473A and GJ 67 passes through Quilombo's gate management system. The community's logistics operations inspect inbound freight for Commission compliance before allowing transit — a practice that is within their rights as the transit authority for their horizon station's apertures. What the community does with the inspection data beyond the minimum Commission reporting requirements is not documented in any external record. Quilombo's logistics operators have, over three hundred years, accumulated a substantial knowledge of what moves through the south_reach's freight flows between these two connection points, and they have never been compelled to share that knowledge with anyone.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
A wave_5 cargo operator has approached the Quilombo Community Assembly with a proposal to formalize a freight forwarding arrangement that would use Quilombo's transit position to consolidate and reroute cargo from several outer-reach systems in ways that would, the operator says, reduce transit costs significantly — but the routing structure the operator is proposing would make the origin of specific cargo streams difficult to trace once they were consolidated at Quilombo, and the Assembly has referred the proposal to a committee that has been discussing it for four months without reaching a recommendation.
|
||||
|
||||
---
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
The K-type header versus G0Ve stellar profile is a generation artifact; G0Ve governs all lore detail. G0Ve is a warm G-type with emission activity, which provides good agricultural conditions and the mild flare risk that the "e" designation indicates — not severe enough to be operationally disruptive, but present in the background. Through-route at hop 7 with wave_3 settlement is consistent with a system that was settled because it was on an identified route rather than as a destination — the founding families chose a through-route position deliberately, as described, because it provided economic infrastructure that a pure dead-end would not. The stub's existing name "Alula Australis B" has been replaced with the settlement name Quilombo, which is the community's own designation; the astronomical designation is preserved in the GJ identifier.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,6 +1,8 @@
|
||||
# PLACEHOLDER_230
|
||||
# GJ 425A
|
||||
**GJ 425A** | K-type | deep_frontier
|
||||
|
||||
An unmanned transit point between Leuchtturm and GJ 177. The corridor through GJ 425A was mapped during the wave_3 expansion of the deep frontier and has never been claimed. Automated relay hardware maintains navigation data for the corridor. No survey expedition has returned to assess whether conditions have changed since the original mapping.
|
||||
|
||||
---
|
||||
|
||||
## System Profile
|
||||
@@ -8,28 +10,29 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K4/K5V · 42.9 ly |
|
||||
| **Star** | K · 38.2 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | unsettled |
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
None. No resident population.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No permanent faction presence. The automated relay systems function without human oversight. Transit traffic through the system is minimal — the Leuchtturm spur_end terminus limits throughput, and the corridor beyond serves only the small population at GJ 177.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
None recorded.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
GJ 425A is the unmaintained gap in the Leuchtturm corridor — a through_route that connects one spur_end to a distant neighbor, passed through by a handful of vessels per year and inspected by no one.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 9
|
||||
- **Adjacent Systems:** GJ 177, GJ 142
|
||||
- **Adjacent Systems:** GJ 142 (Leuchtturm), GJ 177
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_124
|
||||
# Fluchtburg
|
||||
**GJ 428A** | K-type | deep_frontier
|
||||
|
||||
---
|
||||
@@ -8,28 +8,51 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K7V+... · 44.7 ly |
|
||||
| **Star** | K · 37.8 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_4 |
|
||||
|
||||
---
|
||||
|
||||
Fluchtburg means "refuge castle" in German — a fortified place of last resort, a structure built not for comfort but for survival when retreat has run out of options. The name was chosen by the founding generation with full awareness of its meaning, and the community has spent two hundred years deciding whether the name still fits.
|
||||
|
||||
The founding is not disputed because there is nothing to dispute: the records are clear, the descendants know them, and the Assembly has never acknowledged them officially, which means there is no official version to contradict. Two hundred years ago, a series of Assembly enforcement operations in the outer corridors produced a failed military action — details classified, incident never publicly named — in which crew members of several vessels refused orders, declined to participate in whatever had been ordered, and instead continued deeper into the frontier rather than return to face the consequences of their refusal. Some accounts say the orders involved civilian populations. Some accounts say the orders involved something classified that the crew members could not unsee. Some accounts say it was simpler than that — that the orders were wrong in a way that the crew could not articulate formally but could not follow. None of these accounts can be verified from outside the community. The community does not offer clarification.
|
||||
|
||||
What is certain is that the founders arrived at GJ 428A approximately two hundred years ago, settled without authorization, and have remained. The Assembly has no record of authorizing the settlement. Fluchtburg has no Assembly registration. Technically the settlement is unauthorized. Practically, nobody with enforcement authority has any reason to travel to hop 11 to regularize a two-hundred-year-old community of farmers and craftspeople who are not bothering anyone.
|
||||
|
||||
The community's governance is built around the founding mythology of refusal. They have a detailed oral tradition about what was refused and why, and a codified set of principles — the Founding Refusals, formally written down about a hundred years after settlement — about the limits of legitimate institutional authority. The Founding Refusals are not separatist doctrine in the organized political sense; they are the community's internally-maintained account of what authority can and cannot ask of a person. The Commission's absence is considered correct. The Assembly's non-recognition is considered irrelevant. The community governs itself by the principles its founders articulated in the act of refusing to continue.
|
||||
|
||||
Two hundred years of self-governance by people who defined themselves by disobedience has produced a community that is, paradoxically, quite orderly. The founding act was specific and justified by specific principles. The descendants have spent two centuries working out what those principles imply about daily governance. The result is a community with a strong internal rule structure and a consistent, principled refusal of external authority that is not experienced internally as anarchism but as fidelity to the founding moment.
|
||||
|
||||
What makes Fluchtburg unusual rather than merely isolated is the corridor it sits on. Connected to the respected scholar-exile community of Fernlicht at hop 12 on one side and to the empty but attractive GJ 69 on the other, Fluchtburg occupies a position in the deep frontier's social geography that gives it quiet influence. Communities further out in the corridor know it. Communities further in have heard of it. The story of the founding has a life of its own in the deep frontier oral tradition — the crew who refused and kept going is a resonant myth whether the specific facts are known or not.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Processed materials and manufacturing components via the Fernlicht corridor. The community produces food in agricultural surplus and provides logistics and hospitality services to transit vessels. The dependency is on technical and industrial inputs that the community cannot manufacture locally at the required quality or scale.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No Assembly registration, no Commission presence, no Syndic operations. The community maintains its unauthorized status as a matter of principle. Separatist sympathies are near-universal but not organized through any formal separatist movement — the community's self-governance predates most current separatist organizational structures and does not require them. The Guardians of Autonomy have attempted on several occasions to establish a formal relationship; the community has politely declined institutional affiliation while maintaining informal communication.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The specific nature of the orders that were refused at the original enforcement action. The descendants know what their founding generation recorded; the records are internal property. Sharing the specific content with outsiders is considered a breach of something that cannot quite be named — it is not that the content is shameful, but that the specificity is the community's, and has been since the day the founders wrote it down.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
Two hundred years of principled unauthorized existence — a community that defines itself by a refusal nobody in official records acknowledges ever being made.
|
||||
|
||||
---
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 11
|
||||
- **Adjacent Systems:** GJ 69, GJ 61
|
||||
- **Adjacent Systems:** GJ 61 (Fernlicht), GJ 69
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_145
|
||||
**GJ 434** | M-type | deep_frontier
|
||||
# GJ 434
|
||||
**GJ 434** | M-type | east_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -8,26 +8,37 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | G8Vvar · 31.3 ly |
|
||||
| **Star** | M1Vvar · 31.3 ly |
|
||||
| **Gates** | 2 aperture · spur_end |
|
||||
| **Settlement** | unsettled |
|
||||
|
||||
---
|
||||
|
||||
GJ 434 is an empty spur off Taishan (GJ 682) — two apertures, one connecting back toward Taishan, one reaching out toward GJ 117 beyond. The star is a variable M-dwarf with periodic activity cycles that produce significant flare activity. Surveys flagged this as a complicating factor for surface settlement — radiation exposure during flare events requires shielding infrastructure that raises costs and extends timelines.
|
||||
|
||||
Nobody has yet decided the system is worth that investment. Taishan is an established junction that handles significant east_reach traffic, and GJ 434 sits off its shoulder like an afterthought — a spur that goes nowhere permanently inhabited. The gate infrastructure exists because the survey program extended it as a matter of procedure; the route through GJ 117 was part of a corridor mapping pass that never prompted settlement activity.
|
||||
|
||||
The system sees occasional transit — scientific vessels, survey runs, traffic moving between GJ 117 and Taishan that chooses this routing over alternatives. It is not heavily traveled. The star's flare cycles are predictable enough to schedule around, and most captains do exactly that: check the cycle tables, route through during a quiet period, don't linger.
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
None. No population, no extractable resource under active development.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No faction presence. The apertures are Commission-registered and the in-system navigation beacons are maintained on a schedule nominally managed through Taishan's transit authority.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
Not applicable — no population to keep silence.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
A research vessel undertaking stellar activity studies has been parked in a high-orbit station here for three years — significantly longer than its original survey mandate specified, and without updated Commission authorization for the extended stay.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
Unsettled spur_end at hop 6 adjacent to a major east_reach junction reflects the survey-ahead-of-settlement pattern common in east_reach development. The variable star is a plausible settlement barrier.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_041
|
||||
# Mirante
|
||||
**GJ 435** | K-type | south_reach
|
||||
|
||||
---
|
||||
@@ -14,20 +14,49 @@
|
||||
|
||||
---
|
||||
|
||||
Mirante means lookout point in Portuguese — elevated terrain, a place from which you can see what approaches and what recedes. The name fits the topology precisely. GJ 435 sits between Espinho at the dead end and Encrucijada at the hub, the middle position on a three-system spur. From Mirante's horizon station you can see, in the transit log sense, everything moving to and from Espinho, and you can see everything moving between Espinho and the wider Reach that routes through the Encrucijada connection. The community that built here three hundred years ago understood the position they were taking.
|
||||
|
||||
The K5V star at 40.4 light-years is cool and orange, the kind of star that provides sufficient luminosity for habitation without the warmth that makes G-type worlds easy. The founding families were Portuguese and Brazilian — wave_3 settlers with agricultural and light-industrial backgrounds who chose this position because the surveys showed habitability and because the two apertures meant Mirante would not be a dead-end in the way that Espinho would eventually become. The transit position was a calculated choice: the founding families expected that both inward and outward connections would generate enough traffic to make service and logistics viable as secondary economic activities alongside whatever the land could support.
|
||||
|
||||
Three centuries have validated the calculation. Mirante's economy runs on three pillars: agriculture adapted to the K5V's cooler conditions, logistics and transit services for the Espinho-to-Encrucijada corridor, and light manufacturing that serves both the local market and the two connected systems. None of these pillars is dominant. Together they produce a community that is stable, self-sufficient, and modestly prosperous — not wealthy in any inner-reach sense, but not struggling in any outer-reach sense either.
|
||||
|
||||
The community's elevated-terrain character is not purely metaphorical. The primary settlement is built on a plateau that provides natural vantage points over the lower valley terrain where the main agricultural operations sit. The horizon station's gate approaches are visible from the plateau's edge, which makes the settlement feel like it is watching its own connection to the rest of the Reach. This is perhaps a projection of the community's actual psychological relationship to its position: Mirante is aware of what moves through it, attentive to the traffic it carries, and maintaining a quality of attention to its own transit function that most communities of similar size do not.
|
||||
|
||||
The shift in Encrucijada's status forty years ago — from empty system to active hub — changed Mirante's position meaningfully. Before Encrucijada was settled, Mirante's inward connection ran through a more complex chain; after Encrucijada became a hub, Mirante sits one hop from a five-aperture junction. The freight volume moving through Mirante's two apertures has increased, and the logistics services that Mirante provides have grown to match. The founding families' descendants are running an operation that is larger and more complex than the founding generation built for, but the skill set is the same one that has been maintained and transmitted over three centuries, and the operations have scaled without significant structural change.
|
||||
|
||||
Commission presence is the standard outer-reach schedule: infrequent rotating inspections, no permanent presence. Mirante's compliance record is clean and detailed, which reflects both genuine practice and the community's awareness that its transit function means any irregularity that surfaces in the freight data will eventually attract Commission attention.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Mirante exports agricultural products to Espinho (which is more arid and imports a portion of its food supply) and logistics services to both connected systems. Secondary exports include light-manufactured goods — primarily equipment components and maintenance supplies for the Espinho observatory systems and for the transit infrastructure at Encrucijada. Imports are manufactured goods and technical equipment that the local industrial base cannot produce. The trade balance is slightly positive: Mirante collects transit service fees from the freight moving between Espinho and Encrucijada, which supplements the agricultural export revenue.
|
||||
|
||||
The community's agricultural expertise in K5V conditions has produced techniques adapted to lower-luminosity growing conditions that other K-type settlements have occasionally licensed. The licensing income is modest and inconsistent but represents a form of knowledge export that the founding generation did not have and that the community has developed organically through three centuries of trial and refinement.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The **Mirante Transit Cooperative** manages the logistics and gate services that the community provides to freight operators using the Espinho-Encrucijada corridor. The cooperative is a commercial entity with community ownership structure — its profits are distributed to member households — and it is also the de facto manager of the horizon station's docking and freight management infrastructure. The distinction between the commercial cooperative's functions and the civic governance functions is clearer at Mirante than at some other outer-reach systems, but the membership of the cooperative's board and the settlement council overlaps substantially.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The transit log that Mirante maintains for Commission compliance records all freight movements through its two apertures. The community also maintains a secondary internal log that records transit patterns at a finer level of detail than the Commission-required records — freight consolidation patterns, routing choices, timing correlations between Espinho-outbound and Encrucijada-inbound movements. This internal log was established as an operational tool and has been maintained continuously for two centuries. It contains, without the community having intended to build it, a historical record of freight flow patterns through this part of the south_reach that is more detailed than anything in any Commission database. No one outside Mirante knows it exists.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
The internal transit log's two-century record shows a pattern — irregular, separated by gaps of several years, but consistent enough to be recognizable to the cooperative member who found it while reviewing old records for a capacity planning exercise — in which a specific type of freight movement through the Espinho-to-Encrucijada corridor appeared in tight clusters following significant political or economic events in the inner reach, as though someone with access to advance information was using the outer-reach corridor to move assets before the events became public.
|
||||
|
||||
---
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
K5V at 40.4 light-years is cool enough to require specific agricultural adaptation, which is consistent with the knowledge-export detail and the founding families' experience with K-type conditions. Spur_end with 2 apertures at hop 8 is the middle-position topology that makes Mirante's transit service role natural: a system between a dead-end and a hub, with enough traffic to sustain a logistics operation but not enough to constitute a hub itself. Wave_3 settlement is consistent with the founding families' practical motivation — the surveys showed viability and the two-aperture position offered economic diversification that pure dead-ends could not.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_278
|
||||
# Steinfeld
|
||||
**GJ 454** | K-type | west_reach
|
||||
|
||||
---
|
||||
@@ -14,20 +14,37 @@
|
||||
|
||||
---
|
||||
|
||||
Steinfeld was settled approximately three hundred years ago. The name is German and plain: "stone field." The founders were describing the planet from orbit before they landed, and the description remained accurate enough that no one saw cause to change it later. The world is a K0IV subgiant's habitable zone companion — the star is old and slightly evolved, burning warmer than a standard K0 main sequence object, which places the habitable zone at greater orbital distance and produces a planet that receives orange-tinged light at low angles for most of the day cycle. The effect at the settlement's altitude — Steinfeld's population centers are in highland zones — is a quality of late-afternoon light that lasts most of the day, stone surfaces saturated in amber and amber-grey.
|
||||
|
||||
The planet is rocky, high, and cold above the equatorial valleys. The primary geology is exposed sedimentary and metamorphic rock across the highland ranges, with minimal topsoil at altitude — the kind of world where the land tells you immediately what it is and what it is good for. What it is good for is stone. The quarrying operation at Steinfeld has been cutting construction aggregate and finished stone block from the same mountain ranges for three centuries, working through multiple generations of ownership that have all converged on the same conclusion: the deposit base is large enough that the question of exhaustion is academic, and the quality consistency of Steinfeld stone — a dense grey-blue metamorphic type called Bergquarz locally — has made it a recognized material in inner-corridor construction markets.
|
||||
|
||||
The freight route through GJ 505A carries Steinfeld aggregate inward. Most of what leaves the planet is bulk aggregate — cut block, crushed stone, graded construction material. A smaller volume is finished architectural stone, cut to specification for customers in the inner corridor who want the look of genuine Steinfeld Bergquarz rather than a synthetic substitute. The distinction matters to some buyers. The stone has been in enough prominent structures over three centuries that it carries a reputation.
|
||||
|
||||
The settlement's character is shaped by the industry it serves. Quarrying is slow, physical, structural work — it does not attract the transient population a mining boom would, and it does not generate the economic volatility that extraction industries can produce when deposit quality varies. Steinfeld has had approximately the same population for the last hundred years, has approximately the same institutional arrangements, and will probably have approximately the same situation in another hundred years. The community is not stagnant — it maintains its infrastructure, educates its children, handles its disputes — but it is not growing and does not expect to. This is understood as stability rather than failure.
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Steinfeld is moderately self-sufficient. The equatorial valleys support agriculture under the K0IV star's warmth, producing enough food surplus to cover the highland settlements without heavy import dependency. Inbound freight through GJ 505A carries manufactured goods, specialist equipment for the quarrying operation, and a variety of consumer goods that the settlement produces too little population to manufacture locally. The freight relationship is old and reliable — the same transit cooperative that handles Steinfeld's aggregate outbound brings the manufactured goods inbound, and the scheduling has been coordinated for long enough that both sides treat it as a fixed arrangement.
|
||||
|
||||
Outbound: Bergquarz aggregate in bulk construction grades, finished architectural stone cut to inner-corridor specifications, and a small volume of precision-ground stone components used in mechanical and optical applications that require dimensional stability — a niche product that Steinfeld developed in the last century when a geological survey identified a zone of unusually consistent crystal structure in the deep quarry levels.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No Commission post. The aperture transit facility is operated by the Steinfeld Stone Cooperative, which is also the primary quarrying authority and the effective local government. The Cooperative was formed from the merger of three founding family operations approximately a hundred and twenty years ago, after a dispute over freight pricing that threatened to strand all three independently. The settlement charter grants the Cooperative administrative authority over transit, resource management, and civic infrastructure. Assembly representation is a formal role held by the Cooperative's elected chair, with actual engagement limited to filing routine reports.
|
||||
|
||||
The precision stone component operation — a separate business entity within the Cooperative called Tiefquarz Feinbearbeitung — has a different character from the bulk quarrying operation: smaller, more technically demanding, with a staff that has more contact with inner-corridor buyers and more awareness of the broader market. This creates occasional friction within the Cooperative between the bulk operation's conservative planning culture and Tiefquarz's more outward-facing orientation.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The original survey maps. Steinfeld's founding survey identified the exploitable geology and recommended settlement. A standard survey would have covered the full planetary surface. The areas of the planet not included in the quarrying concession — the northern continent, which the founding documents describe only as "unsuitable for settlement and resource extraction" without elaboration — have not been resurveyed. No one has applied for a survey license. The northern continent is not discussed.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
A precision stone component from a Tiefquarz Feinbearbeitung shipment was found in a device recovered from a derelict vessel near GJ 505A — a device whose function no one has been able to identify.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
The K0IV subgiant classification produces a slightly unusual illumination regime for the planet — the evolved star's different luminosity profile compared to a standard K0V shifts the habitable zone outward and affects seasonal dynamics. The amber-light character described is a direct consequence of the subgiant's spectral output at this orbital distance. Wave_3 settlement at hop 8 reflects the deep corridor position — Steinfeld was reached as the inner corridor expanded and established the hop-by-hop chain through GJ 505A.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,6 +1,8 @@
|
||||
# PLACEHOLDER_290
|
||||
# Travessa
|
||||
**GJ 482B** | K-type | deep_frontier
|
||||
|
||||
The name means "crossing," and the community understands what it is. Travessa exists because the corridor between Posto Avançado and the deep south needed a waypoint, and the people who built it understood their role from the first year of settlement. Two centuries of transit services, freight handling, and the economy of being between two other places have produced a community that is not romantic about its function. They are a crossing. They are good at it.
|
||||
|
||||
---
|
||||
|
||||
## System Profile
|
||||
@@ -8,28 +10,35 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | F0 V · 38.6 ly |
|
||||
| **Star** | K · 35.8 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_4 |
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Travessa's economy is transit services. The community does not produce significant agricultural surplus — the habitable world is adequate for local food production and little more. What it produces is throughput: freight handling infrastructure, vessel servicing, cold storage, the bond warehousing and transit documentation that deep frontier freight requires at corridor waypoints.
|
||||
|
||||
The dependency is therefore inverted from agricultural systems: Travessa requires steady transit volume to sustain the infrastructure that sustains the community. A corridor disruption that drops traffic below the threshold needed to maintain the transit facilities becomes an existential problem quickly. The community's leadership is acutely aware of this. They maintain relationships with freight operators in both Posto Avançado and Dois Sóis more carefully than most deep frontier communities maintain any institutional relationships, because the health of those relationships is the health of Travessa.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The Syndics have a formal representation at Travessa — a small office that manages freight bond certification and commercial documentation for the corridor. This is unusually structured for a deep frontier system of this size; most corridor waypoints of comparable population manage commercial relationships informally. The formal Syndic representation exists because Travessa's founding cohort included several operators who had previous Syndic affiliations and understood the value of maintaining verifiable commercial standing in the wider Reach even at frontier distances.
|
||||
|
||||
The Lattice Commission receives freight documentation from Travessa through the Syndic office's filings. No Commission personnel are stationed here — the corridor's commercial record exists because Travessa files it, not because the Commission collects it. At hop 8, the Commission's authority is nominal and its presence is a line in a registry.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What Travessa does not discuss with official inquiries: the character of some of the freight that transits the system's cold storage facilities without appearing in the standard documentation.
|
||||
|
||||
A corridor waypoint at this distance operates under practical oversight that is minimal by any standard. What passes through Travessa's cold storage with incomplete documentation, what transits at off-hours under arrangements that the day-shift operators are not privy to, what the Syndic office's bond records do not reflect — these are questions that no one has asked formally and that the community has developed practiced institutional amnesia about. Travessa does not facilitate contraband by policy. It facilitates it by the structural reality of being a node in a corridor where official oversight is thin and transit documentation is handled by the people being documented.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
Travessa's Syndic office maintains commercial standing documentation for the deep south corridor; what passes through the cold storage facilities on the night shift has been recorded in a separate ledger that the Syndic representative has not filed with anyone for at least six years.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 8
|
||||
- **Adjacent Systems:** GJ 169, GJ 707
|
||||
- **Adjacent Systems:** GJ 169 (Posto Avançado), GJ 707 (Dois Sóis)
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_073
|
||||
**GJ 49** | M-type | deep_frontier
|
||||
# Dernier Quai
|
||||
**GJ 49** | M-type | east_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -8,26 +8,39 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K5V... · 32.5 ly |
|
||||
| **Star** | M2V · 32.5 ly |
|
||||
| **Gates** | 1 aperture · dead_end |
|
||||
| **Settlement** | wave_3 |
|
||||
|
||||
---
|
||||
|
||||
Dernier Quai — "last platform" in French — was named by the community that founded it three centuries ago with a specific awareness of what the name implied. There is one gate. One way in, the same way out. Everything that arrives here was intentionally sent, and the system has no transit function at all; it does not sit between two other places, it simply sits at the end. The founders knew this and named the place accordingly, with the wry precision of people who understood exactly what they were committing to.
|
||||
|
||||
The community grew off a spur from Port Desrochers (GJ 1005A), the east_reach's major junction. Port Desrochers handles traffic and commerce and institutional weight; Dernier Quai handles none of that. It is a dead_end off a junction — reachable, not en route. The French outpost character that defines the place comes from that original founding cohort and has been maintained in language, cultural practice, and civic architecture across three hundred years. It is not a museum; it is a living inheritance.
|
||||
|
||||
The M-dwarf primary is dim and red-shifted, producing the low-light conditions common across this corridor. Three hundred years of agriculture adapted to those conditions have produced a food culture with genuine local character — the kind that gets talked about across the corridor as a reason to make the detour from Port Desrochers.
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Dernier Quai sources manufactured goods, medical hardware, and specialized components from Port Desrochers, with which it has a long commercial relationship. Its agricultural output — processed food products with established regional reputation — moves back through that same gate as export. The balance is comfortable and has been for over a century.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The Commission maintains a minimal post — a charter office and a transit log function — staffed by one or two personnel who rotate out every two years and find the assignment either pleasantly quiet or profoundly boring. Local governance sits with a municipal council whose procedures trace back to the original charter instrument.
|
||||
|
||||
A French-language cultural association, La Société du Quai, holds significant informal authority in civic life — managing community archives, cultural events, and the kind of dispute resolution that communities prefer to handle without formal institutions. It is older than the Commission post.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The circumstances under which a founding-era land claim in the eastern agricultural district was transferred to outside ownership approximately forty years ago. The transaction is legally registered. The details of the negotiation are not discussed.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
A ship has been docked at the system's single transit berth for four months, its crew present and paying berthing fees, its cargo hold sealed with Commission bonding that the local post cannot legally open without authorization from Port Desrochers — authorization that has been requested three times and not issued.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
Wave_3 dead_end at hop 6 off a major junction is consistent with east_reach settlement patterns — established communities founded on spurs during the Trade Expansion era, now stable and culturally distinct.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_082
|
||||
# Velha Guarda
|
||||
**GJ 4A** | K-type | south_reach
|
||||
|
||||
---
|
||||
@@ -14,20 +14,51 @@
|
||||
|
||||
---
|
||||
|
||||
Four hundred years of settlement, one aperture, and no through-traffic. Velha Guarda — old guard — is the oldest inhabited system in this part of the south_reach, settled during the wave_2 expansion when the inner orbit was still being consolidated and the outer reach was barely a concept. The families that came here came because the surveys showed a habitable world and because the wave_2 migration created a pressure of people that pushed new settlers further than the wave_1 founders had imagined going. GJ 4A was, in wave_2 terms, the edge. For three of the four centuries since, it has remained the edge — a dead-end at the terminal point of a spur off GJ 829, one hop beyond a system that itself settled only in wave_5.
|
||||
|
||||
The K2 star at 36.9 light-years is stable, warm enough, unremarkable. The habitable world has good gravity, a reasonable atmosphere, moderate seasons. Nothing about the physical environment explains or requires particular comment. What four hundred years of continuous settlement in a dead-end produces is what explains Velha Guarda: a depth of cultural memory, a density of institutional knowledge, a weight of accumulated habit and practice that makes communities in younger systems feel temporary by comparison.
|
||||
|
||||
The founding families were Portuguese and Cape Verdean. The Cape Verdean component is significant: the islands of Cabo Verde were themselves products of settlement under difficult conditions, built over centuries by people of mixed African and Portuguese heritage who developed a culture that was neither purely African nor purely Portuguese but was specifically Cape Verdean — the result of centuries of isolation, forced migration, agricultural difficulty, and the development of a music called morna that is untranslatable to people who have not grown up with it because it encodes a particular emotional relationship to distance, longing, and resilience that cannot be explained, only accumulated. Four hundred years of life at GJ 4A has added another layer to this already layered heritage. The morna played at Velha Guarda is recognizably related to what was brought from Cape Verde, but it has absorbed four centuries of additional experience, additional distance, additional longing, and additional resilience.
|
||||
|
||||
The founding families' descendants are the community's backbone in a way that would be unremarkable at three hundred years but becomes remarkable at four hundred: there is, at Velha Guarda, a seventh-generation family that has never sent a member to settle elsewhere. The family tree fills a wall in the community's archive building. That tree represents the community's relationship to its own history more precisely than any document: these people have been here, on this world, under this star, for longer than any other human community in the south_reach. They know what they are. The question of what they are is not open for them, and this closure — this settled knowledge of identity — is palpable to anyone who visits.
|
||||
|
||||
The connection to GJ 829 was established in wave_5 when that system was settled, which means that for the first three hundred years of Velha Guarda's existence, the settlement was connected to the rest of the Reach through whatever system sat between it and the inward junction, a topology that changed with the wave_5 expansion. The current connection through GJ 829 is recent relative to Velha Guarda's history, and the community's relationship to it is that of a very old institution accommodating a change that its experience tells it is not unprecedented. Things change. The community endures.
|
||||
|
||||
Commission presence is the standard outer-reach minimum. The community's compliance records are impeccable in the way that four-hundred-year-old institutions' records are impeccable: not because anyone is particularly careful, but because the practices that generate compliance records have been internalized for so many generations that violations would require deliberate effort. The Commission inspectors who visit Velha Guarda have uniformly reported a pleasant stay and nothing requiring follow-up.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Velha Guarda's four-century agricultural tradition has produced a food system that meets local needs with reliability. The exports are cultural rather than material in the narrow sense: the community has a reputation for producing music, specifically the south_reach variant of morna that has developed here over four centuries, and musicians and recordings from Velha Guarda are sought in systems that have Cape Verdean heritage communities. This is not an economic pillar; it is a source of soft influence and a reason for the community to feel that what they have built matters beyond its own borders.
|
||||
|
||||
Physical exports are modest: agricultural products, some manufactured goods from the small industrial operations that serve the local economy and sometimes have surplus capacity. Imports are manufactured goods and the technical equipment that the local economy requires but does not produce. The balance is approximately even. Four centuries of practice have produced a community that knows precisely what it needs and has calibrated its economy to provide it.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The community's governance structure is an elected council with strong informal influence from the founding-wave family networks. This is not unusual in itself, but the depth of the founding families' continuity at Velha Guarda means the informal influence is more persistent and more culturally weighted than in younger systems. A council decision that runs against the preferences of the seventh-generation families is theoretically possible; in practice, it has not happened in the last century.
|
||||
|
||||
The **Cultural Archive of Velha Guarda** is the community's most significant institution after the council itself — an organization that maintains the four-century record of the community's music, oral histories, genealogies, and material culture. The archive is housed in a building that was constructed in the first generation and has been continuously maintained and expanded since. It is staffed by community members whose position is considered a form of service analogous to council membership. The archive's holdings have been digitized, but the physical objects — instruments, clothing, manuscripts, the wall-filling family tree — are considered irreplaceable and the community's formal governance documents specify that their preservation is a collective obligation.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The founding generation's records include a detailed account of the wave_2 migration decision-making that placed the colony at GJ 4A rather than at two other candidate systems that were assessed at the same time. One of the rejected candidate systems is now a wave_3 settlement with a larger population and a more connected topology. The other candidate system was designated as unsuitable and remained unsettled. What the archive records make clear, in documents that have not been formally shared with any external body, is that the founding families' first choice was the system that became a wave_3 settlement — that they were displaced from their first choice by a Syndic combine that had prior authorization on the system's commercial resources and that the wave_2 settlement framework gave priority to. The founding families came to GJ 4A because it was what was left. Four centuries of making it theirs has not erased the knowledge that it was not their first choice.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
The seventh-generation heir of the founding family recently located a communication record in the archive — a formal exchange between the founding generation's migration coordinator and the Syndic combine that displaced them — that references a compensation arrangement for the displacement that was agreed to and, according to the founding generation's subsequent communications, never honored; the combine's successor entity exists today under a different corporate name, is commercially active in the inner reach, and its legal representatives have not been contacted about a four-century-old debt that no currently living person at Velha Guarda would have believed existed until last year.
|
||||
|
||||
---
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
Wave_2 settlement at hop 7 requires explanation: in the wave_2 period, the topology at this distance from the core was not fully mapped, and the founding families reached GJ 4A through a longer chain than the current two-hop path from GJ 829 to the inner-reach junction suggests. The current hop-7 designation reflects post-wave_3 topology with the full Reach gate network in place; the founding families navigated a sparser network and considered GJ 4A genuinely far. The dead_end with one aperture has been the topology throughout; the connection point changed as the network developed around the system, but the system's terminal position has always been its defining condition.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_069
|
||||
# GJ 5
|
||||
**GJ 5** | K-type | deep_frontier
|
||||
|
||||
---
|
||||
@@ -8,28 +8,41 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K0V · 44.6 ly |
|
||||
| **Star** | K · 33.9 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_4 |
|
||||
| **Settlement** | unsettled |
|
||||
|
||||
---
|
||||
|
||||
GJ 5 sits between two worlds that nobody has claimed. On one side, the G-type GJ 524 — the deep frontier's best unclaimed real estate, sitting empty for two centuries with survey reports piling up in the archive. On the other, Ouplaas at GJ 528A — four hundred years of continuous settlement, the oldest farming community in the deep frontier, run by families who have worked the same soil for five generations.
|
||||
|
||||
The primary world of GJ 5 is a K-type habitable zone world: adequate stellar warmth, stable geology, atmospheric conditions that survey teams consistently describe as favorable for agricultural development. The world is not as immediately compelling as GJ 524's garden profile, but it is substantially better than most habitable worlds at this depth. Early survey data suggests good agricultural potential, sufficient water distribution, and the kind of ecological balance that indicates planetary stability over geological timescales.
|
||||
|
||||
The corridor here has curious bones. GJ 524 to one side, GJ 5 in the middle, Ouplaas on the other — two habitable-world systems in a row, both empty, bracketing the oldest farming community in the deep frontier. The geometry invites speculation. Settlement proposals for this corridor have appeared in various forms over the decades, and they consistently note the infrastructure logic: Ouplaas as a supply anchor, GJ 5 as a staging point, GJ 524 as the primary agricultural world, the whole corridor potentially becoming the deep frontier's most productive agricultural chain with a fraction of the investment required to develop each system in isolation.
|
||||
|
||||
Ouplaas's residents have opinions about this. Those opinions are not uniform. The older families tend toward the position that the empty corridors are what makes the depth comfortable; the community's independence and self-sufficiency have been sustained in part by not being embedded in a larger agricultural network with its attendant dependencies and institutional attention. The younger generation includes voices that find the corridor's emptiness wasteful rather than protective. The discussion is ongoing and considered internal family business.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
None.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
No faction presence. Ouplaas's community has informal standing as the nearest settled neighbor and expresses opinions about corridor development when asked. Those opinions carry the weight that four centuries of community existence produces.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
An empty K-type habitable world positioned between the deep frontier's best unclaimed G-type and its oldest settled community — a gap in an otherwise logical chain that the oldest neighbor has complex feelings about filling.
|
||||
|
||||
---
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 11
|
||||
- **Adjacent Systems:** GJ 528A, GJ 524
|
||||
- **Adjacent Systems:** GJ 524, GJ 528A (Ouplaas)
|
||||
|
||||
@@ -22,7 +22,7 @@ MVG's contracts have been active in Bergtor for approximately two hundred and fi
|
||||
|
||||
## Supply Dependency
|
||||
|
||||
Bergtor's supply dependency runs entirely through Eisentor (GJ 3454). The spur_end topology gives the system only this one commercial artery, and its spur terminus at GJ 454 sees little commercial traffic in either direction from Bergtor's perspective — GJ 454 is a stub without significant industrial development, and goods that reach Bergtor from that direction are rare. Manufactured goods, food, medical supplies, and operational equipment all flow in through Eisentor. Raw and semi-processed mineral output flows back out the same way.
|
||||
Bergtor's supply dependency runs entirely through Eisentor (GJ 3454). The spur_end topology gives the system only this one commercial artery, and its spur terminus at GJ 454 sees little commercial traffic in either direction from Bergtor's perspective — GJ 454 is a dead-end quarrying system whose bulk aggregate output moves inward through Bergtor, but generates limited return traffic. Manufactured goods, food, medical supplies, and operational equipment all flow in through Eisentor. Raw and semi-processed mineral output flows back out the same way.
|
||||
|
||||
MVG's logistics chain manages the primary export flow: ore consolidated at Mass's surface operations is loaded onto MVG's scheduled transit and moves inward through Eisentor toward Hansestadt and the wider Reach. Independent operators handle smaller-volume specialty minerals and the refractory ceramic precursors that go to fabrication shops that do not want to buy through MVG's distribution system. These independents use the same gate schedule as MVG's freighters, which means everyone at Bergtor understands that Eisentor's gate scheduling decisions affect them directly.
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_184
|
||||
**GJ 508A** | M-type | deep_frontier
|
||||
# Stilwater
|
||||
**GJ 508A** | M-type | north_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -8,26 +8,37 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K0 · 34.9 ly |
|
||||
| **Star** | M2V · 34.9 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_4 |
|
||||
|
||||
---
|
||||
|
||||
Stilwater is the quiet deep of the Cairn pocket chain. The name — "still water" in Afrikaans and Dutch — was chosen two centuries ago by settlers who found the system's main habitable world unremarkable in all the ways they wanted: no violent weather, no unstable tectonics, no competing interests. Just a planet that would hold still and let people farm it. It has been doing that ever since.
|
||||
|
||||
At hop 7, Stilwater is as far from the interstellar corridor's center of gravity as a settled system can practically be. Commission presence is nominal — a charter filing office, a transit log, a medical station that operates two days a week. Everything else is community-managed and has been for as long as anyone can remember. The original wave_4 settlers were the grandparents of the oldest generation now living here, and the institutional memory of "before we had all this" means something to them.
|
||||
|
||||
The population is small and deliberately so. Land is plentiful, neighbors are infrequent, and the stars at night include the glow of Breëvlei one gate back — visible to the naked eye on clear nights, a reminder of the corridor they sit at the end of.
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Stilwater relies on inbound manufactured goods, medical supplies, and technical components from the corridor behind it, primarily sourced through Breëvlei and Waterkant. Its agricultural output is sufficient for local consumption with modest surplus sent back along the chain. The supply line is long and the delays are part of life here.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
A community council operates all civic functions. No external faction has established a meaningful presence — the system is too far out and too small to justify the overhead. The Landbou Raad cooperative network from the corridor includes Stilwater in its distribution agreements, though the relationship is informal and occasionally slow.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The status of GJ 914A, the system on the far side. Stilwater is a through_route between Breëvlei and GJ 914A, but no one discusses what exactly is there or what the transit logs from that direction contain.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
The through_route beyond Stilwater toward GJ 914A has been technically open for thirty years, but no settlement has taken root there, and the transit logs from vessels coming in from that direction have a pattern of missing hours that no one has formally explained.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
Wave_4 at hop 7 is unusual — most hop 7 settlements are wave_5. Stilwater's early founding reflects the Cairn pocket's original settlement push, which reached deep before the Reach's expansion slowed during the early Secession years.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_194
|
||||
# GJ 524
|
||||
**GJ 524** | G-type | deep_frontier
|
||||
|
||||
---
|
||||
@@ -8,28 +8,43 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | k · 45.2 ly |
|
||||
| **Star** | G · 35.6 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_4 |
|
||||
| **Settlement** | unsettled |
|
||||
|
||||
---
|
||||
|
||||
GJ 524 is the best unclaimed real estate in the deep frontier, and it has been that for two centuries.
|
||||
|
||||
The primary world sits inside the habitable zone of a G-type star — warm, stable, well-lit by deep-frontier standards. Survey teams have visited it five times in two hundred years and produced reports that read, across all five visits, with the same careful and growing frustration: temperate climate, rich soil, diverse native biosphere, no significant atmospheric processing requirements, no geological instability, no meaningful indigenous hazard. The kind of world that survey teams are trained to describe professionally and that they describe professionally while clearly wanting to use different words. One survey report, preserved in the relevant feasibility study archives, notes in its conclusion: "Settlement candidates of this quality are uncommon in any sector. At hop eleven in the deep frontier, this world is exceptional."
|
||||
|
||||
Three separate feasibility studies have been conducted. The first, approximately two hundred years ago, concluded that the world was excellent and recommended a settlement expedition. No expedition was funded. The second, approximately one hundred and thirty years ago, concluded that the world remained excellent and the earlier recommendation stood. No expedition was funded. The third, approximately sixty years ago, concluded that the world was excellent, that two previous feasibility studies had already established this, and that the primary obstacle to settlement was not the world but the logistics of organizing and funding a founding cohort at hop eleven depth. No expedition was funded.
|
||||
|
||||
The system sits on the corridor between Saudade at GJ 1267 and the unsettled GJ 5, carrying transit traffic past a world that every vessel passing through can see in the navigational data. The survey reports are publicly accessible — registered with the Assembly's territorial survey archive, periodically rediscovered by settlement advocates who write enthusiastic proposals, circulate them in inner-corridor political networks, and find that the logistics of actually doing it defeat everyone who tries to organize around the idea.
|
||||
|
||||
The problem is not the world. The problem is that at hop eleven, the cost of founding a settlement is borne almost entirely by the founders, with no guarantee of near-term institutional support or commercial viability, in a system that is excellent for farming and habitation but is not exceptional for anything that attracts early investment. GJ 524 offers exactly what humans actually need — food security, comfortable conditions, biological richness — and nothing that the economic frameworks driving settlement decisions have historically valued above logistics cost. It has been waiting for someone to want what it actually offers more than they want what it cannot offer.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
None.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
No faction presence. The survey archive is maintained by the Assembly's territorial survey authority. Periodic settlement proposals have been filed and archived without action. No formal claim has been staked.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
Five survey reports across two hundred years all reach the same conclusion: this world is exceptional. The world is still there. The reports are still there. Nothing else has happened.
|
||||
|
||||
---
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 11
|
||||
- **Adjacent Systems:** GJ 5, GJ 1267
|
||||
- **Adjacent Systems:** GJ 1267 (Saudade), GJ 5
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# PLACEHOLDER_163
|
||||
# Ouplaas
|
||||
**GJ 528A** | M-type | deep_frontier
|
||||
|
||||
---
|
||||
@@ -8,28 +8,49 @@
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| **Star** | K2 · 43.7 ly |
|
||||
| **Star** | M · 27.3 ly |
|
||||
| **Gates** | 2 aperture · through_route |
|
||||
| **Settlement** | wave_2 |
|
||||
|
||||
---
|
||||
|
||||
Ouplaas means "old farm" in Afrikaans, and that is precisely what it is — the oldest continuously worked agricultural settlement in the deep frontier, founded four centuries ago by farming families who came out along the Cairn pocket chain when the corridor was barely mapped and the systems at the end of it were names on a survey manifest. They came with seed stock, soil cultivators, and the unspoken assumption that they would not be coming back.
|
||||
|
||||
Four hundred years is a long time. Ouplaas predates the Lattice Commission, predates the Compact's current form, predates most of the institutional architecture that structures life elsewhere in the Reach. The families who farm here now are the fifth and sixth generation of people who have never known anything else. The founding names are scratched into the stone markers at the field boundaries. The fields themselves have been turned every year since the first settlers broke the ground. The soil knows what it is.
|
||||
|
||||
The community has a relationship with Reach institutions that can best be described as courteous indifference. Commission liaisons pass through infrequently and are treated with the particular hospitality extended to guests who are not quite welcome and know it. The Assembly's administrative reach is nominal. There are no Syndic operations of consequence — the community produces more than it needs, trades for what it lacks, and has maintained that balance for so long that disrupting it would require more institutional leverage than anyone at this depth can bring to bear. Ouplaas doesn't need saving, doesn't need governing, and doesn't need investment. It is four hundred years into being exactly what it set out to be.
|
||||
|
||||
The connection inward to Skuilplek through the Cairn pocket chain is the system's primary external relationship. The communities know each other the way neighbors know each other across a very long road — occasional visits, reliable trade, the understanding that neither will call for help unless the need is genuine. Ouplaas sends food. Skuilplek sends processed materials and the occasional technical specialist. Both communities benefit from the other's existence. Neither community discusses this arrangement in terms that imply dependency.
|
||||
|
||||
What Ouplaas has that the inner Reach lacks is time. Not just the four hundred years already elapsed, but the sense that the community has enough time ahead of it not to hurry anything. The tempo of life here is agricultural — seasons, harvests, planning cycles measured in decades rather than fiscal quarters. An outsider who arrives expecting urgency finds instead a community that has already thought carefully about whatever the outsider came to offer, found it lacking, and moved on.
|
||||
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Light manufacturing components and technical equipment sourced via the Cairn chain corridor, primarily through Skuilplek. The community is largely self-sufficient in food, basic materials, and most common services; the dependency is on specialized tools and replacement parts for agricultural and atmospheric processing equipment that the community cannot manufacture locally. Disruption would be felt slowly, over years, as equipment aged without replacement.
|
||||
|
||||
---
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
No Commission permanent presence. Assembly representation is filed but administered remotely — the community participates in Assembly processes with the minimum engagement required and no more. No Syndic operations. A small Guardians of Autonomy community, not organized as a formal chapter, informally coordinates the community's consistent resistance to institutional encroachment; their position is widely shared enough that a formal organization is unnecessary. The community governance is council-based, family-representative, and has been operating in roughly the same form for two hundred years.
|
||||
|
||||
---
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The founding families' original land claims and the informal inheritance arrangements that have accumulated over four centuries. The legal basis for land tenure on Ouplaas has never been formalized to Assembly satisfaction, and the community has no intention of formalizing it. Discussing land ownership with outsiders is considered a category of rudeness roughly equivalent to discussing the details of a family's finances.
|
||||
|
||||
---
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
Four centuries of uninterrupted settlement has produced something the Reach cannot quite classify — a community with deeper roots than most institutions and no interest in the institutions' opinion about it.
|
||||
|
||||
---
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
- **Hop Distance from Gateway:** 10
|
||||
- **Adjacent Systems:** GJ 5, GJ 722
|
||||
- **Adjacent Systems:** GJ 5, GJ 722 (Skuilplek)
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Muphrid
|
||||
# Stillvakt
|
||||
**GJ 534** | M-type | west_reach
|
||||
|
||||
---
|
||||
@@ -14,20 +14,37 @@
|
||||
|
||||
---
|
||||
|
||||
Stillvakt was settled approximately three hundred years ago by a consortium of Scandinavian families who had tracked survey data from the inner corridor and recognized the planet's dense boreal belt as commercially exploitable. The name means "quiet watch" — an early settler's description of the long winter nights under a G0IV subgiant that burns too pale and too large on the horizon, never quite matching the warmth its luminosity class implies. The planet has one primary landmass at mid-latitude, heavily forested, with a northern ice sheet and a southern temperate band that hosts the settlement's agricultural margin.
|
||||
|
||||
The Nordmark Skog operation predates most of the corridor institutions behind it. What began as a mapped timber concession covering roughly forty thousand square kilometers of old-growth softwood has compounded across seven generations into something closer to a land trust with logging rights — the Nordmark family does not own the planet, but they have managed its productive belt long enough that the distinction has stopped mattering to anyone local. The company name translates as "northern forest," which started as a geographic description on founding documents and became a brand only gradually, as their milled lumber began moving inward through GJ 3333 with enough consistency to develop a corridor reputation. Nordmark Skog dark-grain panels appear in station interiors two and three hops inward. Most people who buy them do not know where they come from.
|
||||
|
||||
The settlement itself is small and functional — a central processing town called Fällstaden, three satellite logging camps, and a transit handling facility at the aperture site that the family also operates under contract. There is no meaningful separation between civic life and company life. The senior Nordmarks sit on the local council because no one else has the administrative infrastructure to run one. This is not experienced as a grievance. It is experienced as how things work.
|
||||
|
||||
The planet's ecology is cold, wet, and largely undisturbed outside the active harvest zones. Nordmark Skog maintains a regeneration program — not from ecological sentiment, but because a company that has been logging the same ranges for three centuries understands that the alternative is mining a finite asset. Replanting cycles run forty to sixty years per plot, which means there are currently four distinct cohorts of forest at various growth stages visible from orbit.
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Stillvakt depends on inbound freight through GJ 3333 for manufactured goods, processed foods outside its agricultural margin, and technical components for logging and milling equipment. Nordmark Skog maintains a standard parts inventory rotation with a corridor supplier based two hops inward, but lead times on specialist components run long enough that the company keeps deep reserves. Fuel and consumables for the aperture transit facility come in on the same freight runs that carry timber out.
|
||||
|
||||
Outbound: milled softwood lumber, structural panel stock marketed as Nordmark Dark Grain, raw log bundles for processing elsewhere, and a modest volume of seed stock from the regeneration program that has found buyers in reforestation projects on more-settled worlds.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
Nordmark Skog is the only institution of consequence. The family has held the primary land concession through three renewal cycles and has never faced a serious challenge to it. A minority of the workforce are not family members or long-term family employees — seasonal contract cutters, aperture technical staff, a small number of independent trappers who operate in the non-harvest zones under a licensing arrangement the company introduced two generations ago as a social management measure. None of these groups have organized political presence.
|
||||
|
||||
The Commission maintains a nominal registration at the aperture site — a single officer, usually rotated every eighteen months from the GJ 3333 post — whose function is customs logging and nothing more. Enforcement actions at Stillvakt are essentially unheard of, because nothing interesting enough to enforce against happens here.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
The condition of the old-growth zones beyond the current harvest boundary. Nordmark Skog's public-facing regeneration program is genuine, but the original concession surveys mapped significantly more old-growth area than the current regeneration cycle accounts for. What happened in those sections — whether they were logged and quietly dropped from the replanting register, or whether something about that terrain discouraged harvest — is not discussed. The trappers know. They don't bring it up.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
A Nordmark Skog freight manifest that passed through GJ 3333 three months ago listed a shipment of "reclaimed structural timber" with dimensions that do not correspond to any tree species in the boreal catalog.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
The G0IV stellar class reads slightly warm for the cold boreal character described, but the subgiant's low surface gravity means the habitable zone sits at greater orbital distance, producing longer seasons and lower average insolation than a main-sequence star of equivalent luminosity. The mismatch between star type and planetary temperature is deliberate and consistent with the established stellar data.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user