From f3cef86e5fe17778ea34d971343a12ef1ace98b9 Mon Sep 17 00:00:00 2001 From: Jeroen Schweitzer Date: Sat, 14 Mar 2026 19:13:16 +0100 Subject: [PATCH] feat(docs): write west_reach mid ring wiki pages (batch 4, hops 6-7) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 10 systems: Rana, Torsby, Meridian, Rødvik, Bakshi Spur, Seiðrmaðr, Eisentor, Altmark, Pereira's Rest, Traagwater. Notable additions: Seiðrmaðr as innovative skunkworks dead_end (Tiefwerk AG), Altmark as 5-gate hub with Compact financial integration, Eisentor as unsettled 4-gate junction with tripartite governance. Paula review fixes applied. Co-Authored-By: Claude Opus 4.6 --- wiki/star-systems/GJ-150/index.md | 23 +++++++++++++++++------ wiki/star-systems/GJ-208/index.md | 29 ++++++++++++++++++++++------- wiki/star-systems/GJ-3454/index.md | 27 ++++++++++++++++++++------- wiki/star-systems/GJ-357/index.md | 29 ++++++++++++++++++++++------- wiki/star-systems/GJ-370/index.md | 29 ++++++++++++++++++++++------- wiki/star-systems/GJ-442A/index.md | 23 ++++++++++++++++------- wiki/star-systems/GJ-502/index.md | 25 ++++++++++++++++++------- wiki/star-systems/GJ-581/index.md | 25 ++++++++++++++++++------- wiki/star-systems/GJ-631/index.md | 27 ++++++++++++++++++++------- wiki/star-systems/GJ-809/index.md | 29 ++++++++++++++++++++++------- 10 files changed, 197 insertions(+), 69 deletions(-) diff --git a/wiki/star-systems/GJ-150/index.md b/wiki/star-systems/GJ-150/index.md index 7ac0ea1da..1e3ce89c9 100644 --- a/wiki/star-systems/GJ-150/index.md +++ b/wiki/star-systems/GJ-150/index.md @@ -1,5 +1,5 @@ # Rana -**GJ 150** | M-type | west_reach +**GJ 150** | K0IV subgiant | west_reach --- @@ -15,19 +15,30 @@ --- ## Supply Dependency - + +Rana is a redistribution junction more than a producer. Its three gates connect inward to Hansestadt (GJ 832), outward to GJ 320, and north-lateral to GJ 370, making it the first branching point beyond Hansestadt for freight moving into the upper reaches of the corridor. The system's economy is built around the services that transit nodes always generate — warehousing, fuel bunkering, ship maintenance, and the layover hospitality that crews need when cargo schedules don't align. Rana does not manufacture much and it does not extract much. It charges for proximity. + +The K0IV designation sets Rana apart from its neighbors in an immediately visible way: this is not a dim red dwarf but a subgiant star running hotter and larger than a main-sequence K-type, warm enough to illuminate the primary habitable body with something close to early evening on Earth. Settlers noted this favorably. After the cool red light of most west corridor systems, Rana's yellow-orange sun reads as generous. The name comes from the star's proper astronomical designation — Delta Eridani — which was in common catalog use before the settlement council bothered with anything more lyrical. By the time someone suggested a proper name, everyone was already calling it Rana. ## Faction Notes - + +Rana's governance is a commercial cooperative, which is to say the major shipping interests that route through the three apertures collectively hold the governance seats, and independent operators are represented through a smaller bloc that has never quite managed to unseat the established houses. The Assembly has a compliance framework applied to the system, and Rana pays its assessments — not out of loyalty but because Hansestadt's commercial norms require it. A system that falls out of Assembly compliance becomes commercially awkward with the Merchant Assembly, which runs its own parallel arbitration track but does not officially protect non-compliant operators from Assembly claims. + +Rana has not signed the Compact of Westphalia and shows no near-term interest in doing so. The calculus is straightforward: Rana's value derives entirely from being a crossing point between the compliant inner corridor and the increasingly non-compliant outer systems. The moment Rana takes a side, it loses value with the other. Junction neutrality is not an ideology here. It is a business model. + +Gate Corporation presence is operationally significant — three apertures means a permanent maintenance crew and a scheduling office. The Gate Corporation's staff are the most cosmopolitan population in the system, rotating in from across the Reach and contributing the cultural mixing that junction systems in this corridor always carry. ## Silence Topic - + +What the shipping cooperative does not surface in its public governance sessions: the informal arrangement by which cargo manifests moving outward through GJ 320 are reviewed by a member of the Merchant Assembly before Rana's customs office sees them. The arrangement is described as "commercial coordination." In practice it means the Merchant Assembly has advance sight of freight patterns that reveal the commercial strategies of operators who believe their manifests are reviewed only by Rana's local authority. Several of those operators are Compact-affiliated and would object strenuously if they understood the arrangement's scope. ## Narrative Hook - + +Every significant freight shipment moving between the compliant inner corridor and the outer Compact zone crosses Rana's gate scheduling desk — and the person running that desk has been quietly filing summaries to Hansestadt's Merchant Assembly for eleven years. ## Calibration Note - + +`wave_2` settlement is consistent with deliberate early siting at a gate branching point; a junction here was commercially obvious to anyone who mapped the topology. The K0IV subgiant is genuinely unusual — subgiant stars are not common in the catalog of nearby systems, and the warmer, brighter character of this star gives Rana a physical distinctiveness worth flagging. `junction` topology with three gates matches the branching function described throughout. Assembly compliance at hop 6 is explained by the commercial relationship with Hansestadt — Rana's neutrality requires staying inside the framework. ## Topology diff --git a/wiki/star-systems/GJ-208/index.md b/wiki/star-systems/GJ-208/index.md index daacbac16..6fda32874 100644 --- a/wiki/star-systems/GJ-208/index.md +++ b/wiki/star-systems/GJ-208/index.md @@ -1,5 +1,5 @@ -# PLACEHOLDER_036 -**GJ 208** | M-type | west_reach +# Pereira's Rest +**GJ 208** | K7 | west_reach --- @@ -15,19 +15,34 @@ --- ## Supply Dependency - + +Pereira's Rest is wholly dependent on Meridian (GJ 502) for the material imports its small resident population cannot produce locally. The single gate connection means the community's economic relationship with the wider Reach is conducted entirely on Meridian's terms — when Meridian's scheduling office is available, in volumes Meridian's gate capacity allows. In practice this has been adequate: Pereira's Rest is small enough that its import requirements do not strain the connection, and Meridian has found the dead_end spur relationship commercially useful as a captive customer for redistribution. + +The system's local economy is subsistence-supplemented. The K7 primary habitable body is marginal — not hostile, but requiring sustained effort. Agricultural output covers about seventy percent of caloric needs; the remainder is imported. The community also produces high-quality hand-crafted goods — metalwork, textiles, and precision instruments made without automated production chains — that command premium prices from collectors in the inner corridor. This is not an economic strategy so much as what happens when skilled people have time, limited materials, and no reason to rush. + +Henrique Pereira, the Portuguese-heritage founder who led the Wave 4 charter party, chose this system because he wanted it to be difficult to reach. He had spent thirty years in south_reach shipping logistics and had accumulated enough to fund a private charter. He did not want to build a commercial hub. He wanted to build a place where the people who chose to come would have chosen it, not simply arrived because the gate network deposited them here. The "Rest" in the name was his word, applied in his founding charter: a place to rest from the reach of institutions. ## Faction Notes - + +Pereira's Rest is governed by a community council that follows no formal governance template. Decisions are made by consensus among heads of household, a practice that worked when the community was sixty people and is strained but still functional at its current size of approximately eight hundred. There is no Assembly delegate, no corporate presence, and no Lattice Commission office. The Gate Corporation maintains the single aperture through a rotating service contract managed from Meridian — a technician comes through twice a year, checks the hardware, leaves. + +Assembly authority is functionally nonexistent. Henrique Pereira's original charter is Assembly-registered, which technically establishes jurisdiction. No one has exercised it. The system does not pay Assembly assessments. It has never been asked. Pereira's Rest is too small and too isolated to appear in any Assembly enforcement priority framework. + +The Compact of Westphalia's principles — local self-governance, no external authority over internal arrangements — describe exactly what Pereira's Rest has practiced since founding, predating the Compact by a generation. Several Compact council members have cited the system as a living example of what Compact governance means in practice. The community itself has not adopted a formal position; the founder's philosophy was that formal positions invite formal disputes. + +The south_reach cultural heritage of the Portuguese-founding family has been diluted by generations of mixed arrivals drawn by the community's reputation for genuine autonomy rather than by cultural affinity. The founding surname persists; the founding culture's specific inflections are present in architectural vocabulary and calendar traditions but no longer dominant in language or daily life. ## Silence Topic - + +The community council's consensus governance model has a structural problem that has been apparent for two generations and has never been addressed because addressing it would require the kind of formal institutional design the founders explicitly rejected. As the community has grown, the "head of household" definition has become contested. Several multi-generational extended families claim single votes for households that contain forty or fifty people; several younger single-person households claim equal votes. The distribution of voting weight is not written down. The informal practice that has evolved benefits the older founding-lineage families, who have the largest households. Younger arrivals have noticed. The tension is present at every council session and is not discussed directly. ## Narrative Hook - + +Pereira's Rest was founded to be beyond institutional reach and has succeeded — the community governs itself without external authority, Assembly or otherwise — but its consensus governance model, designed for sixty people, is quietly fracturing under the weight of eight hundred. ## Calibration Note - + +`wave_4` settlement for a dead_end at hop 7 is consistent with a private charter founding: Wave 4 private charters were common, and a dead_end position is exactly what a founder seeking genuine isolation would choose. The K7 classification matches the header. `dead_end` with one gate to Meridian is accurate. The cross-corridor Portuguese/south_reach heritage founder in a west_reach system is an "early arrival" exception archetype — Pereira followed a personal agenda, not a cultural migration chain. The cultural dilution over generations is consistent with the cultural framework's treatment of dead_end divergence over time. ## Topology diff --git a/wiki/star-systems/GJ-3454/index.md b/wiki/star-systems/GJ-3454/index.md index 2e696cb6c..98cf89ca7 100644 --- a/wiki/star-systems/GJ-3454/index.md +++ b/wiki/star-systems/GJ-3454/index.md @@ -1,5 +1,5 @@ -# PLACEHOLDER_195 -**GJ 3454** | K-type | west_reach +# Eisentor +**GJ 3454** | M-type | west_reach --- @@ -15,19 +15,32 @@ --- ## Supply Dependency - + +Eisentor is a gate junction, not a producer. Its four apertures connect inward to both Hansestadt (GJ 832) and Altmark (GJ 357), outward to GJ 505A, and laterally to Kraków Junction (GJ 1116B). This position makes Eisentor the primary routing node for freight moving between the west_reach's two dominant commercial systems — Hansestadt and Altmark — and the middle and outer corridor. Every cargo shipment that doesn't route directly between those two systems passes through Eisentor's gate scheduling office. + +The "unsettled" designation reflects a classification artifact: Eisentor has a permanent operational population — gate crews, scheduling staff, transit workers, maintenance personnel — but no formal settlement charter. The population lives aboard station infrastructure rather than on a planetary body. Because the M-type primary has no habitable planets in the conventional sense, and because the founding entities registered this as a transit facility rather than a colony, Eisentor falls into a governance ambiguity that has never been resolved. Approximately eleven thousand people live here permanently. None of them have voted in an election under a formal governance framework. + +The German name ("iron gate") was given by the MVG regional logistics office that built the initial station infrastructure. It describes the function: a hard point of transit that everything passes through and that you do not route around. ## Faction Notes - + +Eisentor's actual governance is a three-party arrangement that emerged without anyone designing it. MVG holds the primary infrastructure contract and controls most of the physical station. The Gate Corporation manages the four apertures and controls the scheduling authority that determines the junction's operational tempo. A resident workers' association, formed two generations ago, holds enough collective leverage through labor organization to have won governance concessions that neither MVG nor the Gate Corporation formally acknowledges but both practically accommodate. The three parties negotiate continuously, without a constitution, in a system that functions because none of the three has found a better arrangement. + +Assembly authority is present through the Gate Corporation's operational framework, which incorporates Assembly commercial standards by default. MVG also operates within Assembly commercial registration requirements. The workers' association has twice petitioned the Assembly for formal settlement recognition, which would create a legal basis for elected governance. The Assembly has twice determined that jurisdictional clarity is a matter for the contracting parties to resolve. The workers' association has begun corresponding with Compact of Westphalia observers about alternative recognition frameworks. + +The junction's position between Hansestadt (Assembly-aligned commercial hub) and the outer corridor creates significant political traffic. Compact-affiliated operators route through Eisentor routinely; so do Assembly compliance officers. The workers' association has a pragmatic interest in staying out of the dispute — they need both streams of customers. MVG's political position follows Hansestadt; the Gate Corporation is formally neutral. The resulting three-way split means Eisentor functionally mirrors Rana's neutrality (GJ 150) at higher volume. ## Silence Topic - + +The Gate Corporation's scheduling system at Eisentor runs on hardware installed during the original station build. The hardware has been patched but never replaced — the replacement schedule requires taking apertures offline sequentially, and no arrangement among the three governing parties has ever survived long enough to implement a maintenance window that all three accept as equitable. MVG wants to minimize freight disruption; the Gate Corporation wants the work done on its timeline; the workers' association wants redundancy guarantees before any aperture goes dark. The existing hardware is running past its certified operational lifespan. The Gate Corporation's internal maintenance team knows the failure probability and has been escalating it to the scheduling office for three years. The scheduling office knows and has not told the other parties. ## Narrative Hook - + +Eleven thousand permanent residents of Eisentor have no legal governance framework, no voting rights, and no formal settlement status — and the Gate Corporation's scheduling hardware that keeps four gates running simultaneously is past its certified lifespan, with failure probability escalating while three parties argue about who owns the maintenance window. ## Calibration Note - + +`unsettled` despite permanent population reflects a real ambiguity in Assembly settlement law — transit facilities are categorized differently from colonies, and this system has never been formally reclassified. `junction` with four apertures connecting both major corridor hubs and the outer west is consistent with a deliberate siting at a topological chokepoint. The M-type dim star with no habitable worlds explains why this is a station settlement rather than a surface one. The name from MVG reflects corporate founding origin consistent with the station-build era; transit facilities of this type were typically established in the Wave 3-4 expansion period even when they never received formal settlement classification. ## Topology diff --git a/wiki/star-systems/GJ-357/index.md b/wiki/star-systems/GJ-357/index.md index fd300b89a..6e80c3c05 100644 --- a/wiki/star-systems/GJ-357/index.md +++ b/wiki/star-systems/GJ-357/index.md @@ -1,5 +1,5 @@ -# PLACEHOLDER_052 -**GJ 357** | M-type | west_reach +# Altmark +**GJ 357** | K | west_reach --- @@ -15,19 +15,34 @@ --- ## Supply Dependency - + +Altmark is the second-largest commercial system in the west_reach after Hansestadt. Its five gates connect inward to Hansestadt (GJ 832) and Eisentor (GJ 3454), and outward to GJ 3333, GJ 635A, and GJ 103, making it the primary distribution hub for the western and southwestern outer corridor. Manufactured goods flow inward from the core through Hansestadt to Altmark; raw materials and extractive outputs flow inward from the outer systems through Altmark toward Hansestadt and beyond. Altmark takes a margin on both directions. + +The system's economy is genuinely diversified in a way that few outer corridor systems manage: heavy fabrication in the inner orbital belt, agricultural production on the temperate primary habitable world, a financial services sector grown up around the trade volume the five gates generate, and a transit logistics industry that exists specifically because ships with mismatched schedules need somewhere to wait. The K-type star provides adequate but not generous stellar energy, and the agricultural sector runs on a combination of supplemental lighting and cold-tolerant crop strains developed locally over generations. Altmark feeds itself and exports modest food surpluses to the less agriculturally capable systems on its outward branches. + +The name comes from the German historical region — the Altmark was the original heartland of the Margraviate of Brandenburg, a place of foundational significance in German history. The founders, a consortium with strong German heritage, chose it to signal permanence and political weight rather than describe a geographic feature. They intended Altmark to become significant. The ambition was not wrong. + +MVG's logistics corridor reaches Altmark: the fabrication sector holds several MVG supplier contracts, and MVG's regional distribution hub for the outer west is located here. This makes Altmark commercially important to MVG in a way that Hansestadt is important strategically. MVG has a larger physical footprint in Altmark than in any other outer corridor system. ## Faction Notes - + +Altmark's governance is a bicameral system with an elected legislative assembly and an appointed commercial council that holds executive authority. The commercial council's seat allocation is weighted by the size of registered commercial entities, which means MVG holds two of nine seats as a matter of structural fact, and the four largest independent shipping and fabrication houses collectively hold another four. Genuinely popular governance is represented by three elected seats that have, in practice, enough collective leverage to block but not enough to initiate. The arrangement was designed by the founding consortium to ensure commercial interests remained in control. It has worked as designed for two hundred years. + +Assembly authority here is institutional and present. Altmark has five gates, which means significant Gate Corporation presence, Assembly commercial registrations for dozens of major operators, and periodic Assembly fleet visits that make the system feel more connected to the core than its hop distance would suggest. The Assembly's west_reach trade delegate is based at Altmark, not Hansestadt — Hansestadt is the Merchant Assembly's seat, which creates a distinction the Assembly enforces: its political office goes to the second hub, not the one dominated by a rival commercial body. + +The Compact of Westphalia represents the most significant political tension in Altmark's recent history. Three of the five outward gate connections lead toward systems that are either Compact signatories or Compact-sympathetic. Commercial pressure from those systems to adopt Compact mutual-tariff structures has been building for a decade. MVG opposes Compact alignment because it would complicate their Assembly-registered contracts. The commercial council has not taken a formal position; the elected assembly seats have twice passed resolutions endorsing "exploratory dialogue with western corridor governance structures." Both resolutions were overridden by the commercial council. ## Silence Topic - + +Altmark's financial services sector — the banks, bond houses, and commercial arbitration firms that grew up to service the trade volume through five gates — has been quietly processing Compact-registered commercial instruments alongside Assembly-registered ones for approximately fifteen years. This is technically legal in the grey space created by Altmark's local commercial framework, which predates the Compact's formation and does not explicitly recognize or exclude it. What the Assembly's trade delegate does not know is that the volume of Compact-registered instruments passing through Altmark's financial sector now exceeds the volume of Assembly-registered instruments on the outward routes. The system is already functionally Compact-integrated in its financial sector. The governance debate is trailing the commercial reality by a decade. ## Narrative Hook - + +Altmark's commercial financial sector has already integrated the Compact of Westphalia's trade instruments at higher volume than Assembly-registered ones on the outward routes — and the Assembly trade delegate is conducting governance diplomacy in a system whose commercial sector finished the conversation in his absence. ## Calibration Note - + +`wave_4` settlement for a five-gate hub reflects the late emergence of Altmark's commercial significance — the western outer corridor did not develop enough traffic to justify a major hub here until Wave 4 expansion created the outward branch systems. The K-type star is accurate to the header. `hub` with five gates is accurate; this is the second node after Hansestadt in the west_reach and its political and commercial weight should be felt. The German historical region name reflects the founding German-heritage consortium's explicit ambition for the system. MVG's significant footprint is consistent with the MVG corridor extending to hop 7-8. ## Topology diff --git a/wiki/star-systems/GJ-370/index.md b/wiki/star-systems/GJ-370/index.md index 199f3c2e8..2ec39994d 100644 --- a/wiki/star-systems/GJ-370/index.md +++ b/wiki/star-systems/GJ-370/index.md @@ -1,5 +1,5 @@ -# PLACEHOLDER_020 -**GJ 370** | K-type | west_reach +# Traagwater +**GJ 370** | K5V | west_reach --- @@ -15,19 +15,34 @@ --- ## Supply Dependency - + +Traagwater depends on Rana (GJ 150) for the manufactured goods and processed materials its agricultural economy does not produce. The dependency is ancient and well-managed: six hundred years of trade through a single gate has produced stable commercial routines, familiar faces on both sides, and a price relationship that fluctuates very little. Rana's redistribution business benefits from a captive agricultural supplier; Traagwater's agricultural surplus finds a reliable market at Rana's warehousing terminals. Neither system has any particular interest in changing this arrangement. + +The primary habitable world is water-rich, temperate, and slow. Three large shallow seas dominate the surface geography. Tidal patterns are gentle — the K5V primary is quiet and the moon configuration produces minimal tidal stress. The early Dutch-heritage settlers, who arrived in Wave 1 as part of an agricultural development program, named the system for the quality of water movement they observed everywhere: sluggish rivers, slow tides, a landscape that did not hurry. Traagwater. Slow water. The name was meant as a practical descriptor for the survey record. It became the name because no one thought of a better one before the first generation was gone. + +The agricultural output — primarily wetland-adapted grain varieties, cultivated fish stocks, and a distinctive fermented product made from a local seed crop — has been exported through Rana for five hundred years. By now the agricultural techniques have drifted significantly from their Earth analogs. The Traagwater farming cooperative maintains its own seed banks, its own cultivation records, and its own fermentation traditions. What they produce is recognizably descended from Dutch-heritage aquaculture and cereal farming, but it is something local now, not a transplant. ## Faction Notes - + +Traagwater is governed by a farming cooperative council that is, functionally, the same institution the Wave 1 founders established under their original settlement charter. The names have changed. The structure has not. Council seats are allocated by land holding within the cooperative system — which means long-settled families have more weight than recent arrivals, and the oldest founding-lineage families have the most. This is not contested. The governance model has been successful for long enough that its structural assumptions read as natural rather than designed. + +Assembly authority is a name on a document. The Wave 1 charter is Assembly-registered; the system has not filed compliance paperwork in living memory; no Assembly agent has visited in anyone's lifetime. The cooperative council knows the Assembly exists in the abstract and regards it as something that happens in places where people cannot work things out among themselves. The Compact of Westphalia is equally abstract. The corridor's political disputes feel very distant from a wet agricultural world whose gate opens onto a redistribution junction. + +Gate Corporation presence is minimal: a rotating maintenance technician visits the single aperture on an annual schedule. The technician routes through Rana (GJ 150) on the annual maintenance cycle, which has produced the system's most reliable news channel about the wider corridor — whatever the Gate Corp technician knows, Traagwater knows a day later. + +The Dutch cultural heritage is present in deep structure: architectural vocabulary in the older farming estates, naming traditions within founding-lineage families, a calendar that marks festivals with Low Dutch origins now six centuries evolved. The living culture is West Reach frontier agricultural, not Dutch. But the bones of the heritage are visible if you know where to look. ## Silence Topic - + +The founding-lineage families collectively hold land grants that, under the original Wave 1 charter, are documented in Assembly records as provisional — subject to renewal under settlement performance criteria. No one has invoked those criteria in five hundred years, and the Assembly almost certainly lacks both the records and the institutional will to do so. But the grants were never formally converted to permanent title under the Assembly's later settlement law, which created a permanent-title pathway that Wave 1 systems were supposed to use but many never did. If the Assembly were ever to examine Traagwater's land tenure structure, several founding families would discover that their six-hundred-year-old farms rest on provisional grants. The cooperative council's legal records contain a single notation from a Wave 3-era council secretary who identified the issue and concluded, correctly, that no one was going to press it. ## Narrative Hook - + +Six hundred years of quiet agricultural life on a slow-water world at the end of a dead_end spur — and the land tenure that the founding families have never questioned rests on provisional Wave 1 grants that no one formally converted to permanent title. ## Calibration Note - + +`wave_1` settlement at hop 7 in a dead_end is unusual and worth explaining: Wave 1 agricultural programs sent settlement parties along the early mapped gate paths before the full topology was understood. A dead_end at this hop distance would have been an early frontier position in Wave 1, not an isolated backwater. By the time the Reach's full topology was mapped, Traagwater was already established and simply remained where it was. The K5V classification matches the header. `dead_end` with one gate to Rana is accurate. The Dutch-heritage founding is consistent with west_reach corridor Germanic/Scandinavian/Central European inflection — Dutch heritage falls within the corridor's cultural envelope. ## Topology diff --git a/wiki/star-systems/GJ-442A/index.md b/wiki/star-systems/GJ-442A/index.md index 7b07ff401..1a0096b7d 100644 --- a/wiki/star-systems/GJ-442A/index.md +++ b/wiki/star-systems/GJ-442A/index.md @@ -1,5 +1,5 @@ -# PLACEHOLDER_269 -**GJ 442A** | M-type | west_reach +# Torsby +**GJ 442A** | G3/G5V | west_reach --- @@ -15,19 +15,28 @@ --- ## Supply Dependency - + +Torsby is a mid-weight industrial system on the loop between Dokkum (GJ 506) and deeper corridor space (GJ 3737). Its two gates make it a through-route station rather than a decision point — freight moves through because the loop exists, not because Torsby specifically attracts it. The system's economy is precision light manufacturing: components that require the stable thermal conditions a G-type star provides more reliably than the red dwarfs that dominate this corridor. MVG holds a secondary supplier contract here for passenger compartment fittings — not their core logistics chain but the kind of ancillary relationship that follows their major corridor presence outward. + +The name comes from a Swedish town in Värmland province — not a direct transplant but a deliberate echo by a founding family with Swedish heritage who wanted something that sounded like home without being a copy of it. The Lindqvist family, who led the Wave 4 settlement charter, held a majority of the founding land grants for the first two generations. Their descendants remain prominent in local manufacturing, which is either a legacy of their early institutional advantage or a demonstration of the competence that justified the charter — depending on who in Torsby you ask. ## Faction Notes - + +Torsby is governed by an elected industrial council, a form of cooperative governance that fits cleanly in the west_reach tradition. The Lindqvist family bloc holds two of the seven council seats; the remaining five rotate among the major manufacturing cooperatives. Assembly authority here is institutional and intermittent — the system files its compliance paperwork, pays reduced assessments under the wave_4 frontier-development framework it qualified for at founding, and receives periodic Gate Corporation maintenance visits. No one from the Assembly has been in-system in several years. + +Torsby's Compact of Westphalia position is sympathetic but not formal. The council has never voted on membership, which is itself a position — not saying yes, not saying no, staying in the space that allows trading relationships in both directions. The Dokkum connection (GJ 506) keeps Torsby commercially oriented toward the inner corridor; the GJ 3737 connection pulls it toward the outer west. The industrial council's standard answer to political questions is that Torsby is a manufacturing system and manufacturing systems need customers in both directions. ## Silence Topic - + +The Lindqvist family's oldest working cooperative holds a patent on a specialized bearing assembly used in gate ferry drive systems. The patent is Assembly-registered, which means it is nominally enforceable across the Reach. Several Compact-affiliated operators have begun producing compatible copies without license. The family has not filed an enforcement action through the Assembly's commercial courts, because filing would require formally acknowledging the Assembly's jurisdiction over a dispute their neighbors would regard as a local commercial matter. The bearing copies are getting better. The patent is eroding in practice. ## Narrative Hook - + +Torsby's most influential family holds intellectual property that only an Assembly-registered patent can protect — and exercising that protection would cost them their standing in the corridor's increasingly Compact-aligned commercial network. ## Calibration Note - + +`wave_4` settlement at hop 6 is consistent with a system that was commercially secondary to its neighbors at founding — the loop topology meant it was a useful through-route but not a priority site. The G3/G5V binary creates the thermal stability that justifies the precision manufacturing specialization, distinguishing Torsby from the red dwarf systems around it. `loop_member` topology is accurate to its function as a through-route on the Dokkum branch. The Swedish name with a Scandinavian founding family fits the west_reach Germanic corridor without being a direct Earth place-name. ## Topology diff --git a/wiki/star-systems/GJ-502/index.md b/wiki/star-systems/GJ-502/index.md index a15540914..44b417102 100644 --- a/wiki/star-systems/GJ-502/index.md +++ b/wiki/star-systems/GJ-502/index.md @@ -1,5 +1,5 @@ -# PLACEHOLDER_157 -**GJ 502** | M-type | west_reach +# Meridian +**GJ 502** | G0V | west_reach --- @@ -15,19 +15,30 @@ --- ## Supply Dependency - + +Meridian's three gates connect it simultaneously to Hansestadt (GJ 832), Freiholt (GJ 453), and its own dead_end spur at Pereira's Rest (GJ 208). This topology makes it the single point through which all traffic between the Assembly's commercial center of the west corridor and the Compact of Westphalia's most organized signatory must pass. There is no routing around Meridian if you want to move between Hansestadt and Freiholt. Every diplomatic contact, every commercial shipment, every Gate Corporation maintenance visit traveling that path comes through Meridian's gates, and Meridian's gate scheduling office decides when. + +The system was founded in Wave 3 as a logistics staging point for the expanding western frontier — the name "Meridian" was chosen by the original survey consortium to mean exactly what it suggests: a dividing line, a reference point from which distances are measured. The founders could not have predicted how precisely the name would come to describe the system's political position. Meridian now sits on the actual organizational boundary between the Assembly-aligned inner west and the Compact-affiliated outer west, and both sides understand that controlling this junction would change the shape of the dispute. + +The G0V star is unusually good — close to solar-type, a stable habitable zone, conditions that made Wave 3 settlement straightforward. Meridian is not hostile. It is, in fact, comfortable in a corridor where comfort is not the default. This has contributed to a larger-than-expected population for its wave and hop position. ## Faction Notes - + +Meridian's governance has been under structural pressure for two generations. The elected transit authority — which governs gate scheduling, transit tariffs, and commercial licensing — sits politically between its two most commercially important neighbors, and those neighbors want different things. Hansestadt wants Meridian to apply the Merchant Assembly's commercial arbitration framework; Freiholt wants Meridian to recognize the Compact's mutual-tariff structure. The transit authority currently operates under a local framework that acknowledges neither as controlling and applies them both in a patchwork that satisfies no one completely but has not collapsed. + +The Compact of Westphalia has approached Meridian's governing council three times in forty years. Each time, the council has declined without formally refusing. The formula is consistent: Meridian's position requires it to maintain relationships with all parties, and formal alignment with any bloc would compromise that function. The Assembly's delegation, which maintains a resident office here, regards this answer as a form of soft Compact sympathy. The Compact's council regards it as the only position available to a system that still needs Hansestadt's commercial framework to function. Both are probably right. ## Silence Topic - + +What Meridian's transit authority does not put in its public gate scheduling reports: the pattern of how it resolves scheduling conflicts between Hansestadt-bound and Freiholt-bound freight when both arrive simultaneously. The tie-breaking rules have evolved over thirty years through unpublicized precedent rather than formal policy. Analysis of the scheduling records — which are technically public but practically voluminous — would reveal that Compact-registered operators have been consistently given the shorter wait since approximately the time the Compact's third round of approach to the council concluded. No individual decision is unusual. The pattern is unmistakable. ## Narrative Hook - + +Meridian's transit scheduling office is the single chokepoint between the Assembly's west corridor hub and the Compact's most organized signatory — and it has been tilting the scales in the Compact's direction for thirty years without ever announcing it. ## Calibration Note - + +`wave_3` settlement is consistent with a deliberate siting by a logistics consortium that understood the junction value early. The G0V star producing good conditions explains why the system developed into a real population center rather than a bare transit node. `junction` topology with three gates is structurally accurate to the role. The name "Meridian" is in the Reach's tradition of abstract/aspirational names (alongside Renaissance, Gateway) and does not require cultural heritage explanation — it is a Wave 3 consortium founding name, not a cultural transplant. The political tension is inherent to the topology; no additional invention is needed to explain why this system is under pressure. ## Topology diff --git a/wiki/star-systems/GJ-581/index.md b/wiki/star-systems/GJ-581/index.md index fb3be8b82..5d41b0f3f 100644 --- a/wiki/star-systems/GJ-581/index.md +++ b/wiki/star-systems/GJ-581/index.md @@ -1,5 +1,5 @@ -# PLACEHOLDER_261 -**GJ 581** | K-type | west_reach +# Rødvik +**GJ 581** | M5 | west_reach --- @@ -15,19 +15,30 @@ --- ## Supply Dependency - + +Rødvik depends on Neustadt (GJ 526) for processed metals and manufacturing components. The loop connection to GJ 231 provides the system's secondary commercial lifeline — a route toward the outer corridor that carries agricultural imports and consumer goods in the inward direction and Rødvik's primary export outward: geothermal energy converted to portable fuel cells. The M5 red dwarf provides almost no useful stellar radiation for solar generation. What the star lacks in light it compensates in tidal flexion: Rødvik's primary habitable body orbits close enough to experience substantial tidal heating, and the geothermal infrastructure built to exploit this heat source is the system's foundational economic asset. The name references the reddish cast of local geological outcroppings seen under the dim stellar light — "red bay" in Norwegian, given by the original survey team whose lead geologist had Bergen heritage and an eye for what would make the place memorable. + +Wave 5 settlement is recent enough that Rødvik still receives Assembly infrastructure development grants. The grants are administered through Neustadt's regional development office, which creates a financial dependency that Rødvik's council finds politically uncomfortable and economically essential. ## Faction Notes - + +Rødvik's governance is a municipal council with strong ties to the energy cooperative that operates the geothermal network. The energy cooperative predates formal governance — it was the founding corporate entity, established to develop the tidal heating resource under an Assembly Wave 5 development charter. The council was formed after the first permanent population reached sufficient size to require more than corporate management. The relationship between the two bodies is not adversarial, but it is not comfortable: the cooperative holds the infrastructure, the council holds the authority, and neither has been tested enough to know which one wins when they disagree. + +Assembly authority here is institutional and present, but primarily expressed through the development grant framework. Wave 5 systems are unusual in the outer corridor in that Assembly engagement is active rather than historical — early-settlement systems get real attention. This creates a paradox: Rødvik has more Assembly contact than most hop-6 systems, but less of the tradition of compliance that older systems built up over generations of habit. The council regards the Assembly as a funding body rather than a government, which is its own form of autonomist thinking. + +Compact of Westphalia sympathy is present in the older workers who arrived from Neustadt and the outer corridor. No formal position has been adopted — the system is too young and too dependent on Assembly development funds to risk it. ## Silence Topic - + +The geothermal cooperative's engineering team knows that the tidal flexion rate is not stable. The primary habitable body's orbit is drifting — very slowly, over geological time — in a direction that will reduce tidal heating by an estimated twelve percent over the next two centuries. This is not an emergency. It is not even urgent. But it means the energy infrastructure that the entire settlement economy depends on is built on a resource that is diminishing. The cooperative's internal projections are classified as proprietary technical data. The development grant documents submitted to the Assembly describe the resource as "long-term stable," which is technically true and practically misleading. ## Narrative Hook - + +Rødvik's founding energy infrastructure rests on a geothermal resource the cooperative knows is slowly depleting — and the Assembly development grants funding the system's expansion are based on projections the cooperative quietly revised downward three years ago. ## Calibration Note - + +`wave_5` settlement is consistent with a system whose primary resource (tidal geothermal energy) requires a specific technological threshold to exploit economically, making it a late-wave rather than early-wave target. The M5 classification matches the star description in the header. `loop_member` topology is accurate — two gates, through-route function on the outer corridor loop. The Norwegian name and Bergen-heritage surveyor connection fits the west_reach cultural corridor with a natural rather than transplanted naming logic. ## Topology diff --git a/wiki/star-systems/GJ-631/index.md b/wiki/star-systems/GJ-631/index.md index c6e3775c2..3f83ea859 100644 --- a/wiki/star-systems/GJ-631/index.md +++ b/wiki/star-systems/GJ-631/index.md @@ -1,5 +1,5 @@ -# PLACEHOLDER_257 -**GJ 631** | G-type | west_reach +# Bakshi Spur +**GJ 631** | K2V | west_reach --- @@ -15,19 +15,32 @@ --- ## Supply Dependency - + +Bakshi Spur is economically dependent on Kraków Junction (GJ 1116B) for manufactured goods, transit services, and most of what passes for institutional contact with the wider Reach. The spur terminus at GJ 1232 provides the system's only other gate connection — a route toward the outer corridor that sees infrequent commercial traffic and functions primarily as a backup route rather than a genuine commercial artery. Bakshi Spur's own economy is built on specialized materials extraction: the K2V star's habitable zone hosts a rocky primary with elevated deposits of rare refractory minerals used in precision heat-shielding components. MVG holds a long-standing materials contract here, which is the primary reason the system has maintained economic viability across six hundred years of isolation. + +The "Spur" suffix is a piece of cartographic slang that became a formal name. When early navigators were charting this branch of the corridor, GJ 631 appeared on working maps as "Bakshi's Spur" — the dead-end branch that surveyor Kiran Bakshi had gone out to examine. Bakshi's family, who were part of the initial Wave 3 founding group, regarded formalizing the navigation name as a reasonable compromise between naming the system after their patriarch and naming it after something that would confuse future residents. The Bakshi family has been gone from the system for two centuries, absorbed into the broader west_reach population, but the name persists. ## Faction Notes - + +Bakshi Spur is governed by a corporate council with MVG holding a permanent seat under the terms of the original materials contract. The remaining seats are elected from the resident population, which means governance is functionally a negotiation between MVG's extraction interests and the residential community that lives with the consequences of extraction. The residential bloc has managed to constrain the worst extraction practices through local environmental regulations, but MVG's contractual position limits how far the council can push. + +Kraków Junction's Polish-heritage political culture has influenced Bakshi Spur more than the South Asian founding heritage now visible primarily in the system's name. The founding Bakshi family's commercial connections ran east — to the Polish-heritage junction community that was already established at hop 5 — rather than south or west, which is unusual for a west_reach system and reflects the practical reality that you go where the gate takes you. + +Assembly authority is institutional and intermittent. The system has been formally compliant for its entire history because MVG's contracts require Assembly commercial registration, and MVG maintains that compliance as a corporate matter rather than delegating it to the local council. In practice, the Assembly's authority here is an extension of MVG's corporate framework. What MVG's contract does not require, the Assembly cannot enforce. + +The Compact of Westphalia's presence is felt primarily through Kraków Junction's sympathies. Bakshi Spur has not adopted a formal position; MVG's requirement for Assembly commercial registration makes formal Compact membership practically complicated. ## Silence Topic - + +The refractory mineral deposits that MVG's contract was written around have been more productive than the original survey anticipated. MVG's current extraction rate would exhaust the economically viable deposits in approximately eighty years. MVG's regional geologists have updated their internal projections twice. The local council's version of the geological survey, which is incorporated into the system's development plan, dates from thirty years ago. The council has requested an updated survey. MVG has described the request as pending review. ## Narrative Hook - + +The mineral resource underlying MVG's century-long contract is running out faster than anyone outside MVG's internal planning office knows — and the system's governance framework gives MVG the contractual position to walk away when they choose. ## Calibration Note - + +`wave_3` settlement at hop 6 with a spur_end topology is consistent with a resource-discovery founding: someone found the refractory minerals, the founding group followed the survey, and the spur was not developed further because nothing outward justified it. The K2V classification is correct. `spur_end` with two gates is accurate to the described topology. The cross-corridor South Asian founding heritage (the Bakshi family) is explicitly an "early arrival" exception archetype — they followed a corporate survey contract, not cultural affinity, and the surrounding corridor absorbed the cultural heritage over generations. ## Topology diff --git a/wiki/star-systems/GJ-809/index.md b/wiki/star-systems/GJ-809/index.md index ef0033dc9..b7630cef5 100644 --- a/wiki/star-systems/GJ-809/index.md +++ b/wiki/star-systems/GJ-809/index.md @@ -1,5 +1,5 @@ -# PLACEHOLDER_170 -**GJ 809** | G-type | west_reach +# Seiðrmaðr +**GJ 809** | M2V | west_reach --- @@ -15,19 +15,34 @@ --- ## Supply Dependency - + +Seiðrmaðr depends entirely on Port Mäkelä (GJ 229) for the physical supply of materials it cannot produce locally — raw feedstocks, agricultural goods, bulk commodities. The single gate to Port Mäkelä is the system's only connection to the broader Reach. Everything enters and exits through one aperture, on a schedule the local transit authority controls, reviewed by no one outside the system. This structural isolation, which most systems at a dead_end position regard as a constraint, was the founding community's explicit design criterion. + +The community that established Seiðrmaðr in Wave 4 was not a corporation, a migration chain, or a government program. It was a group of engineers, fabricators, and applied scientists who wanted a place to work without oversight. Their founding charter made no claims about what they intended to build — only that they required isolation, stable energy (the M2V red dwarf, compact and stable, suited this perfectly), and a single gate that they could control. They paid the Gate Corporation's founding tariff in full at establishment, which bought them the scheduling rights that most systems only earn through long negotiation. The community understood, from the beginning, that controlling the single gate meant controlling who knew what they were doing. ## Faction Notes - + +Seiðrmaðr is governed by Tiefwerk AG, the company the founding engineers established as their legal entity. Tiefwerk AG is not a government in the Assembly's sense — it has no elected representatives, no public governance sessions, no external accountability structure. It is a private company that happens to own and operate everything in the system. The resident population consists of Tiefwerk employees, their families, and a small support community. There are no independent residents. This is not coercive: people choose to come here, knowing the terms, and choose to leave when the terms no longer suit them. The waiting list for Tiefwerk positions is long. + +What Tiefwerk makes is not a mystery to their customers: they produce drive component assemblies for gate ferry vessels — specifically the field-shaping coils that manage the aperture interface during transit. What is not widely understood is how they make them. Tiefwerk's coils operate at tolerances that, according to standard fabrication theory, require manufacturing equipment orders of magnitude more expensive than anything a dead_end system at hop 6 should be able to support. The Gate Corporation has tested them extensively and confirmed they perform as specified. Three competing manufacturers have attempted to replicate the design from the product itself. None has succeeded. + +Trade partners — primarily Port Mäkelä, and through them the broader corridor — started calling the system "Seiðrmaðr" (the Norse word for a practitioner of seiðr, a form of magic worked by seeing what others cannot) sometime in the second generation of operation. Tiefwerk's own community uses the name without irony. The founders, who named the system something unmemorable in their founding charter, were not displeased. + +Assembly authority here is theoretical. Tiefwerk's products cross the Assembly's commercial registration system because the Gate Corporation requires it for certified transit components. That registration is the extent of Assembly contact. No Assembly inspector has visited the system. The system does not pay Assembly assessments and has not been asked to — the Assembly's enforcement posture toward a dead_end at this distance, producing components the Gate Corporation considers essential, is calculated non-confrontation. + +The Compact of Westphalia has no formal relationship with Seiðrmaðr. Tiefwerk is not ideologically opposed to the Assembly; they are simply not interested in either side of the argument. Their political philosophy, to the extent they have one, is that the inside of this gate is their business and the outside is not. ## Silence Topic - + +Tiefwerk's manufacturing process involves a fabrication technique that the company describes internally as "resonance templating" — a method of inducing crystalline alignment in metal alloys through controlled acoustic fields rather than conventional thermal processing. The technique produces the tolerance consistency that makes their coils exceptional. Tiefwerk has not patented the process. Patents require disclosure, and disclosure would invite the kind of attention they built this dead_end to avoid. The technique was developed here, in isolation, by engineers who had time and no one looking over their shoulders. Several of those engineers are now Perpetuals. They remember every iteration of every failed approach that led to what works. The knowledge lives in people, not documents. ## Narrative Hook - + +Tiefwerk AG produces the most reliable gate ferry drive coils in the Reach from inside a dead_end that no one fully understands — and the manufacturing secret that makes them irreplaceable lives only in the memories of engineers who chose this isolation deliberately and have never left. ## Calibration Note - + +`wave_4` settlement at a dead_end position is consistent with a deliberately sited private founding — Wave 4 had looser frontier development frameworks that allowed private charter establishments of this kind. The M2V classification matches the header. `dead_end` with one gate is accurate and thematically central: the isolation is the point. The name is the trade partners' name, not the founders' name, which fits the naming logic — descriptive of what outsiders experience rather than what the founders intended. The Tiefwerk AG governance structure is an unusual corporate arrangement that is justified by the deliberate founding purpose and the Perpetual-class founders who have maintained the vision across generations. ## Topology