Automation in Pax Autocratica

Think in flows, not buildings

Every automated chain has four observable stages: input, worker, processing time and delivery or storage. When output stops, inspect those stages in order. Adding another production building cannot fix a missing input or a hauling gap.

Build a stable labor layer

Use auto-assignment for an efficient first pass, then lock roles that must not be disrupted. Standby assignments make spare labor available for fluctuating work. Recheck the roster after deploying soldiers because the expedition layer can change who remains in the colony.

Read the queue before scaling

The crafting-time HUD provides direct evidence of whether a task is progressing. Watch for idle processors, growing input piles and completed goods that are not moving. Each symptom points to a different problem:

• No input suggests gathering, transport or storage pressure.
• A long active queue suggests processing capacity may be the constraint.
• Finished goods on the ground suggest hauling or collection pressure.
• Unstaffed structures suggest assignment or population pressure.

Why the Prologue is not the benchmark

Official Prologue material explicitly excludes deeper automation. A workaround that feels necessary there may not describe the Early Access system. Keep Prologue examples labeled and use the current build's building details, tutorials and queues before turning an anecdote into a rule.