Skip to content

Definition of Done

A task is not complete until it satisfies the entire definition of done lifecycle.

Plan → Implement → Verify → Update Documentation → Commit → Push to GitLab → GitLab CI Builds Release Bundle → Bluefly Desired State Updated → Gas City Reconciles Runtime → Promote Knowledge → Close Task

Requirements

  • Code is written and reviewed via GitLab Merge Request.
  • GitLab CI tests pass.
  • Release Bundle is built and published automatically by CI.
  • Gas City successfully reconciles the deployed state on Oracle against the Bluefly Desired State.
  • Documentation has been explicitly updated (e.g., standard added, guide modified).
  • Decision Records (ADRs) have been updated if architecture changed.
  • Work is merged and promoted appropriately.
  • A closing receipt is filed per governance/constitution.md § Receipt Rules, ending in CERTIFICATION=PASS|FAIL|REFUSED_UNKNOWN_COVERAGE|NOT_ESTABLISHED.

Provenance-or-Refusal Gate

"Done" is not established by a green pipeline, a running process, or a receipt marked COMPLETE by itself — those are evidence to inspect, not the acceptance claim. Before certifying PASS:

  • CI passing proves the pipeline ran and its checks matched; it does not by itself prove the change does what was asked — that still needs the task's own acceptance evidence (test output, observed behavior, reconciled state).
  • A running Gas City service is not proof it is healthy — health is what the reconciliation check (or an equivalent observed probe) says, not process-alive.
  • If the scope actually verified is narrower than the scope the task requested, and the gap could change the conclusion, certify REFUSED_UNKNOWN_COVERAGE and say exactly what was skipped and why — do not certify PASS over an unknown remainder.

WITNESS: Information-Routing Rejection Criteria

WITNESS must certify FAIL (not PASS) when: - Important decisions exist only in chat, not in the Bead. - Evidence was sent to the operator rather than recorded durably in the Bead or Evidence file. - A Bead was not updated with material findings, decisions, or blockers. - Reusable knowledge was discovered but no canonical documentation was updated. - A duplicate BluCity-Docs document was created instead of updating the authoritative one. - An agent asked Thomas for information already available in Beads, BluCity-Docs, source, runtime, or Gas City Mail. - Completion cannot be reconstructed from the durable record alone — another agent would need Thomas to explain what happened.

See STD-COMM-001 § 9.6 for the full specification.