V12.0 BASE CONTRACT

Install v12.0

Verify the frozen Windows x64 release package, then place dbyte.exe and dbytec.exe on PATH.

DByte 12.0 · Getting started

CURRENT RELEASE IS 12.2.1 · INSTALL 12.2.1 HERE. THE INSTRUCTIONS BELOW REMAIN THE FROZEN 12.0 PACKAGE PATH.

Contract§

The package is 3,196,504 bytes with SHA-256 83f9de1e1116ebfe0fc0a4b24338909ffab39142d4171b0b9364a51727d5e4d2.

Mechanics§

The Windows x64 archive is a portable release bundle containing dbyte.exe, dbytec.exe, tagged documentation, examples, scripts and the Kernel Lab oracle. Installation is extraction plus PATH configuration; no registry, service or package manager state is required.

Validation and failure§

Verify the exact byte size and SHA-256 before execution, then require dbyte --version to report 12.0.0. A name match without a hash match is not the released compiler.

Evidence and boundary§

The website verifier compiles fixtures with binaries extracted from the published archive, not a workspace build.

Copy-paste verification§

COMMAND · WINDOWS POWERSHELL · V12.0.0

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

EXPECTED SIZE    3196504
EXPECTED SHA256  83F9DE1E1116EBFE0FC0A4B24338909FFAB39142D4171B0B9364A51727D5E4D2

Host support§

Surface	12.0 release status
Windows x64 host package	SUPPORTED
Linux host package	NOT RELEASED
macOS host package	NOT RELEASED
i686 bare-metal target	DOCUMENTED
x86_64 application target	DEFERRED

Platform install status§

v12.0.0 has one supported binary host distribution: Windows x64. Linux and macOS are not current host-package surfaces. Do not treat the existence of Rust source or an ELF target as proof that the compiler itself is supported on those hosts.

Host	Install path	Status
Windows x64	Download ZIP → verify SHA-256 → extract → run `scripts\install.ps1` or place binaries on PATH.	SUPPORTED
Linux	No supported v12.0.0 binary install path.	NOT RELEASED
macOS	No supported v12.0.0 binary install path.	NOT RELEASED

HISTORICAL V12.0 ROADMAP NOTE: x86_64-dbyte-linux was proposed for v12.3 at this baseline. That roadmap is superseded: the target shipped in v12.2. This page still documents only the frozen v12.0 host-install truth; use current v12.2 platform status for present target support.

Windows install§

COMMAND · WINDOWS POWERSHELL · SUPPORTED HOST

Expand-Archive .\dbyte-v12.0.0-windows-x64.zip .\dbyte-v12.0.0
cd .\dbyte-v12.0.0
powershell -ExecutionPolicy Bypass -File .\scripts\install.ps1

dbyte --version

Then run the exact release fixture:

dbyte run examples\hello.dby

Expected output:

Hello, DByte!

Troubleshooting§

Use symptom → check → fix. Do not bypass a failed release hash and do not change machine-wide PowerShell policy just to run DByte.

Symptom	Check	Action · success gate
ZIP not found	`Get-Location` `Test-Path .\dbyte-v12.0.0-windows-x64.zip`	Move to the download directory or set `$Zip` to an absolute path. `Test-Path $Zip` must return `True`.
SHA-256 mismatch	`Get-FileHash $Zip -Algorithm SHA256`	STOP. Do not execute the archive. Re-download it and require both 3,196,504 bytes and the frozen release SHA-256 to match.
Archive extraction fails	`Test-Path $Zip` `(Get-Item $Zip).Length`	Verify size/hash first, then use `Expand-Archive -LiteralPath $Zip -DestinationPath .\dbyte-v12.0.0`. Require `dbyte.exe` and `dbytec.exe` to exist after extraction.
`dbyte` not found	`Get-Command dbyte -All` `$env:Path -split ';'`	From the extracted directory, test `.\dbyte.exe --version`. If that works, PATH is the problem; run the helper or add the directory to PATH and open a new PowerShell session.
PowerShell blocks `install.ps1`	`Get-ExecutionPolicy -List`	DByte executables do not require a policy change. Run the helper only with `powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\install.ps1`. No machine-wide `Unrestricted` setting is required.

PATH proof without changing PATH§

COMMAND · WINDOWS POWERSHELL · EXTRACTED RELEASE DIRECTORY

Get-Command .\dbyte.exe
.\dbyte.exe --version
.\dbyte.exe run .\examples\hello.dby

Expected identity: DByte 12.0.0. Expected hello output: Hello, DByte!. If relative execution works while dbyte does not, the compiler is present and only command discovery remains unresolved.

Failure law§

HASH MISMATCH       => DO NOT RUN
RELATIVE EXE WORKS  => PACKAGE OK / PATH ISSUE
SCRIPT BLOCKED      => HELPER POLICY ONLY
EXE RUNS            => NO EXECUTION-POLICY CHANGE NEEDED