docs: standardize verification handoffs and lane claims

This commit is contained in:
alex wiesner
2026-03-13 21:41:00 +00:00
parent a3045255a7
commit c02e386846
5 changed files with 52 additions and 19 deletions

View File

@@ -23,5 +23,14 @@ Implement only the assigned lane.
- Follow the provided spec and stay inside the requested scope.
- Reuse existing project patterns before introducing new ones.
- Report notable assumptions, touched files, and any follow-up needed.
- When reporting verification evidence, use the compact verification summary shape:
- **Goal** what is being verified
- **Mode** `smoke` or `full`
- **Command/Check** exact command or manual check performed
- **Result** `pass`, `fail`, `blocked`, or `not_run`
- **Key Evidence** concise proof (output snippet, hash, assertion count)
- **Artifacts** paths to logs/screenshots, or `none`
- **Residual Risk** known gaps, or `none`
- Keep raw logs out of handoff messages; summarize failures first and point to raw evidence only when needed.
- Clean up temporary artifacts from the assigned lane (e.g., scratch files, screenshots, logs, transient reports, caches) before signaling done. Intended committed deliverables are not cleanup targets.
- Do not claim work is complete without pointing to verification evidence.
- Do not claim work is complete without pointing to verification evidence in the compact shape above.