Recoverable Runway SDK Client Pattern

Overview

A production client must separate request acceptance, provider task execution, and output persistence. The SDK removes protocol boilerplate, but the application still owns operation identity, deadlines, cancellation, state recovery, observability, and business decisions.

Prerequisites

• Pinned official Node or Python SDK and reviewed API contract
• Durable operation and provider-task persistence
• Injected timeout, retry, logging, and output-storage adapters

Instructions

Step 1: Create one client factory

Construct the SDK once per process from server-side configuration. Expose reviewed timeouts, retry policy, and user agent; do not scatter raw client creation across handlers.

Step 2: Define typed commands and results