This timeline is a version control surface for the reference. It keeps the Early Access launch and maintenance context together, retains the pre-launch demo records, and places the prologue on its own historical line. A roadmap note can be listed as a future boundary without being expanded into a feature catalogue. Read the date, kind and change columns together before carrying a statement into the systems pages.
The current anchor is the Early Access launch on 10 August 2026, followed by the 11 August maintenance record covering save-data, tutorial, battle-model and stability corrections. Earlier demo records explain the run-up to launch. The prologue context belongs to the separate historical product line. The planned co-op note is kept as a plan marker with no fabricated date.
RECORD 01 / DATED ENTRIES
Launch, maintenance and the pre-launch line
The dated rows keep the current build easy to identify. The launch entry anchors Early Access on 10 August 2026. The maintenance entry on 11 August covers save-data, tutorial, battle-model and stability corrections. The demo update and hotfix remain pre-launch records, while the prologue entry belongs to the historical product context. A player can scan the date and kind before carrying a change into a systems page.
The final row is a planned co-op note with no date. It is retained because a planned record is useful when clearly marked, but it is not expanded into a schedule or a promised feature list. The timeline therefore behaves as a version lens: it changes how a fact is read without inventing extra facts around it.
Pax Autocratica is out now
Early Access launch announcement
State Maintenance Directive
Save-data, tutorial, battle-model and stability corrections
Demo hotfix
Final demo correction window before launch
Demo update
Late demo content and correction pass
Prologue deployment context
Historical testing and schedule context
Co-op roadmap note
Co-op is a major feature hoped for during Early Access
FIELD NOTE 02 / USING THE RECORD
How to read a version record
Start with the version identifier attached to a row, then read the date and change together. Current rows describe the Early Access state used by the colony and combat pages. Historical rows explain where a prior image or product context came from. Planned rows point forward only as far as the captured source allows. This keeps an update page useful without turning it into a speculative roadmap.
When the question is about installation, pair this route with System requirements. When it is about a system, return to the route whose current-build label matches the row. The timeline is a record of boundaries and transitions, not a replacement for the official news feed.
The route is bounded to the captured official store and publisher record for the current version line.