Product truth / release line
openElement roadmap labels describe the public product surface, not a wish list. Every release stage is tied to package truth, docs truth, and CI evidence.
The current line resolves the Six-Phase Vision into a readable four-product platform: Elements, UI, Framework, and Protocols, with WC Package Protocol boundaries kept visible.
Release rail
The rail is deliberately narrow: only claims that can survive docs, package exports, and build validation stay visible.
Validated app generation, public docs integrity, and the Elements / UI / Framework / Protocols model.
Slimmed the public surface, removed archived promises, and kept the framework direction standards-first.
Align design, docs, WC Package Protocol language, and CI readiness around the current product graph.
Proved Lit, Shoelace, and Material Web consumption while keeping the interop contract standards-first.
PR-green Fresh proof for the lightweight client runtime; awaiting main merge, npm publish, and post-publish smoke evidence.
Client-side router, SPA bootstrap, and a WeRead-style Deno Desktop reader proof backed by local/open fixtures.
Use a real federated social API for public timeline, profile, and status detail without auth or mutations.
Add OAuth, home timeline, compose, favorite, boost, reply, optimistic actions, and rate-limit/error handling.
Stabilize npm artifacts, WC interop, SPA reader proof, and Mastodon practice evidence before the v0.41 tag.
Freeze public APIs after contracts, examples, and release evidence are all stable.
The public website should read like an editorial standards lab: light-first, diagrammatic, useful, and grounded in artifacts users can inspect.
Decision matrix
System visual