repo-b-hardware-first

To diagnose hardware failures without stubs, set strict environment flags and run real preflight checks to validate behavior against the actual hardware path and avoid simulations.

Hardware-first diagnosis is a strict validation workflow that runs doctor and probe checks on real hardware environments to capture deterministic evidence for runtime, telemetry, and inference paths.

Run strict preflight checks by applying strict environment flags and executing doctor and probe checks on your target system to verify fixes and capture diagnostic evidence for integration validation.

Yes, you can diagnose shim issues by enabling strict environment flags and running hardware-path validation to ensure your runtime probes and telemetry rely on real hardware behavior rather than stubs.

The best way to capture evidence for telemetry and inference failures is to execute strict preflight profiles on real hardware, organizing the diagnostic output to support chain recalculation and verification.

Diagnostics mismatch real hardware behavior when strict environment flags are not applied, causing the validation to fall back on stubs or simulations instead of executing real-hardware preflight checks.