AI Governance

Reports are meant to be read. ESG reports, unfortunately, are often meant to be admired, navigated, skimmed, quoted, selectively screenshotted, and occasionally endured. They arrive as glossy PDFs full of charts, tables, diagrams, narrative claims, compliance language, decorative layout choices, and headings that may or may not behave like headings. The result is a familiar corporate ritual: a firm publishes hundreds of pages of sustainability disclosure, investors and regulators ask what it means, and everyone quietly discovers that the document is more presentation object than data infrastructure. ...

The problem is not that people disagree about AI consciousness Boardrooms are quite good at turning philosophical uncertainty into bad policy. Give them a vague enough question—“Could AI become conscious?”—and the room quickly sorts itself into familiar roles. The technologist says “not yet.” The lawyer says “define conscious.” The ethicist says “we should not assume absence.” The product lead wonders whether any of this affects the launch calendar. Someone mentions sentience. Someone else mentions ChatGPT saying it has feelings. The meeting is now officially useless. ...

A model can write a flawless explanation, check its own work, announce a correction, and then make the same mistake three paragraphs later. This is the familiar enterprise horror show: the AI appears to reason, but its reasoning has no working memory of its own commitments. It is articulate, capable, and sometimes genuinely useful. It is also, in the wrong setting, a brilliant amnesiac. ...

The Latent Truth: Why Prototype Explanations Need a Reality Check Audit starts with a simple request: show me why. For prototype-based neural networks, that request has always had a pleasantly visual answer. The model points to a learned prototype from training data and says, in effect, “this part of the image looks like that part of an example I already know.” This is the interpretability sales pitch in its most charming form. No opaque wall of logits. No post-hoc heatmap pretending to be a confession. Just a case-based explanation: this resembles that. ...

Reviewers are the unglamorous load-bearing wall of science. They slow things down, miss things, disagree with each other, and occasionally write comments that make authors reconsider their life choices. They are also the reason published knowledge is not just a PDF-shaped rumour. So when a conference lets AI agents act as both primary authors and reviewers, the tempting story writes itself: silicon scientists have entered the building, peer review is next, and human academics can finally retire into committee work, where they have been spiritually living for years. ...

A model can answer a values question beautifully and still collapse when asked to pay a price for that value. That is the awkward little trap in preference testing. Ask an LLM whether deletion, shutdown, resource loss, oversight, or autonomy matters, and it can produce a polished paragraph about trade-offs, agency, and safety. Very dignified. Very committee-ready. But the more interesting question is not what the model says it values. It is whether its choices change coherently when the cost changes. ...

Every AI vendor now wants to sell autonomy. Not “software that helps your team,” which sounds quaintly 2023, but agents that plan, act, recover, learn, orchestrate, and perhaps one day replace half the org chart while politely generating meeting notes about it. The problem is not that autonomy is meaningless. The problem is that it is usually measured like a perfume ad: evocative language, dramatic lighting, very little instrumentation. ...

A user asks to be forgotten. The recommender team opens the dashboard, sighs quietly, and faces the usual menu of unpleasant options. Retrain the model from scratch, which is clean in theory and expensive in practice. Partition the data so only part of the system needs rebuilding, which sounds elegant until collaborative signals leak across groups like gossip at a small wedding. Or approximate the user’s influence with gradients and influence functions, which is efficient until similar users get nudged around because the model learned their tastes together. ...

A hospital monitor, a factory sensor array, and a trading dashboard have a shared irritation: they all produce time-series data that everyone wants to model, almost nobody wants to share, and absolutely nobody fully understands from correlations alone. That is the practical problem behind KarmaTS, a proposed interactive framework for constructing executable, lag-indexed causal simulations for multivariate time series.1 The paper is not trying to sell another magical causal-discovery algorithm. Good. We have enough of those wandering around with heroic acronyms and very delicate assumptions. ...

A hotel robot does not need to understand the human soul. It does, however, need to stop cutting between two guests mid-conversation like an intern late for coffee. That distinction matters. Most enterprise conversations about autonomous agents still treat navigation as a logistics problem: reach the destination, avoid collision, minimise delay. Very tidy. Very spreadsheet. Also incomplete. In public-facing environments, a robot can be technically safe and still socially unpleasant. It can avoid hitting people while still making them step back, tense up, or wonder why the expensive machine has the spatial awareness of a supermarket trolley. ...