Hara

Build documentation

Build artifacts with explicit contracts.

These guides cover the package, compiler, and runtime boundaries used by Hara Build. Normative specifications remain in the specifications registry and implementation contracts remain with the owning repositories.

Compiler stack

Follow Hara source from parsed forms to HBC and whole-Wasm products.

Understand the reader, namespace rewrite, bytecode compiler, validated program, immutable compiled-product manifest, VM path, whole-Wasm wrapper, and the separate foreign-Wasm bindgen pipeline.

Compiler stack Compiled products

Wasm bindings

Bind an existing Wasm library from a semantic .hal interface.

Inspect raw exports, define Hara-visible types and ownership, generate a deterministic package, and choose the correct core.v1, memory.v1, or hta.v1 route.

Read the guide

Executable specifications

Inspect the canonical registry and conformance surface.

Use the registry for exact specification revisions and the checker for document or package validation.

Registry Check

Packages

Author and validate package metadata before publication.

The Build service validates package descriptors and artifact metadata. Identity and namespace grants remain outside this service.

Package authoring

HTTP API

Use the same registry and check contracts from code.

The versioned API exposes discovery, exact specification source, capabilities, and conformance checks.

API reference

Authority

Docs explain; specs define.

Build documentation is descriptive. When a guide and a versioned specification disagree, use the versioned specification and report the documentation drift.

Compiler, runtime, and bindgen implementationhara-lang/hara Normative specificationshara-lang/hara-specs-registry Build documentation sourcehara-lang/hara-build