What decides what
- Three decisions are rules, full stop. An exhausted citizen SLEEPS; a starving one with food EATS; a healthy one with surplus and a roof HAS A CHILD. None is ever put on the wire — a test scans every escalated request across a live run and asserts sleep and have-child never appear as candidates.
- The rest is scored, then budgeted. farm, work, build, trade, explore — plus fight and flee under raid — each score on the needs snapshot (food deficit, wood need, homeless share, raid pressure). When the top two land within 1.2 value points the engine arbitrates, if the city has an ask-token left; the budget refills at N asks per sim-second. No token → the argmax rule decides and the rung says so.
- The cascade is the product. A shortage is not a scripted animation: it empties the granary, the food-deficit term lifts FARM's score, citizens re-decide, wood income drops, BUILD stalls, homelessness grows. The spec test measures the farm+eat share of decisions in a 30-second window after the event and asserts it beats the uneventful baseline.
- Population is coherent by construction. pop = start + births + migrants − deaths − fled, and the summary carries every term plus the boolean — births are never laundered as migration and raid deaths stay in the identity. The stats overlay checks it every frame.
Honest edges
- The engine is a budgeted voice, not the boss: at the default budget of 2 asks/s twelve citizens decide ~16 times per sim-second, so most decisions are rules — and every one of them says so on the rung. Set the budget to 0 and the city runs entirely on rules.
- The engine often declines to arbitrate: a flat three-way contest lands between the abstain floor and the confidence gate, and the runtime returns abstain rather than guess. That is the honest outcome — the argmax rule takes over and the rung says so.
- Citizens are dots on a town-square grid, not agents with pathfinding — the point is the decision distribution, and the chart of food, wood, population and homes over time is the ledger of what those decisions did.
- The scoreboard is session-only, auto-recorded at every 500th decision: close the tab and it is gone. Nothing leaves this page.