Skip to route content

Issue 91 · evidence before decoration

Show what was measured, what is uncertain, and what cannot be compared.

The guide records accessible patterns for benchmark evidence, package compatibility, and runtime observations. Scales, units, baselines, confidence, source revision, and methodology remain visible while each source system retains authority over its facts.

Reference composition 01 · Benchmarks

Lead with the metric, then expose the evidence.

Bars communicate ordered magnitude. Confidence ranges, sample count, baseline, environment, methodology and exact evidence revision remain adjacent rather than hidden behind a tooltip.

Median wall time · ms

Cold-start executable form

lower is better · baseline 0 ms · domain 0–16 ms

bench-fixture:7b2ac941
Samples30 per measured series
Confidence95% bootstrap interval
EnvironmentLinux x86_64 · 8 vCPU · 16 GiB · isolated process
Generated2026-08-20T19:20:00Z
Accessible data table and methodology

Thirty cold processes per implementation; median shown with a 95% bootstrap interval.

Cold-start executable form — Median wall time; ms; lower is better.
ImplementationMedian95% intervalSamplesStateEvidence
Hara native4.8 ms4.5–5.2 ms30Measuredrun:hara-native:7b2ac941
Babashka6.7 ms6.2–7.3 ms30Measuredrun:babashka:3c88fe20
Clojure JVM12.4 ms11.7–13.2 ms30Measuredrun:clojure-jvm:d67e091b
Hara WasmNot comparableNot available0incomparabletarget lacks an equivalent process-start boundary
ms

Parse 10k forms

1ce20d9a
Hara18.2 ms
Clojure31.6 ms
Babashka22.9 ms
Baseline 0 msScale ends 45 ms
ms

Map 1m integers

830c1be2
Hara34.6 ms
Clojure62.1 ms
Babashka54.8 ms
Baseline 0 msScale ends 80 ms
ms

Dispatch 100k calls

721d829e
Hara13.7 ms
Clojure24.4 ms
Babashka— Missing
Baseline 0 msScale ends 30 ms
Distribution, not only a point estimate

Hara native cold-start distribution

distribution:7b2ac941
Histogram counts for Hara native cold-start distribution
Range (ms)Count
4.2–4.53
4.5–4.89
4.8–5.112
5.1–5.45
5.4–5.71

Reference composition 02 · Packages

A compatibility matrix is a claim ledger, not coloured wallpaper.

Every cell names its state, target, release revision and supporting evidence. Missing, unsupported and incomparable remain different facts; none is rendered as zero or silent absence.

Package/runtime compatibility

Exact release evidence across four target families

Cell symbol + state word + evidence text · fixtures only

compatibility-fixture@2026-08
Representative package compatibility. These deterministic fixtures are not current registry claims.
Package and release revisionJVM 21Rust nativeWasm32JavaScript host
hara/std.typed@0.9.2release:typed:b37d9b71 supported 0.9.2

61/61 conformance

partial 0.9.2

57/61; recursive aliases pending

supported 0.9.2

40/40 portable subset

unsupported No version claim

No direct implementation

hara/std.work@0.3.0-experimentalrelease:work:d4502d3d supported 0.3.0

Reference executor

partial 0.3.0

Checkpoint store only

unsupported No version claim

Durability provider unavailable

incomparable No version claim

Host adapter has no durable-step contract

hara/std.native@2.0.0release:native:845cf281 supported 2.0.0

Portable + JVM capability inventory

supported 2.0.0

Portable + native capability inventory

partial 2.0.0

Browser-safe capability subset

missing No version claim

Evidence index not received

hara/hara-wasm-core@1.4.0release:wasm:71cc80f4 incomparable No version claim

Browser session product, not a JVM package

incomparable No version claim

Compiled through Rust but not installed as a native runtime

supported 1.4.0

Browser session contract 40/40

partial 1.4.0

JavaScript host bridge; evaluator remains Wasm

✓Supported

An exact implementation and evidence set supports the declared release.

—Missing

The expected evidence value was not received. Keep the empty fact and source boundary visible.

◐Partial

Only a named subset is available. State the numerator, denominator or missing dimensions.

×Unsupported

The implementation or target cannot produce this measure. Do not render it as zero.

≠Incomparable

The measurements do not share an equivalent boundary, unit or methodology.

hara/std.typed@0.9.2release:typed:b37d9b71
JVM 21
✓ supported

61/61 conformance

Rust native
◐ partial

57/61; recursive aliases pending

Wasm32
✓ supported

40/40 portable subset

JavaScript host
× unsupported

No direct implementation

hara/std.work@0.3.0-experimentalrelease:work:d4502d3d
JVM 21
✓ supported

Reference executor

Rust native
◐ partial

