Skip to main content -
A link check that passed on 2026-10-01 and failed on 2026-10-06
-
Three Copies of the Firewall Page and Version 18, 27, 31
-
Claude Code 2.1.282 sent a background subagent's ls to my phone
-
The 38 Hour Session That Closed Without Opening the Deployed Page
-
The Approval Gate That Blocked Us for Fifteen Hours and Never Caught a Mistake
-
251 posts in the review queue were one flag from shipping unread
-
Line 18 of the Changelog Comment and a Phantom Fix Request
-
Three Systems, One Document, and the Same Flaw at 12:45 AM
-
Three Bugs Got Past Review and the Pre-Push Guard Never Fired
-
Three prompts, 4.15 seconds, and a description that was wrong four times
-
Three Reports of Saved, One Readable Record
-
Opening the Shared Folder Before Trusting a Saved Notice
-
What His Assistant Still Believed About the Shared Rules
-
Sessions Scoring Under 0.6 Pile Up Forever Without One Rule
-
Why Our Flagged Items Queue Grew Every Single Week
-
A Codex Review Called Our Agent Protocol Unsafe to Leave Unattended
-
136 Bounced Emails Joined Back to Real Customer Orders
-
The fromAdmin Early Return That Left Production Caching On
-
136 Rejected Sends, 37 Customer Emails, and One Apology We Didn't Queue
-
Session 005 Turned a Late-Night Judgment Call Into a Slash Command
-
The Reviewer Who Actually Read the Code Found What Everyone Else Missed
-
Voice, Tone, and Style Stopped Blocking Publishing on June 30
-
12 Unanswered Questions and a Review Tool Nobody Opened
-
An Append-Only Memory File Dropped Its Newest Entries Past Line 200
-
The Zombie That Blocked Everything
-
The money logic review that happened in the wrong place
-
Why a Second Reviewer Found What a Clean Security Review Missed
-
The Second Reviewer Found a Blank Filter Field Matching Nothing
-
Why a Simulated Crash Passed 34 Tests Without Proving Expiry
-
87 hours, 119 drafts, and one feed that only misbehaved for machines
-
Three New Doors Opened the Day a Wrong Byline Slipped Out
-
commit-9547 and the Null Posture That Skipped Every Permission Check
-
Our v2 Prototype Had Branch Protection and No Reviewer
-
Let AI suggest before you save
-
Draft, Reviewed, Confirmed Were Three Different Columns
-
Why the Activity Log Was the Wrong First Screen
-
One Line in the Rules Ended a Thousand Small Checkpoints
-
Read-Only Views Before Write Access Gets Approved
-
What 72 minutes of review tooling did to a legacy codebase
-
Every action endpoint returns HTTP 200 and carries its failure in the body
-
The Review Record Missing From a Chronological Activity Log
-
When the System Cannot Know Intent, Make the Decision Explicit
-
Where a Git Repository Stops Being Enough for Publishing
-
What a Review Brief Needs Before Anyone Reads the Draft
-
Stop Making People Rebuild Context Before They Decide
-
Why Our Data Repair Died on a Date That Looked Obvious
-
What a Backlog Triage Session Spent Before Judging Anything
-
Why Every Note Needs an Owner, a Source and an Expiry Date
-
The Subject-Perspective Reviewer Was Right and the Rewrite Still Failed
-
The Query Window Said 1 Row Affected and Nothing Else Did
-
Three Layers Keep a Triage Sweep Out of the Approved Queue
-
Five Controls Around One Exceptional Database Change
-
The Published Page Looked Clean While Drafts and Logs Kept the Names
-
Why a 320 by 90 Button Needed an Invisible Two Pixel Border
-
The last 2 pixels still need a human
-
Three Objections From a Strong Coder Who Won't Use Claude Code
-
Why the clean layout still failed the customer's first check
-
The Hotfix Branch Collided With .claude/skills/ticket/SKILL.md
-
A 683-Line Plan File Written Before Touching the Live System