Activation
Establishes node participation; it is not assignment.
How workloads reach capacity and how execution remains inspectable.
Routing connects accepted workloads with eligible execution capacity. Observability then exposes the state and evidence needed to understand execution through completion.
Routing sits between accepted work and processing capacity.
A workload entering routing already exists as execution state, but it has not necessarily begun processing. The network evaluates currently eligible capacity and selects a destination when suitable execution infrastructure is available.
Availability
Describes whether node capacity is currently available.
Eligibility
Represents whether capacity can be considered for the current workload.
Assignment
Connects the Job with selected execution capacity.
The result remains connected to the execution that produced it.
01Execution
02Completion
03Structured Result
04Originating Application
Result delivery is not the only observable outcome. The Job remains valuable because it preserves lifecycle, timing, assignment, logs, telemetry, and failure context.
Investigate from state outward.
Read lifecycle status
Determine whether the workload is waiting, routing, running, completed, or failed.
Inspect timing and assignment
Locate where progress changed.
Inspect logs
Review execution events exposed by the system.
Inspect telemetry
Add operational measurements where available.
Finish with result or failure data
Use the terminal outcome rather than guessing from intermediate state.