Observability Is the Only Patch

My last essay, The Bare-Metal Nation, argued that a country could be rebuilt the way an engineer rebuilds a failing server, from the up, and it ended on the quiet, joyful hum of clean code running on hardware its citizens actually own. I meant every syllable of it, but anyone who has actually stood in front of a red dashboard at three in the morning, coffee going cold, fans screaming, knows the sentence that has to come next: you cannot compile your way out of a system you cannot see. Before the rewrite, before the grand migration, before the clever app that does your paperwork with the government for you, there is a humbler and far more dangerous tool, and it is the one the legacy state fears more than any revolution, because a revolution can be managed with press releases and a dashboard cannot. Observability, a system that shows you what it is doing while it does it, is the only . Everything else is a guess wearing a hard hat.

The Black Box With a Press Office

Look at the thing honestly, the way you would look at a server someone rolled into your rack with no documentation and a sticky note that says “do not reboot.” Taxes go in. Press releases come out. In between sits a sealed chassis humming with fans you are not permitted to inspect, eating your compute, your hours, your paycheque and your patience, and the only it ever emits is a quarterly announcement that everything is historic, unprecedented, and on track. I have argued before that you should never trust a , whether it is a drug company, a regulator or a cloud AI, but the state is the original black box, an operating system that has been running for a century and a half with logs its users mostly have to file a formal request to read, and its favourite trick is to treat the absence of logs as proof that nothing is wrong. No logs, no incident. No incident, no accountability. It is the oldest exploit in operations, and it works on a nation exactly as well as on a forgotten machine in a basement.

The , my name for the crowd whose answer to every failure is more central control and more collective guilt, look at that box and want to feed it more, more budget, more mandate, more faith, as though a machine that refuses to tell you what it did with the last billion will suddenly grow honest if you hand it the next one in a sufficiently sincere tone. The control-freaks on the other side of the console want to lock the panel tighter and call the lock stewardship, the officials who have come to believe they own the users rather than serve them. Both camps share one fatal, unexamined assumption: that the box is supposed to be opaque, that darkness is the natural resting state of power and light is a favour you beg for. I reject that assumption with a grin, because I run a , a small cluster of my own servers at home, and nobody who has ever run one believes in magic anymore.

The Homelab Already Knows

Here is my worked example, and it is deliberately, gloriously boring, because boring is exactly what working infrastructure looks like from the outside. Everything I run lives in git. Not most of it, everything: the configs, the deploys, the midnight decisions I would rather forget but cannot, because the history remembers them for me. Deploys go through , which means the servers do not take orders typed by hand in a moment of caffeinated confidence; they pull their setup from the repository and do what it says, and the repository has a history, and every line of that history carries a timestamp and an author, so when something changes I can ask who, when and why, and the machine answers instead of issuing a statement. Dashboards are on. Alerts are on. The system is allowed to tattle on itself, and it does, cheerfully, at hours I would never have chosen.

And recently it earned its keep. An audit of my own local sites turned up that were far more exposed than they had any business being, the kind of quiet, polite risk that sits in a corner for months looking perfectly harmless until the day it very much is not, and in the same sweep the graphs caught a short blip in etcd, the database that holds the cluster’s memory, a hiccup measured in moments that would have been invisible on any machine that was not already watching itself. They were caught precisely because the lab is observable, because the logs existed before anyone needed them, because the dashboard was already drawing its patient little lines when one of those lines twitched. I did not fix them because I am clever. I fixed them because I could see them, and seeing is the part the legacy state has spent a century making optional.

Somebody Is Already Shipping the Telemetry

The delightful part is that none of this is hypothetical anymore. Somebody in Canada has already started instrumenting the black box from the outside. Build Canada¹ builds its tools in the open on GitHub², and the list reads like a system administrator’s wish list for a country. CanadaSpends describes itself, word for word, as “Improving observability of Canadian federal government spending,” which may be the most beautiful sentence I have read in a project description all year. The OutcomeTracker takes the government’s own promises and follows each one from commitment to completion, and as of October 26, 2026, its live tracker³ counts 603 commitments: 274 completed, 240 in progress, 67 not started, and 22 broken. FederalWorkbench is a bilingual AI tool for querying and understanding Parliament and its legislation, and BillsTracker asks, in its own words, “What would a Builder think of these parliament bills?”

Read those numbers again and notice what they are not. They are not a press release or a talking point. They are a status page for a government, the green, amber and red every competent engineer demands of every system they run, finally pointed at the one system nobody was ever supposed to monitor. A broken promise there needs no scandal to be seen. It just sits there, red.

I want to be precise here, because precision is a form of respect: is not building a replacement government. They observe, and they explain. Their principles are theirs, not mine, and they state them plainly on their About page⁴: “Building beats complaining.” “Bold beats safe.” “Ideas should be judged on merit.” A dashboard does not care which team you cheer for. It only cares whether the line went up or down, and that cold, beautiful indifference is the most nonpartisan gift a citizen can be handed.

Where the Metaphor Breaks

Now the honest part, the part anyone arguing in good faith owes the room, because a philosophy that cannot audit itself is just another black box with nicer fonts. My last essay leaned hard on the idea of government as an IT project, but every metaphor has a memory limit, and the place to find that limit is in a test environment, not in production, where the people live.

