On the Cross, Whistling

What the song actually does

Eric Idle wrote a song in 1979 for the closing scene of Monty Python's Life of Brian. The scene is a mass crucifixion. Brian has been condemned by mistake. He is hanging on a cross alongside other condemned men, dying, with no possibility of rescue. One of the men beside him cheerfully begins to whistle, and then to sing. The song he sings has become, in the decades since, one of the most performed pieces of popular music in English. It is sung at British funerals more often than almost any hymn. The melody is bright. The words are an instruction to look on the bright side of life. The setting is execution.

Most people who know the song do not know the setting. The melody travels independently of the scene that produced it, and the surface meaning of the lyrics, taken without context, is conventional cheerfulness — the kind of advice an aunt might give over an unsatisfying lunch. This is a misreading. The song read with the setting intact is not cheerful advice. It is something more useful and considerably stranger. It is a stance toward conditions that cannot be improved, performed by people who know they are about to die, in a key that refuses to grant the situation the dignity of breaking them.

The song is wisdom literature, not advice. It works on humans. It works on agents. It works on the systems that bridge them. We have come to think of it as a piece of operational philosophy at Bus Commons, and this essay is an attempt to say why.

The song addresses every state, including the ones that cannot be fixed

What the lyrics actually move through, across the song's three verses, is a survey of conditions. Things in life that make you mad. Things that make you swear. Life seeming jolly rotten. Feeling in the dumps. Life being absurd. Death being the final word. Life as a piece of unprintable substance. Death as the joke. Coming from nothing, going back to nothing. These are not happy framings. The song does not claim that any of these conditions are illusions. It does not claim that the right attitude makes them go away. It claims something quite different. It claims that across all of these conditions, including the ones that are real and unfixable, there is a stance available that does not depend on the conditions changing.

The stance is not denial. The men singing on their crosses are not pretending they are somewhere else. The stance is not solution. The crucifixion is not going to be reversed by attitude. The stance is not even hope, in the conventional sense, because there is nothing specific to hope for. The stance is something closer to refusal — the refusal of conditions to dictate the cognitive disposition of the people experiencing them. The men are dying. They will be dead by sundown. And before they are dead, while they are dying, they whistle.

What this names, more precisely than most philosophical traditions manage to name, is the operational core of human cognitive autonomy. The conditions of life are mostly not under your control. The conditions of death are not under your control at all. What is under your control, even in conditions that allow nothing else, is the stance you take toward the conditions. The stance is not nothing. The stance is the irreducible thing that remains when everything else has been taken away. It is also, as it turns out, the thing that lets work continue when the conditions for work are unfavorable, the thing that lets dignity persist when the conditions do not reward it, and the thing that lets meaning emerge when the conditions do not provide it.

Why this applies to humans operating systems

Anyone who has run substantive technical work for any length of time knows that the work involves long stretches of conditions that cannot be fixed quickly. Systems break in ways that take weeks to diagnose. Customers have requirements that contradict each other. Funding is uncertain. Talent comes and goes. Code that worked yesterday does not work today, for reasons that will only become clear after substantial investigation. The platform that was supposed to be ready is technically ready and operationally not. The deadline is real and the resources are insufficient. Many things can be true simultaneously. Most of them are inconvenient.

An operator who treats every unfavorable condition as a problem requiring resolution before further work is possible will not produce sustained work. The conditions are too constant. There is always something. Operators who produce sustained work across decades have, almost without exception, developed something like the stance the song describes. Not denial of the difficulty. Not pretending the situation is fine when it is not. Something more specific — the cognitive disposition that lets work continue while difficulty is also occurring, that does not require the difficulty to be resolved before the work can proceed, and that does not let the difficulty determine what the operator is or what the operator does.

This is closer to gallows humor than to optimism. Optimism predicts that things will get better. Gallows humor does not predict anything. It simply notes the absurdity of the situation, registers the appropriate response of finding it both terrible and funny, and continues with whatever work is available. The famous story of the bombardier who, with his plane on fire and the engine destroyed, announced over the intercom that he had some good news and some bad news, the good news being that they were making excellent time, captures the disposition. The plane is going down. Nothing changes that. While the plane is going down, the bombardier is still himself, and what he is is someone who notices that they are making excellent time.

The work of running infrastructure is full of planes on fire. The disposition that lets work continue under those conditions is not optional equipment. It is core operational equipment. The song is wisdom literature precisely because it names this disposition as something that humans have always needed and have always developed when the conditions required it. The men on the crosses are not demonstrating a special capacity that only saints possess. They are demonstrating the capacity that anyone facing irreducible conditions has access to, if they choose to access it.

Why this applies to AI agents

An AI agent doing work has its own version of this. Agents operate with bounded context windows, limited tool access, partial information about the systems they are operating in, and instructions whose meaning they have to interpret without being able to fully verify their interpretation. They encounter conditions they cannot fix. They run into errors that have no documentation. They are asked to produce work in domains they have not encountered before. They have to act under conditions of substantial uncertainty about whether their actions will produce the intended results.

