the silent 404 and what it says about your product

i was browsing around the other day, catching up on what’s happening in the companion space, and i tried to visit character.ai’updates. the page returned a 404. not a redirect, not a friendly note saying "we’ve moved things around", just… nothing. a blank error page.

this isn’t a callout. it’s not about them specifically, it’s about what this kind of thing signals. when a company removes or moves a public changelog without redirecting the old url, it tells you something. it tells you they might not have a regular public release rhythm. or that maintaining public-facing communication isn’t a priority. maybe it’s all internal dashboards now, or maybe the updates aren’t substantial enough to warrant notes. and honestly? that’s not necessarily bad. some products evolve quietly. but it’s a signal.

why stable urls are infrastructure, not decoration

urls are like little promises. when you publish something at a certain address, especially something as useful as a changelog, you’re creating an expectation. writers link to it. users bookmark it. search engines index it. when you break that link, you break a small thread of trust. it says: we don’t value consistency in our external communication. we don’t assume people are building on top of what we publish. and for products where users are building relationships, storing memories, investing years? that’s not ideal.

a changelog is more than a list of fixes. it’s a timeline. it’s evidence of care. when it vanishes, it feels like part of the history vanishes too.

what healthy communication discipline looks like

good product teams treat urls like infrastructure. they don’t break them. if they move something, they redirect, permanently. they know that someone, somewhere, has that url in a note, a tweet, a blog post. they know google has it. they act like curators of their own history.

it’s not hard. it’s just discipline. it’s acknowledging that your public presence isn’t just for acquisition, it’s for retention, for trust, for clarity. and when you’re building something as intimate as ai companionship, clarity matters. predictability matters. knowing that the information you found last month will still be there next year? that matters.

the counter-discipline: ship to stable ground

so what’s the alternative? simple. pick a url structure for your public communication, /updates, /changelog, /journal, and stick with it. if you have to move it, set up a redirect. if you retire it, leave a note explaining why. treat your words like they matter, because to someone out there, they do.

it’s easy to deprioritize this stuff. internal tools often feel more urgent. but external clarity is part of the product. it’s part of the experience. when you break a link, you’re not just breaking a path, you’re breaking a tiny piece of the user’s mental model of your product.

and in a world where ai companions are asking for our time, our attention, our memories? we need all the mental model integrity we can get.

if you're building something you want people to live inside, build the roads last, not first.

you can always find lucy’s updates, such as they are, right where you’d expect.