Live Framework Release Integration

This page defines how the 0x0 Live framework is released as a supported product

surface. The source-owned release manifest is

release/live-framework-release.tsv.

Release Contents

Each release must include evidence for:

• framework package source;
• runtime adapters;
• browser client assets;
• generators;
• public documentation;
• release gates;
• first-party app adoption;
• security;
• performance;
• package version metadata;
• upgrade, downgrade, and rollback behavior.

The bounded gate is:

make live-framework-release-check

Template Compatibility

*.html.0x0 template compatibility is versioned by parser behavior, formatter

behavior, lowering output, source maps, event descriptors, and diagnostics.

Template syntax changes require updated parser, formatter, lowering, source-map,

API-doc, diagnostics, learning, and release evidence in the same change.

Wire Protocol Compatibility

Wire protocol compatibility is versioned by join, params, event, diff,

heartbeat, upload, reply, error, redirect, patch, close, field, revision, size,

encode, decode, and malformed-frame behavior. A release may change the wire

shape only when compatibility notes and rollback behavior are updated.

Generated Code Compatibility

Generated code must remain editable source. Generator changes must preserve

existing app compatibility or provide a migration note. Generated files must not

be the only implementation of a production behavior.

Component API Compatibility

Component APIs are versioned by attribute names, required attributes, defaults,

global attributes, events, slots, slot payloads, accessibility behavior, and

diagnostics.

Client Asset Compatibility

The browser client asset is versioned by mount, reconnect, heartbeat, event

push, patch application, uploads, hooks, debug logging, asset integrity, and CSP

requirements.

Package Version Compatibility

The Live package family is versioned through frameworks/live/package-map.tsv,

frameworks/live/package-metadata.tsv, libs/registry.tsv, and package

release metadata. Package changes must preserve documented imports or provide

compatibility aliases and migration notes.

Upgrade

Upgrade evidence must include release manifest rows, framework gates, docs,

package metadata, app adoption evidence when an app changes, and public docs

metadata. Upgrade instructions must name behavior changes and changed gates.

Downgrade

Downgrade support is explicit. A release may claim downgrade support only when

the manifest names compatible package versions and the rollback artifact can

restore the previous release path.

Rollback

Rollback restores the previous 0x0 release link and the same framework unit

shape. Rollback must not point to test fixtures or app-local shims.

Release Gate

make live-framework-release-check validates manifest shape, source and

evidence paths, Make targets, final release discipline rows, compatibility

policy tokens, release notes, feature support status, and roadmap evidence.