Systems Monday — City Hall: Petition Desk

The trigger
Two signals line up well today. First, there is a direct player ask for "Total War but without the war," meaning deep societal management without army play. Second, hardware sales hitting a 13-year low while prices rise is a reminder that low-spec, PC-first systems games are a safer bet than asset-heavy productions. Add the broader industry mood of scope pain and crowded release calendars, and a compact civic sim built from menus, maps, and authored cases looks commercially rational.

The idea
Make a city hall petition desk sim: a small-scale bureaucracy game where citizens, businesses, unions, landlords, and department heads file requests, complaints, and exemptions, and you decide what gets approved, denied, delayed, or modified. Petitions are concrete: waive back rent penalties after a flood, approve a late-night food market, condemn an unsafe tenement, reroute buses for roadworks, fund a school nurse, issue a demolition permit, forgive utility debt for one block. Every ruling changes a handful of city metrics across a simple district map—trust, health, housing pressure, congestion, commerce, unrest—and creates follow-up cases later. The fantasy is running the chokepoint where policy becomes everyday life.

The core loop
Read today's stack of petitions, inspect the affected district on the map, check budget, current ordinances, and recent precedent, then spend limited actions to investigate, request more documents, or negotiate a compromise. Make the ruling. End the day and watch the city react through metric shifts, headlines, and new petitions caused by prior decisions. Every few days, choose one ordinance or budget adjustment that changes future case rules, then survive the consequences.

Why now
There is visible demand for strategy and governance games that are about managing society rather than commanding troops, and the current options usually push players toward giant grand strategy or full city builders. This is a cleaner wedge: politics at street level, with readable consequences. It also fits current market conditions. If players are slower to buy new hardware, a sharp low-spec management game is easier to reach them with. For a solo developer, replay from systemic interactions is much cheaper than competing in spectacle.

Scope
First playable milestone: 4 districts, 6 city metrics, 25 authored petitions, 8 ordinances, one budget screen, and a 14-day scenario. Enough to prove that one ruling can create a second-order problem two or three days later. Steam-release scope: a 2-3 hour campaign with 80-120 petitions, 3 endings, a few governance styles tracked in the final report, and light variation through shuffled case order plus district state. Keep presentation flat: dossier UI, portraits, map overlays, newspaper cards. No freeform city building, no walkable spaces, no voice acting, no national election layer.

What kills it
If decisions do not create fast, legible downstream effects on districts, the whole thing becomes paperwork with no bite. Then you lose to Papers, Please on moment-to-moment tension and to Suzerain on political drama. The other project-killer is ambition creep: if you add full city-builder placement, procedural citizens, or national politics, the scope breaks immediately.

If you want to test this idea properly, prototype 10 petitions, 4 metrics, and one district feedback screen before writing a bigger script.