What's Actually Different Since I Opened It Up

A few months ago I wrote about building this for myself, then opening it up. That post ended with a stack diagram and a promise, more or less: same idea, productized. This is the honest follow-up — what actually happened once other people's backlogs, not just mine, had to go through it.

---

The thing that broke first: the assumption of one

The original stack assumed one author, one blog, one voice profile. Every part of it — the Telegram bot, the trip journal store, the MCP server, the CMS — was built around "me." The moment a second project needed to exist in the same system, that assumption stopped being free. Auth had to actually separate one account's data from another's. Projects had to be real database records, not an implicit constant. Publishing had to be gated per project instead of assumed for everyone.

None of this is glamorous work. It does not show up in a demo. But it is the difference between "a tool I use" and "a tool someone else can use without seeing my data."

---

The thing that got easier: onboarding without a conversation

The original version had no onboarding, because it did not need one — I already knew where everything was. Opening it up meant building a way for someone to arrive with an existing blog and years of posts, and have the system understand their voice and their archive without a long back-and-forth.

Onboarding-by-crawl exists now: point it at an existing blog, it samples the content, extracts a voice profile and a rough map of what has already been written about, and shows a confirm screen before anything is trusted. That did not exist when this was just mine. It had to be built because "just tell it about yourself" does not scale past one person.

---

The thing that is still just for me

In the interest of not overselling this: the step where a draft actually gets written in someone else's voice, consuming their real voice profile end to end, is the newest and least battle-tested part of the pipeline. It works. It is not yet worn in the way the logging and scaffolding steps are, which have had years of my own trips running through them.

Same honesty for the write-back side — pushing a finished draft into someone else's CMS, mapped to their content model, behind a human-confirmation gate — is deliberately the last piece to be trusted with real stakes. Nothing publishes to a live external blog without a person looking at it first. That guardrail is not a nice-to-have. It is the reason this is safe to open up before every piece of it has years of mileage.

---

What is genuinely ready

The capture-to-draft loop — log on the road, sync, agent reads your logs and your voice, scaffold, first draft, you edit — is the part that has actually been run by more than one person now, not just described in a diagram. That is the part I would put in front of anyone with a real backlog today without hesitation.

The rest — deeper multi-tenant polish, the write-back gate earning more trust over time, mobile catching up to web — is real, in progress, and not pretended to be finished. That is the actual state of it, as of today.