Ship a change
A webhook worker drops retries under load, and the fix matters only when it reaches the base branch and survives its focused check. State the outcome, run the change as one bounded delivery, and stay with it through review, merge, ancestry proof, and post-merge validation. The handoff is a working change with a receipt.
Easy path
> Fix the retry path in the webhook worker and get it merged.Routine implementation runs natively. railyard:deliver can coordinate useful Compound Engineering (CE) stages and carry their result to the requested merge boundary.
Illustrative workflow
The operator asks for webhook retries to survive load and land on the base branch. Native tools implement the bounded fix, with CE stages selected automatically where useful. CE owns review settlement and CI monitoring; findings and failing checks return to that same owner for repair. The requested result is complete only after the merge is observed and its focused post-merge check supports the outcome.
What happens
Choose model and effort together when delegating: Opus 5.5 at medium in Claude Code or GPT-6.1 Sol at medium in Codex. Sol owns implementation, debugging, planning, and ambiguous or multi-file work even when small or bounded. Escalate to Fable 5.1 for harder Claude Code work. For demanding Codex work, raise Sol 6.1 to high, xhigh, or max when justified; reserve Astra for a rare, explicitly justified escalation after a concrete residual failure or quality gap on Sol 6.1. Omitting the model means the child inherits.
Before every push, satisfy the whole-candidate review gate with both Thermos lenses and Codex review covering the complete cumulative change and affected lifecycle. Resolve findings and bind the evidence to the exact candidate, then publish through compound-engineering:ce-commit-push-pr. CE owns feedback settlement and CI; revalidate the complete candidate before repair pushes. After settlement and authorized merge, verify merge ancestry and the smallest applicable post-merge check.
Proof point
The delivery lifecycle records the terminal evidence contract: merge ancestry plus a real post-merge check.