Run a scenario

The hosted workspace is the easiest way to see Themis.

Before you run

Check these fields in the scenario card:

• release ID;
• baseline version;
• candidate version;
• changed dataset;
• changed context;
• replay case count.

The fields describe the test. They are not proof of the result.

Run the gate

1. Open the Themis workspace.
2. Select new run if the run chooser is closed.
3. Select one scenario.
4. Load the run configuration.
5. Select run release gate.
6. Follow the request lifecycle panel.
7. Wait for RUN COMPLETE and a receipt.

The UI must remain in a running state until the API returns the final result. It must not briefly show a result and then reset to NOT RUN.

Read the result

Start with the decision badge. Then read:

1. the policy reason;
2. the selected and passed cases;
3. the SQL and oracle evidence;
4. the DataHub evidence;
5. the OpenTelemetry evidence;
6. the receipt and write-back state.

These are separate facts. A green DataHub status does not mean that the SQL passed. A trace does not mean that the candidate is safe.

The three outcomes

PROMOTE

The configured required checks passed. The candidate is eligible for a human release decision.

REVIEW

The run needs human review. Common reasons include missing DataHub evidence, an explicit ablation, or incomplete replay coverage.

QUARANTINE

A critical check failed. Do not release the candidate until the cause is understood and a new run passes.

No automatic deployment

Themis does not deploy the candidate after PROMOTE. The result is a release-control signal, not a deployment command.

Why a run can take time

A run may download or validate a dataset, call DataHub through MCP, execute several replay cases, run an oracle, write a receipt, and export spans. The progress panel shows the actual lifecycle. Do not refresh during a run unless the operator guide tells you to do so.