Chargers are boring until everyone arrives at the same time. That is the useful way to enter this paper. Not through grand claims about artificial general intelligence, swarm intelligence, or the coming society of agents. Start with something embarrassingly practical: seven autonomous electric vehicles, two charging slots, and no reliable cloud coordinator telling everyone what to do. ...
Budget meetings have a familiar rhythm. Someone brings the spreadsheet. Someone brings the map. Someone else brings the sentence that ruins the spreadsheet: “This district looks inefficient on paper, but the roads are worse than the data says.” Classical optimization knows what to do with numbers. It does not naturally know what to do with that sentence. In public health planning, infrastructure rollout, retail site selection, and ESG investment, those sentences are often where the real institutional knowledge lives. Unfortunately, once the sentence enters the room, the algorithm usually leaves through the back door. Or worse, the organization pretends the sentence has been “encoded” into a weight, because apparently all human judgment becomes rigorous once it is multiplied by 0.37. ...
Capacity looks simple until someone pays to jump the queue. That is the quiet problem behind a large amount of modern AI infrastructure. A platform may have many model instances, edge servers, or compute nodes. Tasks arrive with different business value. Enterprise traffic is more important than free-tier traffic. Some jobs have tighter latency targets. Some users, by contract or politics, are simply not equal. Lovely democratic fiction ends at the load balancer. ...
Budget is not an afterthought Budget is usually treated as the boring part of agent design. The exciting part is the agent: planning, calling tools, trying strategies, revising itself, and occasionally behaving like a junior analyst who has discovered both confidence and the corporate credit card. But in real automation, budget is not boring. Budget is the boundary between useful autonomy and expensive wandering. ...
Quantum Rainbows and Resource Bottlenecks: When DQN Meets Entanglement Scheduling looks simple until it becomes real. One officer is faster at one task, slower at another. Events happen at different times. Moving between locations costs time. Every assignment affects the next assignment. Then management asks the system to “just optimize it,” preferably before lunch. ...
Budgets arrive before outcomes. That is the small administrative tragedy behind many allocation systems. A university decides which students receive financial aid before it knows who will persist. A workforce programme assigns training slots before employment outcomes appear. A healthcare provider prioritises interventions before the full treatment effect is visible. The decision is immediate; the evidence drips in later, usually after the next decision has already been made. Naturally, many algorithms pretend this is not happening. Very elegant. Also very wrong. ...
TL;DR for operators This paper asks a deceptively operational question: can an LLM act as a social planner when it must allocate a fixed budget across competing public projects? Not in the inspirational LinkedIn sense. In the literal sense: choose project IDs, stay within budget, maximise community utility, and return a valid allocation. ...