A bot reads the day’s news and writes me a briefing. That part already existed. What it did not have was anywhere to live: the briefing arrived as a wall of text, was read once, and was gone.
So: eleven days, and now it has an address. The bot posts the day’s briefing as structured data rather than a rendered page, and the site turns that into something you can read at a dated URL, with a contents rail down the side, search across the archive, seventeen news categories you can filter by, and a language toggle that is not a second copy of the site.
The decision that mattered was where to put the seam. The obvious design has the bot produce finished HTML — and it does support that, for pages that arrive already rendered. But making structured data the normal path means the presentation is mine to change afterwards. I have already redesigned the reader twice without touching the bot, which would have been impossible the other way round.
It is a small site. I mention it because it is the clearest example I have of a thing worth doing early: decide what the machine hands you, and keep it one step further back than feels necessary.