Space Physical Target And BSP Claims

S2 defines how 0x0 records space-facing physical target and BSP claims.

The local gate is:

make space-physical-bsp-check

This gate is bounded. It generates emulated sim-cortex-m0 evidence, validates

target claim rows, validates debug and flash workflow rows, validates BSP and

interrupt hook rows, and verifies that the repository default physical inventory

has zero physical claims.

Claim Source

The machine-readable claim tables are:

• space/physical-target-claims.tsv;
• space/debug-flash-workflows.tsv;
• space/bsp-interrupt-hooks.tsv;
• space/s2-emulator-evidence.tsv.

lab-cortex-m0 is the selected first physical board identity for lab evidence.

It is intentionally physical-evidence-pending, not physical-ready.

Physical Claim Rule

A physical target can be claimed only when

make physical-hardware-evidence-check accepts complete target evidence:

• firmware image;
• secure-boot manifest;
• physical log;
• monitor trace;
• recovery trace;
• flashing receipt;
• HIL campaign;
• operator signoff;
• active root-key custody.

Until those artifacts are supplied, make space-physical-bsp-check requires

the default repository inventory to report zero physical claims.

Debug And Flash Workflows

S2 records GDB, OpenOCD, pyOCD, SWD, JTAG, and emulator workflows. Every row

must require:

• exact tool version evidence;
• target identity;
• firmware hash evidence;
• operator signoff.

The workflow rows are ready for lab execution, but physical execution remains

evidence-gated.

BSP And Interrupt Hooks

BSP rows must declare:

• calling convention;
• stack budget;
• blocking behavior;
• priority;
• fault behavior.

The local gate checks UART, timer, watchdog, interrupt, reset, memory map, and

fault hook rows against emulated target evidence. Physical target hook evidence

must be supplied later by lab artifacts.