Bus factor zero

Software teams have measured a certain kind of fragility for decades with a grim little metric. The bus factor is the number of people who would have to be hit by a bus before the project could not continue, and a bus factor of one is the classic emergency: a single person holds the mental model, and everything from vacations to resignations becomes a risk to the system rather than to the person. Every remedy the industry built for this assumes the same thing, that the understanding exists and needs distributing. Pair programming distributes it. Code review distributes it. Documentation preserves it. Onboarding transfers it.

None of those work on a system nobody ever understood. That is the case a fluent generator makes ordinary, and it is one worse than the classic emergency rather than a variation of it. A model produces a subsystem faster than any person can read it, a solo developer or a small team accepts it because it passes, and the code enters production carrying no mental model anywhere. There is nothing to distribute. Six weeks later a bug appears in it and the author is in the position of a stranger reading someone else’s work, except that the someone else cannot be asked, was never a someone, and left no reasoning behind because reasoning was not what it was producing.

The distinction that matters is between knowledge lost and knowledge never formed. Losing it is recoverable in principle, since archaeology on a repository is slow and miserable but it works, and the person who wrote the strange thing usually wrote it for a reason that can be reconstructed from what else was true at the time. Knowledge never formed leaves nothing to excavate. The code has no intent behind it, only the statistical residue of a million other codebases, so the question every maintainer eventually asks, why is it like this, has no answer at all rather than a hidden one. Systems in that state cannot be safely refactored, because you cannot tell load-bearing from accidental, and everything therefore has to be treated as load-bearing, which is another way of saying the system is frozen.

Nothing about this is an argument for generating less. It is an argument that comprehension has to be produced deliberately now, since it is no longer a free byproduct of typing. The reasoning has to be externalized while it still exists, in decision records that say why this database and not that one, why this threshold and not a rounder number, what was rejected and what would have to become true to revisit it. The generated explanation is worth having and is not the same artifact, because a model asked to explain code will tell you what it does with total fluency and cannot tell you what anyone intended. And the practical gate is the one sentence a person has to be able to say without looking, which is why this is safe.

Bus factor zero is not a caution about ambition. It is a reminder that a system is not finished when it runs, it is finished when somebody understands it, and that has always been the standard we were quietly meeting by accident and can now choose to meet on purpose.