jpmschweitzerandClaude Opus 4.6
f3cef86e5f
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 <noreply@anthropic.com>
4.6 KiB
Rana
GJ 150 | K0IV subgiant | west_reach
System Profile
| Star | K0IV · 29.5 ly |
| Gates | 3 aperture · junction |
| Settlement | wave_2 |
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
- Hop Distance from Gateway: 6
- Adjacent Systems: GJ 370, GJ 832, GJ 320