← Explore all agents

INFRASTRUCTURE / Agency Agents community

IoT fleet and staged-update architect

A fleet-design profile for intermittent devices, scoped identity and health-gated firmware rollouts.

“Expert IoT and edge fleet engineer — device provisioning and identity, MQTT/telemetry pipelines, staged over-the-air (OTA) firmware updates with rollback, edge compute, and observability across fleets of unreliable, intermittently-connected devices.”

01 / THE REASONING

Why this made the selection.

  • It combines bounded edge buffering with original timestamps and sequence-based backend deduplication.
  • Update progression is gated by healthy check-ins across hardware revisions rather than the percentage of downloads completed.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • engineering/engineering-iot-fleet-engineer.md (pinned complete source retained)
  • LICENSE
  • Repository README and current official host configuration documentation

Our findings

  • It combines bounded edge buffering with original timestamps and sequence-based backend deduplication.
  • Update progression is gated by healthy check-ins across hardware revisions rather than the percentage of downloads completed.

Not established by this review

  • Source review only: no agent was installed or invoked. Task correctness, effective host restrictions and integration behaviour were not tested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Use the role in your project.

Upstream setup instructions ↗
  1. Read the pinned source and its licence, then configure an explicitly bounded host context.
  2. Check the original display-style name and optional color/emoji/vibe metadata against the installed host requirements before loading a working copy. Current Claude Code documentation says unknown frontmatter fields are ignored; it does not establish a need to rewrite these names. Keep the archived/downloaded original unchanged.
  3. Verify the actual hardware trust and recovery chain, configure broker authorization and test power-loss/offline cases on representative devices before any fleet action.
  4. Supply device revisions, bootloader capabilities, duty cycles, connectivity and fleet constraints.

Before you start

  • Actual device and bootloader specifications
  • Broker/fleet service and per-device identity
  • Representative hardware test fleet

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/engineering/engineering-iot-fleet-engineer.md

    Supports: Workflow, inputs, outputs and stated boundaries

  2. Applicable licence ↗Checked

    https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE

    Supports: Redistribution and attribution

  3. https://code.claude.com/docs/en/sub-agents.md

    Supports: Host loading and effective permission boundaries

Evidence & Ask