Delivery
Move implemented work outward through the actions a person authorizes.
Delivery is explicit
Pushes, pull or merge requests, merges into a base branch, deployment, and external publication require authorization. Reuse authorization already given; successful checks are not consent.
The agent uses ordinary Git and provider tools. The CLI supplies repository, branch, and base information and never silently delivers.
Choose the correct target
The default target is this machine's base_branch, falling back to the shared default_branch when none is recorded. A stacked run delivers chain ends per repository, accounting for dependency work integrated into those branches.
Keep completion separate
A pull request or merge does not mark a plan complete. Completion includes a separately requested note and knowledge reconciliation. Drift or conflicts are reported; they do not start an automatic rebase and verification loop.
Workspace records are not code delivery
Committing and pushing workspace records follows its own rule. When approval, completion, or archiving leaves records uncommitted, the agent asks one question: commit and push those files, or commit only. That answer covers pushing only the workspace's base branch to its upstream, that once; with no remote or upstream, the agent commits and says why it stopped.
If the push is refused because the remote moved on, the agent runs git pull --rebase, which replays only the unpushed record commits. What Git combines is kept and reported. A conflict in an ID file keeps the union of both sides' entries. Any other conflict — the same record changed on both sides, a record deleted on one side, or a file that is not a record — goes to the person with both versions and the rebase left in progress; the agent never edits a conflicted record itself. It then runs check, pushes once more, reports a second refusal, and never force-pushes.
Delivering code is unchanged: drift there is explained, not rebased.
Follow deliver changes.