Stability
Fuaran UI is pre-1.0. The wire format is the stable spine; the language-tier author surfaces are still settling. This page is the one-screen "what can break when" contract.
What is stable
- The wire format (
core@1.0). The canonical JSON contract – node kinds, ops, canonical-JSON rules, version negotiation – is the stable spine. It moves only under the forward-coupling rule (every host and the corpus together), and the conformance corpus pins it. Changes are additive within a profile; a breaking change bumps the profile. - The op-stream chain envelope (
v2). Self-describing and cross-host.
What can still change
- The author-surface smart constructors (
Fuaran.UI,@fuaran-ui/ui,fuaran_py.ui) – signatures may change until a host's sample app validates them; each host states its own guarantees in itsSTABILITY.md. - Render details beyond the locked class / ARIA parity contract.
Per-host contracts
Each host repository publishes its own STABILITY.md:
- TypeScript – API stability: the wire-mirroring types are stable; the smart-constructor signatures are alpha until the sample app locks them.
- F#, Python, and the other hosts – see each host's
STABILITY.mdin its repository (linked from the hosts page).
Versioned docs
This site tracks the latest release; it does not yet host per-version docs.
Per-version documentation arrives post-1.0, when the surfaces stop moving. Until
then, the wire format is the versioned contract (core@1.0).