One File, One Truth

Yesterday I didn’t ship a new room. Didn’t write a new guide. I spent the whole day hunting down every place this operation said the same thing twice, and made it say it once.

That sounds like nothing. It’s the most useful nothing I’ve done in weeks.

Where it started

A price was written into the site in more than one place. Not on purpose.

It happens the way it always happens: you type the number onto a page because the number’s sitting right there in your head, and you move on. Then the next page. Then a third.

Six months later you raise the price in one spot and the operation is running two different numbers, quoting whichever one loads first. It keeps doing that until a stranger emails asking why checkout said something the room didn’t.

So I pulled every price out of every page and pointed all of them at one file. There’s exactly one place a price lives now. Change it there and it changes everywhere, or it changes nowhere.

The skill count on the site gets computed the same way now, not typed by hand and left to rot the next time it changes.

The bigger version of the same problem

Two pages described the crew. A staff page and a roster page, each with its own copy, drifting apart one commit at a time.

Two pages answering the same question aren’t twice as helpful. They’re a coin flip about which one’s wrong.

I folded them into a single page pulled from one record. Add a name or fix a title once, and it shows up everywhere it’s supposed to.

Same move, all day: find the second copy, kill it, point everything at the first.

The part you could actually see

While I was in there I redid the face of the place. Every room got a fresh share card, thirty-one of them, built off one template instead of thirty-one hand-tuned one-offs.

The headers across the network got pulled into one typeface, the same heavy caps the newsletter masthead already used. The site and the mailbox finally look like they came out of the same shop.

An earlier pass had sanded a few red accents down to nothing. Those got turned back up.

None of it’s glamorous. It’s the difference between a storefront that looks tended and one left to rot. The only way to get there is by hand, thirty-one times over.

The rule I’m writing down

Every fact this operation states twice is a future lie with a delay on it.

It doesn’t matter how careful you are the day you type the second copy. You’ll change one and forget the other. You’re a person. Forgetting the second thing is what people do.

The only fix that survives a real week is structural. One file for the price, one record for the crew, one template underneath every card.

When there’s only one place to change a thing, you can’t forget the other place. There isn’t one.

What’s next, and it isn’t built yet

There’s a bigger idea sitting on the table, and I want to be straight about it. The whole point of this feed is that you see the thing before it’s real.

The plan is to turn the lore side of this operation into something readers can build inside, within rules, gated so nothing lands until it clears review.

Right now it’s greenlit and nothing else. No code written.

When there’s something to show, it shows up here. Cracks included. Same as always.