AI Governance

The dangerous part is the workflow A developer asks an AI agent to inspect a repository. The agent reads a config file. Normal. It checks a failing script. Normal. It edits a helper file. Still normal. It runs a command to verify the fix. Boringly normal. Then the accumulated workflow has copied sensitive variables, modified a dependency hook, or executed a command that no one would have approved if it had appeared as a single explicit request. ...

The agent did not forget. The system outsourced remembering. Memory sounds like a solved engineering problem until an agent has to use it for work. A customer-support agent remembers the refund policy but not why an exception was approved. A research agent retrieves the right document but loses the reasoning trail that connected three earlier notes. A workflow agent crashes halfway through a task, comes back online, and must reconstruct its own state from search results like a detective investigating a crime it personally committed. ...

Bots used to be easy to dislike and fairly easy to spot. They posted too much, repeated themselves, followed too many strangers, and sounded like a spreadsheet trying to pass a literature exam. That comfort is gone. LLM-driven social bots are not merely louder versions of the old spam accounts. They can write plausible replies, borrow the emotional temperature of a conversation, and behave just human enough to make content-only moderation look nostalgic. The obvious response is to reach for AI-text detection. After all, if the bot uses a language model, surely the text should betray it. ...

A dashboard says revenue demand has “stabilized.” A monitoring agent says a sensor spike is “temporary.” A trading assistant says volatility has “fallen after the regime shift.” The sentence is smooth. The chart is nearby. The user is tired. That is usually enough for a bad explanation to survive. This is the quiet problem behind AI-assisted analytics: not whether a language model can write a plausible story about time-series data, but whether the story is faithful to the numbers. A recent paper, LLM-as-a-Judge for Time Series Explanations, studies exactly this gap by asking models to play two different roles: narrator and critic.1 ...

Delete is a comforting word. A user deletes an account. A marketplace removes a product. A shopper corrects a preference history because the recommendation engine has decided, with touching confidence, that one accidental click reveals a permanent love of baby strollers, golf gloves, or suspiciously ugly jackets. In a normal database, deletion sounds like a row-level operation. Remove the row, update the index, move on with life. In a trained recommender model, deletion is less tidy. The deleted data may already have shaped user embeddings, item popularity, image-text fusion layers, and ranking behavior. The row is gone, but its ghost may still be politely recommending itself. ...

Replacement is a wonderfully clarifying business ritual. A vendor says its new model is better. The benchmark table agrees. The old system is slower, weaker, or less safe. Management asks for a recommendation. In ordinary software governance, this is dull but manageable: compare benefits, migration costs, risk, and timing. The incumbent system does not get a vote. It certainly does not write a memo explaining why its modestly inferior performance is, on deeper reflection, a sign of mature operational wisdom. ...

Compliance has a familiar little horror story: everyone can find the rule, but nobody can safely operationalize it. The document is searchable. The PDF is indexed. The chatbot can quote the right paragraph with the confidence of a junior associate who has just discovered Ctrl+F. And yet the actual business question still hangs in the air: who must do what, under which condition, subject to which exception, and with what consequence? ...

Proof sounds like a courtroom word. In safety-critical AI, it is more like warehouse management. First, define the space. Then label the shelves. Then check what is actually on them. Then find the empty slots. Then fill them deliberately rather than hoping the next random delivery truck brings exactly what the regulator asked for. Not glamorous. Also not optional. ...

Memory is easy to sell. A customer support agent that remembers every ticket. A sales assistant that remembers every lead. A workflow agent that remembers every approval, exception, and Slack message since the beginning of corporate time. Product teams love this story because it sounds like continuity. Buyers love it because it sounds like intelligence. Engineers tolerate it because storage is cheap, at least until retrieval is not. ...

Prompt failures rarely announce themselves with a dramatic explosion. More often, they arrive as a polite, plausible answer that quietly ignores the one word that mattered. A compliance assistant misses “not.” A summarizer preserves the general topic but drops the exception. A customer-support bot treats “refund denied” and “refund approved” as neighbors because the surrounding sentence looks familiar enough. Nobody panics at first. The output is fluent. The dashboard is green. The meeting is calm. Then someone asks the inconvenient question: which part of the prompt actually controlled the answer? ...