Topazdocs
About Topaz

Roadmap

The trajectory from today’s Lispex command through first-class applications, complete-profile integration, and compiler quality.

This roadmap outlines dependencies and product boundaries rather than promised dates.

Now

  • This manual covers Topaz 5.19.0 / topaz-5.19. Its installed self-hosted compiler remains the default for supported current-language routes.
  • The installed topaz lispex embed run command evaluates a Lispex request using an exact component built into the Topaz binary. It features finite limits and explicit refusal, offering no selector, discovery, download, callback, import, or fallback path.
  • The Rust compiler serves as an explicit comparison, recovery, and compatibility path. Operating as self-hosted by default does not mean the Rust recovery chain has been removed.
  • The compiler, runtime, npm package, artifacts, documentation, and Playground continue to align with the same product identity. Existing native, Python, browser, HTTP, local-data, and binary-media application paths remain supported.
  • Unsupported compiler selections fail explicitly instead of silently switching engines. Full platform and differential campaigns remain release-candidate work. Standard changes use targeted checks.
  • The installed native topaz executable includes the local stdio MCP server and its isolated no-capability worker at topaz mcp serve.

Next priorities

  1. Topaz 5.19 provides complete-current-profile applications. The interpreter and five admitted native targets consume the same profile, component, prepared artifacts, and lock identities. Generated native products run without source or a provider remote. Python, Web, and HTTP routes reject before output, while the Topaz 5.18 restricted profile remains an immutable compatibility route.
  2. Enter 5.20 only after the exact 5.19.0 public receipt. The entire then-current Topaz-authored compiler enters repeated whole-tree audit and refactor waves. The train has no patch ceiling. Candidate work cannot begin while any finding remains actionable, deferred, unknown, unreviewed, or preserved without an owner disposition, concrete invariant, and exact regression guard. Topaz 5.20 becomes eligible only after two consecutive zero-finding audits over identical compiler bytes.
  3. Preserve release evidence. Subsequent releases issue fresh admission and revocation records, keep reused results visibly marked as reused, and periodically test the preserved recovery path.

Evidence boundaries

Primitive capability counts do not measure whole-language conformance. Special forms, control behavior, values, failures, transcripts, diagnostics, resources, host boundaries, and receipts are tracked separately.

The installed evaluator validates only its documented command, component, profile, inputs, limits, outputs, and supported platforms. It does not demonstrate whole-language Lispex equivalence or introduce an independent semantic witness. LIT remains useful same-lineage regression and integration evidence and is still not a Topaz backend.

Product integration, Lispex semantic scope, and Topaz target support are tracked separately. A first-class native application does not by itself satisfy the full Lispex profile or cover generated Python, browser, and MCP execution environments. Completed self-hosting and application milestones remain available in History.

Research

  • Expand differential and fuzzing tools that identify areas where code generators misinterpret the language.
  • Consider model checking or mechanized proofs only when backed by a concrete artifact and a reproducible method.
  • Revisit direct WebAssembly compilation only if justified by a measured product blocker. Keep broad optimizer work, async syntax, recoverable faults, grapheme APIs, user-defined templates, general host FFI, and new syntax outside the current scope.