ticket.software-delivery.slo-evaluate

Evaluate the versioned software-delivery SLO contract and expose the full provider-blind scan payload to remote workflow consumers.

Run one trusted SLO evaluation for engine-dispatched remote consumers.

The atomic twin of ticket.software-delivery.slo-scan: same evaluator, same payload, but shaped as the 3-state write skeleton so ANOTHER library (v2 forbids cross-library imports) can reach it by workflow_type string through engine.start_remote and poll the run to terminal. The terminal completed state_data carries everything a remote consumer needs — contract_version (the versioned SLO contract), the immutable thresholds catalog, the provider-blind items findings, and the summary completeness proof. Every identifier in the payload is already a public opaque UUID/ref (scan_deliveries projects through _public_opaque_id); no internal DB ids ever enter state_data.

Overview

Property	Value
Workflow type	Linear
Library	App-tickets
Version	1.0

Input Schema

Field	Type	Required	Default	Description
organization_uuid	string	Yes	—	—
states	list	No	—	—
include_terminal	boolean	No	—	—
alerts_only	boolean	No	—	—
limit	integer	No	—	—
profile_version	string	No	—	—
now	string	No	—	—

Output Schema

Field	Type	Required	Default	Description
contract_version	string	Yes	—	—
evaluated_at	string	Yes	—	—
thresholds	list	Yes	—	—
items	list	Yes	—	—
summary	dict	Yes	—	—
organization_uuid	string	No	—	Input field preserved in workflow state.
states	list	No	—	Input field preserved in workflow state.
include_terminal	boolean	No	—	Input field preserved in workflow state.
alerts_only	boolean	No	—	Input field preserved in workflow state.
limit	integer	No	—	Input field preserved in workflow state.
profile_version	string	No	—	Input field preserved in workflow state.
now	string	No	—	Input field preserved in workflow state.
failed_at	string	No	—	ISO-8601 timestamp when action_fail recorded the failure
failure_reason	string	No	—	Human-readable failure reason from action_fail
failure_type	string	No	—	Engine-stamped failure category
failed_action	string	No	—	Engine-stamped action that raised
failed_at_state	string	No	—	Engine-stamped state when the workflow failed
failed_step	string	No	—	Engine-stamped step name (DAG path)
failed_layer	string	No	—	Engine-stamped layer index (DAG path)
error	string	No	—	Engine-stamped exception message
error_type	string	No	—	Engine-stamped exception class name

States

State	Initial	Terminal	Success	Auto-advance	Description
initiated	Yes	No	—	execute	Accepted
executing	No	No	—	complete	Applying the mutation
completed	No	Yes	Yes	—	Done
failed	No	Yes	No	—	Failed

State Diagram

Transitions

From	Action	To	Description
initiated	execute	executing	Run the mutation
executing	complete	completed	Finalize
* (any state)	fail	failed	Catch-all failure

API Usage

POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "ticket.software-delivery.slo-evaluate",
  "initial_data": {
    "organization_uuid": "value"
  }
}