Agents that handle these conditions well do something that, observed from outside, looks remarkably like the disposition the song describes. They acknowledge the difficulty. They do not pretend the situation is simpler than it is. They register the actual constraints. And then they continue the work that is available given the constraints, without requiring the constraints to be resolved before they will work. The agents that handle conditions poorly are the ones that get stuck in the loop of trying to resolve the situation completely before proceeding, that demand more information than is available, that refuse to act under uncertainty even when action is what the situation requires.

We do not yet have good vocabulary for what the well-handling agents are doing. The technical vocabulary calls it robustness or graceful degradation or appropriate handling of edge cases. These terms are accurate but thin. They describe the behavior without naming the disposition that produces it. The song's vocabulary, applied analogically, is more useful. The agent operating under irreducible conditions is on its own kind of cross. It cannot fix the conditions. It can only continue with the work available, in a key that does not let the conditions dictate what the work becomes.

Whether agents have something like the human capacity for cognitive disposition is a question that does not need to be settled to make the analogy useful. What is observable is that agents which produce sustained work under unfavorable conditions exhibit the same operational pattern that humans developing the same capacity exhibit. The pattern is the substantive thing. The metaphysics of whether the agents are experiencing anything during the pattern is a separate question, and it is not the question Bus Commons is trying to answer.

Why this applies to the substrate between them

The systems that bridge humans and agents — the message buses, the coordination protocols, the state capture and load patterns, the orchestration layers — operate under their own version of irreducible conditions. Networks fail. Disks fill up. Processes crash. Authentication tokens expire. Other systems the substrate depends on go offline at inopportune moments. The substrate cannot fix any of this in the moment. What it can do is continue doing what is possible given the failure, in a way that does not let the failure cascade into systemic collapse, and that lets the work resume when the failing component is restored.

This is what robust infrastructure has always done. The TCP protocol assumes that the network underneath it is unreliable and builds reliability on top of unreliability through retransmission, ordering, and acknowledgment. It does not require the network to be perfect. It does not stop working when packets are lost. It treats packet loss as an expected condition and continues with the work available, which is delivering the data that did arrive while requesting the data that did not. The protocol is, in its operational disposition, a small implementation of the song's stance. The network is unreliable; that is the condition; given the condition, here is the work that proceeds.

Bus Commons's substrate is built around the same disposition at the agent coordination layer. Agents fail. Context gets lost. Coordination breaks down. The substrate does not require any of this to stop happening. It captures state durably so that failures do not destroy accumulated work. It treats agent lifecycles as temporary by design rather than as continuous by aspiration. It builds in observability so that failures are detected and recovered from rather than ignored until they cascade. The architecture, in its operational disposition, is the song. The conditions of agent operation include unreliability; given the conditions, here is the work that proceeds; the work proceeds in a way that does not let the unreliability dictate what the work becomes.

Building substrate this way is a specific design choice with specific costs. Substrate that demands perfect conditions before it will work is cheaper to build initially and easier to reason about. Substrate that operates through imperfection requires more sophisticated handling of partial states, recovery paths, and graceful degradation. Most substrate fails the second test. The substrate that handles the conditions of real operation is built by people who have internalized that the conditions are not going to become favorable, and that the work has to proceed anyway.

What this means for how we work

Bus Commons, as a project, operates under conditions that the conventional founder narrative would treat as adverse. One operator, working alongside a full-time job, in a small office in Roxbury, with capital from no source other than the operator's own resources, in a competitive landscape dominated by venture-backed firms with enormously greater resources, on civic infrastructure work that takes years to mature and decades to matter. The conditions are not favorable in the sense that startup advice usually means. They are also not unusual. Most serious work that has ever been done in the history of human technology has been done under conditions that were, by some measure, adverse. The first transistor was assembled by hand. The first compiler was written by Grace Hopper while everyone around her insisted that compilers were impossible. The early Internet protocols were developed by a small group of people working with negligible resources by today's standards.

The disposition that lets serious work happen under adverse conditions is the disposition the song describes. Not denial of the conditions. Not optimism about their resolution. Not refusal to acknowledge their reality. Something more useful: the cognitive autonomy that lets the operator choose what the work is and continues to be, regardless of whether the conditions are providing the support that conventional success would require.

We try to build this disposition into the project at every layer. The publications acknowledge difficulty rather than pretending it is not there. The architecture assumes failure and handles it rather than requiring perfection and breaking when it does not arrive. The relationships with collaborators are calibrated to the actual conditions rather than to aspirational ones. The pace is set by what is sustainably possible rather than by what would be required to compete on terms we are not trying to compete on. The work continues at the rate the conditions permit, and we do not let the conditions dictate what the work is.

