Inspect endpoint state and verified outcomes.
Use a synthetic fleet to inspect the product model without exposing customer data. Capability labels and evidence states follow the published capability status.
Inspect the endpoint record.
Search sample devices by hostname, user or site, then inspect platform, state and last-seen context. Data is generated locally in the browser; no customer endpoint data is shown.
BLR-FIN-001
State, action and governance in one evaluation path.
Endpoint state
Identity, online/offline, last seen, platform, site and inventory context.
Action outcome
Requested, executed, observed and verified states remain separate.
Governance
Authorization, tenant scope and evidence are part of the action record.
Execution success can still fail verification.
A provider result is one data point. ZENQIX compares it with what the endpoint reports afterward.
Software desired state
Keep the facts needed to explain the outcome.
The public example shows a bounded event record rather than an unfiltered console log.
Know what evidence you are viewing.
Synthetic models stay labelled. Genuine product screenshots can replace them only after customer and environment data is removed and the capability is approved for public use.
Use product proof to define the pilot.
Compare platform status, deployment requirements and acceptance criteria before putting an agent on a production endpoint.