Execution & Runs¶

Requesting governed runs and tracking them to completion.

Once a submission is translated, ready, and approved, you request a run. Available today.

Request A Run¶

Operation	Purpose
`createRunRequest`	Request a governed run

The platform resolves a governed run bundle, dispatches it asynchronously (Cloud Tasks → GKE/Axion deterministic execution), and returns an operation handle.

Run From A Reference-Pack Scenario¶

Operation	Purpose
`resolveReferencePackScenario`	Resolve a reference scenario
`createGovernedRunFromReferencePackScenario`	Launch a governed run from a resolved scenario

See Reference Packs & Publication.

The Execution Path¶

flowchart LR
    A[createRunRequest] --> B[Resolve run bundle]
    B --> C[Cloud Tasks dispatch]
    C --> D[GKE / Axion deterministic execution]
    D --> E[GCS evidence + artifacts]
    E --> F[Loaded to BigQuery analytical truth]

Tracking¶

Run-shaped calls are asynchronous. Poll the returned operation handle (see Errors & Long-Running Operations). The platform keeps an authoritative run registry of every request, dispatch, and job.

What This Means For Integration¶

Always treat a run as asynchronous; design idempotent polling.
The result of a run is governed facts + evidence, not a synchronous payload.
Reference-pack runs are the fastest way to reproduce a standard scenario.