Hara Build

Registry · checker · attestations

Specifications that can answer yes or no.

Publish signed, versioned specifications as packages. Inspect a document in the browser or through the API and receive an explainable conformity result.

hara spec check project.edn --against hara/package@0.1.0
59specifications indexed
371normative rules found
59registry sources materialized
2execution surfaces

Repository separation

One source of truth. One service surface.

The canonical corpus and package index live in hara-lang/hara-specs-registry. Build resolves every service build to an exact registry commit and presents the developer material around it.

01Registryimmutable spec packages
02Hara kerneldeterministic inspection
03ServiceUI, API, reports

From the registry

Current specifications

Browse all
Draft0.0.0-alpha

hara/host-runtime

HAL host capability boundary

Product-neutral contract between a Hara evaluator and capabilities supplied by its embedding host.

Layer
00-unsorted
Rules
0
Source
Registry source
A

Browser privacy

Run compatible checks locally. The document stays on the device while the signed specification bundle is verified and executed.

B

API parity

The browser workbench and Netlify API share one result contract: completed checks return a yes/no verdict; execution failures remain separate.

C

Project publishing

Coordinates, versions, paths, dependencies, capabilities, fixtures, signatures, and immutable digests are declared once in project.edn.