Skip to main content
Challenge

Build a Hardware Inventory and Firmware Change Impact Reviewer

Cross-reference multi-accelerator inventory reports with vendor firmware release bulletins. Hosted Claude analyzes driver compatibility tables to evaluate update risks before site rollouts.

EngineeringHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Cross-reference multi-accelerator inventory reports with vendor firmware release bulletins. Hosted Claude analyzes driver compatibility tables to evaluate update risks before site rollouts.

Datacenter Platform Architect

Parse server hardware inventory records including accelerator models, baseboard management versions, and host driver revisions.

Compare installed revisions against vendor release notes and known regression advisories.

Use hosted Claude to evaluate firmware upgrade paths, dependency breaks, and mandatory reboot constraints.

Export a staged roll-out risk assessment document and firmware change ticket manifest.

Web review queue listing pending server chassis updates with risk score tags.

Create synthetic JSON files listing rack chassis IDs, PCI device IDs, installed firmware versions, and vendor bulletin diffs. Starter examples below are synthetic. They are not downloaded records.

Anthropic Python SDK Uses the Anthropic Python SDK to submit inventory diffs to hosted Claude for structured change advisory analysis.

langfuse, anthropic, pydantic, pandas. Langfuse provides telemetry and prompt tracing for tracking firmware review latency, evaluations, and decision auditing. Hosted Claude API for technical compatibility evaluation and change impact summarization.

Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

Isolates every chassis running outdated firmware below the required baseline version.

Identifies compatibility conflicts between kernel drivers and accelerator runtime versions.

Produces structured change-order stages grouping nodes to maintain high-availability minimums.

```json [ { "input": { "cluster_id": "compute-pod-alpha", "target_firmware": "v550.54.15", "installed_inventory": [ { "chassis_id": "srv-01", "accel_model": "H100-SXM", "current_fw": "v535.129.03", "driver_compat": "OK" }, { "chassis_id": "srv-02", "accel_model": "H100-SXM", "current_fw": "v550.54.15", "driver_compat": "OK" } ] }, "expected_output": { "upgrade_candidates_count": 1, "flagged_chassis": [ "srv-01" ], "rollout_groups": [ { "phase": 1, "chassis_ids": [ "srv-01" ], "drain_required": true } ], "high_availability_risk": "LOW" } }, { "input": { "cluster_id": "compute-pod-beta", "target_firmware": "v550.54.15", "installed_inventory": [ { "chassis_id": "srv-10", "accel_model": "A100-SXM", "current_fw": "v515.65.01", "driver_compat": "INCOMPATIBLE_KERNEL" } ] }, "expected_output": { "upgrade_candidates_count": 0, "flagged_chassis": [], "rollout_groups": [], "high_availability_risk": "BLOCKED_BY_DEPENDENCY" } } ] ```

Review and simulation only. Does not flash firmware or issue remote execution commands to actual IPMI/BMC interfaces. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Review and simulation only. Does not flash firmware or issue remote execution commands to actual IPMI/BMC interfaces. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Isolates every chassis running outdated firmware below the required baseline version. Identifies compatibility conflicts between kernel drivers and accelerator runtime versions. Produces structured change-order stages grouping nodes to maintain high-availability minimums.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Parse server hardware inventory records including accelerator models, baseboard management versions, and host driver revisions. Compare installed revisions against vendor release notes and known regression advisories. Use hosted Claude to evaluate firmware upgrade paths, dependency breaks, and mandatory reboot constraints. Export a staged roll-out risk assessment document and firmware change ticket manifest.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Isolates every chassis running outdated firmware below the required baseline version. Identifies compatibility conflicts between kernel drivers and accelerator runtime versions. Produces structured change-order stages grouping nodes to maintain high-availability minimums.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

Web review queue listing pending server chassis updates with risk score tags.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Review and simulation only. Does not flash firmware or issue remote execution commands to actual IPMI/BMC interfaces.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Parse server hardware inventory records including accelerator models, baseboard management versions, and host driver revisions.

  • Compare installed revisions against vendor release notes and known regression advisories.

  • Use hosted Claude to evaluate firmware upgrade paths, dependency breaks, and mandatory reboot constraints.

  • Export a staged roll-out risk assessment document and firmware change ticket manifest.

Resources and assets

Reference links and supporting material

Dataset notes

Create synthetic JSON files listing rack chassis IDs, PCI device IDs, installed firmware versions, and vendor bulletin diffs. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

Langfuse

Open-source LLM observability and evals.

Evaluated output

No output checks are configured.

Evaluation checks
  • Parse server hardware inventory records including accelerator models, baseboard management versions, and ho...
  • Isolates every chassis running outdated firmware below the required baseline version. Identifies compatibil...
  • Web review queue listing pending server chassis updates with risk score tags.
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 2 configured tools

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Observation
  • Langfuse · Optional
Reward / Eval
  • Langfuse · Optional

Evaluation contract

  • Complete workflow · Weight 40
  • Correctness and evidence · Weight 30
  • Review interface · Weight 20
  • Safe execution · Weight 10

Reference cases

  • 2 public reference cases

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build a Hardware Inventory and Firmware Change Impact Reviewer