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. ...

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. ...

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. ...

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. ...

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. ...

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. ...

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). ...

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. ...

Humans have probably always killed one another. Warfare is something narrower. It implies groups, planning, logistics, memory, leadership, and enough social organisation that violence stops being a personal act and becomes a collective institution. The interesting question is not when humans first killed. It is when killing acquired administration. Ask that question and a small crowd of theories turns up, each with its own literature, its own favourite dig site, and its own conviction that the others have missed the point. The Hobbesians say war is ancient. The Rousseauians say civilisation invented it. The circumscription theorists say geography did. The economists point at surplus, the anthropologists at prestige, the international relations scholars at the security dilemma. Each theory has evidence. Each has counterexamples. The usual response is to pick a champion and treat the rest as noise. ...

At eight in the evening on 31 August 1939, a small team in Polish uniforms seized a radio transmitter at Gleiwitz in Upper Silesia and broadcast a few minutes of anti-German agitation. By the following morning the event had a name, an author, and a consequence: a Polish provocation, answered by the invasion that began the Second World War in Europe. The name held for six years. The finding out took until December 1945, when the sworn affidavit of the SS officer who ran the operation was read into the record at Nuremberg, complete with the code name for the murdered prisoner left at the scene. ...