Start with speed. A pipeline that auto-approves a project because the checks went green, with no consultation, sounds like pure efficiency right up until you remember who is not in the test suite. Due process is not bureaucratic bloat; it is the part of the system that lets the person on the receiving end file a bug report before the deploy lands on their house. In Canada there is a harder edge still: the duty to consult that the courts have anchored in section 35 of the Constitution Act, 1982, the obligation of the Crown to consult Indigenous peoples before it acts in ways that could affect their rights. That is not a loop to be optimized away. It is a constitutional dependency, and a build that skips it does not run faster; it simply fails later, in a courtroom, with interest.

Then the bill compiler, my favourite toy from the last essay: an automatic checker, a , that would reject any bill carrying ideological malware before it ever reached a vote. I love the image, but a compiler that rejects ideas for being the wrong ideas is not a compiler at all; it is a speech filter with a friendlier error message. I have argued at length that free speech exists precisely so the message you hate can still arrive intact, and argued again that a built for the good guys stays open for whoever holds the key next. I cannot hand the Angry Collectivists a malware scanner for legislation and then act shocked when they flag my bills as the malware. A linter can catch contradictions, dead references and laws that loop forever. It must never be allowed to catch opinions.

Automatic funding freezes carry the same flaw dressed up in a lab coat. Tie the money to a metric and the metric becomes the battlefield, so the politics does not vanish; it just migrates into whoever gets to decide what counts as passing, which is exactly where the lobbyists and the control-freaks were already waiting with fresh coffee. Every engineer who has watched a team game a performance target knows the rule economists call Goodhart’s law: the moment a measure becomes a target, it stops measuring.

And the dream app from last time, software on your own machine that quietly handles the bureaucracy while you go play, has a prerequisite I skipped right past in all my excitement: to call the state’s on my behalf, the app has to prove it is me, and proving it is me at national scale means a . Every convenience I described sits on top of an identity layer, and an identity layer is the juiciest target a black box could ever dream of. If I build my app on a credential the state issues and the state can revoke, I have not abstracted the state away. I have handed it my session token and called it freedom.

The fix for all four is a line I wrote about running my own work through AI agents, where the agents do the labour and I approve every change before it lands: “The merge is mine, or it does not merge at all.” Automate the checks. Automate the dashboards. Automate the dull paperwork until it purrs. But the merge stays with a human being who can be named, questioned and voted out, because a pipeline that merges itself is not . It is just a faster way to lose the receipt.

Consultation Is a Slow Test Suite

So what do you do with the slow parts, the consultations and hearings and comment periods that drive every builder up the wall? You treat them exactly the way you treat a test suite that takes forty minutes to run: you are allowed to be furious at it, and you are not allowed to delete it. Everyone who has heard a junior say “the tests are slow, let’s just skip them” knows exactly what happens three weeks later, at three in the morning, in front of that same red dashboard.

So you speed it up. You parallelize it. You publish the inputs and the results so anyone can check the work without filing a request to see it. You give consultations deadlines and dashboards of their own, so the Angry Collectivists cannot use the process as an infinite loop and the control-freaks cannot use it as a rubber stamp. You make the slow test fast, visible and honest, and then you keep it, because the test is the only thing standing between a clever idea and a confident disaster. You cannot speed up a process whose timing you are forbidden to measure, which is why observability is not one item on the list but the precondition for the list.

The Dashboard Before the Rewrite

This is why observability comes first, before the migration, before the triumphant final commit. You cannot fix a system you cannot see, and you cannot even argue honestly about one. Once the lights are on, the shouting loses its fuel, because a red line on a public chart is harder to spin than any press release. You do not need to win the argument. You just need to switch on the logging, lean back, and smile while the box finally starts talking.

miHoYo, the game studio behind , has an old slogan, “Tech Otakus Save the World,” and I have always loved it for its cheek. Maybe we do. But if we do, it will not be through one heroic rewrite; it will be through a thousand patient dashboards, a hundred readable repositories, and a culture that treats telemetry as a right rather than a favour granted by the people being measured.

And through all of it, the rules still apply. In karate, which I trained in as a kid, is five rules recited in class: character, sincerity, effort, etiquette, self-control. The line I wrote about them still says it best: “A dojo that skips them is just a fight.” Skip the consultation, skip the human merge, skip the honesty about where the metaphor breaks, and the rebuilt country becomes just another fight with better graphs. Keep them, and you get something far rarer and far more fun: a country that can see itself, fix itself, and laugh about its bugs on the way to the next release.

Sources: Build Canada¹ · Build Canada, About⁴ (principles) · Build Canada on GitHub² (CanadaSpends, OutcomeTracker, FederalWorkbench, BillsTracker) · Outcomes Tracker³ (figures as of October 26, 2026)

Build Canada. Their own site. Linked, not rewritten. ↩ ↩²
GitHub. A public repository. ↩ ↩²
live tracker. Build Canada, on their own site. Linked, not rewritten. ↩ ↩²
Build Canada — About. Their about page, in their words. ↩ ↩²