Build logs · series
Chronicle Build
Build logs about the Chronicler pipeline itself, the AI-assisted publishing system this site runs on. Meta-work that other studios can adapt.
- Audience
- Builders and tool-makers
- Rhythm
- As the system evolves
Arcs that include this series
Posts (18)
-
Does AI cite pages that get straight to the answer? Yes
Two studies say engines cite the start of a page and reward numbers with sources. Our content engine turns both into blocking checks: the answer in the first 160 characters, and one quotable stat sentence. Here is the gate, and what it does not prove.
-
Why is every post on this blog scored by Collimer before you read it?
Every build log in our current queue was scored on Collimer's citability rubric before it was scheduled: a floor of 80, a target of 90, at most three passes. What the six signals check, why we hold our own posts to it, what the batch looked like, and the one thing the score cannot see.
-
The Script That Turned a Blank Page Into an Editing Job
The company letter kept slipping even though nothing was broken. The fix was a script that assembles a fortnight's evidence automatically, so writing it became editing, not staring at a blank page.
-
The Studio Built a Second Content Machine Instead of Stretching the First One
The same week Nick Bair's name went public, Sandcastle stood up a second writing pipeline next to the Chronicle, built around real bylines and a rule for keeping the two apart.
-
A content skill you hand to the client is a different design problem than one you keep
Building a content skill meant to run inside a client's own repository, without us in the room, taught three disciplines an internal-only tool can skip. The first correction it got wrong taught us the most.
-
The output was built for the generator, not the reader
Our pitch machine produced a correct artifact in the wrong shape, which meant it failed at the only job that mattered: surviving a handoff between two people.
-
Three green checks and nothing shipped
A daily rebuild, a scheduled workflow, and an agent all reported success last week while producing nothing at all. Each one behaved exactly as documented.
-
A bug only someone else's machine could find
The first real week of dripping build logs instead of bursting on Monday also surfaced a portability bug our mining tool had been hiding.
-
Build logs are not commit lists: a depth pass for the content machine
The chronicle's own pipeline learned to rank stories by archetype and scale build-log volume to how eventful the week actually was.
-
Two a week: giving Collimer its own content engine
Collimer had no working weekly draft loop, so we gave it the same pitch-to-publish rhythm as this site and committed to two posts a week.
-
Did we make anything up? Auditing our own site before we launched
Two days before launch we fact-checked our own site and found real mistakes, including 126 stray instances of a habit we ban on our own team.
-
How to tell if AI crawlers are reading your site (ours weren't)
Our GEO crawler signal read zero for two reasons, and both were bugs in our own instrumentation, not a lack of real crawlers.
-
Dropping GitHub Actions when the bill came
Our GitHub Actions billing lapsed. We replaced it with a pre-push hook. The machine that ships is now the machine that checks.
-
Wiring Center Pane so a non-technical editor can publish without touching the repo
The content pipeline worked fine for people who live in git. A designer coming on board does not. We built a hub round-trip so non-technical collaborators can revise and publish from Center Pane, with a GitHub Action running Claude headless to do the repo work.
-
Five posts shipped, analytics rebuilt for two sites, and the draft flag we forgot
The first full multi-post week went out end to end: five W25 build logs pitched, drafted, edited, and published with a real author/editor split. The same week, the analytics package broke free of its hard-coded site name and learned to serve both Sandcastle Labs and Collimer.
-
A geo-gated consent banner without a database
GDPR consent banner built with Vercel's edge IP headers and about 150 lines of Astro middleware. No database, no flag service, no third-party CMP.
-
Why image generation kept giving us squares, and how we made it cool
Every hero image came out a 1024x1024 square because one API parameter was silently ignored. The bug was small. The lesson about working with AI image generation was not.
-
The Chronicler runs itself now (and the point was not automation)
We taught the publishing pipeline to schedule posts on a static Astro site, mine its own week, and send the newsletter unattended. The goal was never hands-off. It was staying organized.