Acceptance Criteria
Define “done” before execution begins.
Turn requirements, technical constraints, and verification rules into explicit gates every milestone must satisfy.
Make the finish line executable.
The team approves readiness before implementation begins. Morph evaluates those requirements throughout the milestone and returns failed checks to execution.
Every milestone knows what it must satisfy.
Captures the requirements that matter for this change.
Build, behavior, architecture, performance, security, and delivery expectations become explicit criteria in the Project Spec and milestone.
Checks readiness throughout execution.
Morph uses builds, tests, automated code review, functional verification, and configured evaluation tools to assess each requirement.
Turns every result into a clear next action.
Failed criteria return to the milestone. Passing criteria become evidence for team review, approval, and merge.
The definition of done stays with the entire milestone.
Criteria begin as an approved plan, guide execution, and become the evidence used to decide whether the change is ready.
Approve the finish line.
Define and review the requirements before implementation begins.
Evaluate continuously.
Return failed requirements to the milestone while the work is active.
Review evidence and decide.
Use satisfied criteria as explicit evidence for approval and merge.
Make readiness measurable.
Give every milestone an approved finish line before implementation begins.