Roadmap

This is a public planning document, not a commitment or a release announcement. Q+ 1.21.0-dev is a release candidate (NOT PUBLISHED); dates and scope are estimates and may change. Version labels in the tree describe the development line and specification snapshot only.

Status labels: Current (present in the candidate tree), Planned (accepted direction, not implemented), Research (under evaluation, no promise), Not planned (explicitly out of scope for the foreseeable line).

1.4.x line (current)

• Q+ 1.21.0-dev / spec v4.36 (Current, candidate): u64 bitwise operators (& | ^ ~ << >>, clamp semantics, VM/AOT parity); AOT multi-module POC3 (symbols/import-export/telemetry, generic parities, ELF-level cache POC; POC-only); qfmt v3 (project-level/config discovery/CI, 306 checks); OS SDK 1.9.0 external prototype (API-freeze candidate; net BLOCKED; 23/23 tests, 10/5/5); LSP 0.11 optional/dev. See CHANGELOG [1.21.0-dev] and earlier entries.
• 1.4.x (previous candidates; NOT PUBLISHED): A5 residual cleanup (type-10 exponent literals baked; boxed i64 pool 4096; u64 bitwise rejected with TC20; mixed i64/u64 explicit-cast only), Modules B completeness subset (sidecar source map, type depth 16, generic qualified paths), Windows async 27 PASS / 0 FAIL / 2 SKIP, P0 governance drafts, qpm signing/registry-v2 docs, OS SDK 1.5.1 (historical).
• Known residuals carried forward (do not claim as complete): A5 is not an unconditional full-u64 guarantee (5e-324/1e400 loader-loud boundaries; i64 pool cap loud; bitwise rejected; mixed i64/u64 TC9-loud; negative u64 literal TC15-loud); floating-point correct rounding is not claimed (conservative boundaries / up to 1 ulp); qbc v3 source map is module-level only; Windows async is a Fiber sockets subset and not platform-usable; Modules B is incomplete; TSAN is not a gate and TSAN-clean must not be claimed; OS SDK is an external prototype; qpm is local/static only.
• Next patch candidates (Planned): 1.4.6 documentation cleanup and new-docs base (A.12 label, Win-AOT historical row, TSAN/OS-SDK/qpm/LSP doc consistency, Docs index); portability CI maintenance; async-IO capacity default review; error-message improvements.

1.7 development line (Planned; documentation inputs only)

• Network Phase2 (async integration, UDP/DNS/TLS/public network, limits and security documentation) — not implemented or claimed for 1.6.0.
• u64 large-integer literals (the TC15 hex-integer boundary and migration guidance).
• OS SDK 1.7 (API/network/release boundaries) — current prototype is 1.6.0-prep.
• Playground deployment (static-site deployment and reachability documentation).
• These are inputs for future documentation, not implemented features or version claims.

1.5 development line (Planned)

• Platform: Windows async scope beyond the Fiber sockets subset; ARM64 build/smoke expansion; explicit SKIP policy in CI. No Windows/ARM64 AOT backend work is promised for 1.5 (Windows AOT feasibility remains a dedicated MEDIUM-HIGH-risk project; the old 9–15-week HIGH estimate is historical).
• Modules B: complete the remaining visibility/source-map/AOT-native gaps and qpm integration. Module B completion is a prerequisite for stable OS SDK namespaces.
• Async IO: capacity defaults and backpressure; socket connect/accept coverage; additional IO acceptance items. VM remains the reference runtime.
• Tooling/docs: reproducible checks, docs-site publishing pipeline, richer editor diagnostics on top of the supported 0.6.0 component.

2.0 (Planned long-term)

• Modules 2.0 / AOT-native modules: native module map semantics, module-level visibility, toolchain and AOT support.
• OS SDK 1.0: stable os.* API, capability/error model freeze, host VM MVP → target support; Modules B + qpm 2.0 are prerequisites. The current OS SDK 1.9.0 prototype is VM-only, AOT-loud, external, and 0.x unstable (API-freeze candidate; 23/23 own tests; conformance 10 PASS / 5 PARTIAL / 5 BLOCKED; net BLOCKED).
• AOT platform expansion: Windows and ARM64 AOT backends (not started).
• Runtime/language: Futures/state-machine async for AOT, memory ownership/GC design, broader trait/generic capabilities (research).
• Ecosystem: qpm registry v2 with signing/verification and workspace/multi- version resolution; policy and offline-first defaults. qpm 0.5-alpha remains local/static (no central service).

OS SDK (prototype)

• 1.5.4 prototype (Current, external): os.platform/sys/io/time/fs VM subset + os.sync, C-lite module-map package, static capability bitmask, negative error codes, VM-only Linux x86-64, AOT loud. 22/22 own tests; conformance 10 PASS / 5 PARTIAL / 5 BLOCKED (per docs/OS_SDK_1.5_MVP.md); not production-usable; not part of the release package.
• 0.1.0-alpha (Planned): host VM MVP per the frozen 0.1 design, only after the documented acceptance subset passes and independent review completes.
• 1.0 (Planned): stable ABI/compatibility matrix, Modules B/qpm dependencies, target/OS adapter line. Kernel/OS internals are private and out of scope for this public repository.
• See docs/OS_SDK_DESIGN.md, docs/OS_SDK_PROTO.md, and docs/OS_SDK_1.5_MVP.md.

LSP / editor components

• 0.6.0 (Current): supported release component in the 1.5.0 candidate (offline LSP subset + formatter + diagnostics; 190 checks).
• 0.7.0 (optional/dev): earlier development component (208 checks; Modules B qualified paths, OS SDK 0.1 module awareness, TC16/TC17 Explain) — not a supported release component, not in the tar.
• 0.9.0/0.10.0/0.11.0 (optional/dev): optional developer .vsix builds (0.11.0 current); not in the release tar, not a supported release component, and not published to any Marketplace. Features are not a released capability until a future release explicitly includes them.

Platform matrix (current, candidate)

Non-goals (foreseeable line)

• No claim of production readiness, complete platform support, complete Modules B, unconditional full-u64 AOT, correct-rounding floating literals, stable OS SDK, or Marketplace-published editor.
• No Windows/ARM64 AOT support commitment, no bare-metal support in this repository, no kernel/OS internals in the public repository.
• No silent behavior changes: unsupported paths fail loudly (compile/runtime), and documented limitations remain in the specification/release notes.
• No fixed dates or guaranteed feature delivery in this document.

See the release checklist for the current NOT PUBLISHED status and Maintainer decisions required before publication.