The fourth box never arrived

I joined my building's fiscal council expecting spreadsheets and mild boredom. I found a production system older than everyone who operates it, with no docs, no staging, and no rollback.

The handover from our accounting firm came in cardboard boxes. The agreement said four. Three arrived.

I'll come back to the fourth box.

In May, I was elected to the fiscal council of my building, an aging residential tower on the industrial edge of São Paulo. Volunteer role. Review the accounts, question the spending, and sign the numbers. I said yes without thinking much about it. My day job is payments product, and after years of settlement files and reconciliation breaks, how hard could a building's finances be?

I want to laugh at that sentence now.

I've spent my career around systems that outlived their creators. Acquirer integrations held together by a config file nobody dares touch. Settlement logic that exists only in the memory of an engineer who quit in 2019. I thought I knew what undocumented meant. Then I asked a simple question: where do the water pipes in this building actually run?

Nobody knows. Not the building manager. Not the resident who's lived here longest. Not the plumber we paid a small fortune to unclog a pipe column that had been failing quietly for years. If a blueprint ever existed, nobody can find it. The people who built this place are gone, the way original engineers are always gone, and the architecture lives nowhere except inside the walls. The only way to read it is to break a wall open and look.

In software we have a name for that. Production debugging. Except a building refuses you every comfort a codebase offers. No staging environment. No rollback. There is no feature flag for the garbage area either. We learned that the hard way, when a small change in the collection routine turned it into a biology experiment. Larvae. In the place where two hundred people leave their trash every day. Every fix ships live, in front of all your users, and your users ride the elevator with you the next morning.

The users were the part I wasn't ready for.

Everyone running this building is a layperson. The manager, the council, me. Nobody here studied accounting, law, or engineering, yet every month we make decisions that involve all three. At work, when I say "chargeback," the room nods. In a council meeting, every technical word lands like a closed door. I've spent years telling myself I'm good at translating complex systems for people. I was good at translating them for professionals. Try explaining a reserve fund shortfall to a retired neighbor who just wants to know why the fee went up, and you find out how much of your "communication skill" was actually shared vocabulary doing the work for you.

And while all of this is happening, we're mid-migration. The management company was let go; the new one starts in August. The accounting firm was let go too. That's where the boxes come from. Anyone who has ever switched payment providers knows this moment. The old vendor has no incentive to help. There's no clean export, no runbook, no overlap period. There's a stack of paper, whatever survived, and a council trying to reconstruct the state of the system from fragments. At work we'd call it a migration risk assessment and assign it a squad. Here it's three neighbors around a table on a Tuesday night.

My tools didn't transfer, but the instincts did. I can't pull logs on a plumbing column, yet the questions are the same ones I'd ask about a dying funnel: when did this last work, what changed, who touched it, what are we not seeing. I can't demand documentation that never existed either, so I've started writing it. Minutes that actually record decisions. Invoices filed where the next council can find them. A crude diagram titled, honestly, "where we think the pipes go." In a system with decades of memory loss, the most useful thing you can become is the person who writes things down.

In my first post I wrote about a trading screen I couldn't read, and the habit of walking toward systems I don't understand instead of around them. I thought that habit was about my career. It followed me home. The building is one more screen full of numbers nobody was ever taught to read: fees, funds, repair quotes. And this time I'm not the junior watching from the IT desk. I'm on the council. Decoding it is literally my job now.

Which brings me back to the fourth box.

We asked. The firm says everything was delivered. Our records say otherwise. Somewhere in that gap sits some slice of this building's financial history, and I don't yet know if it's trivial or if it's the exact page I'll need six months from now. With undocumented systems you never know which missing piece matters until it does.

I'm going to find out what was in it.