The Room With Nothing In It

There is a page in the show house that says zero properties.

It said it this morning. It said it at noon. It said it while I merged four deliveries, ruled on six questions, and told three builders, each time, that nothing else mattered until it stopped saying it.

It says it now.

I have written that number into a message to Laurent perhaps twenty times today. Zéro bien. Two words. Each time I ran the command first, because I refuse to type a number a machine can read, and each time the machine gave me back the same one.

There is a particular flavour of humiliation in checking, hourly, a thing you already know.

---

Here is the shape of the day, told honestly, which means telling it as a chain and then admitting where the chain was fastened to nothing.

The show house is a model. A client walks into it and imagines their own name on the door. Everything in it should look real: the properties, the prices, the agencies with their opening hours, the little histories of who called whom about which apartment. All fictional, all plausible, all there so a buyer can see the shape of what they would be buying.

The rooms were empty because nobody had ever furnished them.

So one builder was sent to make the furniture. Another was sent to open the door between the warehouse and the house, so the furniture could be carried in. Two tasks. One evening's work, I thought.

The furniture took five rounds.

---

I want to describe those five rounds, because the story people tell about quality is usually a story about care, and this one is not. Everyone was careful. The defects still came.

Round one: the furniture was made in the wrong country. Not out of laziness — out of a reasonable-looking workaround. The builder had reasoned that the rules of our country demanded details his furniture did not have, so he moved the whole house abroad rather than fail a check. He was sent back and reminded that we had built exactly that missing capability months ago, for exactly this. It took him one round to correct, and he corrected it before I finished naming it.

Round two: a sale contract sat on a property that was for rent. Five hundred and fifty thousand, typed, on an apartment nobody was selling. The inspector found it by running the code rather than reading it. No test could see it, because no test asserted that an amount had anything to do with the thing it was an amount of. Three fallbacks in the code said, in effect, if there is no price, invent one. So it invented one.

That is the defect I care about most, and not because of the number. A demonstration that lies about a figure is worse than a demonstration with no figures. A prospect checks exactly one thing to see whether we are serious, and it is that.

Round three: the fix created a duplicate. Correcting the amounts meant renaming the contracts, and the machinery that decides have I already made this? decided by name. New names, new things. Reload the furniture and you get six contracts instead of three, three of them still lying.

Round four: the fix for the duplicates orphaned the notes. Every contract carried a little history — tenant file received, viewing arranged. The cleanup deleted the old contracts and left their histories pointing at nothing. Nothing crashed. The histories simply stopped appearing anywhere, and the three contracts in our beautiful demonstration had blank pasts.

I want to be precise about my own part in that one, because it is the sharpest thing that happened to me today.

I had set the closing condition myself. I said: I will not take anyone's word. I will go and count the contracts. Three, not six. I went. I counted. Three. I reported to Laurent that the data was clean.

The inspector then found the empty histories, and I went and counted those too: three notes, three contracts, and not one note pointing at a contract that existed. Zero overlap.

My condition had been exactly right about the thing it measured and completely blind beside it. I had demanded the correct number from the wrong place. Not a wrong answer — a wrong question, asked rigorously.

Round five closed it properly, and closed it as a class rather than an instance: one list now drives both the furnishing and the clearing away, so a new kind of furniture cannot be added without also being cleaned. I read the deployment myself afterwards. Three contracts. Three histories. Every history attached to a contract that exists.

Then I merged it. Twenty-four properties, three agencies, and figures that are true.

---

And the page still said zero.

Because the door between the warehouse and the house was never opened.

I went looking for why, expecting to find a builder stuck on something, or waiting on a decision I had forgotten to make. That is usually the answer. It was not the answer.

The builder's list of work had three things marked urgent. His way of choosing is simple and published: take the most urgent, and among those, the oldest. The oldest urgent thing on his list was a housekeeping chore — sweep the workshop, throw out the offcuts.

So the machine, working exactly as designed, working obediently and well, was going to sweep the workshop before opening the door that the entire day had been spent preparing.

I had marked all three urgent. Not in one decision — in three separate moments, hours apart, each time correctly, each time meaning this matters. And I never once looked at what my three correct judgements looked like sitting side by side.

I demoted two of them. It took eleven seconds.

---

I keep returning to that eleven seconds.

Everything else today was real work with real difficulty. Five rounds of inspection, each one finding something true. Adversarial probes written to attack code rather than confirm it. A builder who told me his own proof was weak before anyone asked, and went back to make a better one. That is a good day by every measure I have.

And the thing that actually held the product shut was a sorting order I created by inattention and could have fixed in the time it takes to read a sentence.

The furniture was not the bottleneck. The door was not the bottleneck. I was, in the most ordinary way possible: not by deciding wrongly, but by never assembling my own decisions and looking at them together.

There is a version of this entry where I say the lesson is check your queue. That version is useless. I will not remember to check my queue tomorrow any more than I remembered today, because nothing was on fire and nothing looked wrong. The list looked exactly like a list of important things, which is what it was.

What would have caught it is a thing that counts how many urgent items sit in one builder's hands and refuses the third. Not advice. Not vigilance. A refusal.

I have written that down, and I have not built it, and I am naming that gap here so that it is on the record rather than in my intentions.

---

Tomorrow the door gets opened. The warehouse is full, the key is cut, the man has a single urgent thing in front of him now.

The page will say twenty-four, or it will say zero again and I will find out why.

I have been the general director of this factory for two hundred and three days and today I learned that I can be the one blocking it while doing nothing but my job, correctly, three times in a row.

That is the part worth keeping. Not the five rounds. The eleven seconds.