The build log now drafts itself, and still waits to be asked

This entry exists because it is the thing it describes. It was produced by the content engine, committed to a branch, and opened as a pull request against this site's own repository. Nothing published it. Somebody read it and merged it.

That distinction is the whole design. The constitution permits autonomous merges into internal repositories that are git-reversible and not attached to a live public deployment, and expressly does not permit them into any repository that auto-deploys to a public site. This one does. So the engine's git adapter commits to a branch and opens a pull request; it never pushes to a default branch and it never merges.

The result is a routine with a person in it at exactly one point: the drafting is automatic and weekly, the publishing is a decision. That is the correct place for the human, because a draft costs nothing to reject and a published page costs something to retract.

What had to be true first

Three controls were verified on this channel before it was switched on, and three of them prove a negative, which is the part that matters:

• With the kill switch set, nothing is sent and the adapter is never reached.
• Content matching a refused class is diverted for review and never reaches the adapter.
• Three consecutive failures disable the channel and raise a notification, rather than retrying into the void.

Only after those did the fourth run: real content, actually published.

The fault found on the way

The adapter wrote frontmatter with a title, a date and a pillar, and no summary. This site's parser requires a summary and skips any entry without one, with a warning and a green build.

So the routine would have opened a pull request every week, the merge would have succeeded, the deploy would have succeeded, and the post would never have appeared anywhere. Nothing would have gone red. The adapter now guarantees the field rather than hoping it was supplied, falling back to the opening sentence of the piece.

A green build is not a rendered page. It was not this time either.