Checkpoint store only

Wasm32
× unsupported

Durability provider unavailable

JavaScript host
≠ incomparable

Host adapter has no durable-step contract

hara/std.native@2.0.0release:native:845cf281
JVM 21
✓ supported

Portable + JVM capability inventory

Rust native
✓ supported

Portable + native capability inventory

Wasm32
◐ partial

Browser-safe capability subset

JavaScript host
— missing

Evidence index not received

hara/hara-wasm-core@1.4.0release:wasm:71cc80f4
JVM 21
≠ incomparable

Browser session product, not a JVM package

Rust native
≠ incomparable

Compiled through Rust but not installed as a native runtime

Wasm32
✓ supported

Browser session contract 40/40

JavaScript host
◐ partial

JavaScript host bridge; evaluator remains Wasm

Reference composition 03 · Runtime

Telemetry reads as a monotonic event record.

Sequence, generation, source revision, backend and capability fence stay visible while dense observations scroll locally. High-frequency telemetry is not announced as a continuous live region.

Session telemetry

pg-7a91 · generation 4

interpreter · sequence 140–148 · 2026-08-20T19:22:04.100Z/2026-08-20T19:22:05.012Z

source:9f3c2ab7
Evaluation 83 ms ready
Queue wait 12 ms ready
Heap estimate 18.4 MiB partial
3D capability × unsupported
  1. 140
    session.ready+0 ms · success

    generation 4 · interpreter

  2. 141
    eval.queued+12 ms · queued

    source 9f3c2ab7

  3. 142
    eval.started+21 ms · active

    capabilities eval · observations

  4. 143
    namespace.loaded+46 ms · success

    tutorial.profile

  5. 144
    observation+73 ms · partial

    heap estimate sampled

  6. 145
    eval.completed+95 ms · success

    83 ms

  7. 146
    canvas.unavailable+108 ms · unsupported

    sample declares no canvas capability

  8. 147
    heartbeat+514 ms · stale

    interval exceeded 400 ms review threshold

  9. 148
    session.observed+912 ms · success

    monotonic sequence retained

Accessible event table and session fence
Session
pg-7a91
Generation
4
Source revision
source:9f3c2ab7
Backend
interpreter
Capability revision
capabilities:1f72aa90
Sequence range
140–148
Monotonic event sequence for pg-7a91, generation 4
SequenceOffsetEventStateDetail
140+0 mssession.readysuccessgeneration 4 · interpreter
141+12 mseval.queuedqueuedsource 9f3c2ab7
142+21 mseval.startedactivecapabilities eval · observations
143+46 msnamespace.loadedsuccesstutorial.profile
144+73 msobservationpartialheap estimate sampled
145+95 mseval.completedsuccess83 ms
146+108 mscanvas.unavailableunsupportedsample declares no canvas capability
147+514 msheartbeatstaleinterval exceeded 400 ms review threshold
148+912 mssession.observedsuccessmonotonic sequence retained

Evidence states and ownership

Absence has more than one meaning.

Shared presentation grammar keeps these states legible. Benchmarks, package registries and runtimes still own the underlying values, freshness policy, methodology and compatibility decisions.

—

Missing

The expected evidence value was not received. Keep the empty fact and source boundary visible.

△

Stale

The value exists but is older than the declared freshness window. Show its timestamp and threshold.

◐

Partial

Only a named subset is available. State the numerator, denominator or missing dimensions.

×

Unsupported

The implementation or target cannot produce this measure. Do not render it as zero.

≠

Incomparable

The measurements do not share an equivalent boundary, unit or methodology.

Shared visual grammar8 rules
  1. Name metric, unit, direction and baseline next to the graphic.
  2. Retain exact source, methodology, environment and revision references.
  3. Use position and length before area, volume or decorative perspective.
  4. Pair colour with words, symbols, patterns or structural placement.
  5. Keep confidence, ranges and sample counts visible when a point estimate is shown.
  6. Render missing, stale, partial, unsupported and incomparable as different facts.
  7. Provide an accessible table or ordered textual alternative for every evidence graphic.
  8. Let products own data and methodology; the package owns presentation grammar only.

Downstream adoption

Adopt the grammar without copying the fixtures.

The additive stylesheet supplies evidence-graphic composition classes. Products bind those classes to their own exact data, methodology, states and accessible descriptions.

Benchmarks

Use comparison, confidence, distribution and table patterns while retaining workload and methodology authority in `hara-benchmarks`.

Packages

Use the matrix and state grammar while retaining exact release and target evidence in the package registry.

Playground and tools

Use event-sequence and telemetry patterns while runtime systems remain authoritative for observations and receipts.

Docs and WWW

Use simplified evidence projections with direct links to the exact data, method and current revision.