From trigger to done

Run lifecycle

trigger
  → resolve Subject + Engagement
  → insert Run (queued), pin Process version
  → spawn sandbox; agent works
  → write structured truth + artifacts
  → sandbox dies
  → awaiting approval / next stage
  ── hours or days; cost ≈ storage ──
  → human or stakeholder answers
  → fresh short sandbox for the next step

Two compute shapes

Autonomous runs — spawn → complete → die. No warm hold.
Interactive sessions — drive writer slot, stream turns, snapshot on idle, resume on the next message.

Status for "where is Acme?" always comes from the database. Waiting does not require a live machine.