Completion and quality gates
Deciding whether work is finished, with a contract every line of which passes or fails.
Deciding whether work is finished, with a contract every line of which passes or fails.
- use cases
- 7
- executable
- 1
- guaranteed
- 6
-
guaranteed intermediate
Decide whether finished work is actually finished
Evaluate a contract line by line instead of accepting a sentence that says the work is done.
finish · question · check -
guaranteed intermediate
Block acceptance on a question nobody has answered
Open a question against the task, watch finish refuse completion while it is unresolved, resolve it with the answer, and only then complete.
question · finish · check -
guaranteed basic
Catch an agent that says it is done when it is not
One task, start to finish: a worker strays outside its scope, claims it is finished, hands over, and is accepted only once the repository's own verification passes.
start · check · finish · handover · context -
guaranteed intermediate
Complete an issue only when its evidence exists
See an issue refuse completion while a required piece of evidence is missing, read the roadmap the milestone state derives, and keep the GitHub projection a projection.
plan -
executable basic
Know whether the work in this checkout is finished
Ask the repository you are standing in, and be told what is still owed by name.
check · watch -
guaranteed basic
Prove what a task owed before calling it done
A task declares what it owes, records evidence against each obligation, and is refused when that evidence no longer describes the tree it was taken over.
start · evidence · check · finish -
guaranteed basic
Say what reached the remote and what did not
The obligations that reach past the working tree are settled by asking git and the published site, so a report cannot call uncommitted work committed or unpushed work pushed.
evidence · check · finish