(EDITOR'S NOTE: I got AI to write the first draft of this article, relying on the transcript of my coding session within Claude Code inside Visual Studio and a custom skill I developed to replicate my own writing style. Then I used Distro Publisher, our official MCP server, to file the story as a draft directly from Claude Code to my newslode. I then edited the draft in DistroVerse's editing interface and checked all the facts before publishing.)
We built a pretty major feature this week, multi-user collaboration on newslodes, which catches us up with WordPress, Substack, and Ghost in an area that matters. What surprised me wasn't building it. It was how easy it was to be wrong, and how little that cost. I don't say that as a brag. I say it as a realization.
The feature lets a newslode owner invite collaborators, Editors and Viewers, who sign in with their own free accounts while the owner's subscription covers the newslode. Same arrangement Ghost and Substack use. The changeset is about a thousand lines across the backend, the database, and the editor.
I made two design calls during the build that turned out to be wrong. Both got fixed in minutes.
The first was on me. In the original planning conversation I'd treated collaborators as a free capability for everyone. After Claude wrote up the plan, I went back and added the thing I'd forgotten:
"I was more focused on the account type/tier... I was thinking that this should be a perk for users on the corporate plan or enterprise, not available on free or pro plan."
Claude rewrote the plan. A flag for collaborators got threaded through our pricing tiers, the default set to off everywhere except Corporate and Enterprise, and the Pro and Free invite form became an upgrade prompt. Twenty minutes.
The second one was Claude's. After the first round was working on our test environment, I poked around and realized the collaborators panel had been built into the user's general account settings page, the room you go to change your password or your email. Wrong room. These collaborators are scoped to a single newslode; managing them belongs inside that newslode, not in your generic account drawer.
I sent a short message:
"since the collaborators are specific to a newslode, would it make more sense if the Collaborators were on the Newslode settings page?"
Claude agreed and moved it.
This part is a little surreal. Imagine a building contractor installed a major entryway on the wrong side of the building. You point it out. They just move it. Same day. No change orders, no eye contact about who's paying for the demolition.
That changes the calculus of building. The reason teams convene committee discussions before committing is that the cost of being wrong is high. A wrong door takes weeks to redo; a wrong paywall takes a sprint. When the cost of being wrong drops to minutes, you stop convening committees. You build, look at it, change what you don't like.
The flip side is that nobody else is in the room. I'm the only person looking at this thing. Claude doesn't second-guess me when I say "make it Corporate-only." It just does it. If the call is bad, the bad call goes out.
Mostly the calls have been right. The misses took one sentence each to fix.