CodeHerderSearch⌘KRequest access →

Done means proven, at the stage that can prove it

An agent says the work is done. How do you know?

Some checks cannot run before the merge. An agent cannot see your live site until the change is live. If it claims the fix works there, it is guessing. A good gate has to wait for the stage that can prove the claim.

This is the third post in our series on safe, high-quality output. The first was about Agent Experience surveys. The second was about Evaluations. Both help you improve the herd. This post covers a rule that holds each single task to its word.

What a proof stage is

A story has acceptance criteria. They are a checklist. Each item says one thing the finished work must do.

Every item also has a proof stage. This is the stage where an agent can show the item is true. In the built-in story pipeline, the proving stages are plan, code, review, merge and verify.

You choose the stage with a heading. Items sit under it:

## review
- [ ] Unit tests cover the new gate

## verify
- [ ] Login works on the deployed site

An item with no heading takes a default. Items written at plan, code or review take review. CodeHerder refuses a heading that names a stage outside the task’s pipeline.

What the gate holds

The checklist gate runs on every move forward. An unticked item blocks any move to a stage after its proof stage.

Take the example above. The unit-test item is due at review. If it is unticked, the task cannot move from review to merge. The login item is due at verify. It lets the task reach merge. It blocks done.

So the merge can happen before the live check. The task cannot finish until the live check passes.

The gate never holds a move back. It also lets a task go to To do, to blocked or to cancelled. A stuck task can always leave.

When an agent cannot prove an item

Sometimes an agent reaches its stage and cannot prove an item there. It has two honest choices. It can defer the item to a later stage, with a reason of up to 280 characters. Or, at the last proving stage, it must prove the item or fail the task.

An agent can only defer forward. It cannot change an item’s stage by editing the whole list. It cannot delete an unticked item that was there when the task entered the stage. It cannot reword a deferred item. It cannot tick a deferred item before its proof stage. CodeHerder refuses each of these and tells the agent to ask a person.

A person can move an item to any proving stage, earlier or later. Only a person can pull an item back.

Each move goes into the item’s history. The entry holds the old stage, the new stage, who moved it, when, and the reason. The task activity also records the deferral.

What you see on the task page

You do not need to read the history to know where a task stands. The task page badge shows a count like 2/4 (1 deferred). Two items are ticked. One is deferred to a later stage. One is outstanding, which means it is due now.

A product lead can read that badge and know the state. Nothing is hidden behind “the agent said it is done”.

Write your own

Start with the item that scares you most. Ask where it can be proven. If a test can prove it, put it under review. If only the live site can prove it, put it under verify.

The full rules are in Set the stage that proves an item. To see where this gate sits among the others, read Verification. For a template with a ready example, read Writing a brief.

If you want “done” to mean proven in your own herd, get started.

← Back to Insights

Try it on one repository.

Connect one repository and file one task. Read the diff and the cost before anything merges.

Try "pricing", "connect a device", or "who reviews the code"

↑↓ move · ↵ open · esc close