With Stado#

Stado installs Zrodlo's release and places the binary in ~/.stado/bin; how it chooses and checks a release is Stado's own documentation:

stado product install zrodlo --surface cli
stado product status --surface cli zrodlo
zrodlo --help

The release for darwin-arm64 is built with Metal, so --device metal --ordinal 0 trains on the Mac's GPU. The release for linux-amd64 computes on the CPU.

Zrodlo Desktop#

The macOS window over the installed zrodlo installs the same way, into ~/Applications/Zrodlo.app:

stado product install zrodlo --surface desktop

It finds zrodlo where ZRODLO names it, else on PATH, else in ~/.stado/bin, and shows one form per command that binary lists.

From source#

Zrodlo needs Rust 1.88 or newer, Stado, and a checkout of its repository, which is private to members of the Wisent organization. Stado builds Rust with kompilator, never Cargo, and compiles kompilator itself from the sources it carries, so there is nothing else to install (Building Rust with kompilator). In that checkout:

WISENT_OUTPUT_DIR="$PWD/.build" stado product kompilator stage --bin zrodlo

The binary is .build/zrodlo; WISENT_OUTPUT_DIR must be an absolute path. Add --features metal on a Mac, or --features cuda on a machine with the CUDA toolkit, to compute on the GPU. A binary built without the feature refuses --device metal or --device cuda.

What it needs#

Zrodlo runs without any other Wisent product: preparing data, training, resuming and evaluating involve no gateway, vault, fleet or service. It reads only the files you name: text or JSON Lines files, a tokenizer.json, a Transformers config.json, and the corpora, models and checkpoints it wrote itself.

--precision bf16 needs a GPU: Candle's CPU backend has no bfloat16 matrix product, so a bf16 command on the CPU is refused before anything is written.