Working draft · not stableSpecifications include planned features, not blanket implementation or proof claims.
From the README

Getting started

These sections are the repository README: how to build the CLI, the host Wasmtime prerequisite, one session, what works today, and how to work on the compiler. Editor reports, numeric graphs, and the rest of the README stay in the repository.

Try it

The supplied Nix flake targets x86_64 Linux. It requires Nix with flakes enabled and GitHub SSH access for the pinned OnixResearch/octet and OnixResearch/cairn inputs.

git clone https://github.com/OnixResearch/noble-lang.git
cd noble-lang

# Realize the exact runtime tools selected by this checkout.
nix build .#node .#wasm-tools .#binaryen --no-link
nix build .#noble

printf '40 2 quote [ + ] compose run\n' > example.noble
./result/bin/noble run example.noble --opt off

The CLI writes JSON reports. A successful run reports normal, with one I64 value of "42" on the output stack. Stack order is bottom-to-top; integers are encoded as decimal strings.

Host-local Wasmtime source. flake.nix sets selectedWasmtimeSource = builtins.path { path = /nix/store/26a8xzacbx01hidm70lpyphyw926zhc5-source; … }, and crates/noble-cli/Cargo.toml and crates/noble-wasm/Cargo.toml declare wasmtime = { path = "/nix/store/26a8xzacbx01hidm70lpyphyw926zhc5-source/crates/wasmtime", … }. No flake input or fetcher produces that store path, so evaluation and the crate build both require a host that already has it. On any other machine flake evaluation fails at builtins.path and the path dependency cannot resolve; supply the reviewed source closure at that path (or change the pin and both manifests together) before building.

Persistent sessions

A session keeps its stack, definitions, captured values, and compiled programs between submissions. Each line is one submission:

printf '%s\n' \
  'def n [ 1 ]' \
  '[ n ]' \
  'def n [ 2 ]' \
  'run n' |
  ./result/bin/noble session

The final stack contains 1 2. The saved program still uses the first definition of n; the later direct call uses the second.

A static rejection preserves the previous stack and namespace. A runtime trap or exhausted execution quota ends the session, retaining any host requests already observed. Sessions use a bounded arena that does not reclaim individual cells (only the separate Calculator-v1 profile compacts, at submission boundaries). Use noble session --framed for framed multiline input and --emit NEW_DIR to retain reports and emitted artifacts. Run noble --help for available CLI flags.

What works today

These features have separate implementation and acceptance scopes. Enabling one does not make every other feature available in that runtime.

AreaImplemented scope
Core language and Wasm sessionsWrapping I64 arithmetic; Bool, Text, Unit, Pair, Sum, and List values; stack operations; checked branches; quotation, capture, composition, execution, and reflection; nonrecursive definitions.
Guarded live REPLIn-process Wasm emission and explicit reload use one resident Node/V8 arena and checked publication; tested acyclic dependent rebuild and retained old Programs. Automatic watch is unavailable because rename events cannot authenticate bytes. Guest self-edit refuses current dependents; scoped indirect self-rebind/cycle refusal was exercised without general proof or canonical LIVE case acceptance. No declared-module snapshots or full LIVE-05 acceptance.
Declared modulesOpt-in opaque types, two-constructor variants, versioned session-local modules, imports and exports, and an explicit typed test.emit adapter. Available through compile and framed session.
Contracts and proof checkingA pure contract language, Lean obligations, proof/refutation checking, and verify / explain-proof.
Evidence companionsLive certified programs, evidence composition, guarded invocation, and proof-required build admission for the selected core scope.
Synchronous componentsSelected WIT bindings, component compilation, host resources, ownership transfer, and authorization checks.
Native async componentsA separate bounded component profile with native async execution and cancellation controls. General guest async syntax remains open.
Local services and choreographyA bounded local synchronous publisher/subscriber service and finite one- or two-round protocols over that service.
Numeric graphsOpt-in Numeric-Graph-v1, only through noble ngraph: checked ngraph-ir/0 graph files, exact I64 graphs extracted from Core source, directly authored F32 graphs (no kernel F32), reference and compiled CPU evaluators, adam/0 training into immutable snapshot files, and provenance replay. Recorded cases: 14 passed / 1 held (CASE-02), with six additional fresh finite observations bound to the final candidate; the exact review and terminal receipts decide case registration. Implementation partial, change active, not archived. Phase C measured 0.06–0.18× the speed of host-native Rust, so there is no performance or GPU claim; NG-PO-A..H remain open.

Ordinary run and session use the resource-free Core-Bootstrap profile. Their host words are test.emit and test.abort. Resources and component features use separate entry points. Recursive definitions, local bindings, general libraries and capability modules, portable package identities, and general distributed services remain open.

The exact calculator is the planned reference application; an experimental guest-backed noble calculator exists, but its acceptance criteria remain open. Its numeric error schema prerequisite has a finite 18-case compiled-guest observation on a rebuilt binary, explicitly not source-bound; the opt-in byte cursor does not establish MA1 or CALC acceptance. The typed-worker design describes future worker admission and lifecycle contracts. Neither is a completed application or agent runtime.

Working on Noble

nix develop
cargo build -p noble-cli --bin noble
cargo test --workspace --all-targets --all-features --locked

Build and test from the repository root. Source builds use the pinned Rust toolchain; runtime checks also need the tools realized in the quickstart. Use Cargo's configured target directory when locating the resulting binary.

LocationPurpose
crates/noble-kernelIndependent acceptance checks and deterministic semantic state transitions.
crates/noble-contractsSource parsing, resolution, inference, modules, and application contracts.
crates/noble-wasmChecked Wasm lowering, runtime assets, and component compilation.
crates/noble-cliCLI, compiled sessions, host orchestration, and isolated proof checking.
crates/noble-syndicateBounded local service and choreography support.
.cairn/specsCanonical language and implementation specifications.
specsRoadmap, status, conformance scenarios, and generated compatibility views.
proofs and verificationLean sources, acceptance harnesses, and recorded evidence.

Start with the language specification, bootstrap scope, and implementation roadmap. Specifications include planned features; consult the status ledger for implementation progress. The Cairn guide explains document validation and how to edit specifications.