Aging and reproduction change workforce planning over a longer horizon than a single job or expedition. Directive AG-12 added an option to disable soldier aging, so advice must begin with the setting used by the current save. Directive AG-14 also fixed incorrect pregnancy states under Mandatory Reproduction, showing that exact outcomes remain sensitive to the installed branch.
Verify the aging setting first
Open the current settings and population interfaces and record whether aging is enabled for this colony. Do not assume the control’s location or effect from an older build; use the wording shown in the live game. If the setting can be changed in an existing campaign, save before testing and observe what the interface says will happen.
With aging active, the state needs succession plans for essential work and military roles. With it disabled, the immediate replacement clock changes, but food, capacity, relationships, and casualties still matter.
Record visible life stages without inventing durations
Inspect age and status fields the current citizen or soldier panel exposes. Build a roster view around who can work now, who is approaching a visible transition, and which jobs have only one trained holder. Do not publish exact stage lengths or penalties unless your installed public branch shows them.
Treat reproduction as a capacity decision
Before using a reproduction policy, inspect food stability, living capacity, healthcare or other requirements named by the current interface, relationships, and the time before a new person can contribute. Reproduction is not an instant worker purchase. It adds needs and policy consequences before it adds labor.
State the intended result: replace an aging workforce, grow a future military pool, or maintain population after losses. If the colony cannot support the dependent period, repair supply and capacity first.
Investigate impossible pregnancy or age states
AG-14 fixed cases where Mandatory Reproduction assigned inappropriate pregnancy states. If you see a state that still contradicts the current citizen information, do not reinterpret it as a hidden mechanic. Preserve a manual save, record the affected citizen, active policy, relationship context, and directive date, then report the reproduction.
Similarly, if an aging transition does not match the live description, compare the setting and status before changing the roster. An isolated bug should not become a general rule for every citizen.
Build role overlap before the transition arrives
Pair unique workers with a second citizen who can cover the same essential outcome. In the military, maintain more than one person capable of frontline, focused, control, or capture work. Succession is easier when roles are defined by the job they accomplish rather than by one irreplaceable individual.
Stagger expansion where the population panel makes cohorts visible. Adding many dependents under one policy state can create a later wave of simultaneous food, housing, training, and assignment demand. Smaller deliberate additions give each cohort a functioning support chain and let the state learn the real maturation and care burden from its own save.
Review the roster after deaths, conversions, births, aging transitions, and major policy changes. The Soldier Guide handles deployment condition, Worker Management covers job continuity, and Policies explains how to test population directives.
Sources checked August 15, 2026
- Official Steam News — AG-12 aging toggle and AG-14 Mandatory Reproduction state fix.
- Official Pax Autocratica website — reproduction, relationships, citizen conditions, and policy scope.
- Pax Autocratica on Steam — current colony and citizen-management product scope.