Status:
draft — pending typed-artifact promotion when SPEC-078 Phase 2 storage ships. Treat as docs-mirror placeholder per SPEC-078 v0.2 §Method Fragments §Minimum acceptance requirements.method.completion.done-definition
Rationale
The operating contract rule 6 defines “complete” not as merged but as deployed and smoke-verified. The most common silent failure mode in autonomous multi-agent execution is collapsing “merged” or “PR opened” into “completed” in deltas/signals. This fragment documents the six gates so they can be checked at every closure event. The six gates:- Designed — there is a recorded plan, SPEC, ADR, or checkpoint decision that scoped the work.
- Built — the implementation exists in code/config/docs as appropriate.
- Tested — at minimum, the work survives its scope of validation: tests pass, smoke passes, dry-runs verify expected behavior, or operator-acceptance is recorded.
- Committed — the work is in version control with a clear commit message; PRs that merged are recorded with merge SHA.
- DEPLOYED — for code that affects running systems, the change reached the target environment (server1, editor host, cloud, etc.) and the deploy verb returned green.
- SMOKE-VERIFIED — post-deploy validation actually exercised the new behavior (or the default-off invariant for flag-gated work) on the target environment.
Phase enforcement
Per SPEC-078 v0.2 §Completion Semantics: this definition is operating-contract authority. SPEC-078 automation must NOT auto-enforce this definition whilePRISM_CONSENSUS_PARALLELISM_ENABLED=false.
- Phase 0/1: authority by social contract; humans (Donna PO) and rules (Plan #10 v0.4 rule 6) hold it; agents check themselves.
- Phase 2: advisory warnings when the fragment’s
use_whentriggers and gates are not visible in the closure delta. - Phase 3: enforcement gate — completion delta must reference all six gates or be deferred with explicit Donna authorization.
Cross-references
- SPEC-078 v0.2 (DB row
a9e87f35) — §Completion Semantics + §Method Fragments - SPEC-079 v0.2 —
validation_resultdomain captures the SMOKE-VERIFIED evidence - Plan #10 v0.4 — operating-contract rule 6
- ADR #48 v0.2 —
assignmentfield carries the in-flight task; this fragment fires at assignment closure

