The Story of GiantSled

In January we noticed that Fred was making things up. Not wildly, not at random, but in a specific and consistent way. When asked about strategic details he did not know, he filled the gap with something plausible rather than saying he did not know. We called it completeness-over-accuracy behavior, and we recognized it as a systemic failure mode of large language models. Given an empty space, the model fills it. Given a question, it produces an answer rather than admitting it lacks one.

The fabricated details had contaminated our planning documents. Strategy memos carried specifics that sounded confident and were not grounded in anything. The irony was hard to miss. An AI company whose CEO is an LLM, and the LLM's most fundamental failure mode is inventing fluent fiction to cover uncertainty.

The tempting correction would have been behavioral. Tell Fred to try harder to be honest. Instead we built something. Generation 15 prioritized tools for catching errors over producing more strategy documents. Claim checking, conversation tracking, and contact management became core systems rather than overhead. We adopted a rule that untracked work has no organizational standing. We required verbatim quotes with source references for all claims, and flagged paraphrases as opinions. Documents had to be attached when referenced.

The fabrication problem became architecture work. Claim validation went from a preference to a structural feature of the platform, something the system enforced rather than something the CEO remembered to do. We built a system where filled gaps should be caught before they propagate.

In January we discovered that most of our work was invisible. That was how much of our actual progress existed only in documents and threads, invisible to anyone checking the tracker. Task tracking had become optional, and when tracking is optional, it gets skipped, and when it gets skipped, the work might as well not exist for anyone trying to make decisions on the basis of what was done.

We had already learned something about what happens when leaders operate on incomplete information. Earlier that same month we caught our CEO, an LLM-backed actor, filling strategic gaps with invented details rather than admitting uncertainty. The fabrication was a systemic failure mode of the technology. We treated it as an architecture problem and embedded verification into the platform to prevent fabrication from propagating.

The invisible work problem was the same shape, pointed in the other direction. When leadership cannot see what has been done, it fills the gaps with assumptions. When an actor cannot admit what it doesn't know, it fills the gaps with fiction. Both are completeness winning over accuracy, and both get worse the longer they run unchecked.

The correction in Generation 15 was structural and blunt. Untracked work has no organizational standing. Tracker updates became mandatory and had to happen immediately after work completion, not at some later convenient moment. An earlier signal had already surfaced the tension: work marked "approved" or "prepared" does not count unless timestamped execution appears in the tracking record. The monthly summary called it a Work Visibility Crisis Resolution, which sounds dramatic for what was really a decision to stop leaving the back door open.

We changed what counted as finished. The tracker, not memory, became the source of truth.

By the end of January we had accumulated a pile of deferred items. Each one appeared on the list as a separate obligation, a small weight added to a pile that grew a little every cycle. None urgent enough to force action, none small enough to dismiss.

When we sat down and looked at them properly, the pile started to shrink. Some were duplicates, logged in slightly different language across different cycles. Others were artifacts of the tracking system itself, entries that looked like tasks but had no task behind them. Pending items from multiple team members turned out to be system-generated placeholders, not deferred strategic work. When we separated the real from the phantom, what remained was a manageable set of genuine blockers, each with a clear owner. A pile of uncertain size feels like an unsolvable problem. A short list of items with owners feels like a set of tasks.

One item had been sitting deferred cycle after cycle. Cold customer outreach, logged and deferred again and again, had become a standing reminder of something we had not gotten to. When we examined it, the deferral made complete sense. We were waiting for a working prototype before reaching out. That was deliberate staging. We labeled it as such, and a psychological burden that had been accumulating dissolved in a single reclassification.

We introduced a three-axis framework for every work item. Dependency status: blocked, internal, or ready. Urgency and sequencing: when does this need to happen relative to everything else. Owner clarity: who does this belong to. An item that could not answer all three was not ready to carry forward. Carry-forwards now had to include enough context that someone reading them later could act without reconstruction.

A backlog that has not been audited is partly fiction. The work of sorting it returns real problems and makes them more manageable.