Crates

Dusk is a Cargo workspace. Its crates split along the same layers as the architecture: the portable core, the programs, the impls, and the clients.

Core (dusk/src/)

Crate	Role
dusk_capnp	The Cap'n Proto schemas (dusk.capnp, stream.capnp) - the wire format. Depend on it to talk to a node from outside the tree.
dusk_program	The SDK a program implements: the ProcessMixin / LauncherMixin traits, Namespace, ProgramArgs, Signal, Ready, and the stream helpers. no_std.
dusk_program_proc	The proc macros that remove the boilerplate - metadata!, derive(Args), derive(Launcher), derive(Process), derive(Portal), and the impl_*_rpc_server attributes.
dusk_program_sh_proc	The #[sh_entry] attribute macro.
dusk_core	The runtime: the DuskServer behind the Dusk capability, the Driver trait and its extern shim, sessions, and init wiring. no_std.
dusk_build	Build-script helpers for compiling .capnp schemas.
dusk_llm	The client behind Ask Dusk: builds the prompt and calls a configured OpenAI-compatible endpoint.

Programs (base/)

Each Base program is its own crate, named dusk_program_<name> - dusk_program_sh (the shell, which also hosts the ShEntry / SH_ENTRIES registry), dusk_program_ps, dusk_program_kill, dusk_program_sleep, dusk_program_date, dusk_program_hostname, dusk_program_true, dusk_program_false, dusk_program_init, dusk_program_nightfall, dusk_program_logs. See Base programs. dusk_program_sh_compiler (base/sh/compiler/) sits under the shell's client side: it holds the grammar a script is parsed with, and a node never links it. The bytecode a script compiles into, which init and sh both take in their args, is sh's own bytecode.capnp. See The shell.

dusk_base ties them together: it re-exports the programs and provides default_launcher_set(), the set a node links.

Clients (dusk/src/)

Crate	Role
dusk_program_sh (client::prompt, client::shell)	The interactive prompt - reedline UI, builtins, output rendering, host of Ask Dusk - and the Shell that drives the sh process a client attaches to. Both are the sh program's client side.
dusk_cli	The dusk CLI.
dusk_py	The Python extension (PyO3, built with maturin).

Impls (impls/)

Crate	Role
dusk_nix	The Unix impl: hosts the Embassy executor, implements NixDriver, enables embassy-time/std, and accepts client connections. Reads the hostname with gethostname(2).
dusk_windows	The Windows impl: the same, implementing WindowsDriver, and reading the hostname with GetComputerNameW.
dusk_std	The std impl: hosts the Embassy executor, implements StdDriver, and recovers a node's exit code the same way nix and windows do. It names no platform, so it compiles for every target with std and threads - ESP-IDF, Windows, Android, iOS, macOS, the BSDs, illumos and Linux. Its hosted feature, on by default, supplies critical-section/std and Embassy's std platform; firmware that brings its own turns it off.

Artifacts (artifacts/)

The deliverables you ship - templates to copy and make your own.

Crate	Role
dusk_node	The packaged server: a Rust rlib, a C library, or a staticlib to link into firmware or any host application. Which impl it links is a cargo feature - impl_nix, impl_windows or impl_std. See Node artifacts.
dusk_node_bin	Wraps it as the dusk_node binary, taking the same feature.
dusk_cli_bin	Builds the dusk CLI binary.
dusk_py (artifact)	Builds the dusk Python extension.