os:Status
The execution status of a process.
Usage
Query os:status on a process to determine its current lifecycle state. Use the named individuals (os:InProgress, os:Completed, os:Failed, os:Interrupted, os:Suspended) for comparisons rather than string matching.
Explanatory Note
Status is represented as named individuals rather than string values, enabling type-safe references and inference. Every process has exactly one status at any point in time.
Named Individuals
os:Completed
The process finished successfully and produced its expected result.
Usage: Not all process types use Completed. Orchestrator workflows use Suspended between utterances and are never marked Completed. Sub-agent tasks and action invocations use Completed to signal success.
os:Failed
The process encountered an error and could not produce its expected result.
Explanatory Note: When a process fails, os:failedWith links to the exception entity containing the error message and cause chain. If action healing is enabled, a healer process may attempt recovery before the failure propagates.
os:InProgress
The process is currently executing.
Explanatory Note: This is the initial status for most processes. A process remains InProgress until it completes, fails, is interrupted, or is suspended.
os:Interrupted
The process was cancelled before it could complete.
Explanatory Note: Interruption cascades to all child processes. An interrupted process does not produce a result and its partial work may be incomplete.
os:Suspended
The process is paused and waiting to be resumed.
Explanatory Note: Suspension is used in two contexts. For the orchestrator workflow, Suspended is the idle state between user utterances (the orchestrator is never marked Completed, only InProgress or Suspended). For action invocations, Suspended indicates the process is waiting for a human-in-the-loop response, such as an escalation approval.