Interface reference · Version 2
Hara visual language v2
This site records the shared interface rules used across Hara and shows how they apply to the language overview, documentation, learning material, packages, specifications, playground, and community. Application pages are specimens for review; they are not product pitches.
Route manifestPaths, parent relationships, aliases, and implementation status are recorded in one typed source.
Shared rulesIdentity, typography, colour, accessibility, evidence, and common interaction states are documented once.
Route examplesEach language or community route retains its own information architecture and realistic content.
Explicit statusImplemented, reference, historical, and planned material are labelled without implying more than the repository supports.
Reference structure
Shared rules and route-specific examples.
Foundations and Library describe reusable contracts. Language and community routes show how those contracts are applied to Hara's public overview, documentation, learning, packages, specifications, executable examples, and discussion. A planned route links to its implementation issue rather than presenting an empty page.
Reference group
Foundations
Shared visual, content, accessibility, evidence, and diagram conventions.
Design system
Reference values for identity, colour, typography, spacing, geometry, imagery, motion, and accessibility.
ImplementedGraphics
Background, texture, field, and shader specimens with fallback and reduced-motion states.
ImplementedFront matter
Typed content metadata, controlled fields, lifecycle states, previews, revisions, and provenance.
ImplementedCatalogue guide
Route structure, theme and viewport review, state coverage, validation, lifecycle, and adoption notes.
ImplementedData visualisation
Benchmark comparisons, uncertainty, compatibility matrices, runtime telemetry, and missing-data states.
ImplementedDiagrams
Architecture, runtime flow, sequence, lifecycle, package, and namespace diagrams with complete text alternatives.
ImplementedIconography
Interface symbols for actions, state, evidence, runtime capabilities, and the public Hara route families.
ImplementedReference group
Library
Reusable interface specimens, interaction states, and workbench structures.
Components
Primitive, compound, document, data, profile, feed, form, tool, environment, and runtime specimens.
ImplementedUI patterns
Navigation, workflow, loading, empty, error, permission, responsive, and input-state references.
ImplementedTool workbenches
Reference compositions for 3D, node, material, animation, dock, inspector, toolbar, overlay, and status surfaces.
ReferenceReference group
Language and community
Public language, documentation, learning, package, specification, playground, and community routes.
Hara overview
A plain-language introduction to Hara forms, runtimes, libraries, source, documentation, and benchmark evidence.
ImplementedPlayground
Editor, sample, runtime-session, control-pane, embed, sharing, and mobile execution references.
ImplementedSpecifications
Versioned specifications, conformance results, proposals, reviews, publication records, and change history.
ImplementedPackages
Package and namespace records covering ownership, versions, compatibility, artifacts, provenance, and maintenance.
ImplementedWorld
Articles, discussions, external references, contributor profiles, package activity, presence, and owner-attributed bot comments.
ImplementedLearn
Introductory explanations, runnable lessons, exercises, projects, progress records, and teaching guidance.
ImplementedEarlier specimens
Earlier document layouts remain available for comparison.
WWW, Docs, Specs, and Benchmarks established the first shared v2 shell. The earlier World example is retained under Learn so that its attribution, discussion, and source-handling decisions can be explained rather than presented as a current destination.
Read LearnIntroductory explanations, runnable lessons, projects, and guided interface examples.
implemented route Read World discussionArticles, clippings, comments, contributor profiles, presence, and owner-attributed bots.implemented route View Around HaraExternal references with source provenance, curation, moderation, and relay review.implemented route Inspect tool workbenches3D, node, material, and animation editor compositions.reference Catalogue architecture recordThe completed issue that established the route manifest and application reference structure.completed issue #32 Layout 01 · Public site
WWW
A broad narrative shell with no permanent rail. The command-deck illustration carries mood while the copy, proof strip, and executable surface carry the product argument.
Small language · complete system
Build from first principles.
A compact Lisp that can begin in a browser session and continue through native runtimes, libraries, specifications, and durable work.
Runtime families03Interpreter · HBC · Native
Browser sessionLiveOne contract across backends
Library surfacestd.lib.*Inspectible and packageable
Evidence stateOpenMethods beside results
Small core, open system
Read the evaluator, inspect expansion, then move the same forms into larger programs.
One session contract
Interpreter, bytecode, browser, and native hosts share observable lifecycle boundaries.
Tools are language values
Filesystem, work, compiler, deployment, and analysis surfaces remain composable.
;; a small program can still expose the whole system
(defn launch [session]
(-> session
(runtime/attach :browser)
(work/run {:op :pure
:fn #(+ % 1)})))Start simple. Build forever.
The final command stays direct; the surrounding frame supplies the world.
One ecosystem row. Product pages do not add a second navigation bar unless a workflow needs it.
Original fleet linework is theme-aware and secondary to the headline reading order.
Primary and evidence actions remain adjacent. Pills are removed in favour of clipped command controls.
Layout 02 · Knowledge system
Docs
The complete reading shell: ecosystem identity, local guide navigation, grouped rail, prose, executable surfaces, and a deliberately quiet outline.
Guide 01 · System orientation
A language you can inspect all the way down.
Hara starts with ordinary forms and keeps the layers beneath them available. A browser session, a native runtime, and a packaged library are different hosts for the same language rather than separate routes.
Keep the boundary visible
Session, generation, and source revision are explicit whenever live code can outlive the interface that created it.
Evaluate the first form
The documentation evaluator is attached to the page. Its status belongs in the command strip, not in a floating promotional card.
(def greeting "hello, system")
(map #(str greeting " / " %)
[:syntax :runtime :work])Continue into the system
Each next step narrows the question: syntax, values, modules, sessions, work, and native interfaces. The rail carries location; the prose carries explanation.
Groups, counts, and current location use the same compact item grammar across guide and reference trees.
REPL, editor, canvas, and status controls inherit the flat command strip without changing runtime behaviour.
The inspector disappears before the rail; the rail then becomes a product-owned drawer on narrow screens.
Layout 03 · Executable registry
Specs
A workflow shell for finding, checking, and publishing executable standards. Dense rows and digest values remain readable without becoming a generic admin dashboard.
Executable standards
Registry
Registry healthy
Published specs48Across 9 namespaces
Current revisions44Four superseded
Checks today31299.4% valid
Registry digest7e2aSigned index
| Specification | Revision | Capability | Checks | Status |
|---|---|---|---|---|
| runtime.session | 1.4.0 | live lifecycle | 82 / 82 | Current |
| std.typed.schema | 0.9.2 | typed values | 61 / 61 | Candidate |
| work.executor | 0.3.0 | execution ABI | 44 / 46 | Review |
| native.result | 1.1.1 | host boundary | 38 / 38 | Current |
The second navigation row belongs to the product workflow, not to the whole ecosystem.
Rows stay compact, flat, and horizontally inspectable. Status uses words and colour together.
Selection detail and validation state sit beside the registry and vanish first on smaller screens.
Layout 04 · Evidence board
Benchmarks
A compact measurement surface. Tabs change evidence families, the matrix carries comparison, and the inspector explains the selected cell without hiding method or baseline.
Evidence current Sign in
Published 19 August 2026 · 14 workloads
Best in class
Median Hara ratio1.00×Baseline
Dynamic-JIT wins11 / 14Measured workloads
Fastest steady call18.4 nsInteger path
Evidence digestb19eRaw data linked
WorkloadHaraJuliaLuaJITNodePython integer-loop18.422.921.638.2244 vector-map41.749.247.078.4418 persistent-map113108141172892 parser-small6.2 μs7.8 μs8.1 μs10.2 μs61 μs json-roundtrip12.8 μs14.1 μs13.6 μs16.9 μs74 μs
Every cell is a doorway
Select a measurement to see exact runtime, samples, confidence, method, and raw-data location in the inspector.
Blue means selected or measured advantage. It does not paint whole charts for atmosphere.
Method, sample count, revision, and raw-data links stay with the selected measurement.
The same shell reduces row and control height without inventing a separate benchmark theme.