Adds Bodies and Population rows to System Profile tables across all 301 star-system wiki pages. Adds Industries, Exports, and Imports economic profile rows derived from systems.db economic_base + body type + topology. Includes 9 body/station name changes from cultural diversity remediation. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
8.0 KiB
Eisentor
GJ 3454 | M-type | west_reach
System Profile
| Star | m · 20.1 ly |
| Bodies | 0 habitable · 3 inhabited |
| Gates | 4 aperture · junction |
| Settlement | unsettled |
| Industries | fusion_fuel, metallic_ore, financial_services, insurance, legal_services |
| Exports | financial_services, legal_services |
| Imports | processed_food, electronics, consumer_goods, medical_goods, refined_metals, heavy_equipment |
| Population | — |
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.
Celestial Bodies
| Orbit | ID | Name | Type | Inhabited | Pop | Mass | Gravity | Year (d) | Day (h) | Atmo | Biome | Hydro | Economy | Settlement | Industrial |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | GJ3454b |
— | planet | no | — | terrestrial | 0.31g | 6 | 148.8 | none | barren | — | — | — | — |
| 2 | GJ3454c |
— | planet | no | — | terrestrial | 0.56g | 38 | 912.0 | thin | cold_arid | — | — | — | — |
| 3 | GJ3454-belt |
— | asteroid_belt | no | — | — | — | — | — | — | — | — | — | — | — |
| 4 | GJ3454d |
— | planet | no | — | terrestrial | 0.44g | 160 | 21.8 | trace | frozen | — | — | — | — |
| 5 | GJ3454e |
— | gas_giant | no | — | — | — | 540 | 12.2 | gas_giant | — | — | — | — | — |
| ↳ 5.1 | GJ3454e-m1 |
— | moon | no | — | dwarf | 0.12g | 5 | 129.6 | trace | frozen | — | — | — | — |
| ↳ 5.2 | GJ3454e-m2 |
— | moon | no | — | dwarf | 0.08g | 12 | 283.2 | — | barren | — | — | — | — |
| 6 | GJ3454f |
— | planet | no | — | terrestrial | 0.36g | 1600 | 31.4 | trace | frozen | ice | — | — | — |
| 7 | GJ3454g |
— | planet | no | — | dwarf | 0.11g | 4200 | 26.8 | none | frozen | ice | — | — | — |
| 8 | GJ3454h |
— | planet | no | — | dwarf | 0.10g | 9400 | 21.6 | none | frozen | ice | — | — | — |
| 9 | GJ3454-oort |
— | oort_cloud | no | — | — | — | — | — | — | — | — | — | — | — |
Stations & Facilities
| ID | Name | Type | Orbits | Population | Economy | Governance | Docking | Gate | Districts |
|---|---|---|---|---|---|---|---|---|---|
GJ3454-oort-S1 |
Eisentor Horizon | horizon | GJ3454-oort |
4K | transit | — | major | yes | 1 |
GJ3454e-S1 |
Eisenhof | commercial | GJ3454e |
8K | transit | — | major | no | 1 |
GJ3454e-S2 |
Leitwerk | industrial | GJ3454e |
2K | transit | — | major | no | 1 |
Topology
- Hop Distance from Gateway: 6
- Adjacent Systems: GJ 357, GJ 832, GJ 505A, GJ 1116B