What a green pass means
LabWired is a deterministic digital twin: same firmware, same system, same inputs → same result. A pass is a check against an explicit test or oracle — not a model saying “looks fine.”
What we claim
| Claim | Meaning |
|---|---|
| Register-accurate where modeled | Firmware sees MMIO like silicon for supported blocks |
| Same binary | No special LabWired HAL; vendor SDK binaries |
| Replayable | CI and agents can re-run and get the same result |
| Honest matrix | Per-board ✅ / ⚠️ / ❌ — stubs are labeled |
Details: board pages · Target support rubric
What we do not claim
- Full analog / SPICE board physics (unless a page says otherwise)
- RF certification or perfect radio PHY
- Every peripheral on every chip at full silicon depth
- That access to an unmodeled register is safe — expect faults or stuck polls
Prefer a loud fail over a silent fake success.
Evidence (not marketing)
| Scoreboard | Page |
|---|---|
| Chip conformance | coverage/chip-conformance |
| Tier-1 peripherals | coverage/tier1-scoreboard |
| Hardware–sim parity | golden_reference |
| Run limits | limits |
Board pages that were checked on silicon list dates and harnesses (example: nRF52840).
Rule for agents
Do not claim the firmware is correct until labwired_verify (or a labwired test script) is green.
See First agent run.