0x0 Documentation

0x0 is the current language and toolchain path for new work.

This site teaches what 0x0 does today. When a feature is unsupported,

target-gated, or app-specific, the page says so directly.

Start Here

If you are new to 0x0, read these in order:

1. Learn 0x0

2. First program

3. Syntax, values, and control

4. Functions, bindings, and annotations

5. Packages and imports

After that, use Tasks when you know what you want to do, or

Cookbook when you want a working example.

What 0x0 Source Looks Like

A small executable 0x0 file has a module form and a main function:

(⊙ main)

(ƒ main
  (∷ (→ Unit I64))
  (_)
  42)

Run the repository example with:

./bin/zero run examples/main.0x0

The expected output is:

42

Learn

• Repository docs home: beginner, intermediate, advanced,

and reference paths through the full source docs.

• Getting started: setup, first program, imports,

ADTs, examples, and checks.

• Concepts: source-owned compiler, seed boundary, OISA,

capabilities, packages, scripting, and evidence gates.

• Learn 0x0: the beginner course.
• Tutorials: grouped learning paths.
• How-to guides: short task workflows.
• Cookbook: examples backed by repository files.
• Tasks: the shortest path for common jobs.

Build

• Architecture
• Language guide
• Package guide
• Core library guide
• Runtime capabilities
• Examples guide
• Safe command guidance

Public documentation work should use the smaller public-docs gates unless it

also changes source documentation policy.

Reference

• Reference index
• Generated API reference
• API reference guide
• Diagnostics
• Compiler
• ABI
• Release compatibility
• Versioning

Reference pages stay technical. They are the exact source of truth for syntax,

compiler behavior, runtime boundaries, packages, and release rules.

Libraries

• Libraries overview
• Package docs
• Core API docs

The local 0x0 libraries are documented now. The public libs.jmp0x1b.com

registry is the active registry site for 0x0 library packages.

Operate

• Runtime production capabilities
• Troubleshooting
• Web runtime
• Live framework
• Service boundary runtime
• Embedded and hardware runtime
• Feature support matrix

App-specific behavior is documented as app behavior. It is not treated as a

generic language feature unless the language/runtime docs say it is.

Embedded And Distributed Runtime

Embedded, bare-metal, HAL, RTOS/BSP, secure boot, space assurance, hardware

proof, actors, supervision, replay, distributed execution, and generic

LiveView-style runtime now have a current 0x0 boundary. See

Embedded And Hardware Runtime for what is supported now and what

still needs target-specific implementation evidence.