Deploy an Asynchronous Runway Worker

Overview

Runway generation does not fit a synchronous request-response handler. Production deployment should accept intent quickly, persist it, execute through bounded workers, reconcile provider task state after restarts, and move successful assets into owned storage.

Prerequisites

• A deployment environment with queues, durable database, and object storage
• Server-side secrets, egress policy, and reviewed Runway contract
• Capacity, credit, moderation, retention, and rollback owners

Instructions

Step 1: Split API from worker

Make the public endpoint validate intent, assign an operation ID, persist approval and request fingerprint, enqueue work, and return an internal status handle. Do not hold an HTTP request open for generation.

Step 2: Persist provider identity