feat(docs): write east_reach mid ring wiki pages (batch 2, hops 5-6)
10 systems: Relay 7, Jinghu, p Eridani, Thornfield Station, Port Desrochers, Gliese 667, Binh Trang, Kovács Loop, Whitfield Crossing, Novaya Zarya. Paula review fixes applied: GJ-908 hop anomaly flagged, p Eridani missing gate connection added, Kovács Loop routing claim tightened, Binh Trang junction characterization corrected. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Claude Opus 4.6
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_039
|
||||
**GJ 1005A** | F-type | east_reach
|
||||
# Port Desrochers
|
||||
**GJ 1005A** | M: · east_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -15,19 +15,32 @@
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
The "Port" in Port Desrochers is not decorative. The system's three gates connect outward on two branches and inward toward GJ 105A, and the founding Desrochers family understood from the beginning that a junction system's commercial value lies in traffic management rather than production. Port Desrochers operates as a transit-service economy: gate ferry scheduling, cargo bonding services, passenger transit accommodation, and the commercial dispute resolution infrastructure that traffic concentration generates. The habitable body has sufficient agricultural output to feed the resident population without imports, which the founders considered a strategic priority — a system that can feed itself without being dependent on gate connections is a more defensible commercial position than one that cannot.
|
||||
|
||||
What Port Desrochers exports, functionally, is connectivity. Remove it from the junction topology and two outward branches lose their coordination node. The Desrochers family's original development application framed this explicitly as a commercial value proposition, and three generations of competent management have made the argument self-evidently true.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
Mathieu Desrochers filed the wave_3 development application with a north_reach heritage that is notable in this part of the east corridor. He was French-Canadian, a transit infrastructure specialist whose family had been in the gate ferry business in the north_reach for two generations before he identified the GJ 1005A junction opportunity as a better commercial position than anything available in the north_reach at the time. His move is documented in the Desrochers family's own commercial archive as an economic calculation rather than a geographic preference. He followed the gate topology, not the cultural corridor.
|
||||
|
||||
Three generations later, the Desrochers family still holds the primary commercial licenses for the system's major transit infrastructure, but the system's population is substantially east_reach in cultural character — the migration that filled Port Desrochers after the founding was drawn from the east corridor's labor pool, and the Desrochers family has been a French-Canadian founding layer over an east_reach demographic base ever since. The family name is the most visibly non-east_reach thing about the system.
|
||||
|
||||
The Lattice Commission has a standard junction office. Assembly compliance is maintained — the junction's commercial operators require Commission-certified documentation and therefore comply with Commission frameworks as a commercial necessity. Port Desrochers is neither Assembly-enthusiastic nor Assembly-resistant; the institutional framework is useful and treated accordingly.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What the Desrochers family does not discuss publicly: the original terms of the development application's third-party financing.
|
||||
|
||||
Mathieu Desrochers did not have the capital to develop a three-gate junction independently. The application was financed by a north_reach investment consortium that held a silent equity stake in the system's transit infrastructure for the first forty years of operation. The stake was bought out — the Desrochers family's records confirm this — but the terms of the buyout, including what the consortium received and what commitments the family made as a condition of the buyout, are in the consortium's private records rather than any public filing. At least one subsequent commercial decision by the family — the selection of a specific gate ferry contractor over a lower-cost alternative — has been attributed by people who know the family well to a relationship obligation from that buyout rather than a purely commercial judgment.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
Port Desrochers was financed by a north_reach consortium whose silent equity stake was bought out forty years into the settlement's history, and the terms of that buyout have shaped the Desrochers family's commercial relationships ever since in ways that are visible in their contracting patterns but never explained in their public communications.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
`wave_3` at `hop 5` as a `junction` with 3 apertures is consistent with deliberate commercial siting after the east corridor's initial wave_2 topology was established. M: star classification (active M-type variant) matches the stub. French-Canadian founder surname in east_reach territory is a cross-corridor exception of the Early Arrival archetype — the founder followed economic logic rather than cultural affinity, which is the Section 6.2 explanation. The "Port" modifier is a Section 6.3 functional designation that signals the system's transit identity rather than a geographic transplant.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_185
|
||||
**GJ 137** | binary-type | east_reach
|
||||
# Novaya Zarya
|
||||
**GJ 137** | G5Vvar · east_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -15,19 +15,34 @@
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Novaya Zarya is the largest traffic node in this batch of systems — four gates, a junction topology, and a G5Vvar primary that supports a genuinely habitable world with agricultural capacity sufficient to feed the resident population and export surpluses. The four connections reach to GJ 635B, GJ 909A, p Eridani (GJ 66A) inward, and GJ 325A outward, making Novaya Zarya the redistribution hub for the outer segment of this corridor branch. Commercial traffic that would otherwise require routing through p Eridani's congested junction flows through Novaya Zarya instead, and the system has developed a commercial infrastructure commensurate with that role: bonded warehousing, commercial arbitration services, gate ferry scheduling, and the technical support ecosystem that four-gate traffic requires.
|
||||
|
||||
The G5Vvar variable classification is a commercial reality that the transit operators manage carefully: the star has mild variability cycles that periodically affect communications infrastructure but do not significantly impact surface conditions on the habitable world. Operators who route through Novaya Zarya know to check variability projections when scheduling time-sensitive freight.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The founding community was Russian-heritage — a wave_3 collective of engineering and agricultural families who named the system "New Dawn" in a moment of deliberate aspirational naming consistent with the displacement narrative that brought them here. The wave_3 period saw significant outward migration from Russian successor-state communities following a political disruption in the inner corridor that is referenced obliquely in several founding documents but never described directly. What the founding archive makes clear is that the community intended Novaya Zarya to be a fresh beginning, and that the institutional structures they built were consciously designed to avoid what they describe as "the errors of the previous arrangement" without specifying what those errors were.
|
||||
|
||||
Five generations on, the Russian-heritage founding culture is visible in naming conventions, a distinctive architectural aesthetic that uses geometric modularity as a structural principle, and a formal community assembly process that requires all major decisions to pass through a recorded public deliberation before implementation. The population is now substantially mixed — four gates at hop 6 attract diverse migration streams — but the founding community's governance framework has proven durable enough to persist as the operating system despite demographic dilution.
|
||||
|
||||
The Assembly's presence is intermittent but not negligible for a hop-6 system. Four gates and significant commercial traffic means the Lattice Commission has a genuine junction office here, and Gate Corporation maintains a full maintenance team. Novaya Zarya's assembly process participates in Assembly governance frameworks more actively than most comparable-distance systems — the community's governance culture places high value on documented procedural legitimacy, which makes Assembly compliance frameworks feel native rather than imposed.
|
||||
|
||||
The Guardians of Autonomy have a chapter but it operates as loyal opposition within the community assembly's procedural framework rather than as an anti-institutional force. The GoA's corridor-dependency critique finds limited purchase in a system that is a net distributor of connectivity rather than a dependent node.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What the community assembly does not discuss in public record: the founding displacement.
|
||||
|
||||
The vague references in the founding archive to "the errors of the previous arrangement" point to a specific institutional failure in the inner corridor — a commercial cooperative that collapsed under circumstances the founding community's members were party to and, in some accounts, partially responsible for. The collapse harmed other parties. Some of those parties' successors are institutional entities in the inner corridor that Novaya Zarya's commercial operators deal with today. The founding community's decision not to document the specific events in the public record was a deliberate choice, made in the first generation, to allow the settlement to establish commercial relationships without the weight of the prior history following them outward. Whether this constitutes a cover-up or a practical boundary-setting is a question that depends on what the undocumented events actually involved.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
Novaya Zarya's founding archive describes a displacement from the inner corridor in terms deliberately vague enough to obscure a specific institutional failure, and the founding community's commercial successors today have active business relationships with institutional descendants of the parties that failure harmed.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
`wave_3` at `hop 6` as a `junction` with 4 apertures and a G5Vvar primary at 29.8 ly is the largest hub in this batch and justified by the G-type star's genuine agricultural and habitable-world potential — a G5Vvar at 29.8 ly would be a high-priority commercial development target for wave_3 operators who wanted a real settlement rather than an industrial waystation. Russian-heritage founding community is a cross-corridor exception of the Early Arrival type, here driven by internal-corridor displacement rather than pure commercial logic. "Novaya Zarya" (New Dawn) is a Section 6.3 abstract/aspirational naming category consistent with a displacement-motivated founding. The G5Vvar variable designation is accurate to the star type and creates a practical detail (variability cycles) that gives the system texture without being a narrative obstacle.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_064
|
||||
**GJ 17** | G-type | east_reach
|
||||
# Binh Trang
|
||||
**GJ 17** | F9V · east_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -15,19 +15,34 @@
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Binh Trang sits between Thornfield Station (GJ 908) on one branch and Kaelong (GJ 172) on another, with its third gate opening toward GJ 660A in the outer corridor. This position made the system commercially significant almost immediately after founding: it connects an isolated dead_end community to the junction network that includes Kaelong's Vietnamese agricultural corridor deeper in the reach. The F9V primary is brighter and more energetic than the M-dwarf stars that dominate this corridor band, which has produced a habitable world with better agricultural conditions than most of its hop-6 neighbors. Binh Trang exports food surpluses that go primarily to Thornfield Station, completing an economic dependency loop that the Thornfield community has mixed feelings about.
|
||||
|
||||
The system also handles transit logistics for the outer corridor branch toward GJ 660A — personnel and equipment moving deeper into the reach pass through Binh Trang's gate facilities, giving the system a secondary economy in transit services alongside its primary agricultural base.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
Binh Trang was settled in wave_3 by a Vietnamese-heritage farming cooperative whose members came from Kaelong's extended agricultural network. The founding decision was partly cultural — families from Kaelong's founding stock who wanted to establish their own settlement on terms they controlled rather than under the Kaelong Agricultural Syndicate's cooperative framework — and partly commercial, because the F9V star's agricultural potential was substantially better than Kaelong's K8V system had offered the earlier wave_2 founders. The name means "peaceful embankment" in Vietnamese, referencing the habitable world's prominent river-delta geography.
|
||||
|
||||
The founding cooperative's governance model draws on the same Vietnamese agricultural cooperative tradition as Kaelong's, but the two communities' relationship is more complicated than the shared heritage would suggest. Binh Trang's founders explicitly left Kaelong's governance structure, and their descendants have a persistent identity as independent from the Kaelong Syndicate's cultural weight even as they trade extensively with it.
|
||||
|
||||
The Assembly's presence is intermittent — a delegate circuit reaches Binh Trang on a schedule that reflects the system's hop distance. The governing council treats Assembly compliance as a background requirement, met without enthusiasm and without active resistance.
|
||||
|
||||
Guardians of Autonomy have a more active presence here than at Kaelong — partly because Binh Trang's relationship with Thornfield Station creates an economic dependency dynamic (Thornfield depends on Binh Trang food imports) that GoA organizers describe as an example of structural corridor dependency. The organizing rhetoric does not always match the actual relationship, which is bilateral and generally equitable, but it finds enough purchase to sustain a functioning chapter.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What Binh Trang's council does not discuss with Thornfield Station: the agricultural pricing structure.
|
||||
|
||||
Binh Trang's food exports to Thornfield are priced under a bilateral trade agreement that has been in place since the two systems established the relationship in wave_3. The agreement includes a price stability provision — prices cannot be adjusted by more than a set percentage per cycle without joint council review. What the provision does not address is currency adjustment: the pricing is denominated in credits tied to an inner-corridor index, which means when inner-corridor index inflation runs above the stability cap's implied rate, Thornfield is effectively paying more in real terms without any formal price revision having occurred. The Binh Trang council's commercial advisors understand this dynamic. The Thornfield Station council does not, as far as Binh Trang's administrators are aware.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
Binh Trang's food trade agreement with Thornfield Station includes a currency denomination clause that produces real-terms price increases without triggering the formal review mechanism, and whether this is a deliberate design feature or an oversight neither council has cared to examine.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
`wave_3` at `hop 6` as a `junction` with 3 apertures and an F9V primary is consistent with deliberate agricultural expansion along the Vietnamese corridor — the F9V star's better conditions would justify pushing a generation further out than the K8V systems that anchored the earlier wave. Vietnamese heritage founding community continuing the corridor identity established at Kaelong is a corridor-consistent choice that also explains the cultural relationship tension. The junction topology with an F9V star at 28.0 ly is calibrated correctly — the star's energy output supports the agricultural basis that a pure-M-dwarf system at this distance could not.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_062
|
||||
**GJ 3135** | M-type | east_reach
|
||||
# Whitfield Crossing
|
||||
**GJ 3135** | K:... · east_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -15,19 +15,32 @@
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Whitfield Crossing exists because the gate path between Kurashiki (GJ 205) and the outer corridor has to go through something, and what it goes through is this system. The "Crossing" designation was the founding naming convention for through_route systems in the east corridor's wave_3 development push — a practice that produced several similar names along the corridor branches before the practice fell out of fashion. Whitfield Crossing kept the name while other "Crossings" were eventually renamed; the founder surname gave it enough specificity to survive as a community identity.
|
||||
|
||||
The habitable body is unremarkable: a rocky planet with managed atmosphere and subsistence agriculture. The economy is organized around the transit function — gate ferry services, cargo inspection and documentation, crew accommodation, and the small-volume commercial traffic that accretes around any through_route that sees consistent corridor use. Whitfield Crossing exports processed agricultural surpluses in modest quantities and imports higher-order equipment and consumer goods. The supply dependency is bilateral in the conventional through_route pattern: the system needs Kurashiki's coreward connection for manufactured goods and the outer gate for whatever economic relationship has developed with GJ 423A over three wave_3 generations.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
Margaret Whitfield was the wave_3 development license holder — an English-heritage transit planner who spent her career identifying under-utilized gate path segments and filing development applications before the commercial value became obvious to larger operators. Whitfield Crossing was her third application and her most successful. She never lived in the system herself; the first generation of settlers were workers recruited under her license rather than her own extended community. Her name persists on the system because the first generation named it in her honor and the second generation found no reason to change it.
|
||||
|
||||
The governing structure is a transit authority board, the standard form for through_route systems in this corridor. The board administers gate operations, sets facility fees, and manages the labor contracts for transit support workers. Residential governance is managed through a separate community council that handles everything the transit authority board does not, which in practice is mostly housing and local services. The two bodies coordinate effectively; their jurisdictions rarely conflict because the transit economy and the residential community operate in largely separate domains.
|
||||
|
||||
The Lattice Commission has a documentation compliance officer. No full office. The through_route generates enough documentation requirements to justify one officer's attention but not enough to justify a team. Gate Corporation runs standard maintenance contracts for both gates.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What Whitfield Crossing's transit authority board does not discuss publicly: the fee-sharing arrangement with Kurashiki.
|
||||
|
||||
The gate fee schedule for corridor traffic passing through Whitfield Crossing was set in a bilateral agreement with Kurashiki's cooperative council during the wave_3 founding period. The agreement included a revenue-sharing provision — a percentage of Whitfield Crossing's gate fees pass to Kurashiki's infrastructure fund in exchange for Kurashiki's preferential routing of its commercial traffic through Whitfield rather than alternative paths. The revenue-sharing provision is not illegal; it is a commercial arrangement between two adjacent systems. What it effectively does is tie Whitfield Crossing's transit board's revenue partly to Kurashiki's commercial interests, which creates an alignment of incentives that the board is careful not to make explicit when it deals with commercial operators from other corridor systems who might prefer not to know that their routing through Whitfield benefits Kurashiki.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
Whitfield Crossing's gate fee revenue includes a percentage that flows to Kurashiki under a founding-era bilateral agreement, and the transit board's commercial routing decisions are structurally aligned with Kurashiki's interests in ways that outside operators moving through the system do not know to account for.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
`wave_3` at `hop 6` as a `through_route` with 2 apertures at 30.3 ly is consistent with deliberate wave_3 siting to connect Kurashiki's coreward commercial infrastructure to the outer corridor. K:... classification (uncertain-type K star) matches the stub. English founder surname plus "Crossing" functional topological descriptor fits Section 6.3 guidelines — the founding-figure attribution is secondary to the functional identity, which is the dominant naming logic for through_route systems. English heritage in the east_reach is a cross-corridor exception of the Early Arrival type: Whitfield followed gate path commercial logic rather than cultural corridor affinity.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_005
|
||||
**GJ 438** | M-type | east_reach
|
||||
# Relay 7
|
||||
**GJ 438** | K0 · east_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -15,19 +15,32 @@
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Relay 7's economy is inseparable from the logistics chain it was built to serve. The system was designated Relay 7 in a freight-routing catalog maintained by one of the Yongli Combine's wave_2 predecessor entities — the seventh waystation in a planned supply corridor that would eventually anchor at Haodu (GJ 566A). The preceding six relays were renamed or absorbed into larger commercial identities when the corridor matured. Relay 7 was not. Whether this reflects bureaucratic inertia or a deliberate choice by a community that prefers functional clarity to sentiment is a question locals answer differently depending on who you ask.
|
||||
|
||||
The two-gate loop keeps Relay 7 in a tight economic relationship with Haodu and GJ 1128 on the other branch. The system's commercial function today is the same as its founding function: staging, repackaging, and forwarding freight that needs to change container format, adjust documentation, or wait for a connection slot in Haodu's congested gate schedule. The system produces little that it exports as primary product. Its value is positional and logistical, which makes its population stable but modest — large enough to run the staging facilities, small enough that expansion would require a commercial reason that has never quite materialized.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The Yongli Combine does not own Relay 7 outright, but its operational fingerprints are on every significant facility in the system. The founding corporate entity's records were absorbed into Combine administrative archives during wave_3 commercial consolidation, and several of the long-term facility leases still reference the Combine's predecessor designation rather than the current parent entity. Locals are aware of this. They find it either amusing or vaguely uncomfortable depending on whether they work for a Combine-affiliated contractor.
|
||||
|
||||
Effective governance is a Transit Operations Board — a hybrid body of facility operators and elected resident representatives that emerged from a labor dispute in the system's third generation. The Board runs efficiently because the system is not complex enough to require complicated governance. The Lattice Commission has a registration officer but no active enforcement presence; the Commission's interest in a staging waystation is limited to ensuring freight documentation meets corridor standards, which the Board enforces as a commercial matter independent of Commission oversight.
|
||||
|
||||
The Assembly exists at Relay 7 as a compliance framework, not as an institutional presence. The most recent Assembly delegate visit was over a decade ago.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What the Transit Operations Board does not discuss openly: the origin of the name itself, specifically why the seven preceding relay designations in the corporate catalog were retired and Relay 7 was not.
|
||||
|
||||
The answer, which any archivist with access to the Yongli Combine's predecessor records could theoretically reconstruct, involves a contract dispute during wave_3 consolidation in which the settlement's founding community refused to accept a commercial rebranding the acquiring entity wanted to impose. The community won the dispute. The corporate entity dropped the rebranding effort without explanation in the public record. What the corporate records actually show — accessible only to those with Combine archive credentials — is that the community's refusal was backed by a provision in the original relay charter that gave the resident population naming authority the corporate entity had not noticed when it acquired the contract. The Combine has been careful, in every subsequent founding charter it has participated in, to ensure that provision does not appear again.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
Relay 7 kept its logistical designation while six predecessor stations were renamed, and the Yongli Combine's internal archive contains the charter provision that explains why — a provision the Combine has quietly ensured no founding charter since has replicated.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
`loop_member` at `hop 5` for a `wave_2` system with 2 apertures is consistent with an early-settled waystation that became part of the corridor's commercial loop as the Haodu hub developed. The K0 star at 27.4 ly provides adequate energy for a staging facility operation. The corporate-designation name is a Section 6.3 category exception — not a cultural heritage name but a functional designation that stuck — appropriate for a wave_2 industrial-logistics system in the east_reach's commercially-founded corridor.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_298
|
||||
**GJ 445** | M-type | east_reach
|
||||
# Jinghu
|
||||
**GJ 445** | M4 · east_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -15,19 +15,32 @@
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Jinghu's three gates connect Haodu (GJ 566A) to two deeper corridor branches, making it one of the east_reach's quiet multipliers: a system that adds more commercial throughput than it produces, because its junction value redistributes economic activity from the hub to systems that would otherwise be less accessible. The name — Chinese for "mirror lake," chosen by the founding community for a still-water feature of the habitable moon's largest basin — has become somewhat ironic over time. Jinghu does not reflect Haodu so much as route around it, giving traders and freight operators an alternative path when Haodu's congested gate schedule creates delays.
|
||||
|
||||
The primary economic base is service infrastructure for transit: bonded warehousing, gate ferry maintenance, crew rotation facilities, and short-term cargo insurance adjudication. None of these activities require large populations, but all of them require competent ones, and Jinghu has developed a mid-reach reputation for technical reliability that the Yongli Combine's logistics analysts reference by name when calculating corridor routing efficiency.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The founding community was Chinese-heritage — a wave_2 cooperative that came to the M4 dwarf because the gate survey showed junction potential that a larger corporate entity had not yet claimed. They got there before the Yongli Combine's predecessor entities consolidated the inner corridor, and they negotiated their integration terms from a position of established occupancy rather than corporate dependency. The distinction matters: Jinghu is Combine-adjacent, not Combine-owned. The founding cooperative's descendants hold the primary commercial and residential seats on the Administrative Council, and the Combine's transit affiliate operates here under a service contract rather than a governance arrangement.
|
||||
|
||||
The Lattice Commission has a standard junction office. Gate Corporation runs a full maintenance team. Neither has significant influence on local governance — the administrative council is competent and the Commission's compliance requirements are met without friction, which means there is nothing for the Commission to push on.
|
||||
|
||||
The Assembly's authority at Jinghu is institutional and intermittent: a delegate visits on the standard circuit, assessments are paid, and the council participates in Assembly procedural processes when they have a direct commercial interest. The founding cooperative's persistent governance structure means Jinghu has never had the governance instability that invites more intensive Assembly engagement.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What the Administrative Council does not discuss publicly: the terms of the gate scheduling agreement with Haodu.
|
||||
|
||||
When Haodu's congestion problems became commercially significant — approximately eighty years ago — Jinghu negotiated a gate scheduling coordination agreement that gave Jinghu's transit operators preferential slot access on two of Haodu's gate sequences in exchange for guaranteed throughput commitments. The agreement is commercially valid. What it effectively does is allow Jinghu's transit operators to route around Haodu's public queue, which increases Jinghu's commercial throughput at the cost of making Haodu's public-access slot allocation marginally less predictable. The residents of systems that route through Haodu and encounter unexplained slot delays would not immediately identify Jinghu's preferential access as a contributing factor. The Combine's logistics analysts have identified it. They have not raised it with the Commission, because the Combine's own transit affiliate also benefits from the agreement.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
Jinghu's transit operators have had preferential gate scheduling access at Haodu for eighty years under an agreement that both parties treat as commercially confidential, and the unexplained queue delays that smaller corridor operators encounter at Haodu can be traced, with sufficient documentation, back to that arrangement.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
`wave_2` at `hop 5` as a `junction` is consistent with an early-claimed corridor position where the gate survey value was recognized before corporate consolidation could foreclose independent settlement. M4 star classification matches the stub. Chinese heritage founding community and aspirational natural-feature naming (mirror lake) fits Section 6.3 conventions and east_reach corridor norms. The Combine-adjacent-but-not-owned governance dynamic is a meaningful distinction from Haodu's fully Combine-integrated structure — realistic for a system founded just before the Combine's wave_3 consolidation reached this corridor branch.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_098
|
||||
**GJ 667C** | M-type | east_reach
|
||||
# Gliese 667
|
||||
**GJ 667C** | M2.5 · east_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -15,19 +15,32 @@
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Gliese 667 imports almost everything. Wave_5 activation means the settlement is recent enough that its productive base is still being established, and the dead_end topology means all imports and exports flow through the single gate connection to Shenwei (GJ 3379). The relationship with Shenwei is therefore not just geographic but existential: every supply shipment, every outbound research package, every personnel rotation passes through Shenwei's administrative systems. The Gliese 667 research consortium negotiated a transit agreement with Shenwei's administrative council before the settlement was activated, and that agreement's terms are the most consequential document in the new system's founding archive.
|
||||
|
||||
What Gliese 667 produces — or intends to produce — is data. The system's multiple rocky planets in or near the habitable zone generated significant pre-settlement astronomical attention when the gate survey confirmed what the remote observations had suggested. The founding consortium is a research partnership of Veil Institute affiliates and independent planetary scientists who want access to those planets as study subjects. Whether this produces commercially valuable findings within a timeframe that justifies the settlement costs is an open question that the consortium's five-year review is scheduled to address.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The decision to keep the scientific catalog name was made by the founding consortium over the objection of one faction that wanted to honor a founding benefactor. The catalog-name faction won on the argument that the system was being settled specifically because of its pre-settlement scientific reputation, and that reputation was attached to the Gliese 667 designation in the scientific literature. Changing the name would, they argued, make it harder for researchers elsewhere in the Reach to find the community's publications in the literature networks. This argument was sound enough that even the faction that wanted the benefactor honored conceded it.
|
||||
|
||||
The settlement is governed by a research council — five elected representatives, one from each founding partner institution. The Veil Institute's representative holds structural weight because the Institute's funding constitutes the largest single share of the settlement's operating budget. This creates a governance dynamic the other partners are aware of and manage carefully: the Institute's representative does not vote disproportionately, but the Institute's budget share means its representative's concerns receive proportionate weight in deliberations that technically require consensus.
|
||||
|
||||
No Lattice Commission office. No Assembly presence beyond a registration filing. Wave_5 systems at dead_end topology exist at the outer edge of institutional reach.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What the founding consortium does not discuss publicly: the relationship between Gliese 667's founding and Shenwei's classified wave_1 anomaly report.
|
||||
|
||||
Shenwei (GJ 3379) holds a classified wave_1 anomaly report describing a geological formation on one of the system's outer bodies that the original survey team considered inconsistent with natural formation processes. That report was filed against Shenwei but the outer body in question is at the edge of the survey team's mapping range — within what subsequent charting confirmed is the Gliese 667 system's gravitational neighborhood. At least one member of the Gliese 667 founding consortium is a Veil Institute affiliate who has read the Shenwei anomaly report summary through Institute archive access. Whether the settlement was partially motivated by interest in that anomaly is a question that member has not answered in any forum accessible to the other founders.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
Gliese 667 was settled by researchers with legitimate scientific reasons to be here, and at least one of those researchers has access to a classified wave_1 document describing an anomaly in this system's neighborhood that has never been publicly discussed.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
`wave_5` at `hop 6` as a `dead_end` with 1 aperture is consistent with recent research-motivated settlement — the system's pre-settlement astronomical reputation would attract a dedicated founding consortium in the Activation Edge wave. M2.5 classification matches the stub. Keeping the scientific catalog designation is a Section 6.3 functional-designation exception, here justified by research community norms rather than commercial logistics (as in Relay 7) — the system's identity is its astronomical designation in the literature. The Veil Institute connection threads back to Shenwei's established faction notes.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# p Eridani
|
||||
**GJ 66A** | M-type | east_reach
|
||||
**GJ 66A** | K2 V · east_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -15,19 +15,32 @@
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
p Eridani is a junction that kept its catalog designation because no one could agree on anything else. The system was settled in wave_2 by a consortium of three distinct founding groups whose interests aligned well enough to establish a gate facility but not well enough to agree on a name. By the time any individual group had accumulated enough local standing to impose a preference, two generations had passed and the catalog designation had become the community's de facto identity. Later attempts to hold formal renaming votes have all produced the same outcome: the vote passes for a new name, the name is used in official documents for a few years, and then the community drifts back to p Eridani because that is what the gate charts say and gate charts are what ships use.
|
||||
|
||||
The three gates connect outward toward Novaya Zarya (GJ 137) on one branch, down to Korhonen (GJ 412B) on the dead_end extraction branch, and toward GJ 1125 on a spur that reaches deeper into the outer corridor. That last connection defines p Eridani's primary economic function: it is the sole external link for Korhonen's ore shipments, which gives p Eridani's freight brokers and transit operators structural leverage over the extraction system's pricing that has been a source of resentment in Korhonen for three generations. p Eridani's logistics operators regard this as commercial arithmetic. Korhonen's council describes it using different terms.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The three founding groups — a Finnish mineral survey cooperative, a Chinese-heritage transit infrastructure firm, and a mixed-heritage agricultural community that underestimated how little agricultural potential the K2 star's habitable zone would offer — have long since blended into a general local population. Their descendants hold no formal privileged positions and there are no founding-family governance provisions. What persists is a cultural pattern of factional negotiation: p Eridani's governance by elected committee has always featured competing blocs, and the community has developed elaborate informal norms for managing those competitions that are deeply opaque to outsiders.
|
||||
|
||||
The Lattice Commission junction office is substantial — three-gate systems generate enough commercial complexity to justify it. Gate Corporation maintains a standard junction team. Neither has leverage over the committee's internal politics; both operate within the community's external compliance requirements without friction because p Eridani's commercial operators understand that friction with the Commission creates documentation problems downstream.
|
||||
|
||||
The Assembly's presence is institutional. The committee sends delegates, pays assessments, and treats Assembly governance frameworks as background law rather than active management.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What p Eridani's committee does not discuss in public session: the Korhonen transit fee schedule.
|
||||
|
||||
The fee schedule for Korhonen-originating freight has been revised upward three times in the last forty years, each time justified by infrastructure maintenance costs that the committee's records show are real but which independent analysis would reveal to be a fraction of the fee increase. The gap between infrastructure cost and fee revenue flows into p Eridani's general operating fund, where it is not labeled as a markup on Korhonen's commercial isolation. Korhonen's council has raised the issue in formal correspondence. p Eridani's committee has responded with detailed infrastructure cost documentation that is accurate and incomplete. The Assembly framework provides a dispute mechanism that would require both parties to open their full accounts to Commission review, which neither party has invoked, apparently for different reasons.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
p Eridani has been overcharging Korhonen's freight operators for forty years under documentation that is accurate enough to survive a surface review and incomplete enough that a full Commission audit would raise uncomfortable questions about what the committee's infrastructure fund is actually paying for.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
`wave_2` at `hop 5` as a `K2 V junction` with 3 apertures is consistent with an early-settled corridor position where gate infrastructure was established before commercial consolidation gave any single entity naming authority. The catalog designation as community name is a Section 6.3 event-category naming exception — named after what happened (no one could agree) rather than a heritage or founder attribution. The Finnish/Chinese/mixed founding blend produces a cross-corridor heritage exception consistent with the cultural framework's guidance that inner-hop junctions are among the most demographically mixed systems in the corridor.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_068
|
||||
**GJ 784** | binary-type | east_reach
|
||||
# Kovács Loop
|
||||
**GJ 784** | M0V · east_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -15,19 +15,32 @@
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
The "Loop" in Kovács Loop is topological self-description. The two gates connect to Taishan (GJ 682) and GJ 1128, positioning the system on a corridor path that maintains consistent through-traffic without the volume of a full junction node. Endre Kovács filed the original development license knowing this — his assessment of the gate survey data was explicitly framed in terms of transit routing value, and the settlement he founded was designed from the beginning around the support infrastructure that loop-path traffic requires.
|
||||
|
||||
Kovács Loop's economic base is industrial maintenance and transit support: machine shop services for gate ferry equipment, fuel processing, crew accommodation facilities, and the kind of practical engineering work that keeps corridor transit infrastructure functional between major service stops. The M0V primary is a reliable, stable red dwarf that suits industrial operations — no dramatic flare cycles, consistent energy output, and a habitable moon in the inner zone that Kovács's founding community converted to industrial use within two generations. The loop position means the system sees consistent through-traffic without being a traffic node, which has produced a steady-state economy that has not grown substantially since wave_3 but has also not contracted.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
Endre Kovács was Hungarian-heritage, part of the wave_2 frontier push by central European industrial communities that were following gate survey data rather than cultural corridor logic. He was a mechanical engineer by training, practical in orientation, and his founding community reflected that: forty-three families, most with industrial or technical backgrounds, chosen for their ability to build and maintain rather than their cultural or political compatibility with any established corridor identity.
|
||||
|
||||
The Kovács family's descendants are still in the system but no longer hold any formal governance advantage. The community is governed by a workers' cooperative structure that evolved from the founding period's informal labor-allocation arrangements — the kind of governance that emerges when a small industrial community with no external oversight organizes itself around practical necessity. Decisions are made by assembly when they matter, and by whoever is actually present when they do not.
|
||||
|
||||
The Assembly's presence is nominal. The community is compliant because compliance costs nothing significant at this distance and the transit operators who use Kovács Loop's services prefer to operate in Assembly-compliant systems for documentation purposes. Gate Corporation maintains a minimal service contract for the two gates.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What the community does not discuss with outside visitors: the founding population's departure record.
|
||||
|
||||
Endre Kovács's founding license listed a specific founding community that was vetted and approved through the wave_2 application process. What the license does not mention, and what the community's internal archive documents but does not publicize, is that Kovács recruited his founding community specifically from central European industrial workers who had been terminated or displaced by Syndic corporate restructuring in the inner corridor. His argument to them was straightforward: the Syndics will not follow you to hop 6, and what you build at hop 6 is yours. Several members of the founding community had active disputes with inner-corridor corporate entities at the time of departure. Some of those disputes have never been formally resolved. Whether any of those corporate entities have institutional successors who would take interest in the founding archive is something the community's administrators think about occasionally.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
Kovács Loop's founding population was drawn specifically from industrial workers with unresolved disputes against inner-corridor Syndic entities, and Endre Kovács's founding archive contains documentation that some of those entities' successor organizations would find inconvenient.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
`wave_2` at `hop 6` as a `loop_member` with 2 apertures is consistent with early-settled industrial waystation that became part of the corridor loop as the Taishan junction developed. M0V classification matches the stub. Hungarian founder surname plus "Loop" topological descriptor is a Section 6.3 category that combines founding-figure attribution with functional/topological self-description — a naming pattern that fits the founder's practical character. Central European heritage in the east_reach is a cross-corridor exception of the Early Arrival type: the founder followed gate survey logic independent of cultural corridor alignment.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# PLACEHOLDER_234
|
||||
**GJ 908** | K-type | east_reach
|
||||
# Thornfield Station
|
||||
**GJ 908** | M2V · east_reach
|
||||
|
||||
---
|
||||
|
||||
@@ -15,19 +15,32 @@
|
||||
---
|
||||
|
||||
## Supply Dependency
|
||||
<!-- Required for manufacturing/transit_logistics base and narrative_notable systems -->
|
||||
|
||||
Thornfield Station's single gate connects to Binh Trang (GJ 17), making Binh Trang the only commercial lifeline for a community that has been self-sufficient by necessity and suspicious of supply-chain dependency by inclination. The "Station" modifier in the name dates to the founding period, when the community anticipated growth that never came — it was intended to distinguish this initial settlement from future expansion sites. There are no other settlements. The Station is all there is.
|
||||
|
||||
The habitable body is marginal: slightly low gravity, a thin but breathable atmosphere, and surface conditions that require climate management infrastructure for comfortable habitation. Agriculture is subsistence-level with modest surpluses in two growing seasons; there is extractable mineralization but not at commercial quantities. What Thornfield exports is primarily specialist labor — residents who develop technical skills locally and contract out to corridor systems for defined periods, then return. This pattern has produced a community with disproportionately high technical competency relative to its economic output, and a persistent culture of individual return: you can leave, but you come back.
|
||||
|
||||
## Faction Notes
|
||||
<!-- Significant local factions not covered by standard columns -->
|
||||
|
||||
The Thornfield family are documented wave_2 founders — James Thornfield and his extended family group held the original development license. James Thornfield was English-heritage, a structural engineer who took a frontier development license on grounds that the M2V star's habitable zone offered more long-term potential than the surveys suggested. He was not wrong to see potential, but he was optimistic about what "potential" could be built into in one generation. The family's descendants remain on the council as a founding-heritage presence but do not hold disproportionate authority — the community is small enough that everyone knows everyone, and governance by formal council is somewhat ornamental over informal community consensus.
|
||||
|
||||
No Lattice Commission office. No Gate Corporation full team — a rotating maintenance contractor handles the single gate on a quarterly service schedule. The Assembly knows Thornfield Station exists because the development license was registered in wave_2, but the relationship since then has been a registration record and an annual self-reported compliance filing that no one at the Assembly has reviewed in detail in living memory.
|
||||
|
||||
The Guardians of Autonomy have a theoretical presence in the sense that several residents identify with the organization's philosophy. There is no chapter structure. The philosophy is ambient.
|
||||
|
||||
## Silence Topic
|
||||
<!-- Required for narrative_notable and Institutional Core / Diplomatic Periphery zones -->
|
||||
|
||||
What Thornfield Station does not discuss with outside visitors: the reason for the original community's size.
|
||||
|
||||
The wave_2 development license was filed for a much larger founding group than arrived. The original application listed 847 settlers. The actual founding population was 312. The discrepancy has never been formally explained in any document accessible outside the community's own archive. Local oral history attributes it to a last-minute decision by a large faction of the licensed group to redirect to a different development opportunity that opened unexpectedly. Whether that explanation is complete or partial is not a question the council's archive makes easy to answer. The practical consequence — a community permanently smaller than its infrastructure was designed to support — is visible in the founding period buildings, which have more capacity than Thornfield's current population fills.
|
||||
|
||||
## Narrative Hook
|
||||
<!-- Required if narrative_notable = true. One sentence. -->
|
||||
|
||||
Thornfield Station's original development license listed two and a half times the settlers who actually arrived, and the community has been living in infrastructure designed for a population it never had for three hundred years without ever providing a complete official explanation for why.
|
||||
|
||||
## Calibration Note
|
||||
<!-- Unusual column combinations requiring justification -->
|
||||
|
||||
`wave_2` as a `dead_end` with one gate is consistent with an early-settled marginal system where the founding ambition exceeded the conditions that could support it. Note: the READ-ONLY hop distance field shows `5`, but the system's sole gate connects to Binh Trang (GJ 17) at hop 6 — a dead_end spur off a hop-6 junction should be hop 7. This is a data anomaly in the star-map generation; the narrative treats the system as deep-corridor consistent with its actual network position. M2V classification matches the stub. English founder surname plus "Station" modifier is a Section 6.3 category that falls between founding-figure attribution and aspirational naming — the Thornfield surname establishes heritage, and "Station" marks the founding expectation of growth. The cross-corridor English heritage in the east_reach is a legitimate exception: frontier development licenses in wave_2 were awarded to individuals regardless of corridor cultural stream, and an individual English founder at hop 5 in the east_reach is structurally explained by the license system rather than migration patterns.
|
||||
|
||||
## Topology
|
||||
<!-- READ-ONLY — regenerated from star-map.json edges -->
|
||||
|
||||
Reference in New Issue
Block a user