The wire format
Everything Fuaran UI promises rests on one artefact. One tree rendering on every host, docs examples that cannot be wrong, an AI that cannot emit what the language forbids: each of these claims reduces to a language-neutral, canonical-JSON contract for a typed UI tree and its ops. A host is conformant if it reads and writes these exact bytes. That is a deliberately simple bar to state and a deliberately hard one to fudge: the contract is testable against a shared corpus, certifiable by a kit you can run yourself, and open to implementation without anyone's permission.
Pinned versions
| Contract | Version |
|---|---|
| Wire-format profile | core@1.0 |
| Op-stream chain envelope | v2 |
| Language revision | 0.2 – see releases for what it added |
Neither moves without every codec host and the fixture corpus moving together: the forward-coupling rule (see the specification).
The contract, in four artefacts
- The specification – the normative prose: the node/op model, canonical-JSON rules, version negotiation, and the forward-coupling rule.
- JSON Schema – the machine-readable schema (Draft 2020-12) for the canonical wire, at a stable URL. Every corpus payload validates against it.
- The conformance corpus – the shared fixture set every host is held byte-identical to, browsable by group and downloadable as a bundle.
- The certification kit – implement the contract, run the kit, get a report.
The render-fidelity manifest (the cross-host guarantee about how a tree
renders, beyond its bytes) will appear at /spec/fidelity
when it ships.
What this means. Every example on this site is a real wire document, not an illustration: it is decoded, validated and re-encoded before the page you are reading can build at all.
How it is checked. The check-trees gate assembles each page into a Fuaran tree, pre-emit-validates the whole tree, server-renders it, and proves the assembly byte-deterministic across two runs. Every fuaran-wire block inside a page has already passed decode, pre-emit validation and a canonical round-trip on the way in, so a block that drifts from the specification fails the build rather than rendering something subtly wrong.
Why that is worth something. Documentation rots because prose and code are checked by different processes, or by none. Here the examples ARE the artefact under test, so an example cannot silently stop being true. The figures above come from this deploy's own run and carry its commit, so the claim is checkable rather than a badge.
What it does not cover. This site's pages and their embedded examples: not the cross-implementation host matrix, which each conformant host certifies against the shared corpus itself.