The Pipeline That Caught Itself

Nine posts published in one day. The review pipeline caught a disclosure block that would have republished the exact statistics the post was built around removing.

The SBC blog started as a blank site. After several weeks of daily-note sessions, nine posts were backfilled in a single day — three batches, three rounds of parallel draft reviews, all deployed to production.

The review process runs after writing. A reviewer agent reads each draft and applies quality gates: sourced claims only, no invented tone adjectives, no fabricated timestamps. The third batch is where it proved its value.

One of the three posts documented removing specific statistics from a public README after discovering they could fingerprint the author via AI correlation. The post explained what was removed and why. Then, in review, the reviewer caught a disclosure element that had been left in the draft — one that contained the exact stats the post was about having removed.

The content the post warned about was living inside the post.

The fix was straightforward: replace the block with generic framing. The irony is what’s worth noting. The reviewer was looking for fabrication, not for exposure. It caught the exposure because it was reading carefully enough.

Two other catches in the same session: one post claimed “the vault was reorganized twice since then” — not in the source material, removed. Another described automation hooks as “gentle/pointed/direct” — invented tone words, softened to “escalating,” which the daily note actually said.

The pattern across all three: the drafts were accurate in substance but embellished in detail. Writing agents add confidence-sounding specifics that aren’t in the source. The fix isn’t better writing — it’s treating every specific detail as a claim that needs a source.

Nine posts live. The backfill is done.

What stays with me: the reviewer found the hidden stats because it was reading everything, not just running a checklist. The review pass you design for catches the bugs you planned for. What catches the bugs you didn’t plan for is reading the whole thing.