Topazdocs
About Topaz

Roadmap

Current product priorities for release evidence, external tools, and bounded integration.

This page describes Topaz v5.17. Before treating it as current, compare /version.json with version 5.17.

This roadmap shows dependencies and product boundaries, not promised dates.

Now

  • This manual describes Topaz 5.17.0 / topaz-5.17. Its installed self-hosted compiler remains the default for supported current-language routes.
  • The installed topaz lispex embed run command evaluates one bounded Lispex request through an exact component built into the Topaz binary. It has finite limits, explicit refusal, and no selector, discovery, download, callback, import, or fallback path.
  • The Rust compiler remains an explicit comparison, recovery, and compatibility path. Self-hosted by default does not mean that the Rust recovery chain has disappeared.
  • Compiler, runtime, npm package, artifacts, documentation, and Playground continue to identify the same product. Existing native, Python, browser, HTTP, local-data, and binary-media application paths remain supported.
  • Unsupported compiler selections fail instead of silently switching engines. Full platform and differential campaigns remain release-candidate work; ordinary changes use targeted checks.

Next priorities

  1. Preserve release evidence. Every later release must issue fresh admission and revocation records, keep reused results visibly marked as reused, and periodically exercise the preserved recovery path.
  2. Update external tools on their own release trains. The editor extension already launches the installed language server. topaz-mcp 0.1.1 remains a check-only package tied to its verified 5.16 reference set. Its next release comes only after those embedded references and its native package are rebuilt and reverified against the current language authority. topaz_run remains a separate later product that requires both a no-capability Topaz host and an operating-system resource sandbox.
  3. Widen the Lispex boundary only from evidence. A broader profile, selectable evaluator, portable provider receipt, or additional input route needs its own contract and admission. The installed 5.17 result does not reserve any of them.

Evidence boundaries

Primitive capability counts are not a denominator for whole-language conformance. Special forms, control behavior, values, failures, transcripts, diagnostics, resources, the host boundary, and receipts are tracked separately.

The installed bounded evaluator proves only its documented command, component, profile, inputs, limits, outputs, and supported platforms. It does not prove whole-language Lispex equivalence or add an independent semantic witness. LIT remains useful same-lineage regression and integration evidence and is still not a Topaz backend. Completed self-hosting and application milestones remain available in History.

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.
  • Revisit direct WebAssembly compilation only if a measured product blocker justifies it. Keep broad optimizer work, async syntax, recoverable faults, grapheme APIs, user-defined templates, general host FFI, and new syntax outside the current plan.