jpmschweitzerandClaude Opus 4.7
25eb8bd096
Spring-cleaning accumulated v0.1 vertical-slice residue across the wiki. Scope per Jeroen's pre-decisions on 2026-04-21: - Delete outright: wiki/star-systems/GJ-35/sova/ subtree (5 files + 2 dirs) — v0.1 Station Sova / Transit District content. - Strip example blocks in authoring guides and _templates/ that cited dropped v0.1 NPCs (Kael Davan, Sera Venn, Nils Davan, Devra, Torek, Renn, Pell, Tav, Lera Sessik, Sabel). Replaced with short "v0.1 examples removed — D-122" notes pointing authors to the active NPC roster. - Rewrite canonical-lore references file-by-file: faction pages, technology pages, contraband pages, concepts pages, corp pages that cited v0.1 names/places. Preserve institutional/structural content, drop specific-name citations. - Commission name drift: replace "Concord Commission" and "Assembly Commission" with "the Lattice Commission" (D-193) throughout. - Van Maanen's Star cultural references: the canonical in-game name is Vuurkloof. "Van Maanen's Star" is retained only as an astronomical designation (glossary + GJ-35 Calibration Note). All cultural/system references converted to Vuurkloof across culture-authoring-guide, cultural-generation-guide, founder-gates, and star-system adjacent-system descriptions. - Strip `v0.1` from faction/triangle frontmatter tags (8 files). - wiki/triangles/hub-power.md and wiki/factions/the-ring.md: rewritten using role-name exemplars (Ring Coordinator / Shift Supervisor / THE FRIEND) instead of named v0.1 NPCs. Triangle pattern preserved as a structural reference. Also applies drive-by Commission drift fixes and minor cross-ref updates to canonical corps (gate-corporation, mastroianni-vehicle-group, stalownia-kowalski, prometheus-labs, ferreira-monteiro, vins-de-grand-vide, and 13 others). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
100 lines
3.2 KiB
Markdown
100 lines
3.2 KiB
Markdown
# Wiki Governance
|
|
|
|
**Owner:** Miri (structure and worldbuilding)
|
|
**Contributors:** Anyone on the team, following templates
|
|
|
|
---
|
|
|
|
## Status Lifecycle
|
|
|
|
Every wiki entry has a `status` field in its YAML frontmatter:
|
|
|
|
| Status | Meaning | Who Can Set |
|
|
|--------|---------|-------------|
|
|
| `proposed` | Under consideration, not yet reviewed | Anyone |
|
|
| `draft` | In review, content being refined | Author + reviewer |
|
|
| `canonical` | Confirmed setting truth, safe to reference | Miri or project lead |
|
|
|
|
**Progression:** `proposed` → `draft` → `canonical`
|
|
|
|
**Demotion:** A `canonical` entry can be demoted to `draft` if a decision changes its foundation. Only Miri or the project lead can demote canonical entries.
|
|
|
|
---
|
|
|
|
## Creating New Entries
|
|
|
|
1. Copy the appropriate template from `_templates/`
|
|
2. Fill in the YAML frontmatter (all fields)
|
|
3. Write a concise `description` — one line that captures what makes this entry distinct. This field enables context-aware loading (agents filter by description before loading full files).
|
|
4. Set `status: proposed`
|
|
5. Write the content following the template structure
|
|
6. Submit for review
|
|
|
|
**Templates available:** `star-system`, `station`, `district`, `location`, `character`, `faction`, `technology`, `cultural-group`, `contraband`, `institution`, `species`, `lore`, `concept`, `triangle`
|
|
|
|
---
|
|
|
|
## Directory Rules
|
|
|
|
### Spatial Hierarchy (`star-systems/`)
|
|
|
|
```
|
|
star-systems/
|
|
{system-slug}/
|
|
index.md # System overview
|
|
{station-slug}/
|
|
index.md # Station overview
|
|
{district-slug}/
|
|
index.md # District overview
|
|
{location-slug}.md # Location files (flat within district)
|
|
```
|
|
|
|
- Systems contain stations (nested directories)
|
|
- Stations contain districts (nested directories)
|
|
- Districts contain locations (flat files, no subdirectory)
|
|
- Each directory level has an `index.md` with that entity's overview
|
|
- Slugs are lowercase, hyphenated, unique within their parent
|
|
|
|
### Flat Categories
|
|
|
|
All other categories use flat file structure:
|
|
|
|
```
|
|
{category}/
|
|
{entry-slug}.md
|
|
```
|
|
|
|
No nesting within flat categories. Use `cross_refs` in frontmatter for relationships.
|
|
|
|
---
|
|
|
|
## Cross-Referencing
|
|
|
|
- Use `cross_refs` in YAML frontmatter for machine-readable references (slugs only)
|
|
- Use markdown links in body text for human-readable navigation
|
|
- Use `decision_refs` for links to `decisions/*.md` entries (e.g., `[D-036]`)
|
|
|
|
---
|
|
|
|
## Scale Considerations
|
|
|
|
The spatial hierarchy is designed to scale from a single starting system to 500+ (full game):
|
|
|
|
- Each system is a self-contained directory tree
|
|
- Cross-system references use full slug paths (e.g., `star-systems/{system-slug}/{station-slug}/{district-slug}`)
|
|
- Characters, factions, and other flat categories remain at wiki root — they are not nested per system
|
|
- Characters reference their home district via `home_district` frontmatter field
|
|
|
|
---
|
|
|
|
## Naming Conventions
|
|
|
|
- **File slugs:** lowercase, hyphenated (e.g., `vuurkloof.md`, `freight-exchange.md`)
|
|
- **Directory slugs:** lowercase, hyphenated (e.g., `vuurkloof/`, `{station-slug}/`, `{district-slug}/`)
|
|
- **Canonical IDs:** match content schema format (e.g., `npc:{character-slug}`)
|
|
- **Display names:** title case, as they appear in-game
|
|
|
|
---
|
|
|
|
**Last updated:** 2026-02-13
|