Phase 1 wiki completion (cultural sweep, GTTR depth, star map popups) + infrastructure refactors (atlas.rs, main.gd, Python tooling). 8 tickets: copy (4), client (2), server (1), ci (1). Cascade dependencies locked: Phase 1→2→3→4→5→6. #693 cancelled (superseded by #704 compositor). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2.2 KiB
Sprint 31: Bedrock — Joint Notes
Goal: Complete Phase 1 wiki content (cultural sweep, GTTR depth, star map popups) and refactor accumulated complexity in atlas.rs, main.gd, and Python tooling.
Sprint Completion Proof
When Sprint 31 is done, you can:
- Click any system in the star map and see a popup with its name, star type, corridor, GTTR excerpt, body count, and adjacent systems
- Read culturally diverse wiki entries — at least 2 subversion entries per top-3 imbalanced cultural groups
- Read GTTR entries for major moons and stations — hub system bodies at hops 1-4 have individual entries
- Run
ruff check tooling/and get a clean pass - Browse atlas.rs and find subcommands in separate module files
- Browse main.gd and find it under 15KB with responsibilities extracted
Phase 1 Context
This sprint advances Phase 1 of the development cascade (epic #746). Phase 1 deliverable: "Implant-ready Godot map of the Reach with click-throughs + wiki/GTTR popups."
What's done: 301/301 systems, body catalogs, star map insert, GTTR coverage What this sprint adds: Star map popups (#780), cultural quality (#766), GTTR depth (#782) What remains after this sprint: Heightmaps (#778), planetary screenshots (#779), economic profiles (#781) — these need design discussion before implementation, targeted for Sprint 32.
Not In Scope
The following are Phase 2-6 work and must NOT be started until Phase 1 is complete:
- Character creation production UI (#694)
- Location-to-culture resolution (#679)
- NPC personality surface area (#621)
- Tycoon starting state design (#615)
- Economic simulation
- Settlement generation
The cascade is enforced in the ticket system: #747 (Phase 2) is blocked by #746 (Phase 1).
Refactor Rationale
The three refactors (#775, #776, #777) are infrastructure work, not feature development. They reduce complexity that compounds every sprint:
atlas.rs(2000+ lines) — every atlas feature adds to a single filemain.gd(28KB) +game_state.gd(19KB) — every client feature touches these- Python tooling (5 files with duplicated DB path logic) — every new script copies the pattern
Doing these now prevents the debt from growing further as Phase 1 content work continues.