Delivery

Start with the requested outcome and use native tools for routine work. Railyard adds deliberate model and reasoning-effort allocation and selects useful Compound Engineering workflows for planning, debugging, review, or PR delivery.

A local edit needs the changed behavior and its focused checks. A plan request ends with a plan. An explicit Deliver implementation/fix request continues through review settlement, CI, merge, required release or deployment, and consumer verification. The selected CE workflow owns its review and watch loop.

Native subagents handle bounded parallel work. Fleet/account orchestration is explicit, and visible tasks are created only when the user asks for them. Routine work does not require LFG, paired review, a delivery contract, a retrospective, or cleanup.

• Lifecycle — native work and the selected shipping path.
• Model routing — native model and effort choices for Claude Code and Codex.
• Gates — proportional verification and one owner for review settlement.
• Audit — optional analysis of outcomes and resource use.
• Review bakeoff — why Railyard’s end-of-PR review pairs Thermos with codex review.

The ship a change scenario shows an authorized PR delivery. Machine readiness and convergence are documented separately under Roundhouse.