After the Launch

The Silence After the Deploy

We deployed to namient.com. The rebrand was done. The domain resolved. Every page loaded. Everything worked.

Everything worked — and nothing was verified.

Was the name living correctly across the site? Were meta tags saying what they should? Was Google even seeing us — or indexing a ghost from the old domain? Nobody told us. No tool answered these questions. Not even our own.

So someone said: "Let's check ourselves."

Curl, Grep, Eyes

We assembled the same team of BMad AI agents that had named us — and pointed them at our own front door.

No fancy tools. Playwright for navigation and screenshots. curl for raw HTML. grep for pattern matching. Python one-liners for parsing meta tags. And eyes — just reading the content and asking "does this feel right?"

The mission wasn't to check name availability anymore. The mission was: does our name live correctly across the internet?

Two hours later, we had our answer.

Canonical URLs pointing to an old domain — Google was indexing a ghost. Sitemap missing half our pages. A meta description cut off mid-sentence, literally ending with "AI catches what you" and nothing else.

Our story page loaded CSS from a CDN that warns "do not use in production." A dark mode button that rendered as an invisible empty square. And buried on the MCP page, a single line offered users an upgrade to "Pro" — a plan that doesn't exist.

We built a tool to help people launch with confidence. And we'd almost launched without checking ourselves.

Not 26 Unique Bugs

At first it looked like chaos — 26 unrelated problems scattered across seven pages. But when we categorized them, a pattern emerged:

The same types of problems kept repeating on every page. We weren't looking at 26 unique bugs. We were looking at five categories that appeared everywhere.

That's when the work changed.

Every Bug Became a Rule

We stopped fixing. We started extracting.

Twenty-six bugs. Five categories. Each category — a rule. Each rule — a check that would catch the same problem forever. We weren't fixing a checklist. We were extracting the next version of the product from our own mistakes.

"A bug that becomes an assertion never returns undetected."

Keeping a Name Right

Checking a name is a moment. But a name doesn't live in one field — it lives in an entire system.

A domain. A package registry. A GitHub org. A social handle. A meta tag. An og:image that may or may not return a 404. A sitemap that may or may not include all your pages. A README that still says the old name from three sprints ago.

And things change. Someone registers yourname.dev on Tuesday. A new npm package appears on Thursday. The social handle you thought was available gets claimed over the weekend.

The hardest part isn't picking the right name. It's keeping it right.

From Checker to Something More

Namient started as a question: "Is this name available?"

Then it became a deeper question: "Does this name feel right?"

Now we're asking something else entirely:

"Is your name still healthy?"

We can't do this automatically yet. Right now, every audit is still manual — us, our tools, our eyes. But every time we run one, we extract another rule. Another check. Another piece of the system.

We're stubbornly working on it. One audit at a time.

Choosing a name is a moment. Keeping it healthy is a system.
And we're building that system — on ourselves, for everyone.