V13 MACHINE FOUNDATION: WHAT THE PROOF OWNS.
The stable contract is an x86_64 freestanding software foundation with virtual G1-G5 acceptance. It is not a blanket claim that every PC boots, every disk is safe to write, or a finished desktop OS exists.
00 G1 · BIOS-first discovery
G1 uses Multiboot2 and a checked two-argument entry ABI. It validates versioned BootInfo, bounds and normalizes the memory map, validates ACPI discovery data, discovers APIC/IOAPIC/timer topology, enumerates PCI mechanism #1 read-only, keeps COM1/VGA diagnostics available and produces deterministic ELF/ISO artifacts. The bounded path halts after G1 COMPLETE. PCI BAR sizing writes, bus-master enable, storage writes and guessed routing do not belong in this discovery proof.
10 G2 · primitives and memory ownership
G2 owns width-correct CPU/device primitives, descriptor/control-register work, TSS64/IST and a documented interrupt/resume image. Paging moves away from old 32-bit assumptions toward four-level translation and firmware-derived physical ownership. Volatile access alone is not treated as a cache policy or a device-memory barrier.
20 G3 · topology and interrupts
G3 validates firmware topology before using it: ACPI lengths/checksums and referenced physical ranges, PCI bridge/function discovery, APIC/IOAPIC routing and timer bring-up. Unsupported firmware that needs unimplemented behavior must fail explicitly. Invented routing is not compatibility.
30 G4 · storage and input
Virtual acceptance can exercise storage and input contracts without granting physical write authority. Storage is introduced behind a narrow sector service, then DBFS1/minimal VFS and durability proof. On physical hardware, controller and media selection require separate observed evidence.
40 G5 · userspace boundary
The final virtual generation covers x86_64 DByte userspace, private address spaces, worker/syscall ownership, validated copyin/copyout, owner-qualified file descriptors, deferred fault/exit cleanup and shell-level execution. GUI, networking and SMP remain separate future boundaries.
50 physical boundary
G1-G5 VIRTUAL PASS REAL_BIOSTAR PENDING REAL_STORAGE DISARMED FULL_OS PENDING
Read the raw stable contract: V13_MACHINE_FOUNDATION.md.
60 how to read machine evidence
Source inspection proves that a path exists. A verifier proves only the behavior it actually executed. QEMU proves behavior under the selected virtual machine. A physical receipt proves behavior on the named hardware configuration. None of those evidence classes automatically upgrades into the next one.
That is why discovery remains read-only before driver selection and why storage authority is separated from inventory. Firmware tables, PCI enumeration and controller identity are inputs to a later decision; they are not permission to enable bus mastering or write a sector. Unknown topology stays unknown instead of being filled with a plausible guess.