V12.0 BASE CONTRACT

Reproduce this proof

Commands, input identities and evidence-record rules for reproducing release, hosted and machine proofs.

Published release verifier§

/proofs/verify-v12-release.ps1 is shipped with this site as a portable Windows PowerShell smoke verifier.

powershell -ExecutionPolicy Bypass -File .\proofs\verify-v12-release.ps1 `
    -ZipPath .\downloads\dbyte-v12.0.0-windows-x64.zip

It checks: exact archive size/hash; exact examples/hello.dby hash; presence of dbyte.exe/dbytec.exe; a 12.0.0 version identity; and exact tree + VM output Hello, DByte!.

BOUNDARY: this proves release identity plus hosted execution parity for the hello fixture. It does not prove IRQ delivery, ATA, DBFS1 persistence, Ring3 transitions, or future x86_64/Linux support.

Proof-class map§

Proof	Entry	Claim bounded to
Release package	published PowerShell verifier	bytes + hello tree/VM smoke
V12 semantic/toolchain corpus	repository verifier suite at the release identity	HIR · generics · enums · ownership · closure · C-ABI corpus
V11 machine milestones	verification ledger	QEMU/serial/trace/disk milestone-specific evidence
Website	structural QA during build	routes · hashes · zero-JS · local references

REPRODUCTION LAW: command + exact input identity + acceptance condition + captured output. A report that only says PASS is not enough.

01 release identity§

$Zip = ".\\dbyte-v12.0.0-windows-x64.zip"
(Get-Item $Zip).Length
(Get-FileHash $Zip -Algorithm SHA256).Hash

# expected
3196504
83F9DE1E1116EBFE0FC0A4B24338909FFAB39142D4171B0B9364A51727D5E4D2

02 hosted smoke§

dbyte --version
dbyte run examples\\hello.dby
dbyte run --vm examples\\hello.dby

03 v12 HIR proof entrypoint§

# Repository checkout at the v12.0.0 release identity:
powershell -ExecutionPolicy Bypass -File scripts\\verify_native_v12_hir.ps1

The supplied Windows release bundle used for this audit contains scripts/install.ps1 but not the repository verification suite. The v12 HIR command is therefore a repository-source proof entrypoint, not a claim that the release ZIP alone contains that script.

04 v11 machine proof entrypoints§

scripts\\verify_native.ps1
scripts\\verify_native_kernel_core.ps1
scripts\\verify_native_memory_core.ps1
scripts\\verify_native_runtime_core.ps1
scripts\\verify_native_scheduler_core.ps1
scripts\\verify_native_blocking_core.ps1
scripts\\verify_native_irq_io_core.ps1
scripts\\verify_native_block_device_core.ps1
scripts\\verify_native_filesystem_core.ps1
scripts\\verify_native_filesystem_runtime.ps1

Exact acceptance strings and milestone-specific negative gates remain in the V11 verification ledger.

05 evidence record format§

PROOF-ID:
SOURCE-COMMIT:
PACKAGE-SHA256:
COMMAND:
ENVIRONMENT:
INPUT-HASHES:
EXPECTED-ACCEPTANCE:
OBSERVED-OUTPUT:
OUTPUT-HASHES:
RESULT: PASS | FAIL

SOURCE POLICY: release/tag documents define contracts; examples are copied from the supplied v12.0.0 package or explicitly marked as explanatory. Unsupported claims are not upgraded by prose.