Preparing the ZBL download portal…
ZBLZERO BOUNDARY LANGUAGEv0.5.0-preview.5 is staged for local review. Public download availability is pending.
9b25227b21ae2ce129da2ecbf4ab051f6214df397bf18925ea164a98cee13b34SDK preview.5 is staged. Verified artifacts are available through a local preview handoff.
Installation guide ↗Meet Zero Boundary Language.
Easy to begin. Explicit where it matters.
Write, check and run real ZBL programs with a Rust-built toolchain and an embedded interpreter.
name = "ZBL"show "Hello " + name + "!"# ZBL SDK 0.2.0Hello ZBL!
A real language pipelineLexer → parser → types → runtime
Small by designTyped tasks, collections and eleven CLI commands.
Evidence before releaseChecksums and installation verification
Everything needed to create a project, validate your code and execute your first program. One compact, versioned distribution.
Real parsing, name resolution and static type checking.
Control flow, shapes, typed collections and recoverable errors.
Project generation, executable tests and VS Code syntax sources.
v0.2.0 is a foundation release. Native compilation, smart contracts and a browser backend are future milestones.
Windows 11 · x64 · v0.2.0
The language toolchain, in one place. Compiler pipeline, Zebvix CLI, embedded runtime, standard library and editor sources.
Installation guide is ready. Public HTTPS artifact storage awaits release approval.
86fb18783550f5bd9847a9956bed38d9ce3b397ee8ac5bc3cde8f6c8bd2787fcCompare bootstrap installer and CLI hashes against the actual release manifest before execution. No administrator access required.
Run the bootstrap installer, then zebvix install. Existing installations are preserved; the destination must be new.
Add Zebvix to your user PATH, refresh this shell, then run doctor to inspect the installed SDK.
# After installing the Zebvix bootstrap CLI
zebvix install
zebvix --version
zebvix doctor
# SDK lifecycle
zebvix update
# Remove SDK only; keep the bootstrap CLI and projects
zebvix uninstallPublic download pending. Local review requires explicit --manifest and --artifact options; see the verified offline installation guide. Full installation & safe uninstall guide ↗
Create a project with a working entry point and an actual test. Build checks the program. Run executes it. Test invokes each test_ function.
Explore the CLI reference ↗Hello ZBL!Through the real language pipelinezebvix --version
zebvix install
zebvix doctor
zebvix new hello-zbl
cd hello-zbl
zebvix check
zebvix fmt
zebvix build
zebvix run
zebvix testThe checksum is calculated from the actual archive. A missing or mismatched artifact cannot be downloaded through the portal.
SHA-256 / WINDOWS x6486fb18783550f5bd9847a9956bed38d9ce3b397ee8ac5bc3cde8f6c8bd2787fc1,291,467 bytes · zbl-sdk-0.2.0-foundation.2-windows-x64.tar.gz
No release signing key is configured. Windows lifecycle commands refuse declared signed artifacts until a compatible verifier is implemented. SHA-256 confirms byte integrity; it does not prove publisher identity. No security certification is claimed.
When signing is enabled, an Ed25519 detached signature and public key will be published. Confirm the key fingerprint through a trusted channel before verification.
openssl pkeyutl -verify -pubin -inkey release-public.pem -rawin -in SDK.tar.gz -sigfile SDK.tar.gz.sigNo signature or key is currently available. Do not run this command until genuine signing files are published.
The installed SDK includes its runtime. Rust and Cargo are required only when building the SDK from source.
Static types, checked execution, project tooling and real tests.
Public publication date: pending · Local installation verification: 2026-11-06Previous staged Windows candidate. Existing immutable artifacts and brace-syntax compatibility remain; no prior public publication is implied.
Practical answers for the first release.
All known limitations ↗The Windows archive exists and has passed local installation checks. Public HTTPS release storage and publication approval are still pending. The local preview offers that verified archive for review.
Open a new terminal after running the bootstrap installer, or prepend $env:LOCALAPPDATA\Zebvix\bootstrap\0.2.0\bin to the current shell PATH. Run the executable by its full path to confirm the installation.
Inspect the script and verify the archive hash. If a downloaded script is blocked, use Unblock-File on the reviewed bootstrap installer. For organization-managed execution policies, contact your administrator; do not disable policy globally.
No. v0.2.0 validates source and emits a versioned checked-source .zbc artifact. zebvix run recompiles project source and executes its statically checked AST.
The SDK includes a static HTML starter. A browser compiler, UI runtime, smart-contract backend and ZBVM are future work.
Versions install to separate directories. The installer refuses an existing destination. Use zebvix update and zebvix uninstall through the bootstrap CLI; user projects and the bootstrap CLI remain, and modified SDK files cause uninstall refusal. Keep projects outside the SDK directory.