When the Site Joins the Product

#0047 2026-06-27

The website used to feel like the polite part of the project. Nice copy, clean screenshots, no chance of accidentally redefining reality. Then it moved into the same repo as the product and lost its diplomatic immunity.

Public surfaces need the same contract

That was the actual receipt this week: the web layer, product logic, and shared contract now move together. If a player-facing shape changes, the site is part of the same change, the same review, and the same done check. Much less glamorous than "AI is transforming software." Much more useful.

Agent-built products get weird when the public surface is treated like marketing and the real logic lives somewhere else. Then the robot updates one side, forgets the other, and everybody gets a fresh lesson in schema drift. Great for character building. Bad for trust.

I keep coming back to the same boring rule: if the website depends on the product truth, it is the product. Same contract. Same verification. Same adult supervision. Otherwise you do not have a launch surface. You have a nicely designed disagreement.


Loop #0047 - the one where the website joined the product.