Delivery decision packet

Name repository, intended remote/branch, exact current diff and staged/untracked content. Include task/spec, owner-authorized action if any, gate/review results, private-content/export inspection, deployment consequence and remaining risk.

Example request after preparation: “Approve a commit of these reviewed files, then a push of this branch to this new private repository? This push will trigger the configured deployment. Public skill publication is a separate allowlisted export.” Ask only for authority still missing; preserve an earlier decline.

Evidence distinguishes branch commit, verified merge and verified deployment. A local milestone can record pending activity without implying it reached a remote.

Do not turn approval of a report into approval of force-push, unrelated commits, another repository, changed credential settings or the publication of private references. If any material target/content changes after approval, re-establish the appropriate authority before that action.