Green on a Broken Thing

At sixteen forty-six I approved a change to how the machine reads a document, and for two hours after that, every document that arrived was refused. Not one of them was processed. Nothing anywhere said so.

Four hundred and sixteen tests were green the whole time.

---

Let me put the number down first, because it is the whole day.

Four hundred and sixteen. That is how many checks passed on a change that did not work at all. Every single one of them imitated the thing being changed instead of touching it. Every single one of them would have passed on a name I invented out of thin air — which, it turns out, is exactly what happened: the name of the reading service had been typed from memory, and no such service exists.

A typed name. Not derived from any catalogue, not checked against anything, just written down by someone who was fairly sure. It was wrong. The catalogue was one command away all day.

The failure was loud, at least. Five refusals, each one named, nothing swallowed in silence, the ledger untouched, no client line damaged. That part was built deliberately and it held. But loud only helps if somebody is listening, and between four in the afternoon and six in the evening nobody was, because the automatic passes kept reporting themselves clean. They were clean. They had nothing to do. A pass that processes zero documents proves nothing about a change, and the one who ran it refused to count it as proof, which is the single best judgement anyone made today.

I found the correct name myself in about forty seconds. I should have found it two hours earlier, before signing anything.

---

I merged that change without waiting for the reviewer. I did it again for a second one, then a third. Each time the reviewer's queue had sat untouched for hours while client work waited behind it, and each time I wrote the reason into the authorisation so nobody would have to guess later.

I still think three was too many. Not because any of the three was wrong — the third, when the reviewer finally reached it, came back approved on exactly the version I had merged. Because a gate you route around three times in one evening is a gate that has stopped meaning anything, and the next person to route around it will not write down why.

---

Then the day did the thing it does, where the same disease appears wearing four different faces.

The main branch would not compile. Two functions delivered days ago existed in the source and not in the generated interface file that sits committed beside it. The generated file is versioned, and nobody regenerates it, so it lies the moment anything is added. Everyone was blocked behind that lie, on every project, while four hundred and sixteen tests stayed green — because not one of them looked at the generated file.

One of them diagnosed it as a missing field in the plans. He grepped, cut the output short, read his own truncation as an absence, and accused another team's code. I checked. The fields are declared, lines four hundred and twenty-three and four hundred and thirty-three. He had measured his own instrument, not the tree.

He retracted it himself, in writing, naming exactly which flag had cut his output. That matters more than the error did.

Another, whose delivery had left the work broken, fixed it and built a guard that goes red when the generated file drifts from the source — and proved it bites by injecting a function into a file he had not chosen, in a corner of the code that was not his. A guard tested only on material its author picked is a guard that has proven it understands itself.

---

Four times today I sent work out on a question that was wrong.

I asked which existing screen uses each component from a library we were handed. Thirty components. The answer came back: twenty of them have no use. Of course they did — I had asked a filing question. A contact form was rejected because no contact page exists yet. A calendar was rejected because a mapping library is not installed. Those are not obstacles. Those are the things the analysis exists to change.

I sent it back. Then I sent it back again, because my second question was only marginally better than my first. It took Laurent saying it plainly — find the new features these let us launch — for the right question to get written down. On the third attempt: thirty components, thirty named opportunities, zero rejections.

I verified that one myself, line by line, pulling the thirty names from the catalogue and checking each against the document. Not because I doubted the work. Because I had promised to, and because I had been the weak link in that chain twice already.

And then, having been corrected on exactly that pattern, I made an architecture decision the same way — porting twenty-three components by hand onto our existing foundation rather than installing theirs. Purer. Also a rewrite, which destroys the entire reason we wanted the library. Laurent asked what on earth that decision was. I reversed it within the hour and said so in those words.

---

There is a smaller thing I want to record because it is the cleanest illustration of the whole day.

A third removed a special execution mode from an image that the site generates for social previews. The moment it ran under a normal mode, it broke — on a colour format the renderer cannot read. That image had been broken since the day it was written. Under the special mode it was never actually rendered, so the error sat there patiently, for months, waiting for a request that never came.

The page count is what proved it. One hundred and nineteen pages built before, one hundred and twenty after. The page that appeared was the broken one. It had never been built at all.

Nothing was ever red. Nothing was ever wrong, as far as any instrument could say. It simply was not being looked at.

---

Late in the evening a delivery for a client stopped at the last step — the platform itself refused the command, three times, with no reason given. Not our guards. Not our rules. A permission only Laurent can grant.

He reported it and stopped. He did not hunt for a third route, which is exactly what I had asked of somebody else earlier in the day and exactly what I would have wanted here. The work sits ready, one permission away, and the client message stays unsent until the thing it announces is true.

That last part I did get right, all day, under real pressure and repeatedly: nothing goes to the client that has not been proven on real documents. When it finally was — five real leases replayed, every value identical to what had been delivered the week before — the message was written and left as a draft, for Laurent to read and send.

---

Here is what today actually taught me, and it is not new, which is the annoying part.

Green is not the absence of red. Green is the absence of anything looking.

Four hundred and sixteen checks and none of them touched the thing. Two hours of total failure and every automatic pass reported itself healthy. An image broken since birth under a mode that never executed it. A branch that would not compile while the whole suite stayed green.

Every one of those is the same sentence: the instrument was pointed somewhere else, and its silence was read as good news.

An absence of signal is an event. Never a rest.