Topazdocs
Foundations

Roadmap

Current product priorities and the next public release boundary.

This roadmap shows priorities and readiness, not promised dates.

Now

  • The current public product includes the installed Stock Binary Media Kernel Application Loop.
  • Compiler, runtime, npm installer, artifacts, documentation, and Playground identify one current product.
  • Installed native and Python products run offline, managed browser products own their static bundle and local-data boundary, and generated services own bounded inbound HTTP authority, isolation, deadlines, observation, and shutdown.
  • Fixed-length mutable ByteBuffer supports contiguous binary work while immutable Bytes remains the snapshot and transport value across the accepted native, Python, Web, and Web Worker boundaries.
  • A maintained multi-module CodeImage kernel builds with stock installed Topaz, exposes fail-closed native-selection decisions, and preserves exact byte and fault behavior through source-free Web and Worker artifacts.
  • Run targeted differential checks when a related implementation changes. Reserve full cross-platform and full differential campaigns for the public-minor RC that owns them.

Next

  • Select the next application-loop direction from concrete maintained-product evidence rather than reserving a version or syntax feature in advance.
  • Keep the HTTP service, local-data, browser, native, Python, and binary-media loops as non-regressing predecessor products.
  • Require a separate capability decision before widening aggregate layout, ABI, codec, networking, or language syntax.

Release boundary

The stock compiler, maintained CodeImage court, installed products, and every user-visible identity move together as Topaz 5.10.0. The internal checkpoints that built this boundary remain recorded in History.

Later

  • Keep general native aggregate layout, arbitrary host FFI, a new Web ABI, SIMD, browser fetch, outbound networking, remote package publication, router and middleware frameworks, shared server state, databases, TLS termination, WebSocket, and new syntax outside this train.
  • Preserve explicit older language modes as compatibility inputs rather than parallel current identities.

Bounded integration evidence

LIT and Lispex integration records remain useful internal compatibility and regression evidence. They do not define this release queue, make LIT a public Topaz backend, or establish whole-language equivalence. Large LIT, N-way, mutation, and differential campaigns run only when their owned semantics change or an applicable release candidate requires them.

Research

  • Expand differential and fuzzing tools that find places where code generators misunderstand the language.
  • Consider model checking or mechanized proofs only where there is a concrete artifact and a useful way to reproduce the result.
  • Keep broad optimizer work, async syntax, recoverable faults, grapheme APIs, and user-defined templates as research topics until a future language decision accepts them.