Public roadmap lanes
This issue publishes the launch roadmap lanes from docs/roadmap-rfc.md so users can follow and comment on user-visible direction without requiring access to the monorepo PRD.
| Lane |
Scope |
Current launch posture |
Public evidence required |
| Authoring quality |
Criterion editor, validation, templates, accessibility, keyboard workflows |
Launch surface is active |
Public issue labels and triage board |
| Engine interoperability |
rubric-spec, IAA, judge-bench, EvalKit, conformance adapters |
Launch surface is active |
Engine compatibility issues and release notes |
| Desktop distribution |
Signed macOS, Windows, Linux, update server, clean-machine QA |
Blocked on signing and registry evidence |
Signed release, installer QA, and update endpoint evidence |
| Browser edition |
File System Access workflow, direct BYO-provider calls, no local sidecars |
Launch surface is active |
Browser support issues and docs feedback |
| OSS community |
Discussions, support SLA, community channel, contribution path |
Blocked on public seeding and launch ops |
Public discussion URLs and moderation log |
| Post-launch P4 |
Plugin marketplace, read-only CRDT collaboration, Snap/Flatpak, store distribution, i18n, advanced calibration, advanced diff |
Planned after launch feedback |
Approved P4 issues/RFCs and release evidence |
Current public feedback threads
Non-public evidence rule
Do not post private user data, customer names, security findings, legal advice, employee information, credentials, or unpublished partner feedback in this issue. Public updates should use redacted summaries and public links.
Public roadmap lanes
This issue publishes the launch roadmap lanes from
docs/roadmap-rfc.mdso users can follow and comment on user-visible direction without requiring access to the monorepo PRD.rubric-spec, IAA, judge-bench, EvalKit, conformance adaptersCurrent public feedback threads
Non-public evidence rule
Do not post private user data, customer names, security findings, legal advice, employee information, credentials, or unpublished partner feedback in this issue. Public updates should use redacted summaries and public links.