Separate Hardware and Controller Lifecycle States in Status Views
Inventory status subjects
Identify the manager, hardware components, controllers and downstream task state separately. Jazzy manager activity includes managed hardware and controller lifecycle information.
Review status reception
The documentation describes activity on state changes with transient-local durability. Inspect subscriber settings, observation time and source. An empty late-joining display should not automatically imply hardware failure.
Explain combined states
Hardware availability and controller activation are distinct conditions. Include examples with only one present, both present and stale observations, documenting how each combination is presented.
Join state changes to evidence
Associate transitions with activation responses, interface claims or hardware errors from the same run. Task completion requires evidence from the consumer responsible for the activity.
Deliver a status dictionary
Retain source, timestamp meaning, stale handling and aggregation for every indicator. Revisit names and state mappings after manager or interface changes to preserve component identity.
Original documentation and further reading
Continue with related articles in this section, or use selection guides to prepare the next review. Apply the device-specific documentation and agreed operating conditions when implementing a test.