Gremlins at Work

Public Posts

• Meet Quartergremlin

  A scaffolding agent with a silly name and a deadly serious stop condition. Quartergremlin works because it knows exactly where to quit.

• Labs, Gremlins, and Other Bad Ideas That Somehow Work

  Calling your automation a gremlin sounds unserious. It survives review because the name is a handle and the contract is the architecture.

• The Drift Checker That Couldn't See Its Own Drift

  The mirror-staleness detector ran on schedule and reported current. It was comparing one field: the latest date heading. Nine fresh entries and one stale mirror looked identical to it. The most dangerous checker is the one that runs fine and compares too little.

• The Docs Said "No Code Yet"

  A platform-wide integration review found two labs whose READMEs still read 'scaffolded' or 'initial setup in progress' over roughly 2.8k and 1.4k lines of real code apiece. Nobody wrote a false sentence. The docs were just true once, and the code moved on without them -- so the fix was a bounded agent role, not a cleanup sprint.

• The Rework Path That Never Existed

  The CLI's own error message told you to block a failed task for rework. That advice was an illegal state transition every time it printed, since the day the vocabulary was written, and nobody noticed until a review actually read the transition table.

  Part 7 of 9 in From Control Tower to First Product

Draft Queue

No draft placeholders assigned to this series yet.