AI Governance

Fact-checking has always had a small public-relations problem: being right is not the same as being believed. A platform can label a claim false. A newsroom can publish a careful correction. A compliance team can flag a misleading ad, remove it, document the action, and still watch the same claim reappear in a shinier costume three hours later. The hard part is not only detection. It is persuasion. People need to understand why a claim fails, not merely be informed that someone with a badge disapproves of it. ...

A credit model approves the familiar applicant. A diagnostic model reads the common scan. A pricing model values the house in a neighbourhood it has seen a thousand times before. Everyone relaxes. The model is “confident”. Then a strange case arrives. The applicant has an unusual income pattern. The scan comes from an underrepresented patient group. The house sits outside the areas covered by historic transactions. The model still produces an answer, because that is what models are trained to do. Press button, receive number. Very efficient. Occasionally ridiculous. ...

Procurement is where compliance anxiety goes to acquire a purchase order. A laboratory wants to buy an item. Perhaps it is ordinary. Perhaps it is dual-use. Perhaps it belongs under the U.S. Munitions List, Nuclear Regulatory Commission controls, the Commerce Control List, or the broad residual category of EAR99. The practical question is not just “what is this?” It is “what is this under the rules, according to which rule text, with enough evidence that someone can defend the decision later?” ...

A company announces an AI governance committee. There is a policy document, a risk register, a review workflow, a few tasteful slides, and perhaps a new Slack channel with “responsible” in the name. Everyone feels governed. Excellent. The bureaucracy has successfully acquired stationery. The harder question is not whether the institution has an AI governance process. It is who can actually move it. ...

TL;DR for operators AI governance is usually treated as oversight: write the policy, assign the committee, run the audit, update the spreadsheet when legal asks why nobody can find the spreadsheet. Charming, in the way filing cabinets were charming. The stronger operational idea is governance with memory. Not memory in the sentimental sense. Memory as structured continuity: which AI systems exist, which rules bind them, which evidence proves compliance, which incidents changed the risk picture, which obligations were revised, and which executive promise quietly expired the moment political weather changed. ...

The machine said the right answer. Annoyingly, that is not the same thing as being right. Audit a model-generated legal memo, clinical explanation, or compliance answer and the same awkward question appears: did the system reason correctly, or did it simply land on the right sentence after a scenic tour through nonsense? ...

A junior researcher is not usually asked to invent an entirely new field before lunch. They are given a paper, a codebase, a baseline, and a moderately suspicious supervisor. They read, try a few modifications, break something, fix it, run experiments, write up the result, and then discover that reviewers are not, in fact, decorative. ...

When Democracy Meets the Algorithm: Auditing Representation in the Age of LLMs Agenda-setting is where participation quietly becomes power. Anyone can invite hundreds of people to submit questions. That part is now cheap. The difficult part arrives ten minutes later, when an expert panel has time to answer only seven of them, and someone has to decide which seven. This is the small administrative hinge on which democratic legitimacy loves to swing. A moderator chooses. A platform ranks. An LLM summarises. Everyone else is told, usually with a straight face, that their concerns were “reflected”. ...

Legal teams do not usually ask for AI that sounds clever. They ask for AI that does not accidentally invent a statute, misread a precedent, or confidently advise someone into a procedural ditch. That makes legal AI an awkward domain for large language models. The model may be fluent. The law, inconveniently, is not graded on fluency. It is graded on source, jurisdiction, timing, interpretation, and traceability. A beautiful answer with the wrong legal basis is not “almost useful”. It is professionally radioactive. ...

A customer support bot does not need a soul. Pleasantly, most airlines have not yet advertised one. But it does need to remember what role it is playing. If it gives policy advice, that advice must remain anchored to the policy. If it apologises for an error, the correction should bind future answers. If the company has told users the assistant is a support agent, the assistant cannot conveniently become a speculative travel blogger, a therapist, a lawyer, or a magic refund machine, depending on which prompt arrives next. ...