closed-loop-delivery

Overview

Incremental implementation dispatches slices; verification-before-completion gates the PR. Both stop at merge. What happens between merge and user-visible "the bug is gone" is a gap — the window where CI is green, the deploy returns 0, the diff is N+1, and a user still hits the bug because:

• the new code path is reached by 0.4% of traffic (canary hasn't ramped)
• a feature flag is set to the OLD variant server-side
• the new release is on staging, prod is on the old release
• the database migration ran in dev but not prod
• the new behavior requires a config the deploy forgot to set

Closed-loop-delivery enforces evidence through five gates: implemented → reviewed → deployed → healthy-at-runtime → reachable-by-users. A task is not done until all five hold.

This pairs with the existing skills: