Deploy and operate

Turn local behavior into bounded, recoverable work.

Questions to answer

What survives a crash? Can retries duplicate a side effect? Who releases resources after failure?

Start here

Read durable-state mechanics and provider failure behavior. Specify timeout, cancellation, concurrency, identity, secrets, and cleanup ownership before selecting infrastructure.

Prerequisites: a small task you can describe, its permitted effects, and basic Python for executable examples. Reading the guides needs no API key.

Evidence and coverage

Restart evidence exists for specific adapters. Production SLOs, distributed guarantees, and cloud configurations require deployment-specific validation.

Follow the concept and build path for runnable lessons and the ecosystem map for wider coverage. Return to all journeys.