settled-reach/wiki/star-systems/GJ-866A/index.md

EZ Aqr

GJ 866A | M-type | east_reach

---

System Profile

Star	M5 e · 11.1 ly
Bodies	0 habitable · 2 inhabited
Gates	2 aperture · through_route
Settlement	wave_5
Industries	hospitality, financial_services, legal_services
Exports	financial_services
Imports	processed_food, electronics, consumer_goods, medical_goods, fusion_fuel, refined_metals
Population	—

---

Supply Dependency

EZ Aqr produces almost nothing and exports that fact as a service. It is a Gate Corporation monitoring waypoint that became a permanent settlement only after enough transit personnel, maintenance contractors, and support staff had been stationed here long enough to stop thinking of themselves as temporary. The system's economic output is entirely transit-adjacent: refueling, minor vessel maintenance, gate diagnostic services, and the hospitality infrastructure that grows wherever people wait between ships.

What EZ Aqr imports is everything else. Food, fabricated goods, discretionary equipment — all comes through on the same gate traffic the system monitors. The through_route topology keeps it viable: one gate faces the inner corridor toward GJ 1221, one faces outward toward Bridgepoint. Neither direction is optional. The system's institutional dependence on Gate Corporation is nearly total, which is understood by everyone here and discussed by no one.

Faction Notes

Gate Corporation is not merely present at EZ Aqr — it is the system's founding institution, its largest employer, its infrastructure owner, and the effective government for the majority of residents who live in company-managed habitat modules. The nominal Assembly compliance framework applies, but the Assembly's practical authority here is mediated entirely through Gate Corp's institutional cooperation, which is reliable but conditional. Local governance exists as a transit worker council with consultative authority on habitat conditions and shift scheduling; no one mistakes it for political power.

The settlement's heritage profile is mixed in the way Gate Corporation postings always are: staff drawn from across the Reach with no dominant founding community. There is no cultural corridor identity at EZ Aqr because the system never had a founding population that chose to be here. Residents arrived on contract, stayed past their contracts, and called the result a community. Some second-generation locals have begun the kinds of civic organizing that precede genuine self-governance — a local school collective, a mutual aid fund — but these are very recent and fragile.

Silence Topic

What is not discussed openly: the data archive question.

Gate Corporation's monitoring function at EZ Aqr generates continuous records of transit patterns, cargo manifests, and vessel identification logs for every ship that passes through both gates. This archive is Gate Corp proprietary, reviewed internally, and shared with the Lattice Commission on formal request. The records go back nearly thirty years — the full duration of the monitoring station's operation. Several freight operators transiting the corridor believe the archive contains scheduling anomalies that would, if examined, demonstrate systematic favoritism toward certain cargo handlers at the Yongjin junction. No one has successfully filed a formal access request. Gate Corp's position is that transit monitoring data is operational infrastructure documentation, not commercial records subject to Commission audit. That position has not been tested in Assembly adjudication.

Narrative Hook

Every ship transiting between the core and the east corridor's inner systems passes through EZ Aqr's gate logs, and the thirty-year archive has never been reviewed by any party outside Gate Corporation's own compliance office.

Calibration Note

wave_5 at hop 3 is extremely late for a system this close to Gateway. The explanation is institutional rather than geographic: EZ Aqr was never developed — it was staffed. Gate Corporation classified it as an operational facility rather than a settlement for most of its occupied history, which meant population counts for Assembly settlement-wave tracking were not filed until the resident population exceeded the threshold that triggers mandatory registration. By then the community had been functionally present for two generations. The wave_5 designation reflects bureaucratic acknowledgment, not recent arrival.

The inner rocky body Srok Thmei (Khmer: 'new district') was named by a Khmer-heritage monitoring technician cohort during the station's early years, when body designations were informal and passed around in maintenance shift logs rather than filed with any authority. The name was conventional enough by the time the settlement was formally registered that it went into the founding documentation without challenge. The Robaat station name (possibly Persian origin, possibly a contraction of 'robot' in the operations register's phonetic shorthand — the file is inconclusive) represents the same informal naming period. EZ Aqr's geography was named by the people who happened to be here, not by cultural planners.

Topology

• Hop Distance from Gateway: 3
• Adjacent Systems: GJ 1221, GJ 53A

Celestial Bodies

Orbit	ID	Name	Type	Inhabited	Pop	Mass	Gravity	Year (d)	Day (h)	Atmo	Biome	Hydro	Economy	Settlement	Industrial
1	GJ866Ab	—	planet	no	—	terrestrial	0.18g	6	144.0	none	barren	none	—	—	—
2	GJ866Ac	Srok Thmei	planet	no	—	terrestrial	0.30g	20	480.0	none	barren	none	—	—	—
3	GJ866Ad	—	planet	no	—	terrestrial	0.40g	55	1320.0	thin	barren	none	—	—	—
4	GJ866Ae	—	planet	no	—	terrestrial	0.32g	150	14.0	none	frozen	ice	—	—	—
5	GJ866Af	—	planet	no	—	terrestrial	0.25g	400	17.0	none	frozen	none	—	—	—
6	GJ866A-oort	—	oort_cloud	no	—	—	—	—	—	—	—	—	—	—	—

Stations & Facilities

ID	Name	Type	Orbits	Population	Economy	Governance	Docking	Gate	Districts
GJ866A-oort-S1	Horizon Station	horizon	GJ866A-oort	—	transit	—	standard	yes	1
GJ866Ad-S1	Robaat	commercial	GJ866Ad	45K	transit	—	standard	no	1