DO NOT TURN SOFTWARE PROOF INTO HARDWARE FICTION.
Current project authority still says physical BIOSTAR qualification is pending, real storage is disarmed and full OS is pending. The 13.1 language work does not change that boundary.
00 current statement
G1-G5 VIRTUAL ACCEPTANCE PASS REAL_BIOSTAR PENDING REAL_STORAGE DISARMED FULL_OS PENDING
The roadmap requires a read-only inventory from the actual spare target, verification of that receipt, selection of storage/input families only from observed topology, and boot of the exact v13 artifact before any physical qualification claim.
10 storage writes are separate authority
Inventory is not permission to format or write a disk. A future write gate requires a disposable disk identity, model, serial, device path, capacity, controller relation and non-system status to be revalidated immediately before the run. Unknown, changed or ambiguous media means no write.
20 future boundaries
UEFI, SMP, GUI and networking remain separate future boundaries unless a later approved milestone brings them into scope. Current 13.1 work is primarily language/compiler work: portability and explicit floating-point behavior.
30 why 13.1 does not widen the hardware claim
Strict portability and explicit floating-point work change compiler contracts, not the physical-machine acceptance boundary. A correct SSE2 sequence in a deterministic native package does not prove a storage controller, keyboard path or firmware topology on the spare target. Those claims still require their own observed evidence.
This separation also keeps regression analysis useful: a 13.1 float failure belongs first to semantic representation, Native MIR, ABI transport or instruction selection. A physical boot failure belongs first to the machine evidence chain. Mixing those layers would make both harder to debug.