Process-Aware Done
Completion requires:
- Artifact: the real thing exists and works where it matters.
- Trajectory: the path that produced it was legitimate, independent, and reproducible.
- Stewardship, when applicable: ephemeral resources created by the task were removed or retained with a named owner, reason, and expiry.
Do not accept proxies as completion. Passing CI is not the same as a working product flow, a send ID is not the same as a received message, and a matched answer is not trustworthy without source lineage.
Checklist
- Name the artifact checked: PR, deployment, trace, email, document, workflow run, API response, or user-visible behavior.
- Explain how it was produced: source data, tool path, repo branch, execution path, or build/deploy path.
- For a bug, incident, or runtime edge case, name the same-PR regression ratchet that would have caught it. Use the cheapest durable layer: container-structure test or runtime smoke assertion for container/runtime shape, unit/regression test for code behavior, policy/Helm/IaC test for configuration gaps, or monitoring alert when no test can catch the failure.
- State the anti-shortcut check: no copied answer, no data leakage, no overfit/lookahead, no hallucinated route or feature, no unverified send.
- Record gaps explicitly. If verification is queued or blocked, call it waiting or blocked, not done.
- Name the tail that owns any yielded or handed-off remainder, with its link or ID; a note that names only the handed-off stage is incomplete.
- Apply
ephemeral-workspace-lifecyclewhen the task created worktrees, temporary clones, scratch directories, build outputs, or local caches.
Handoff Is Not Done
A stage may yield — park a wait, hand work to another worker, open a PR for review — but the parent delivery and cleanup obligations stay tracked until their own evidence exists. Closing a queue item, opening a PR, or parking a wait completes at most the stage; it never completes the task.
- When yielding, name the tail that owns the remainder: queued verification item, review thread, or cleanup receipt.
- A merged or closed change is not done while its worktree, clone, scratch
directory, or cache has no verified disposition; apply
ephemeral-workspace-lifecycleand reportremoved,retained, orblockedwith evidence. - Record the tail link and the pending cleanup owner in the completion note.
Hard Stops
- A circular evaluation is not an independent win.
- A merged PR with a broken user flow is not done.
- A synthetic artifact without source-backed verification is a demo only.
- A fix PR for a reproduced failure without its regression ratchet is incomplete.
- A task that leaves unowned ephemeral resources with no expiry is incomplete.
- A handed-off stage with no tracked tail is incomplete.