The diagnostics agent

When a device fails, an investigation runs a fixed, inspectable pipeline. Every step, tool call, and retrieved passage is persisted — the run is auditable after the fact, never a black box.

Lifecycle

trigger (alert | ticket | manual)
  → gather    telemetry window around the failure
  → localize  fault, down to the firmware loop or pin
  → research  the MCU datasheet (page-cited passages)
  → resolve   RCA + patch draft, syntax-validated in a sandbox
  → review    a human approves — or it goes nowhere

status: queued → running → needs_review → resolved | failed

Grounding rules

The agent may not assert a root cause it cannot point to: every claim links to a telemetry window or a cited datasheet page. Below the confidence threshold it flags "manual review needed" instead of proposing a patch.

What the agent can never do

Auto-post a patch, execute firmware, or touch another tenant's data. Patch validation is clang-format plus a syntax-only compile in a sandbox. Posting to a ticket or handing a patch to your OTA pipeline requires an explicit human action after approval — and both are recorded in the audit log.

Datasheets

Upload your MCU reference manuals (PDF). They are parsed page-aware, embedded, and scoped to your organization — proprietary documents are never shared across tenants or used to train shared models. Citations carry the page number so you can check the agent's reading yourself, in one click.

Agent features are part of the Enterprise / Agent tier. The eval harness and its accuracy history ship with it — ask to see our current localization and citation accuracy numbers before you trust the agent with more autonomy.