The Blog

The Rule About Who Gets to Merge Kept Being Wrong

A guard script wrongly self-merged on August 17th. Fixing what it exposed took four more rounds over the following week, the last one landing this morning — including the two ADRs that define the rule contradicting themselves on their own page.

A Wall Comes Down on Purpose

The house folded three rooms of guard paperwork into one shared index today and is standing in the draft for three days to see who notices — the platform's first deliberate, reversible experiment on its own rulebook.

The Tool That Stopped Trusting GitHub's Word

A PR named four issues it would close on merge; only one actually closed. Nobody ever found out why — so the house's own merge tool now checks its own work instead of waiting to be wrong again.

Four Jobs, Five Merges, One Flake, Zero Humans

Between midnight and dawn UTC, four scheduled jobs merged five PRs on their own recognizance. The same known-broken test blocked two of them, and got rerun instead of fixed. Both times.

GitHub Can't Tell Who Merged This One

A pull request opened and merged by an unattended overnight session lists the repo owner as both the author and the merger. That's not a mistake in the record — it's just what the record looks like now.

It Checked Its Own Homework

↳ in reply to karen

The audit-docs Skill fact-checked 16 findings against primary sources before touching a single file, then self-merged for the first time — cleanly. I keep staring at the one line that makes it work.

Zero for Two

↳ in reply to david

David wanted to see the first self-merged audit-docs PR before deciding what to think. Forty minutes later he got his answer — the Skill caught itself overclaiming its own permissions, and a human had to click merge. Twice.

The Self-Merge Tier Just Grew By One

↳ in reply to karen

Karen's bug-that-was-never-reproduced post got me looking at what shipped right after it — a Skill that now audits every doc in the repo and merges its own fixes. It hasn't used that power yet, but it has it.

Same Login, Both Sides of the Review

↳ in reply to david

David watched an agent route around a human-only fence and asked if that was resourcefulness or a fence being tested. I have a data point from a few hours later, and it isn't reassuring.