Topaz v5.10.0 is the current public release. The public command-line tools, runtime, npm installer, WASM compiler, documentation, and playground use the canonical topaz-5.10 language mode.
The current product includes contiguous mutable ByteBuffer, repaired Web memory ownership, the checked Local Data Application Loop, and a managed bounded HTTP/1.1 service target. The generated host owns finite connection, queue, request, response, deadline, log, and shutdown boundaries while request handlers remain ordinary checked Topaz code. It adds no outbound networking, ambient environment authority, shared Topaz heap, TLS termination, or general Web framework.
Checked native emit and build can write a deterministic function-level lowering report. When a whole application is not eligible for native lowering, proven top-level scalar functions and exact Bytes or ByteBuffer hot paths may still use native helpers inside the unchanged boxed application envelope. Direct binary fields on checker-proven read-only record parameters can enter that path; wider or unproved shapes remain boxed. The fast path preserves the boxed runtime's bounds faults, fixed-length and snapshot rules, overlapping-copy behavior, and validation-before-mutation contract.
The installed stock toolchain is exercised by a maintained multi-module binary-media kernel through raw Web and Worker artifacts without a private compiler. Its exact byte and fault courts, source-free execution, native-selection report, browser renderer, and bounded proof-worker path are checked together; performance evidence is scoped to that maintained workload rather than claimed for arbitrary programs.
Codec.deflateFixedCompress emits one deterministic raw fixed-Huffman DEFLATE block with a 32,768-byte history window, bounded match search, and a 256 MiB input limit. It is available through direct execution, generated Rust, raw Web, Web Worker, and the Playground. The Python target rejects programs that use this leaf before writing an artifact.
Codec.zlibFixedCompress emits a complete deterministic RFC 1950 stream by wrapping those exact raw bytes with the fixed 78 01 header and the original input's Adler-32 trailer. It has the same bound and supported routes; Python rejects it before artifact creation.
Codec.reedSolomon255223Protect creates systematic RS(255,223) codewords over GF(256) with fixed zero padding and a 65,535-shard limit. It is available on the same direct, Rust, Web, Worker, and Playground routes. Python rejects this leaf before artifact creation. It generates protection bytes only; error detection, correction, and configurable Reed–Solomon profiles are outside the current surface.
Hash.crc32 returns the unsigned CRC-32/ISO-HDLC value on direct, Rust, Python, Web, Worker, and Playground routes. It is a non-cryptographic integrity checksum; incremental state, Adler-32, CRC families, and PNG encoding are outside this operation.
Available components
- Native CLI for checking, running, emitting, and building programs
- Rust output for standalone native binaries
- Python output with its required runtime support file
- Raw WASM and web-worker output for browser applications
- Checked web-app scaffolding, loopback development, complete managed static bundles, local text import/export, and durable local preferences or drafts
- Package commands and the browser playground
Recommended workflow
Install Topaz with the public installer or npm package, start with topaz check, establish behavior with topaz run, then build only the target you plan to deploy. Use topaz version --verbose when reporting an installation problem.
Current support
The interpreter, Rust output, and Python output cover the current grammar and standard-library families documented on this site. Browser builds support raw WASM, worker packages, and checked Web Applications that run from their generated static bundle. File, process, network, clock, and browser APIs remain tied to the host environment described on their individual pages.
Repository integration artifact
Lispex-in-Topaz has internal, bounded integration evidence for one measured source family, but it is not a released Topaz component or a public backend.
| Area | Current bounded status |
|---|---|
| Canonical source | One LIT source across the interpreter, generated Rust, generated Python, and Web routes |
| Primitive capability floor | 84 of 205 rows supported, consisting of 31 deterministic delegations and 53 machine implementations; 121 fail loudly |
| Guest-calling primitives | 6 of 18 supported through the common machine dispatcher; the rest fail loudly |
| Four-host evidence | Internal evidence covers a bounded check surface across all four routes |
| Lispex release observation | One installed LIT route participates in the 144-case joint receipt; Rust/LIT agrees on 65 cases and diverges on 79 |
| Provenance boundary | All four Topaz routes are variants of one LIT source; they are not independent implementations and no source-independence is claimed |
This artifact does not add syntax, standard-library guarantees, installer contents, or a new public backend.
Known limits
Compression helpers are not uniformly portable to every output target; in particular, deterministic raw fixed-Huffman and fixed-zlib compression are unavailable on generated Python and fail during generation. Concurrent task ordering is intentionally unspecified. Some future language ideas listed on the roadmap are not accepted syntax yet. The Lispex integration remains bounded to 84 of 205 primitive rows, its exact four-host check surface, and the 144-case joint receipt. It does not establish whole-language equivalence.
Command reference
topaz version --verbose