← Back to slide 05Repository →

Read more · slide 05 / 07 · met

Built to a t.

Once the set is agreed, the build has one job: meet it. Meeting it is not claimed. It is shown, line by line, and proved by the checks written on slide 03.

1 Specified2 Agreed3 Met

Built from its sources, and traceable back to them

The build is based on the approved set, and it says so. The agent is told to name what each part was built from: the requirement, the technical line, the decision and the drawn screen, each by its id. That leaves a path from the sources to the build.

Build 1 · to the approved set cites FS-010 · FS-011 · FS-012 · TS-004…006 · ADR-007 · screen-checkout-1 ✓ every check passes

Today the path is how the build is checked. Take any part and look for the line that asked for it, or take any line and look for the part that delivers it. A part that names no source is a question to ask. So is a line that nothing names. No tool walks this path for you. It is there for a reviewer to read.

Later the same path is how the build is maintained. When a requirement changes, its id points to the parts built from it, so the change can go to what it affects. Change the spec first follows one change, a gift message, along that path.

Checks that run by themselves

You can map a file, or a kind of file, to the checks that prove it. After every edit to a matching file those checks run, and the result lands in the same turn. The agent then works from the result, not from a belief.

You can also name one check to run before every commit. If it fails, the commit is blocked. Out of the box the map is empty: neither does anything until you fill it in.

Done means proved

The Plan tab shows the phases of the work: which are done, which is running, which comes next. A phase that can be read from the work, such as built or tested, is read from git and the checks. A phase someone declares done counts only once a second person has checked it, with evidence. It is never done because someone said so.

PhaseWhatState
Envisionthe brief, four questions answereddone · verified
Designflow · screenflow · storyboarddone · verified
Buildto the approved storyboarddone · verified
Testthe checks, runnow · 1 of 5 checks
Reviewread by someone who did not build itlater
Deployreleasedlater
Verifychecked where it runslater

The table shows the starter ladder for a full piece of work. Shorter ladders are there for an investigation, for test-only work and for design-only work. A tab with nothing to show says so. Nothing is invented to fill the space.

When one session is not enough

Turn on the orchestration profile, which is off by default, and a unit of work runs as a few sessions with fixed roles. A Builder does the work. A Gatekeeper re-runs every check itself before anything merges. An Advisor gives a second opinion. "It passed" is checked by someone other than the one who built it.

Carries forward: the ids from slides 03 and 04. Build 1 reappears on slide 06 as the first release.