RL Needs a Menu, Not a Miracle Menus are underrated. When a language model knows only one way to solve a problem, reinforcement learning can mostly reward or punish that route. It can make the model more confident, more selective, and sometimes more verbose. But it has little room to choose among genuinely different ways of reaching the answer. ...
Training a reasoning model is starting to look less like feeding a student more textbooks and more like taking that student into a difficult city with a very opinionated guide. The guide should not carry the student through every street. That creates a tourist, not a navigator. But leaving the student alone with a reward signal that says only “correct” or “wrong” is not exactly enlightened pedagogy either. The student may find one narrow route, repeat it forever, and call that intelligence. We have all seen corporate training programs with roughly this level of imagination. ...
A daily dashboard for monitoring free AI inference providers, with curated vendor boards and a machine-refreshable OpenRouter free-model roster.
Scorecards are useful until people learn how the scorecard works. That is not a cynical observation. It is basic management. Sales teams optimize for commission rules. Customer-service teams optimize for handle-time dashboards. Students optimize for exams. And language models, with their charming lack of shame, optimize whatever reward function we put in front of them. ...
Documents are the easiest way to fool an AI system into looking serious. A procurement team uploads the full contract archive. A compliance team adds policy manuals, audit notes, and emails. A financial analyst stuffs transcripts, filings, and market commentary into one heroic prompt. The interface accepts it. The model answers fluently. Everyone relaxes. ...
Policy is where language stops being poetry and starts becoming liability. A content moderation policy, a warranty clause, a procurement rule, a safety instruction, a legal test: all of them look like ordinary prose until someone asks the system to apply them consistently. Then the prose turns into a machine with hidden gears. Some gears are logical: this condition and that condition, this exception unless that threshold is met. Other gears are semantic: whether a message is threatening, whether a disclosure is meaningful, whether a clause covers a warranty period. Humans navigate this mixture badly but socially. LLMs navigate it fluently but not always reliably. Solvers navigate it reliably but only after the world has been turned into formal symbols. Which is, inconveniently, not how most business documents arrive. ...
Most office work has a draft problem. A junior analyst writes a first version of a financial memo. A lawyer marks up an argument. A consultant turns messy meeting notes into a client-ready recommendation. The first attempt is rarely useless. It is usually half-right, locally clever, and globally flawed. The expensive part is not starting from zero. The expensive part is learning how to improve a decent draft without being hypnotized by it. ...
Warehouse. That is a better place to start than “large language models for combinatorial optimization,” because the business problem is not philosophical. A warehouse has stacks, access directions, priorities, robots, blocked items, and deadlines. Someone has to decide which unit load moves first, which move creates future trouble, and how to search through the possible rearrangements without melting the compute budget. ...
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. ...
Hiring. A candidate writes a personal statement. A screening model gives a score. A manager asks the AI system why. The explanation says work experience mattered most, education came next, and demographic variables barely moved the decision. Everyone relaxes, because the explanation sounds reasonable. That is the dangerous part. A reasonable explanation is not necessarily a faithful explanation. A counterfactual edit that looks plausible is not necessarily a causal counterfactual. And a model that appears insensitive to demographic concepts may not be “fair”; it may simply have learned, or been aligned, to suppress visible sensitivity in the narrow setting being tested. ...