The current manual describes the Topaz language that users should write today. Its examples use the same grammar accepted by the checker, and the command-line tools report unsupported forms as errors instead of guessing.
Language definition
The language reference defines syntax, types, evaluation order, errors, modules, and the standard library. The covers metadata on each page helps maintainers keep that material synchronized, but readers do not need private design documents to understand the language.
Checking a program
Use topaz check for static validation and topaz run to execute a program directly. When you need a deployable artifact, build the Rust, Python, or web target documented for that environment.
Compatibility across outputs
Supported output targets are tested against direct execution for the language features they accept. A target that cannot preserve a feature must reject it clearly. The Toolchain Status page lists the currently available targets and their practical limits.
Version boundaries
The manual follows the latest language policy. The version number appears where installation, packages, generated artifacts, or migration depend on it. Long-form guides remain available in Classic.
Common checks
topaz check main.tpz
topaz run main.tpz
topaz build main.tpz --out-dir build