Skip to content

Browse by version

Most docs describe what the game should do at launch — the Release target. Some describe what's already shipped, with two flavors: Live (verified through gameplay) and Current (shipped to the code, not yet gameplay-verified). The rest sketch ideas for after launch — Future. Every page in this repo is tagged with one or more of those four lanes so you can filter the docset to whichever audience matches you right now.

The mode switcher in the topbar (top-right, next to search and the dark/light toggle) controls the filter. Sections in your chosen mode show; others fade out. Pages with no content in your mode dim in the left nav and surface an empty-state callout if you visit them. Print and search ignore the filter — they always show everything.

The four lanes

  • Live

    Shipped AND verified through gameplay by a maintainer within the last 90 days, with the observation recorded in FINDINGS.md. Read this when you want to know what you can play right now and trust to behave as written.

  • Current

    Shipped on main. The code path is reachable end-to-end, but gameplay verification is absent or stale. Read this when answering "what's in the build today" — the default for engineers debugging current behavior.

  • Release

    Planned for the 1.0 launch. Not yet shipped, but committed via a non-superseded Accepted ADR, the launch roadmap, or an explicit launch-commitment line. Design is settled. Read this when scoping launch work.

  • Future

    Post-launch, aspirational, exploratory, or design-in-flight. No committed delivery slot. Read this when thinking about the long-term vision rather than the launch critical path.

How the filter works

  • Mode selection is cumulative. Picking Current shows Live + Current. Picking Release shows Live + Current + Release. Picking Future shows everything. Picking Live shows only Live.
  • Pages may carry one to three of the four tags. A page with all four would mix too many audiences and is split instead.
  • Inside a page, sections whose maturity diverges from the page's primary lane carry an inline marker. Unmarked prose inherits the page's frontmatter tags.
  • Mode persists per-reader in localStorage. A ?mode=… URL parameter overrides per-visit without writing to storage. Append ?show=all to any URL to bypass the filter for one page view.

For the full vocabulary rules, see ADR-0071. For author-facing tagging rules and the per-doc audit checklist, see CONTRIBUTING.md. Meta files (this page, README, CONTRIBUTING, GLOSSARY, etc.) carry no tag and are always visible.

Composition with inline status markers

In FEATURES/, four inline status markers indicate code-vs-spec drift at the sentence or bullet granularity:

Marker Meaning
✅ Shipped Implemented and reachable end-to-end.
🚧 Partial Some pieces shipped, some still missing.
📐 Design-only Documented intent; no code yet.
🐛 Bug Implemented, but live behaviour diverges from the spec.

The version tags describe release timeline; the status markers describe implementation drift. They are orthogonal but constrained — Future cannot mix with ✅/🚧/🐛, and Live/Current cannot mix with 📐. The linter enforces the matrix.

Index

Every tagged page is listed below, grouped by tag. The list is auto-generated by the MkDocs Material tags plugin; do not hand-edit.

Current

Future

Release