Review, Deliver, Verify and CloseThe back half of the pipeline is where trust is earned: you see what changed against what was promised, the app running locally, and then the delivery watched all the way to green.ReviewThe card reopens with the plan as approved, each step marked held or changed, with the deviation spelled out. Below that: what was done, the changes, and the local run with its port, started from make <repo> start.Two ways to review, and you can mix them:·Per change: walk the diff file by file and approve, revise or roll back each one, in a modal that shows the change with syntax highlighting and line numbers.·All at once: Approve all, Request changes (back to Doing with your note), Reject to Inbox, or Reject and close (undo everything).DeliverDeliver creates the delivery configured for the project, reports the link on the card, and then monitors the deployment that follows: pipeline status, environment, and the release it landed in.MODEWHAT HAPPENSPull requestBranch pushed, PR opened with the card summary as the description.Merge requestThe same against GitLab.Push to branchFor projects that deploy from a branch, no review app in between.
VerifyVerify answers "did it actually land, and did anything else break": the PR merged, the deploy went green, the suite passed, and a regression sweep ran over the parts of the project the card did not touch. A red Verify hands the card back to Doing with the failing step attached, rather than closing quietly.CloseClose is bookkeeping that matters: memory written (what was decided and why), documentation updated, and one last conflict check across the project so a card that was correct in isolation does not leave the project inconsistent. Then the worktree is removed and the branch pruned.