Start with one complete production chain, not a burst of expansion: inspect your people, connect a resource to processing and transport, confirm usable stock, then prepare an expedition without removing every essential worker.
Read the colony before you build
Begin by reading the current tasks and inspecting the available personnel. The official game description establishes the colony's responsibilities—resource work, hauling, research, manufacturing, food, and personnel—but does not publish one correct opening build order.
That distinction matters. A checklist can help you diagnose the opening, but it should not pretend that every map, patch, or population begins with the same optimal placement. The first goal is legibility: be able to say who is gathering, who is moving output, where processing happens, and where usable stock ends up.
If the layout already makes that answer difficult, pause expansion. The colony layout guide explains the official production relationships and labels spacing or zoning advice as player-tested rather than universal.
Prove one production chain end to end
Work on one chain until its result is usable. For food, that means more than seeing a Kitchen active. The evidence-backed chain is raw-material availability, Kitchen production, transport, arrival at the Food Hall or consumable stock, and an opportunity for soldiers to eat. The hunger and food guide walks through each boundary without inventing consumption rates.
For other manufactured items, use the same questions:
- Is the required input available to the producer?
- Is someone assigned to the relevant work?
- Does finished output leave the building or its immediate buffer?
- Can transport reach the destination?
- Does the Warehouse or consuming facility accept the output?
Change one link, then observe again. This is a player-tested diagnostic method, not an official optimal routine. Its value is that a working change remains attributable to a specific part of the chain.
Official production modes solve only the production decision. Order requests a chosen amount, Stock aims to keep inventory above a set threshold, and Auto repeats production while materials are available. None of them replaces hauling. See automatic restocking and the Resource Transport Station before diagnosing a stopped queue as a recipe failure.
Stabilize food and transport before expansion
A visible finished food item is not proof that the population can consume it. Confirm the route into the Food Hall or usable inventory, then observe whether hunger improves. Avoid adding population while that route is still intermittent, because the supplied research links population growth with added food, housing, wage, and work pressure.
Do not assume a single building solves the food problem. A Kitchen can wait on inputs. Transport can wait on available workers. The Food Hall can be disconnected from the chain even while production appears healthy. Keep those responsibilities separate in your diagnosis.
The same principle applies to general resources. Assigned soldiers at a Resource Transport Station collect output from resource buildings; after the station is upgraded, the official description says they can deliver materials directly to the Warehouse. That station does not create material, replace upstream workers, or create storage capacity.
Prepare the Leader, squad, and colony together
Research and manufacturing support the expedition, but do not assume ordinary soldiers use a traditional individual inventory. In the documented build, crafted personal equipment is for the Leader, while soldier weapons and abilities follow their role or character cards. Use the soldier gear guide to inspect that distinction without searching for an unsupported drag-and-drop workflow.
Squad selection changes the colony workforce. Before departing, identify which chosen soldiers were doing essential gathering, cooking, or transport. Leave those functions staffed rather than discovering during a long expedition that the base stopped feeding itself.
Treat the first expedition as reconnaissance and learning. Check the Leader's documented equipment options, review soldier cards in the current interface, carry the supported means to capture enemies if you intend to use that system, and preserve a safe return. The supplied research does not establish a universal squad composition or route, so this guide does not provide one.
Review the return before starting another project
Back at the colony, inspect what changed. Official descriptions connect expedition rewards, Cores, captives, and the Prison to further colony progression. Review returned resources, current Core choices, and captive handling before modifying several production chains at once.
If a new recruit or converted captive increases the population, check the food chain and workforce again. If the expedition removed a key worker, restore that job before assuming the building itself is broken. If a production queue stopped, walk through input, worker, output, transport, and destination in that order.
The broader Pax Autocratica guide explains how colony preparation and expedition results form one repeating progression loop.
Choose the aging rule deliberately
The official Soldier Aging toggle supports two management preferences. With aging On, soldiers age over time; with it Off, they remain in their best state. The setting can be changed at any time and takes effect immediately. The aging toggle guide also covers the documented movement and work penalties of the Aged state.
This is a preference, not an early-game optimization backed by a universal formula. Community players discuss turnover, food, and wages as part of the choice, but the official sources do not prescribe which state is correct.
Keep an Early Access boundary around every checklist
Pax Autocratica is still changing. Names such as Order, Stock, Auto, Resource Transport Station, Warehouse, Food Hall, Prison, and Cores are preserved here because the supplied official research supports them. Exact menu paths, capacities, production rates, aging schedules, food consumption, and optimal layouts are omitted because that evidence is absent or build-sensitive.
When an update lands, verify the current interface and official notes before following an older video. A useful beginner routine should survive UI movement because it asks about inputs, workers, transport, destinations, and colony staffing—not a memorized sequence of clicks.