For when rants trigger RCU stall detection

and my patience buffer overflows into /dev/null. The rants are technically supposed to be brief. And let’s be real, some system bugs deserve a full kernel panic’s worth of fury.
A drawn fantasy map titled The Metier Landscape. Everyday Settlements sit at the front, with trailheads marked Dashboards, Meetings, Glossary, Projects, AI Tools, Audits, Reorg and Incidents. Paths climb through Operations Plain and Information Valley to Concept Ridge, Concern Ridge and the High Country beyond. A panel in the corner reads: many entrances, many paths, no single route.

All of it would survive an audit

The Monday report is accurate and on time. Its third column has a name that made sense to whoever built it, and that person moved teams in 2021. Everyone who reads it knows roughly what the column counts, and no two of them would write the same sentence about it. Down the corridor a working group is meeting for the fourth time. It has a chair, terms of reference and eleven open actions, three of them carried over from the group that came before it. What it was convened about happened again in September. ...

August 5, 2026 · 2 min

Concerns as an organising principle

The reorganisation was announced in October. Four directorates became three, the data team moved out of IT into a function called Information and Insight, two roles went and three were created. The intranet A to Z was updated inside a fortnight. By April the new structure was being asked what the old one had been asked: who owns this, why it broke at the handover, why it was found so late, and why nobody had the whole picture. ...

August 5, 2026 · 3 min

The organisation without a model of itself

In March a new starter sat for a week without a login. Six people met four times and recommended a pre-start checklist. The checklist was adopted. In September a new starter sat for a week without a login. The March report named three causes: unclear ownership of onboarding, a communication gap between IT and HR, and a need for better forecasting of start dates. All three were true. January, February, March In January IT consolidated identity management onto one platform. The licence cost fell, and provisioning moved from on request to a nightly run. ...

August 5, 2026 · 3 min

Why maturity models disappoint

The assessors came for three days in October. The evidence pack ran to 412 documents, 61 of them written that fortnight. The verdict was level three of five, with a roadmap to level four. The certificate hangs by the lift. In November a release went out without a rollback plan, the way releases had always gone out. Policies, minutes, screenshots Policies. Process descriptions. Minutes. Review schedules. Screenshots of the pipeline configuration. Nine interviews. None of it was untrue. ...

August 5, 2026 · 3 min

AI is exposing old organisational weaknesses

The assistant went live on a Tuesday, indexed the intranet, and was asked by somebody about to resign what notice period applies. It answered three months, quoting a policy page from 2019. The answer has been one month since the 2022 handbook. The pilot review recorded a hallucination. The model had not hallucinated. It had read the intranet. Nobody had taken the 2019 page down. There was never a reason to. The people reading it were checking a rule that applied to them, and they knew to go past it to the handbook. The ones who did not know asked somebody who did. The page does not link to the handbook, and the handbook does not link to the page. ...

August 5, 2026 · 4 min

Why intelligent people disagree while using exactly the same words

Four people leave a meeting agreed about the risk of moving payroll to a new provider in January. The minute says so, and none of them has reason to doubt it. In the room, the payroll manager meant the chance that the first run would come out wrong. Finance meant what it would cost to put right. Legal meant who would answer for wages paid late. The programme lead meant the three months of roadmap a parallel run would eat. All four said risk, all four heard risk, and nothing in the hour gave any of them cause to check. ...

August 5, 2026 · 4 min

Most organisations do not have an information problem

A familiar ritual follows organisational trouble. A decision goes wrong, a delivery slips, a risk materialises that somebody somewhere had documented, and the retrospective lands on a convenient conclusion: the information wasn’t good enough. The remedy writes itself. Another dashboard. A new report. A data lake, properly governed this time. An AI pilot to surface insights. More policy on how information ought to flow. The ritual is comfortable because it frames the problem as scarcity, and scarcity has an obvious cure. A walk through almost any large organisation suggests no shortage at all. Dashboards refresh nightly and go unwatched. The same metric appears in three decks with three different values. Reports run on schedules nobody remembers setting, for audiences nobody has confirmed still exist. Meetings re-litigate facts that were settled in other meetings. The organisation is not starving. It is standing in a warehouse of maps, unsure which one describes the territory outside. ...

August 5, 2026 · 5 min
Cross-section illustration of a medieval castle's concentric defences seen from above at a slight angle: moat, outer wall, gatehouse, courtyard, inner keep

The phrase survived. The definition did not.

Consider a medieval castle. It is tempting to imagine that its security rested on the thickness of its walls, and that a besieging army faced essentially one problem, repeated: get past the stone. But that is not how a defended position worked, and the people who built them knew it. A castle was arranged so that every successful advance exposed the attacker to a new disadvantage. The moat forced engineering work under fire. The wall forced escalade or breach, both slow, both loud, both costly in men. The gatehouse compressed the attackers into a killing corridor where their numbers stopped helping them. The courtyard beyond it was overlooked from every side, so that taking the gate meant standing in the open beneath defenders who had been waiting for exactly this. And the inner keep meant that even total success outside its walls bought the attacker another siege, on worse ground, with a depleted force. ...

July 21, 2026 · 10 min
A walled medieval city at dusk seen from slightly above, gates standing open, lantern-lit lanes, guild banners hanging from timbered houses, small figures greeting one another at the gate and leaning from windows to watch a lone stranger in the lane. One long section of the city wall has been replaced by an incongruous row of sleek modern turnstiles and a faint blue-glowing server cabinet.

The trouble with calling it zero trust

A medieval city was never secured by its wall alone. It had guilds that vouched for their members, letters of introduction carried from town to town, gate guards who knew faces, innkeepers who noticed accents, and neighbours who registered a stranger in the lane before any official did. The wall was one instrument among many, and arguably not the most effective one. What kept the city safe was a dense weave of overlapping trust relationships, most of them informal, all of them cheap (in financial terms). ...

July 20, 2026 · 11 min

Peace has running costs

Organised violence tends to appear where the substrate makes it the higher-return move, and to recede where it does not. That is one way to read the origins of war. Inverted, the same reading yields a second claim, less obvious and more useful. If war is what the ground rewards under some conditions, then peace is what the ground rewards under others, and neither is the default. A long stretch without organised violence is not the absence of something. It is the presence of conditions under which cooperation pays, and conditions like that can be built, and they can wear out. ...

July 16, 2026 · 10 min