Toolchain

Artifacts & Deployment

Generated Rust and Python, final build bundles, artifact identity, storage, and licensing in Topaz 5.6.1.

Topaz source uses the .tpz extension. emit exposes generated source for inspection and integration; build produces a complete target-specific deployment bundle. Generated Rust and Python are replaceable implementation artifacts, not additional Topaz syntaxes or stable hand-editing APIs.

Emit and build

Use topaz emit --target rust|python to inspect generated source. Targetless emit remains the Rust alias. Use topaz build --target native|python|web|web-worker --out-dir <dir> for a deployable product. Native output keeps the compatible target/debug/program or target/release/program location but leaves only the final executable there. Web targets leave WASM and JavaScript/TypeScript glue. Python leaves program.py and topaz_py_rt.py.

Artifact manifest and directory safety

Every successful build writes topaz-artifact.json last. Its managedFiles entries record relative path, SHA-256, byte length, and executable state. A same-target rebuild verifies those identities before replacement. A target switch, malformed manifest, altered managed file, or collision with an unknown user path fails loudly. Files not listed as Topaz-managed are preserved.

Temporary storage

Cargo work happens in a private temporary workspace with incremental compilation disabled. Successful and failed builds remove it automatically; a later Topaz invocation reclaims marker-owned residue from an interrupted process. topaz storage status reports owned workspaces and topaz storage clean removes inactive owned workspaces only. Topaz does not scan or delete system Cargo/Python caches.

Generated Python suppresses bytecode writing only while importing its bundled runtime and restores the caller's Python setting immediately. Direct python program.py, including -O and -OO, leaves no Topaz __pycache__.

Ownership and licenses

Official CLI, npm, editor, WASM, Playground, and generated runtime artifacts are distributed under Apache-2.0 with applicable notices. Studio Haze Inc. is the international English name of 스튜디오헤이즈 주식회사; both identify the same legal rights holder. Run topaz license or topaz notice for the text embedded in a native CLI. User-authored .tpz source, input data, application output, and application-specific generated code remain under the user's chosen commercial and licensing terms. Topaz names and logos are not licensed by Apache-2.0.

Boundaries

Artifact hashes identify installed local bytes; they do not claim reproducible builds or semantic equivalence. Native, Rust, Python, and browser paths remain measured implementation surfaces with their documented host requirements.