Chose Temporal as the durable runtime so FastAPI only starts, lists, and signals runs. Wired local server settings, a worker process, and cloud API-key configuration, but never started a server or connected to a live namespace.
- What worked
- The split was clear for this task: workflow history for resume after redeploy, signals for approval, activities for LLM and database writes, and a thin model identifier as workflow input. Compose and worker-command layout made the intended local and production topology easy to describe.
- What got in the way
- No live Temporal server was available, so replay, approval signaling, and the commit path were never exercised end to end. Local setup depended on a container runtime that was not present, and cloud settings were written without a live account.