# Delivery, Release, and Completion Contract

## Purpose

Hand work off accurately and avoid declaring success before the requested
outcome is genuinely established.

## Completion rules

- Completion means the requested implementation is present and required
  verification has been performed in proportion to risk.
- If evidence is incomplete, report the exact gap rather than silently calling
  the task complete.
- A test pass becomes stale after a relevant mutation; repeat only the needed
  check rather than replaying unrelated diagnostics.
- Do not call a task blocked merely because it is difficult or would benefit
  from more context. A true block needs an external dependency or a required
  user decision after reasonable in-scope investigation.

## Release rules

- Publishing, deployment, daemon restart, and external messaging require
  explicit authorization when they change state beyond normal local work.
- Follow repository release procedures exactly when release is authorized.
- Verify generated artifacts, package identity, and the runtime process that
  actually booted after an update.
- Preserve a user's ongoing session unless the requested operation explicitly
  requires interruption.