Quartz 5

README

3 min read

Sectors – README

This directory contains canonical documentation for sectors: named interstellar regions that group multiple star systems (and the states within them). Use the template in this directory for all entries.

Scope

A sector file is a regional index and summary. It groups existing SYSTEM_*.md and STATE_*.md entries under a shared region, notes which power(s) hold sway there, and gives a short account of the region’s history and strategic situation. It is not the canonical source for system or state details — those remain authoritative in their own files. If a sector listing conflicts with a SYSTEM_*.md or STATE_*.md file, the individual file wins and the sector listing should be corrected.

Sector names are already used informally across the canon (the Region field in canon/systems/*.md, references in canon/timelines/*.md and elsewhere). This directory is where those names become first-class entries, so boundaries stop drifting between documents.

Naming and IDs

  • File: SECTOR_<ID>.md, ID in SCREAMING_SNAKE_CASE derived from the sector’s working name (e.g. SECTOR_CERUNNOS_HORN, SECTOR_RIGS_TRAVERSE).
  • Reuse the exact same name in the Region field of any SYSTEM_*.md that belongs to the sector, so the two stay cross-referenceable. If a sector is renamed, update those Region fields too.
  • Sectors are administrative/map groupings, not political entities — a sector can contain multiple unrelated or hostile states, and a state’s territory does not need to respect sector lines. Keep Major Powers descriptive, not a claim of ownership over the sector itself.

Known Sectors (draft registry)

Names already in use elsewhere in canon, not yet formalized as SECTOR_*.md files. Use this as a checklist when transferring the map; update a row’s status once its file exists.

SectorReferenced inStatus
Róg CerunnosaSYSTEM_AKRAS, SYSTEM_ANANN, SYSTEM_ARTALAN, SYSTEM_JANUS, SYSTEM_NEW_ULSTER, SYSTEM_NILUS, SYSTEM_QUELOZ, SYSTEM_VALMY, SYSTEM_WO_9605; timelines/CERUNNOS_HORN.mdFormalized: SECTOR_ROG_CERUNNOSA.md
Trawers RigaSYSTEM_APHRODITE, SYSTEM_DESCARTES, SYSTEM_FARINGOR, SYSTEM_HELGRAUM, SYSTEM_KERBEROS, SYSTEM_MELINOE, SYSTEM_NEW_SAKI, SYSTEM_NEW_SPARTA, SYSTEM_NIFLHEIM, SYSTEM_UTGARD, SYSTEM_YGGDRASILFormalized: SECTOR_TRAWERS_RIGA.md
American Sector (Sektor Amerykański)SYSTEM_SARATOGA; timelines/Insectorid_war.mdNot formalized
Sektor Externustimelines/Insectorid_war.mdNot formalized, no systems assigned yet
Sektor Helveticatimelines/Insectorid_war.mdNot formalized, no systems assigned yet
Ultima Thuletimelines/Insectorid_war.mdNot formalized, no systems assigned yet
Nova Acadiatimelines/Insectorid_war.mdNot formalized, no systems assigned yet
Granica Trimurtitimelines/Insectorid_war.md, data/politics/FPC_general.csvNot formalized, no systems assigned yet
Przejście Verkmannatimelines/Insectorid_war.mdNot formalized, no systems assigned yet

Systems already flagged in canon as unassigned to any sector: Mwanzo, Kennedy, Nobel, Nonnus (see canon/timelines/Insectorid_war.md).

Filling a sector file

  1. Copy TEMPLATE.md to SECTOR_<ID>.md.
  2. Add member systems/states as you confirm them against the reference map. A partial file (systems only, no narrative yet) is fine — mark what’s missing rather than guessing.
  3. Update the Region field in the corresponding SYSTEM_*.md files if a sector is added, renamed, or a system’s assignment changes.
  4. Update this file’s registry table once a sector has its own SECTOR_*.md.

Graph View