hardware-bringup-checklist

name	hardware-bringup-checklist
description	Validate power, buses, firmware, interfaces, and low-level sanity checks during hardware bringup. Use when a new robot or board is first being brought online.

Hardware Bringup Checklist

Overview

Validate power, buses, firmware, interfaces, and low-level sanity checks during hardware bringup.

Core Workflow

1. Gather goals, constraints, current state, and the relevant systems or stakeholders involved.
2. Identify the main options, dependencies, risks, and sequencing constraints before proposing a path.
3. Build a staged plan, comparison, or checklist that makes tradeoffs explicit instead of hiding them.
4. Attach the validation, rollback, or decision checkpoints needed to execute safely.

Deliver

• A staged plan, scorecard, or checklist that can actually be executed.
• The assumptions, tradeoffs, and blockers that matter most.
• Clear next actions, decision points, and validation steps.

Guardrails

• Do not collapse risky work into a single step when sequencing matters.
• Keep assumptions explicit and highlight missing information early.
• Prefer reversible steps and clear checkpoints when the task has operational risk.
• Avoid commands that actuate hardware, move robots, or change live controller state unless explicitly requested.