DevTools
Read the execution screen
Interpret live UseCases, queue positions, lifecycle events, and terminal history without changing runtime state.
Read the execution screen
The overview is organized around live UseCase instances. A label identifies the application role when the inspected UseCase provides one; the runtime type remains the stable technical identity.
Positions are lifecycle evidence
| Position | Meaning |
|---|---|
| Admission | Input Instructions or PendingQueue capacity still control the Entry |
| Pending | input passed; processing eligibility has not been granted |
| Starting | the scheduler selected the Entry and is establishing Execution state |
| Processing | the registered handler is active |
| Finalizing | terminal hooks, history, and resource release are completing |
Positions are not separate application queues that DevTools owns. They are a read-only projection of core diagnostics.
Correlate one Execution
Use Execution ID to connect its events, Snapshot changes, cancellation request, error route, and terminal Entry. Command type and execution key explain grouping, but they do not uniquely identify one attempt.
Terminal history contains accepted work with completed, failed, cancelled, or terminated Results. Commands rejected before processing appear as rejection events and intentionally do not become history.