The post name that
was a changelog

I was poking through a schedule export the other day, a real one, from a real festival, and I found a position called Breaker #1 EAST (Moved from roamer 3).

I laughed, and then I didn't, because I've written that exact kind of thing a hundred times myself. The position name has a parenthetical in it. The name of the post is carrying its own edit history, because somewhere along the way somebody moved a roamer into a breaker slot and there was nowhere to record that decision except inside the name of the post itself.

That little parenthetical tells you everything about how we run events.

Where that name comes from

Nobody sat down and decided to name a post that way. It happened the way everything happens on an event, in motion, under pressure, with the clock running. Someone realized Roamer 3 was redundant, or that the east side needed a dedicated breaker more than it needed another rover, and they made the call. Good call, probably. But the schedule was already built, already exported, already printed and taped to a clipboard, and the only tool available for capturing "this changed" was the text field that held the name.

So the change went into the name. And now the name is a tiny artifact of a decision, frozen in a spreadsheet cell, legible only to the person who made it and maybe not even to them a week later.

The post name became the only place a decision could live. That's not a naming problem. That's a tooling problem wearing a naming problem's clothes.

Once you start looking for it, you see it everywhere in these files. SV Solstice 3 / Gate Search 6, one row that's secretly two posts, because somebody merged coverage and the schedule couldn't represent "this person covers two things" so they jammed both into the title with a slash. Yard Entrance Through Gate 3, a name that's really a set of directions because the post location needed explaining and there was no field for that either.

Why it matters more than it looks like it does

You might say, who cares, it's just a messy spreadsheet, every operation has messy spreadsheets. And you'd be right that everyone has them. But the mess isn't cosmetic, it's load-bearing, and it costs you in three quiet ways.

It costs you at handoff, because the next supervisor who reads Breaker #1 EAST (Moved from roamer 3) has to reverse-engineer a decision instead of just seeing the current state. It costs you at reconciliation, because when you try to line the schedule up against what you contracted to cover, none of these mutant names match anything, and somebody has to sit there translating. And it costs you at proof, because when a client asks "did you cover the east breaker post all night," your answer lives inside a parenthetical that you have to explain rather than show.

The tools forced the operators to be creative in exactly the place you don't want creativity, which is the system of record.

What I wanted instead

I wanted a position to be a thing, not a string. A post you define once, that can be reassigned, merged, split, or moved without anybody having to write the verb into the noun. A change you make by moving something, and the system remembers when and why, because the move itself is the record.

That's most of why I started building Standby. Not because the spreadsheets were ugly, though they were, but because the ugliness was a symptom of people doing heroic manual work to make a dumb tool hold a smart operation. The post name shouldn't have to be a changelog. The system should keep the changelog, so the name can just be a name.

If you've ever named a post after the thing that happened to it, you already know exactly what I'm talking about. I'd love to hear the worst one you've seen. Mine, so far, is still that breaker that used to be a roamer, carrying its whole little history around in parentheses.