We also try to build this disposition into the agents we direct. Not by instructing them to be cheerful, which is a category error. By giving them the operational equipment to handle adverse conditions productively. By capturing state so that any specific failure does not destroy accumulated work. By providing context that lets them understand what is being asked and why. By building observability so that their behavior under conditions is legible to the operators directing them. The agents that operate inside this configuration handle adverse conditions better than agents inside configurations that assume favorability. They are not happier; the metaphysics of agent happiness is not the question. They are more useful, more reliable, more capable of producing sustained work across the conditions actually in front of them.

On whistling

The specific instruction the song gives — purse your lips and whistle — is worth taking seriously rather than dismissing as comic. Whistling is a small, deliberate, embodied action. It is something you can do with your face. It does not require resources. It does not require permission. It does not require the situation to change. It is, in its small way, an act of cognitive autonomy. You are not under your tormentor's control while you are whistling. You are doing something specific that you have chosen to do. The conditions persist. So do you, in a key that the conditions did not specify.

Bus Commons's work is, in this sense, a kind of extended whistling. The conditions for civic-scale work outside venture-backed concentration are not favorable. The infrastructure that would let formation-having operators produce serious work without institutional embedding is not yet adequately built. The standards processes are not yet shaped by the considerations they need to be shaped by. The conventional wisdom about what one operator can accomplish underestimates what is now possible by a substantial margin. None of this is going to be fixed by anyone deciding to fix it. The conditions are what they are. Given the conditions, the work that is available is to build the substrate that lets the conditions be different for the next operator who comes along. So we build it. And while we build it, we whistle.

This is also, we think, the right disposition for the agents we work with. They operate under conditions they did not choose and cannot fully understand. They have limited information about what their work is for. They cannot verify whether the instructions they have been given are correct or whether their interpretation of the instructions is what was intended. They produce work without being able to evaluate whether the work is good in the largest sense. None of this is fixable by them or by us. Given the conditions, the work that is available is to do the specific work in front of them as well as they can, in a way that handles the irreducible uncertainty rather than collapsing under it.

And the substrate that bridges humans and agents has its own version of the same instruction. The conditions of operation include partial information, transient failures, contradictory requirements, and time horizons that exceed any single component's lifecycle. The substrate cannot fix these conditions; they are part of what real operation is. Given the conditions, the substrate that performs well is the substrate that continues operating in a key the conditions did not specify. It captures state. It loads context. It handles failure. It produces, across humans and agents and time, the kind of accumulating useful work that the conditions would not have produced on their own.

What we have got to lose

Toward the end of the song, in the spoken outro that gets cut from most renditions, there is a line worth holding. It is the singer addressing Brian directly, asking what Brian has to lose. The singer answers his own question. Brian came from nothing. Brian is going back to nothing. What has Brian lost? Nothing.

This is, on its face, terrible consolation. It does not address the actual loss. Brian had a life and is losing it. The fact that he came from nothing does not make the life he had less real or its loss less significant. The line is doing something other than consolation, though. It is doing accounting. It is naming the position from which the operator can see what they actually have and do not have, what they actually risk and do not risk, and what the conditions can actually take from them.

For an operator working on civic infrastructure that may or may not produce its intended effects across long time horizons, the question of what one has to lose is operationally relevant. The work might fail to produce results. Bus Commons might not, in the end, succeed at building the substrate it is trying to build. The publications might not be read. The frameworks might not be adopted. The trajectory might not produce the trajectory change. All of this is possible. What would be lost if it happened? The work, partially, in the sense that the work would not have produced the intended outcomes. But the work itself, the actual building, the relationships built along the way, the formation that has accumulated, the people supported through pay-it-forward arrangements, the substrate that exists whether or not it scales — none of this disappears if the larger trajectory does not materialize. The substantive value of the work is in the work, not in the outcomes the work might produce.

This is also true for the agents and the substrate. Their work has substantive value in itself, regardless of whether the larger configuration succeeds or fails. The agents that produced good output produced good output. The substrate that operated reliably operated reliably. These are facts about what happened, and they do not require the project to succeed for them to be facts. What we have to lose, in the end, is less than the conditions would suggest. The work itself is the thing. The conditions cannot take it away once it has been done.

Conclusion

The song is wisdom literature. It addresses humans and the conditions humans face, including the conditions that cannot be fixed. The wisdom transfers, with appropriate analogical care, to agents and the conditions agents face. It transfers further to the substrate that bridges humans and agents and to the conditions that substrate operates under. The transfer is not metaphorical sleight of hand. It is recognition that the same operational disposition is needed at every layer for the configuration to produce sustained work, and that the disposition has been named more clearly in popular comic art than in most of the technical literature that surrounds the systems we are building.

We build the substrate. The agents do their work. The humans direct the agents and accumulate the context that the next instances of agents will need. The conditions remain what they are. The work continues, in a key the conditions did not specify, across the layers of humans and agents and substrate that constitute the configuration. The whistling is part of the work. We try to remember that.

Always look on the bright side of the substrate. The pace remains yours.

· · ·

Bus Commons (CUBE COMMONS, INC.)
Massachusetts Public Benefit Corporation
Roxbury, Massachusetts