Decision 0048 · Accepted
Delivery phrases
are approvals
Questions and acceptance belong to planning. After that, the user wants one phrase per delivery depth, each one a full approval, with no overlap that dictation could blur.
- Status
- Accepted
- Built from:
- da88c48
Status: Accepted (2026-10-29). Amends 0044 (amendment item 1: build never waits on CI and the review runs in ship; amendment item 2: fall back to local when gh is unauthenticated), 0040 (liveness only after shipping), and 0019 (two or three trigger variants per skill; Flow avoids generic host verbs). Spec: 035. Amended by 0055 (a repository writer's build-it issue label is that issue's "build it"). Amended by 0057 (CI runs on the ready head, not every push). Amended by 0058 (human-tier work ships only on a yes given after build's report).
Context
Questions and acceptance belong to planning. After that, the user wants one phrase per delivery depth, each one a full approval, with no overlap that dictation could blur. Build currently ends before anything is verified, so "build it, then check the branch" has nothing to check.
Decision
- Three phrases, each an approval. "Push it" / "deploy it": push the current or named branch. "Build it": a ready, reviewed, green, live branch. "Ship it": build if needed, merge, live on the default branch. One trigger set per skill; no shared variants.
- Build verifies; ship lands. Review (depth set by the size guard), fixes, and checks run once in build, on the final head. Ship reruns them only when the head changed.
- Light liveness at every depth. Commit on the remote plus the host's deployment status for that commit and one
GET. It reports and never gates. Behavioral verification (acceptance verdicts, UI checks) stays inreview. unmetblocks;unresolvedis listed. Build lists unresolved steps before the user says "ship it", and the phrase approves them.- No silent fallback. A GitHub
originwithout an authenticatedghstops with how to authenticate.
Alternatives
- Keep build light and ship heavy (0044). Rejected: the user checks the branch after "build it", so the branch must already be verified.
- Handle "push it" without a skill. Rejected for now: build and ship forbid pushing outside their own flow, so a narrow home for the push is clearer than an exception in both.
- Make
unresolvedblock landing. Rejected: it adds a confirmation after the approval phrase. The evidence gap is shown before the phrase instead.
Consequences
One user turn per delivery when planning is done. CI waits move from ship to build. "Push it" can push the default branch when named; the safety rules (no force-push, no protection bypass) still hold. Watch CI failure rate and post-merge fixes over the follow-up batch, and restore a gate if either rises.