AI Governance

Failure should be boring Approval workflows are supposed to be boring. A client submits documents, a system checks the required conditions, and an approval either happens or does not happen. Boring is good. Boring means the process does not accidentally approve a case while also escalating it as problematic. The trouble begins when a workflow is written as a best-effort model of reality. Someone encodes the actions. Someone else adds an exception. A third person adds a shortcut because the quarterly dashboard prefers speed over philosophy. Eventually, a sequence exists that should not exist. It does not look like a bug when inspected locally. Each action seems defensible. The path as a whole is the problem. ...

Collections. That is probably not the first word people expect in an article about emotionally intelligent AI agents. It sounds too ordinary, too administrative, too full of overdue invoices and politely threatening emails. Good. That is exactly why it is useful. Imagine an automated debt-recovery assistant calling a small business owner whose cash flow has collapsed. The assistant has a target: shorten repayment time. The debtor has a story: delayed receivables, layoffs avoided, a promise to pay later. A normal chatbot can respond with empathy. A larger model can produce warmer phrasing. A compliance-tuned model can avoid saying obviously illegal things, which is a charmingly low bar. ...

Agents are easy to demo and hard to measure. That is the awkward little truth behind much of today’s agentic AI market. A browser agent completes a booking task. A coding agent opens a pull request. A customer-service agent handles a simulated refund conversation. Everyone nods politely. Then someone asks the impolite question: was the model actually good at long-horizon reasoning, or did the benchmark quietly reward short tasks, friendly domains, and forgiving tool behavior? ...

A name can do a suspicious amount of work. Give an LLM a table of colorectal cancer gene candidates and ask it to rank the best drug targets. When the gene names are visible, KRAS lands at #1. The model justifies the choice with a confident reference to “proven therapeutic tractability via covalent RAS inhibitors.” Sensible enough, if the task is to combine the supplied table with the model’s accumulated biomedical knowledge. ...

The agent finished the task. That is not the same as doing the task. Inbox sorted. Calendar updated. Report generated. Customer record changed. Dashboard refreshed. For a demo, that is usually enough. The screen shows a plausible answer, the final artifact looks tidy, and everyone politely pretends the agent must have followed the correct path because the output did not immediately burst into flames. ...

Supermarkets look simple from the aisle. Milk is cold. Apples are stacked. Shampoo is there because, apparently, civilization requires thirty-seven variants of “moisture repair.” Behind that calm retail surface is a coordination machine that never really sleeps: demand planners, inventory teams, procurement staff, suppliers, warehouse coordinators, truck schedules, exception reports, and the occasional emergency because one popular SKU suddenly became everyone’s personality for the week. ...

The checklist problem that exposes the model Checklist tasks look boring. That is exactly why they are useful. Ask an LLM to write a formal email under 50 words, include one required term, avoid another term, and return the result as JSON. None of this sounds intellectually difficult. No theorem proving. No multimodal reasoning. No dramatic benchmark leaderboard screenshot. Just instructions. ...

The verifier that cannot know everything Verification sounds like the sensible adult in the AI safety room. The model may hallucinate, the benchmark may flatter, the demo may sparkle under conference lighting, but the verifier is supposed to be the hard stop: a formal mechanism that checks whether an AI system’s behavior satisfies a specified policy. ...

Inventory is where AI governance usually begins to lie Inventory sounds harmless. Every governance program begins by asking a simple question: what systems do we have? Then reality behaves rudely. A developer tests a model API for one customer-support workflow. A product team quietly connects a retrieval system to internal documents. A data team fine-tunes a classifier because the foundation model was “almost good enough,” which is how many operational risks enter the building wearing a visitor badge. By the time compliance asks for the official AI system inventory, the list is already stale. ...

Update Day Is Where Evaluation Gets Weird Update day is usually presented as a clean managerial ritual. A model gets retrained. A validation report arrives. The new AUROC is higher, or at least not embarrassing. Everyone is invited to believe that the system has improved. That belief is comfortable. It is also incomplete. ...