Verification can establish that a result is ready to ship. It cannot truthfully say the result shipped, because shipping requires a human to authorize the remote action and the run to record durable delivery evidence afterward. Those are two different states, and Fusion keeps them apart on purpose.
Ready to ship is a proof-complete state
A final reaches readiness after the protected gate, jury selection, fresh QA review, and the required QA audit all pass. At that point the Receipt can be complete enough for a human decision.
No merge or deployment is implied. The exact commit may still exist only in a local worktree.
The customer pull request path keeps authority visible
For customer repositories, the normal handoff can be a branch or pull request with the Receipt attached. Owners review repository policy, approvals, release timing, and business context before merging.
Fusion should not treat technical verification as permission to bypass those controls.
Direct delivery still needs a human gate
An internal workflow may ship by pushing a selected final directly to a shared target. The human still approves that mutation. Before every push, the delivery process checks whether the remote advanced and halts on overlapping changes.
Closeout follows durable evidence
Only after the approved commit is present in the intended remote can closeout mark the deliverable done, reconcile internal role nodes, record provenance, and clean up worktrees.
The order protects a simple truth: a local success is not a delivered result. "Verified" answers whether the evidence supports readiness. "Shipped" answers whether the authorized artifact reached its destination.