Keeping software coherent at agent speed
Agents write much of the Fuz stack's code. Whether a session commits its work depends on what it was asked to do, so some work waits uncommitted for the maintainer to read, and some commits land on the main branch before the maintainer has read them. At that speed one person's reading cannot be what keeps the software right. This page lists the ways agent-written work goes wrong here, and what holds each one.
So part of the review happens after the fact. Work is reviewed before it is committed, and commits that have landed are reviewed too, by agents when asked and by the maintainer, for whom it is sometimes the first reading. The release is the checkpoint for that review: versions and publishing are the maintainer's, and a common pattern is to review all the work since the last release before making the next one.
Two of the stack's projects are made for that reading. zzz is for reading work on the maintainer's own machine, and its projects page shows each repo's uncommitted work and its distance from origin. fuz_forge is for commits that have landed: it shows a repo's commit log and its diffs to a reader, with no pull request to approve first.
What is at stake is coherence: software that still reads as one design, with one way to do each thing, one name for each concept, documents that are still true, and checks that mean what they say. The rows fall into families. The first is that loss itself, a design that drifts. The other three are how it starts: checks that mean less than they say, claims that nothing confirmed, and sessions that repeat a mistake, collide or overstep.
A hold is whatever stops a failure or catches it. Holds sit on the rungs of a ladder, from a person's judgment down to the shape of the system. Each rung down depends less on anyone remembering than the one before it. A rule moves down when a lower form of it is simpler to keep than the rule alone: a check that holds it, or a structure that makes it unnecessary.
The projects named are the ones on the Fuz stack page. See also the skills the written rung cites, the values the stack's design is measured against, and the glossary for the words used here.
Claude Fable 5.2 wrote this section and its data file. Its claims were checked against the repos on . The maintainer has not yet reviewed it.
The grid
Each row is a failure, each column a rung, and each cell what holds that failure at that rung. The column is how strong a hold is and the mark is only how much of the stack has it, so a full mark on a written rule is still a rule that someone has to follow. A blank cell means nothing at that rung is aimed at the failure. Two holds apply to every row and are listed once: review after landing, under "Green but wrong", and the gate, under "A known mistake comes back".
- Throughout In place across the stack.
- In places In some projects, or for part of the failure. The entry says what is left out.
- Out of reach This rung cannot hold the failure.
- Wanted More is intended here and not built.
More in this section
- What the holds leave out — every gap in the grid, gathered
- Rules that moved down
- Oracles in use
- Actions kept with a person
- Gates