Full Parity Milestone 4 Embedded And Hardware Evidence

Milestone 4 tracks embedded, hardware, HAL, RTOS/BSP, secure boot, hardware

probe, physical evidence, and certification evidence parity for the active full

parity roadmap.

The milestone is active. Milestone 3 is pending, not complete.

Gate

Use the bounded source gate:


make full-parity-milestone4-check

Generate the evidence ledger when the embedded and hardware surface changes:


make full-parity-milestone4

The gate does not self-host, flash a physical board, start remote services, or

run deployment commands.

The machine-readable ledger is:

It records each Milestone 4 submilestone, the production path, positive and

negative gates, public docs, release boundary, and status.

make embedded-hardware-check executes the emulated hardware path. It builds

deterministic MCU object and image artifacts, linker scripts, vector tables,

maps, metadata, and checksums from a 0x0 source fixture. It runs that image

through the virtual MCU harness, checks HAL and RTOS/BSP behavior, verifies

secure-boot signatures, exercises dry-run and emulator flashing, runs virtual

hardware probes, and aggregates safety evidence.

The RTOS/BSP fixture is intentionally named virtual-rtos-v1. It is a bounded

virtual runtime fixture, not a fake production adapter.

The committed repository inventory is emulated-only. It does not claim an

attached physical board or active root-key custody.

make physical-hardware-evidence-check verifies the strict physical evidence

intake path and proves that physical target claims fail closed when signoff,

placeholder-free logs, HIL campaigns, root-key custody, secure boot manifests,

or firmware hashes are missing.

make certification-evidence-check creates deterministic evidence bundles and

physical-readiness reports for local review. External certification remains an

external approval step and must be attached to a release if a release claims a

certified physical target.

Every embedded, hardware, HAL, RTOS/BSP, secure boot, physical evidence, or

certification behavior change must update this file, docs/embedded-hardware.html,

docs/physical-hardware-evidence.html, docs/certification-evidence.html,

docs/feature-support-matrix.html, and docs/release-notes.html in the same

change unless the ADR/RFC explicitly explains why a location is unaffected.