Files
settled-reach/wiki/star-systems/GJ-1116B/index.md
T
jpmschweitzerandClaude Opus 4.6 199770ee41 data(wiki): add Bodies/Population rows + economic profiles to 301 systems (#790, #781)
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>
2026-04-06 16:03:56 +02:00

9.9 KiB

Kraków Junction

GJ 1116B | M-type | west_reach


System Profile

Star m · 17.0 ly
Bodies 0 habitable · 4 inhabited
Gates 3 aperture · junction
Settlement wave_3
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, chemicals
Population —

Supply Dependency

Kraków Junction is named for a Polish city — one of Central Europe's oldest continuously inhabited urban centers, a place that survived conquest, partition, and occupation by repeatedly becoming indispensable to whatever power controlled the surrounding territory. The Wave 3 founders chose the name deliberately. They were Polish and Czech-heritage settlers who had tracked the gate topology carefully before committing to this position, recognized that a three-aperture junction at hop 5 connecting GJ 3454, GJ 631, and GJ 896A would carry traffic regardless of which corridor or faction held the systems around it, and named their home after a city that had made the same calculation on Earth.

The calculation has held. Kraków Junction sits at the intersection of two distinct west_reach branch paths. Traffic moving between the inner corridor's deep west connections and the outer systems beyond GJ 3454 passes through here or routes around a significant detour. Goods moving between the GJ 631 branch and either of the other two paths require Kraków Junction as an intermediate. The system is not as large as Hansestadt and makes no claim to match it; it is a mid-corridor junction that handles the volume its topology generates and makes a stable economy from it.

The export profile is transit services: bunkering, warehousing, transit documentation, crew services. The system imports food from the inner corridor and has no significant production exports. At hop 5, this is a sustainable model; further out, it would be precarious without the triple-aperture traffic volume supporting the service economy.

Faction Notes

The Central European founding character — Polish, Czech, and a smaller Hungarian stream — is more visible at Kraków Junction than corridor-dominant Germanic heritage because the founders were settlers of deliberate choice who brought institutional structures from their heritage rather than adopting the corridor's emerging governance forms. The result is a civic culture with a specific character: formal public debate, strong municipal governance traditions, a preference for decisions made in front of audiences rather than in back rooms. The Kraków Council — a deliberate reference to the city's historical governance tradition — is the system's primary civic body, and its sessions are public, recorded, and genuinely attended by residents in a way that is unusual for a system of this size.

The Polish and Czech cultural heritage remains visible in the naming of districts, streets, and civic buildings, in the language conventions used in formal governance sessions, and in the food culture that has persisted through three hundred years of mixed-heritage arrivals. The heritage shows most clearly in the institutional architecture of governance rather than in the daily cultural texture, because governance is where deliberate founding choices leave the longest marks.

Gate Corporation has a junction-appropriate operational base here — not as large as Kapteyn's Star's, but significantly larger than a loop-member presence. The Gate Corp staff number in the low hundreds and have their own residential district that the Kraków Council administers under a protocol negotiated with Gate Corp's regional management. The protocol has been revised three times; each revision involved the public sessions that characterize the Council's governance style, which Gate Corp's regional management has found alternately admirable and exhausting.

MVG's supply chain reaches this far through a logistics contract with the system's warehousing cooperative. The contract covers forwarding services — MVG goods in transit, not locally produced materials — and gives MVG preferential routing through Kraków Junction's Gate Corp-managed scheduling queue. The Council debated this contract publicly for eight months before approving it. The vote was close.

The Assembly's presence at hop 5, junction topology, is institutional — stronger than at dead-end systems at comparable distance, weaker than at inner-orbit junctions. An Assembly delegate maintains a permanent office here, which is unusual for this hop depth. The delegate's presence reflects the Assembly's recognition that Kraków Junction's traffic volume makes it worth maintaining an institutional footprint. The Kraków Council uses the delegate's presence as a resource rather than resenting it — they are reliably the first west_reach council to formally raise corridor-wide economic grievances through Assembly channels when other systems are still deciding whether to complain at all.

Silence Topic

What Kraków Junction does not examine in its otherwise open governance: the terms of the routing priority agreement within the MVG forwarding contract, and specifically how those terms interact with the independent operators who move goods through the junction.

The MVG forwarding contract includes a scheduling priority provision that was approved during the eight-month public debate under the framing of "preferential commercial routing." The specific priority structure — which gives MVG-affiliated freight priority in the Gate Corp scheduling queue over independent operators with equivalent or higher volumes — was presented in summary form during the public debate rather than in the full contract language. The Council voted on the summary. Several independent operators who transit regularly through Kraków Junction have since reported queue delays that are consistent with the priority provision's operation but inconsistent with the transit timeline projections the Council used in its approval vote. Whether the Council was given inaccurate projections, or whether the Council gave the public an inaccurate summary, is a question that the governance transparency traditions here make more awkward to suppress than it would be elsewhere, which is why it has not been suppressed so much as deferred, repeatedly, through procedural mechanisms that the Council's own rules provide for.

Narrative Hook

The junction that named itself after a city that survived by being indispensable approved an MVG routing contract in public, and the public did not receive the part of the contract that explains why the independent operators have been waiting longer ever since.

Calibration Note

Polish/Czech/Hungarian founding heritage is consistent with the Central European stream described in the west_reach corridor framework — a cultural presence within the broader Germanic tendency that represents the eastern flank of Central European migration. The naming of the system after Kraków is a direct Earth-geography transplant, which is appropriate for a Wave 3 founding population that was deliberate about its cultural identity and institutional inheritance. "Junction" as a modifier is functional and honest — the system's significance is topological, and the founders knew it. The small M-type classification (lowercase "m" in the catalog, consistent with a dim M-dwarf) is unremarkable; the system's significance is entirely structural. wave_3 settlement with junction topology reflects deliberate early siting by settlers who read the gate charts and chose their position strategically.

Celestial Bodies

Orbit ID Name Type Inhabited Pop Mass Gravity Year (d) Day (h) Atmo Biome Hydro Economy Settlement Industrial
1 GJ1116Bb — planet no — terrestrial 0.32g 6 153.6 none barren — — — —
2 GJ1116Bc Rynek planet yes 22M terrestrial 0.86g 45 1080.0 standard temperate_terminator liquid_water transit urban_concentrated logistics
3 GJ1116B-belt — asteroid_belt no — — — — — — — — — — —
4 GJ1116Bd — planet no — terrestrial 0.46g 220 22.4 thin frozen — — — —
5 GJ1116Be — gas_giant no — — — 680 12.4 gas_giant — — — — —
↳ 5.1 GJ1116Be-m1 — moon no — dwarf 0.12g 5 124.8 trace frozen — — — —
↳ 5.2 GJ1116Be-m2 — moon no — dwarf 0.08g 11 273.6 — barren — — — —
6 GJ1116Bf — planet no — terrestrial 0.37g 1800 31.4 trace frozen ice — — —
7 GJ1116Bg — planet no — terrestrial 0.28g 4600 39.8 trace frozen ice — — —
8 GJ1116Bh — planet no — dwarf 0.11g 10200 26.8 none frozen ice — — —
9 GJ1116B-oort — oort_cloud no — — — — — — — — — — —

Stations & Facilities

ID Name Type Orbits Population Economy Governance Docking Gate Districts
GJ1116B-oort-S1 Kraków Junction Horizon horizon GJ1116B-oort 1K transit — major yes 1
GJ1116Bc-S1 Brama commercial GJ1116Bc 4K transit — major no 1
GJ1116Bc-S2 Komora commercial GJ1116Bc 1K commercial — standard no 1

Topology

  • Hop Distance from Gateway: 5
  • Adjacent Systems: GJ 3454, GJ 631, GJ 896A