Roadmap to 2.0

Roadmap labels describe intended scope; they are not evidence that a capability shipped. Every milestone page distinguishes Delivered, Partial and Deferred work. A feature is delivered only when code, public contract, documentation, tests/evidence and published artifacts agree.

Release plan

Version	Theme	Current state
1.1	Certification and fallback	Published RC; several certification/fallback items remain Partial or Deferred
1.2	Image and time editing	rc.2 remediation; core time/keyframe work delivered, broader subtitle/analysis/WebGPU work remains
1.3	Boundaries, consumers and ecosystem	Planned; harden package/runtime boundaries before multiplying framework bindings
1.4	Audio and arrangement	Planned
1.5	Intelligence	Planned
1.6	Collaboration and protocols	Planned
2.0	Contract-first stabilization	Planned; ordered migration/schema/IR/boundary/integration/freeze/certification program

Versioning rules

• Every Project schema revision gets a new immutable URI and schemaVersion.
• Additive 1.x APIs preserve behavior or ship a documented migration/deprecation path.
• Breaking changes require migration fixtures and loss reporting before removal.
• Automated, supported and certified are different claims; use the vocabulary from Compatibility and deployment.
• Prereleases use next. Moving latest requires a bound source manifest, complete release gates, registry smoke and an independent blocker review.

Decisions that remain open

1. Actual software codec execution: small targeted WASM backends, a large ffmpeg-class dependency, remote execution, or a deliberate platform-codec-only policy.
2. Physical-device certification ownership and recurring device-farm budget.
3. On-device versus remote intelligence provider boundaries.
4. CRDT versus server-coordinated collaboration semantics.
5. The post-stable deprecation window and long-term support policy.