ticket.coding-artifact.available

Mark an artifact available only when storage provenance, digest, size, and session identity match the frozen artifact.

Attach an exact organization-scoped storage object.

Overview

Property	Value
Workflow type	Dag
Library	App-tickets
Version	1.0

Input Schema

Field	Type	Required	Default	Description
organization_uuid	string	Yes	—	Authenticated organization scope; control-plane injected, never caller authority.
artifact_uuid	string	Yes	—	Prepared or uploading organization-scoped artifact.
storage_object_uuid	string	Yes	—	Same-organization StorageObject UUID with kind coding-git-artifact and exact frozen digest, size, and AgentSession identity.

Output Schema

Field	Type	Required	Default	Description
artifact	dict	No	—	Provider-neutral artifact; excludes storage coordinates and credentials.
changed	boolean	No	—	Whether availability was newly recorded.
plan	json	No	—	Local plan step output (whether storage evidence is required).
evidence	json	No	—	Terminal state of storage.coding-artifact.cost-evidence when collected.
commit	json	No	—	Local persist step output including the artifact projection.
workflow_run_uuid	string	No	—	DAG run identity stamped by the engine.
organization_uuid	string	No	—	Echoed root input: organization that owns the artifact.
artifact_uuid	string	No	—	Echoed root input: the artifact marked available.
storage_object_uuid	string	No	—	Echoed root input: the attached storage object.
failure_reason	string	No	—	Engine-stamped human-readable failure reason
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
failed_at	string	No	—	ISO-8601 timestamp when action_fail recorded the failure

DAG Layers

#	Layer	Steps	Compensation
1	plan	ticket.coding-artifact.available-plan	—
2	evidence	storage.coding-artifact.cost-evidence	—
3	commit	ticket.coding-artifact.available-commit	—
4	artifact	ticket.coding-artifact.available-artifact	—

Execution Flow

Sub-workflows

Sub-workflow	Step name
ticket.coding-artifact.available-plan	plan
storage.coding-artifact.cost-evidence	evidence
ticket.coding-artifact.available-commit	commit
ticket.coding-artifact.available-artifact	artifact

API Usage

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

{
  "workflow_type": "ticket.coding-artifact.available",
  "initial_data": {
    "organization_uuid": "value",
    "artifact_uuid": "value",
    "storage_object_uuid": "value"
  }
}