31 batches and 1,642 creatives went into one catalogued library. Then the live library quietly showed 7 of them, and the thumbs-up learning loop starved after 212 ratings. What a creative registry needs beyond “put everything in one place”.
A product launch for us touches about twenty surfaces. We turned it into a durable publication run with preconditions and a post-write read-back. 237 runs later, a quarter failed, and almost none of the failures were in our logic. Here is what failed, the six launch bugs that each became a hard rule
A Sunday job crawls our marketplace reviews, emails a digest and turns new five-star reviews into social posts. For a month it reported “0 new reviews” while customers wrote 46. Here is the data model, the three bugs, the gate that rejected seven five-star reviews, and the alert I should have built
Nine weeks of a weekly SEO job that recommends exactly three fixes: the real numbers, the title fix it called a win while clicks fell, the three weeks it repeated itself, and the verdict rule I would build first next time.
In one September week our daily ad spend went from a quarter of the budget’s daily rate to 4.6 times it, with nothing broken. Here is the guard I wrote afterwards, the ranking code it runs every three hours, the cents-versus-dollars bug that briefly multiplied our account cap by 100, and the weekly
Three months, 12,131 logged agent tasks, ten named AI teammates and 124 rule files. What the activity log says about running a company’s operations from a code editor: where ownership, handoffs and cost attribution held up, and where they quietly did not.
