Software Overview
Runtime, portal, repository, and content boundaries.
The game runtime is a Godot project. Scenes compose runtime objects and authored spaces, typed scripts own behavior, Godot resources hold serializable definitions and tuning data, and game-ready assets remain separate from editable sources and generated caches.
The development portal is a server-rendered Next.js application backed by PostgreSQL. The database is the working source of truth for live edits. Markdown in site/src/content/docs/ is its deterministic repository mirror and seed surface, with WIKI_INDEX.md at the repository root as the entry point for people and AI agents.
Page maturity uses exactly three states: Stub, In Progress, and Complete. Category progress indicators aggregate those states across the category and all descendants. Display names do not define page relationships; durable category IDs and canonical routes do.
The timeline app stores editable events in PostgreSQL. Each event carries a signed year, optional range, classification, popup copy, and source. Historical, traditional, and authored events remain explicitly distinguishable in both data and presentation.
The production host checks for wiki changes every 30 minutes. When content differs, it exports every live page into the URL-shaped Markdown tree and pushes one mirror commit to main; when nothing differs, it does not commit or contact GitHub beyond checking the branch. This cadence keeps GitHub useful without producing a commit for every keystroke.
Repository boundaries:
game/contains runtime-facing Godot work and game-ready assets.site/src/content/docs/contains the GitHub-readable mirror of live design and production documentation.portal/contains the database-backed working portal.site/public/presentations/contains self-contained presentations.tools/contains project-specific utilities.