Kelft language specification

Read the public specification online or use the bundled pages below. Core 0.1, Intent 0.2, runtime profiles, and compiler packages identify separate contracts. A specification snapshot alone does not establish target availability or release qualification.

Reading order

1. Core language 0.1: lexical rules, grammar, types, evaluation, modules, mutation and errors. Core is executable deterministic source.
2. Intent source 0.2: declarations, prose, formal predicates, entities, capabilities and reviewed authoring. Core and Intent files both use .kelft; an Intent module starts with app after whitespace/comments.
3. Intent IR 0.1, Core IR, and runtime: intermediate contracts and program behavior. Declaring or checking a requirement is not evidence that it holds.
4. Compatibility and glossary: terminology, status and specification corrections.

See source examples for separate Core and Intent modules.

Target and platform contracts

Area	Specification
JavaScript/runtime intrinsics	Runtime, intrinsic inventory
Wasm/WASI and browser	Wasm, browser
Native execution and private backend boundary	Native profile, direct native
Native aggregate storage	Owned storage, aggregates, enums, maps, graphs
Native text and host access	Strings, streams, paths, processes, filesystems, artifacts
Service and application profiles	Services, application platform
External execution evidence	Driver protocol

Language semantics are normative; target/profile documents specify the named profile, rather than a guarantee that every installation contains it. Backend-private IR/ABI contracts are not portable application APIs. Consult the compiler's capabilities and release notes for availability and tested hosts.

Prose is CC-BY-4.0; first-party copyable code examples are MIT-0; machine-readable intrinsic data retains the software license. See the root LICENSE and licensing inventory.

---

Source: public Kelft compiler, commit f567c21684362db37e0aa0a68e71e7614502c45a. Compiler 0.1.0-alpha.2; Core 0.1; Intent 0.2.