Wyzer (meaning *wiser*) is a statically typed, compiled, resource‑oriented language that integrates distributed safety through choreographic programming and a perceus memory model. The project began months ago out of frustration with Rust: while Rust guarantees memory safety, it offers no protection against distributed deadlocks, protocol mismatches, or cross‑service correctness. Wyzer addresses these gaps by generalizing choreographic programming into a high‑level language and replacing complex borrow checkers with linear/affine types and a lighter perceus reference counting system.

After five months of research and a few weeks of coding, the author is preparing to release version 0.1.0. Contributions are welcomed; the RESEARCH.md file explains the theoretical foundations, and the official documentation covers variables, structs, control flow, and error handling. Wyzer aims to be simple, explicit, and easy to read, offering a single ownership rule that applies to memory, threads, and networks.

The community can join the Discord server (https://discord.gg/Rhp) to discuss development, ask questions, or contribute. Sample projects, such as the donut.wyz rewrite of the famous donut program, demonstrate Wyzer’s practical applicability.

Wyzer’s designatings like Koka and Lean 4 inspired its memory model, while academic research informs its choreographic approach.