Pax Autocratica Database

The Pax Autocratica Database organizes game systems without pretending that an Early Access build has a permanent, fully published encyclopedia. Use it to identify the right category, distinguish official facts from current-build observations, and record the Directive version behind a value. For exact costs, damage, durations, and unlock positions, the live base game remains the final reference.

Keep the product identity fixed

This database covers Steam base AppID 1067360. It does not merge content from Demo AppID 1069590, Prologue AppID 4107120, Playtest AppID 2194080, or the Prologue Playtest AppID 4150700. Similar names and shared development history do not make those applications interchangeable evidence.

Record the public branch and the date with any observed entry. The base game entered Early Access on August 10, 2026 and received several rapid Directives by August 15. A copied number without that context can be accurate for an older build and misleading for the current one.

Classify what you are looking up

A name belongs in the database only when its scope is clear. If an item appears in footage from another product or an old development build, keep it out of the base-game index until the current AppID confirms it.

Read weapons by battlefield job

Weapon records should answer how an attack is delivered and what squad problem it solves. Note whether it is used for focused pressure, area coverage, capture preparation, or another observable role. Pair the record with the user, mission, and current core rather than assigning a permanent universal tier.

The combat result also depends on position, target selection, citizen condition, and commands. A database entry can describe an effect, but it cannot prove that the same equipment is optimal for every sector. Use the Combat hub to turn records into a squad plan.

Record cores with patch history

Official AG-14 notes say Vortex Shell damage increased and Thunderbolt Arrow’s area increased. Earlier notes mention a Toxic Fog Core interaction with the Tree of Asherah. These named changes belong in a version ledger because they establish what changed, not every hidden formula.

For each current core, read the tooltip, identify delivery and coverage, then test it in a controlled encounter. The Weapon Cores guide shows a test method that separates the core from changes to the user, weapon, and target group.

Map buildings as production relationships

A useful building entry connects prerequisites, repair state, assigned citizen, accepted input, processing queue, output destination, and the system that consumes the output. This turns a list of names into a troubleshooting map. If a queue stops, check the earliest missing relationship instead of treating the building as broken.

The Command Center and Victory Square appear in current patch notes because their research interfaces could show the wrong state when the structures were not repaired. That is a concrete reminder to include progression and repair state in a building record. The Colony hub covers layout and logistics around those relationships.

Evaluate policies by affected population

The Policies guide explains how to test a directive without stacking several changes. Current notes matter here: AG-12 added manual exile and an aging toggle, while AG-14 fixed incorrect pregnancy states tied to Mandatory Reproduction.

Trace items and resources through custody

For a resource, record where it is gathered, who hauls it, where it can wait, what transforms it, and which queue consumes it. An inventory count alone does not show that the item is reachable by the intended building. Manual deposit quantities added in AG-12 make destination and reserve part of the player’s control.

AG-14 fixed disappearing resources during soldier hauling and corrected Trade Port prices. Treat those as dated fixes. If a current item vanishes, first inspect active queues and destinations; if a trade value looks wrong, compare the present interface before repeating a pre-fix report.

Mark evidence strength in every entry

Use official store and developer material for product identity, public features, dates, and named patch changes. Use the current in-game interface for exact values and interaction steps. Community observations can expose a question or reproduction path, but they need same-AppID and current-branch confirmation before becoming a definitive field.

When evidence disagrees, retain the narrower claim. A patch note proves that a named behavior was changed; it does not prove that all similar problems were removed. A current tooltip establishes the displayed description; it may not explain every internal interaction. This method keeps the database useful as the Early Access build evolves.

Sources checked August 15, 2026

• Steam base-game listing — AppID identity, Early Access status, public systems, platform, and features.
• Official Pax Autocratica website — weapons, cores, buildings, citizen conditions, policies, items, and expedition context.
• Official Steam News — dated changes to cores, research interfaces, deposits, trade, hauling, aging, exile, and reproduction.