Skip to content
You are reading version 1 of this piece, kept available for readers who prefer it. The current version is here, and the full history is here.

brick · v1 · 2026-08-03

Ceremonial deletion

Closing a chapter is an act a person performs, not a state a database arrives at

Why the delete button is a rite rather than a maintenance operation, and what a system owes someone who has decided that a chapter is finished. The canonical treatment of ceremonial deletion.

Every culture that moves a person from one life stage to the next does it with an act rather than an announcement. Arnold van Gennep, cataloguing them across societies in Les rites de passage in 1909, found the same three-part shape almost everywhere: a separation, a threshold, and an incorporation into the new state. The separation is nearly always something performed. A thing is burned, cut, buried, washed off, or given away, and the performance is not decoration on the transition. It is how the transition gets accomplished.

Software offers, at the equivalent moment, a settings page. Under account preferences there is a link, then a dialog worded as a warning, then silence. The material being disposed of is frequently the most consequential a person has ever produced: the record of the year they came apart, the inventory of what they were carrying, the letter written at three in the morning to someone who will never receive it. People doing that kind of work know before any engineer does that its ending has to be enacted. Practitioners running transformation programs describe the same pattern reliably enough to design for. A person finishes the work of a phase, wants to mark that it is over, and reaches for the destruction of the evidence as the mark.

The mechanism is that closure is an action rather than a state, so a deletion the person performs deliberately, and that the system answers irreversibly, does psychological work that the same bytes expiring quietly on a retention schedule cannot do. Michael Norton and Francesca Gino reported in 2014 that people who performed rituals after a loss experienced less grief afterward, with restored feelings of control as the proposed pathway. Notice the direction of that finding. The ritual does not alter the fact; it alters who is standing over it. Deleting on purpose is the difference between having lost something and having finished with it.

What this asks of a product is small and consists mostly of refusals. The act belongs to the person, which means a button they press at a moment they choose and room to say in their own words what they are releasing, rather than a retention policy that expires the material on their behalf while they are asleep. The system’s answer has to be true, and that is the half most software fails, because deleted usually means flagged, hidden from your view, and alive in three derived copies. A ceremony performed over a lie is worse than no ceremony at all, since the person has now spent a real act of closure on a fiction. And the threshold stays uncrowded. An interface that argues at the moment of deletion, offering a discount, a pause, a list of everything you are about to lose, is not protecting you. It is protecting its own retention.

The essay behind this one is about firing: the decision that turns a draft into an artifact, attributed, dated, finished. Deletion is that same faculty exercised in the other direction, the second decision an artifact can receive, and a corpus that can only accumulate is not being curated, it is being hoarded. Anyone can run the rite tonight on a file they have been carrying for no reason. The person who can end things inside a system is the person who can trust it with beginnings, and an ending someone chose is not a loss at all but a finish.