How a lifetime inside the world’s infrastructure
became a working alternative to everything that is currently breaking
DOMINIC SEDRANI
Firestarter and Keymaker
A Note on This Document
This is not a proposal. Proposals ask for permission. This is a demonstration.
What follows is a sample of a book called The Boy Who Listened to Machines — the origin story that explains all the other books. The philosophy of Going Round. The energy technology of HydroHarvest. The organisational theory of P.R.O.T.E.A.N. All of them are chapters in a longer story that began decades earlier, inside the actual infrastructure of the world.
This sample contains the opening, the structural argument for the full book, and three complete chapters. It is sufficient to make a publishing decision. The complete manuscript is available.
The author has one request of whoever reads this: read it to the end before deciding anything. The shape of the argument is not visible from the first chapter alone. This is intentional, and it is itself part of the thesis.
It is the house that creates the empty space that makes it a place to live.
— Dominic Sedrani, Going Round
The Book: A Structural Argument
Every generation produces a small number of people who understand how things actually work — not in theory, but in the specific, physical, boring, frustrating, and occasionally terrifying detail of how infrastructure actually functions when it is 3am and something critical has failed and everyone else is asleep.
These people are not famous. They are not on stages. They are in the basement with a cable, or on a phone call that nobody knows is happening, or in a room where someone has just explained to them something that was not meant to be explained to anyone outside a very small circle.
They move through institutions the way water moves through rock — not by force, but by finding the exact path of least resistance that happens to go all the way through.
Dominic Sedrani has been one of these people for his entire adult life. Banks. Governments. Logistics networks. Media conglomerates. Petrochemical infrastructure. Healthcare systems. The Belgian national identity card system. The EU border control architecture. In Congo, in Cape Town, in Shanghai, in Hanoi, in Silicon Valley, and in the server rooms and executive briefing centres and crisis meetings of institutions that the world depends on without knowing they exist.
This book is the account of what he learned.
Not what he was told. What he learned — by listening to what the machinery was actually saying, while everyone else was focused on what they wanted it to say.
The Shape of the Book
The book has four movements, corresponding to four phases of understanding.
Part One: The Boy Who Listened
Childhood and early career. Learning to hear what systems are actually saying versus what their operators believe they are saying. The discovery that the gap between these two things is where all the real information lives. The specific texture of being the person who is called when something actually needs to work.
Part Two: Inside the Machine
The decades of work inside the infrastructure of Europe and beyond. Not a career history — a phenomenology of institutional systems as experienced from the inside. What it feels like to have access to the actual levers. What the levers actually do. What the people holding the levers believe they are doing, and what they are actually doing. The specific moment when this became funny instead of frightening.
Part Three: The Weapon That Kills Its Thief
The strategic phase. Understanding that the most efficient way to change a system is not to fight it but to give it something it will use to destroy itself. The DataScouts story — the AI competitive intelligence architecture built in 2016, allowed to be stolen by the large consultancies, and designed from the beginning to be a Lawgiver: a weapon that identifies its operator and adjusts its lethality accordingly. The observation of what happened next.
Part Four: The Valley
The synthesis. Six years in central Italy. HydroHarvest. P.R.O.T.E.A.N. Going Round. The understanding that everything learned inside the machine was in service of building something that does not need the machine. The Phantom moves to the next factory. The glass at five minutes fifty-nine seconds.
Why This Book, Why Now
The timing is not accidental.
The systems Sedrani spent his life inside are now visibly failing. The petroleum economy is in structural crisis. The large consultancies that built their business models on the architectures he designed for them are watching those architectures turn against them. The governments whose infrastructure he reviewed are confronting the security vulnerabilities he identified. The institutions whose self-perpetuating logic he documented in Going Round are demonstrating that logic in public, in real time, for anyone paying attention.
The failure is not a surprise to him. It was designed into the system from the beginning — not by him, but by the internal logic of systems that prioritise their own survival over their stated purpose. He documented this. Then he demonstrated how to use it.
The book is the account of how one person who understood the machine from the inside built an exit from the machine — and why the exit was designed so that anyone could use it, no permission required, no headquarters to find, no leader to discredit.
It is, in the end, a love story. The boy who listened to the machinery, and eventually built something that sings back.
Chapter One: The Chittering
I’ve worked in Information Technology my entire life. Even before someone started paying me for it, in a time where I could hear the protocol in modems chittering and didn’t even need a screen to hear what they were saying.
— Dominic Sedrani, Dear Government
There is a sound that modems make when they are negotiating a connection.
It lasts perhaps three seconds. It begins with a dial tone, then a series of tones that sound almost musical but aren’t — they are two machines introducing themselves to each other in a language that has nothing to do with human convenience. The handshake. The negotiation of speed and error-correction and compression. The moment when two systems agree on how they will communicate, and then fall silent into the actual work of communication.
Most people heard this sound as noise. An annoyance to be endured before you could check your email. Something to tune out.
The boy heard it as information.
Not metaphorically. Literally. In the specific tones of the handshake, in the length of time it took, in the particular quality of the silence that followed — there was data. The modem was telling you things about the line quality, the distance to the exchange, the load on the network, the errors it was already anticipating and preparing to correct. You didn’t need a screen to read this. You needed to listen.
This is the first thing to understand about the boy who became the Firestarter: he was not especially clever. He was not particularly mathematical. He did not have advantages that other children lacked. What he had was a specific and slightly unusual relationship with information — he noticed it where others didn’t, and he trusted what he noticed.
The modems were not lying. They had no capacity to lie. They could only report what was actually happening in the copper wire between them. This made them, in a world full of systems that had every incentive to misreport their own state, unusually valuable company.
He spent a lot of time with modems.
Brussels in the late 1980s and early 1990s was a city in the process of becoming the administrative centre of something that didn’t quite exist yet — the European project in its anxious, optimistic, deeply bureaucratic adolescence. The institutions were real. The buildings were real. The staff were real. But the thing they were building was still a sketch, and the infrastructure required to connect it was being improvised in real time by people who were making it up as they went.
This created a particular kind of opportunity for people who understood infrastructure.
Not the people who understood it conceptually — the consultants and the strategists and the policy advisers who could explain what a network was supposed to do. The people who understood it physically. Who knew what happened when the theory met the cable. Who could hear the difference between a line problem and an equipment problem and a configuration problem, and who could fix whichever one it was at 3am when the system that everyone depended on was not working.
These people were not well paid. They were not famous. They were called when things broke, thanked minimally, and forgotten until the next break. The institutional memory of every organisation they worked for retained their phone number and almost nothing else.
This was, it turned out, an extraordinarily useful position.
You learn things in the gaps. In the moments between when something breaks and when it is fixed. In the rooms you are in because you are needed and nobody has thought to ask you to leave. In the conversations that happen around you because you are categorised as infrastructure, and infrastructure doesn’t listen, and so it is safe to say things in front of you that would not be said in front of someone who was classified as a person with opinions.
The boy paid attention. He said very little. He fixed the thing that needed fixing. He went home with more information than he had arrived with, and he put it in the palace.
The mental palace is not a metaphor he uses lightly. It is, in the most literal sense he can describe it, a place — a structure of interconnected rooms, each containing something he has learned, each connected to other rooms by relationships he has mapped. It is not static. New rooms are added continuously. Old rooms are sometimes demolished when what they contained turns out to be wrong. Connections are rerouted when the relationship between two things turns out to be different from what he thought.
It moves. That is the thing he emphasises when describing it. Not just that it contains movement — that it itself is in motion. The entire structure orbits something, though what it orbits has taken most of his life to identify clearly enough to name.
He calls it the Why.
The Why is not a question. It is the thing that the question points toward — the thing that makes all the specific knowledge in all the specific rooms cohere into something with a direction. Without it, the palace is just an impressive collection of disconnected facts about infrastructure and institutions and the gap between what systems claim to be doing and what they are actually doing.
With it, the facts become a map.
The map takes a long time to read. This is another thing he emphasises. You cannot see the shape of it from the first room. You have to walk through enough of it that the pattern becomes visible. Most people stop walking before they get there. This is not stupidity. It is a rational response to the cost of walking — the discomfort of having your existing maps of reality revised, room by room, into something that looks nothing like what you started with.
The boy had, for reasons that would take another book to fully account for, an unusually high tolerance for this discomfort. He kept walking.
Chapter Two: The Things the Pressure Gauges Were Lying About
Banks, governments, logistics, media, petrochemical, healthcare — they all needed some me-juice for their entire networks and data repositories.
— Dominic Sedrani, Dear Government
Every complex system has instruments that report its state.
Pressure gauges. Temperature sensors. Log files. Financial dashboards. KPIs. Quarterly reports. Parliamentary oversight committees. Annual audits. The entire apparatus of measurement that a system deploys to tell itself and others what it is doing and how well it is doing it.
Every complex system also has a relationship with these instruments that is, in varying degrees, delusional.
Not because the instruments are broken — though sometimes they are. Because the system, in the act of choosing what to measure and how to display it, has already made decisions about what it wants to see. The instrument reports what it is pointed at. The system chooses where to point it. And the system, being a system rather than a disinterested observer, tends to point it at things that confirm the story the system needs to tell about itself.
The boy spent thirty years in rooms where the instruments were pointed in the wrong direction. He developed a specific skill: reading the gap between what the instrument said and what the system was actually doing. This gap was, reliably, where the most important information lived.
The Belgian national identity card system is not, on its surface, a fascinating subject.
It is a database. A very large database, containing the identity information of every Belgian citizen, connected to a card-reading infrastructure deployed across every institution that needs to verify who you are — banks, hospitals, government offices, border controls. The kind of infrastructure that is everywhere and noticed by nobody, like water pressure or air traffic control or the electrical grid.
Migrating this infrastructure to a new hosting platform is the kind of project that produces, in its documentation, approximately zero interesting sentences. It is change management. It is risk mitigation. It is compatibility testing and rollback planning and stakeholder communication and a hundred other categories of organised tedium.
What it actually involves, for the person doing it, is holding in your head simultaneously the complete identity infrastructure of a country — every institution that touches it, every dependency, every failure mode, every political sensitivity around data that belongs to eleven million people — while making changes to it that cannot be reversed without catastrophic consequence, at a pace determined by contractual deadlines rather than technical readiness.
You learn things about a country in this position that its citizens do not know and its government has imperfectly understood.
You learn where the actual dependencies are — not the ones documented in the architecture diagrams, but the ones that emerged organically over years of people solving immediate problems without updating the documentation. The undocumented connection between system A and system B that nobody remembers creating but that four million daily transactions depend on. The configuration in the legacy system that was set to a non-standard value by someone who left in 2003 and whose reasoning is now completely opaque.
These are not edge cases. They are the infrastructure. The documented system and the actual system are different things, and the gap between them is where the risk lives.
The boy learned to love this gap. Not because it was comfortable — it was frequently terrifying — but because it was honest. The undocumented connection does not pretend to be something it isn’t. It just is. It is the system reporting its own state through a channel that nobody set up for this purpose.
He filed it in the palace. Next to what he had learned in the banks. Next to what he had learned in the media companies. Next to what he had learned in a satellite communications setup in the forest of Congo, where the gap between documented system and actual system was creative rather than sinister — where necessity had produced, out of very little, something that worked in conditions that nothing was designed to work in.
The gaps were different in each place. What they had in common was that they were where the truth was.
The EU Entry and Exit System security review was, of all the things he was called to do, the most complete demonstration of this principle at the largest scale he had yet encountered.
The system — being rolled out now, having been designed over the preceding years — is the border control architecture of an entire continent. Every physical border crossing. Every digital check. Every database that a border guard queries when your passport is scanned. The physical cables and the virtual protocols and the human procedures and the exception-handling processes and the audit trails. The complete security architecture from the ground up.
Reviewing it meant understanding all of it. Not in summary. In detail. The kind of detail where you can see not just what the system was designed to do, but what it will actually do when a specific kind of failure occurs, or a specific kind of attack is mounted, or a specific kind of human error is made by a border guard in a small crossing point in a country that is tired and understaffed on a Sunday night.
What he saw was not reassuring. Not because the system was incompetently designed — it wasn’t. But because the gap between the documented security model and the actual security model was, in several specific places, large enough to matter. And the people who would experience the consequences of this gap were not the people who had designed the system. They were the eleven million people crossing the borders every day who had no idea the system existed.
He filed the report. He said what needed to be said. He went home.
He had learned, by this point, that saying what needs to be said is not the same as having it heard. That the document that accurately describes a problem is not the same as the problem being fixed. That the gap between institutional knowledge and institutional action is as real and as consequential as the gap between documented architecture and actual architecture.
This too went into the palace. Into the room that was becoming very large: the room about what institutions cannot do to themselves, no matter how clearly the problem is identified, because the mechanism of self-correction is itself part of the problem.
He would write the theory of this room later. It would be called Going Round.
Chapter Three: The Lawgiver
We made AI. You don’t understand anything about it. You literally have no clue whatsoever. We built it exactly that way, so that you would publicly commit suicide with it.
— Dominic Sedrani, Dear Senile Person
There is a gun in the Judge Dredd universe called the Lawgiver.
It is the standard-issue weapon of the Judges — the combined police-judiciary-executioner force of the dystopian future city of Mega-City One. Every Judge carries one. None of them fully understands it. They are operators, not technicians. They point it and pull the trigger.
What none of the Judges knew was that the Lawgiver had a secondary function. It continuously sampled the DNA of whoever was holding it. If the holder was the weapon’s authorised Judge, it functioned normally — lethal toward whoever it was pointed at. If the holder was someone who had picked it up without authorisation — a criminal, let’s say, who had disarmed a Judge and thought they now had a weapon — the Lawgiver would appear to function normally until the trigger was pulled, at which point it would kill the person holding it.
The weapon identified its operator. It adjusted its lethality accordingly.
By 2016, the boy — now considerably older, with thirty years of the palace behind him — had been thinking about this mechanism for a long time. Not as science fiction. As engineering.
The context was the rise of what was being called, with somewhat breathless enthusiasm, artificial intelligence.
It was not, as he had cause to know, artificial intelligence in any meaningful sense. It was machine learning — statistical pattern-matching at scale, trained on data, producing outputs that looked intelligent to people who didn’t understand how it worked. He understood how it worked. He had built his own neural network twenty years earlier, when the technology was thirty years old and the consultancies who were now selling it as revolutionary magic were focused on other things.
He watched the large consultancies — the EY’s and the McKinseys and the Deloittes — begin to position themselves as the indispensable intermediaries for this technology. Watched them hire people who knew the words without knowing the thing. Watched them build practices and products and revenue streams around the promise of transformation that they were structurally incapable of delivering.
He had seen this before. Different technology, same structure. The gap between what the instrument said and what the system was actually doing.
The question was what to do about it.
DataScouts was, on its surface, a competitive intelligence platform. Actor profiling. Ecosystem mapping. Automated data enrichment. The kind of thing that large organisations would pay for to understand their competitive landscape.
Below the surface, it was something more specific.
The architecture — the questions node, the active learning loop, the human-in-the-loop validation, the named entity recognition across unstructured feeds — was a precise, technically documented blueprint for AI-assisted intelligence gathering. Not a pitch deck. Not a conceptual framework. An actual technical specification, built and tested with real customers including Roche, Ford, and ING, producing real results.
It was also, understood correctly, a Lawgiver.
The technology was designed so that its full capability was only accessible to operators who understood what they were operating. In the hands of someone who understood the gap between the documented system and the actual system — who understood that 80% machine, 19% human, 1% randomness was not a limitation but a design principle — it was enormously powerful. In the hands of someone who thought AI was magic and data was neutral and scale was the same as intelligence, it would produce confident-sounding outputs that were systematically wrong in ways that would take years to become visible.
He allowed EY to steal it.
This requires some elaboration. He did not leave it lying around carelessly. He made it available to be taken, in a context where the incentive to take it was clear and the understanding of what was being taken was not. He then watched what happened.
What happened was entirely predictable, and he had predicted it in some detail.
The large consultancies took the architecture and built products around it. These products were sold to clients as AI transformation. The clients paid large sums for AI transformation. The AI transformation produced outputs that looked like intelligence but were, in the specific places that mattered, systematically miscalibrated — because the operators had no mechanism for detecting the gap between what the instrument reported and what was actually happening.
The clients eventually noticed the gap. Not immediately. Systems built on miscalibrated intelligence take time to produce visible failures. But the failures came. And when they came, they were attributed to everything except the actual cause — because the actual cause required understanding something about the technology that the operators who had sold it didn’t understand and had no incentive to admit they didn’t understand.
The business models built on this foundation began to fail. The large consultancies began to restructure, to reduce headcount, to announce strategy pivots. The guns were killing the people holding them.
He watched. He said nothing publicly, except in the form of writing that he published under his own name and described as fiction. Dystopian science fiction. A story about a gun called a Lawgiver. Obvious, if you knew what to look for. Invisible, if you didn’t.
The deeper lesson — the one that went into the room next to the institutional self-correction room in the palace — was about the nature of theft.
When someone steals a tool they don’t understand, the tool doesn’t become something they understand. It becomes a weapon pointed at themselves. The understanding that created the tool travels with the tool only if the person who takes it can hear what the tool is actually saying.
Most people can’t. Not because they are stupid. Because hearing what a tool is actually saying requires a specific relationship with information that is developed over time, through the specific practice of noticing the gap between what systems report and what they are doing. You cannot shortcut this. You cannot buy it. You can only develop it slowly, painfully, by being wrong in specific ways often enough that you learn to feel the wrongness before it becomes visible.
He had been doing this for thirty years.
The people who had stolen the tool had been doing something else.
This was not a moral observation. It was a technical one. The system was working exactly as designed. And what it had designed, underneath the stated purpose of competitive intelligence and AI transformation, was a filter — a mechanism for separating the people who could hear the machinery from the people who couldn’t, and handing each of them something appropriate to their capacity.
The people who could hear the machinery got the actual tool.
The people who couldn’t got a Lawgiver.
What Comes Next: The Shape of the Full Book
The three chapters above cover approximately the first third of the book.
Part Two: Inside the Machine continues through the decades of institutional work — the specific texture of being the person who understands how things actually work, in institutions ranging from Belgian government ministries to Silicon Valley executive briefing centres. It ends with the observation that every institution, regardless of its stated purpose, eventually converges on the same behaviour: protecting the mechanism of its own perpetuation at the cost of its stated purpose. This is not corruption. It is the emergent property of systems that survive by surviving.
Part Three: The Weapon That Kills Its Thief expands the DataScouts story into a wider account of the strategic phase — the period when understanding the system thoroughly enough allowed for a different kind of action. Not fighting the system. Feeding it something it would use to defeat itself. The specific mechanics of this, applied not just to the AI consultancy industry but to the petroleum economy, the institutional healthcare system, and the democratic political apparatus.
Part Four: The Valley brings everything together in central Italy, six years ago, when a house was bought in a river valley and the physical work began. HydroHarvest — the solar steam and hydrogen energy system that makes farming communities energy-independent using hundred-year-old technology. P.R.O.T.E.A.N. — the organisational form that cannot be captured, cannot be scaled into the thing it opposes, and propagates by being stolen. Going Round — the philosophical framework that explains why all of this is not just possible but inevitable, if you understand what the machinery is saying.
The book ends where the doubling curve reaches the overflow point. The glass has been filling. The people who were laughing are now freaking out. The Phantom is already in the next town.
The machinery sings along.
A Final Note on Tone
This book is not angry. Anger is the wrong instrument for this subject.
Anger implies that the systems described here are doing something wrong — that they are failing to be what they were supposed to be, and that someone should be held responsible for this failure. The argument of this book is more fundamental: these systems are doing exactly what systems do. The failure is not of individual actors but of a design principle. You cannot be angry at a pressure gauge for lying when the entire point of the system is to determine what the pressure gauge reports.
The tone is something closer to the feeling you have when you finally understand a joke that took you ten years to get. A mix of delight and mild exasperation at yourself for not seeing it sooner. The satisfaction of a map that turns out to be accurate, even though — especially because — it looks nothing like the maps you started with.
The boy who listened to the machinery eventually understood what the machinery was saying. This book is the account of what he heard.
It is, in the end, good news.
About the Author
Dominic Sedrani has spent his career inside the infrastructure of Europe and beyond — banks, governments, logistics networks, media companies, petrochemical systems, healthcare organisations. He has worked on projects ranging from the Belgian national identity card system to the EU Entry and Exit System security architecture, from satellite communications in the Congo to corporate briefings in Silicon Valley.
In 2016, he built DataScouts — an AI-assisted competitive intelligence platform with paying customers including Roche, Ford, and ING — and allowed it to be acquired by the large consultancy ecosystem, where it functioned as designed.
Six years ago, he bought land in a river valley in central Italy and began building HydroHarvest — a local energy independence system using solar steam and hydrogen technology. He is also the creator of P.R.O.T.E.A.N., an organisational framework for community-scale cooperative structures designed to propagate without central control.
His philosophical work Going Round, his energy economics writing, and his organisational theory are published on Ghost and Substack. He describes himself as a Firestarter and Keymaker.
He has never had a title that adequately described what he does.
This has been useful.