Runway Production Readiness Gate

Overview

Go-live is an evidence gate, not a list of intentions. The release must prove model-aware validation, durable asynchronous state, credit and concurrency controls, moderation handling, owned output storage, secret rotation, observability, and a rollback that does not orphan provider tasks.

Prerequisites

• Release SHA, environment, owner, SLO, budget, and rollback candidate
• Current first-party API, models, limits, pricing, and go-live guidance
• Passing contract, security, load, failure, and canary evidence

Instructions

Step 1: Verify contract and supply chain

Pin the reviewed SDK, API version, model or router schemas, and lockfile. Reject retired identifiers such as gen3a_turbo and any request shape copied across model variants.

Step 2: Verify identity and secrets