Weyl Standard Nix

A collection of coding standards, patterns, and conventions for building production systems, codifying principles for high-performance computing, infrastructure, and software engineering.

A specification for building reproducible, composable infrastructure on Nix with flakes, flake-parts, and consistent naming conventions.

Thanks to all contributors to Weyl Standard Nix and acknowledgments to the Nix community.

Weyl Standard provides coding guidelines for production systems across multiple languages, optimizing for disambiguation, testability, and maintainability.

Production Python for GPU inference and ML orchestration, emphasizing type safety, structured logging, and disambiguation over brevity.

C++ guidelines for extreme performance requirements, using modern C++23 features with emphasis on clarity and disambiguation in agent-heavy development.

Production Haskell guidelines optimizing for disambiguation, focusing on pragmatic patterns for web servers, compilers, and systems programming.

Production Rust for memory safety without garbage collection: explicit error handling, type-driven development, and agent-friendly patterns.

Conventions, patterns, and requirements for TypeScript code within Weyl AI systems for web services and tooling.

Conventions, patterns, and requirements for Bash scripts within Weyl AI systems.

Building for aarch64 targets from x86_64 workstations.

Prerequisites and setup for Weyl Standard Nix projects.

Use ndg for modules, nixdoc-style comments for functions, and helpful error messages with clear explanations and examples.

Advanced overlay composition patterns.

Create your first conformant flake with Weyl Standard.

Nix is infrastructure, not the main attraction. All Nix code lives under nix/ with clear organization for modules, packages, overlays, and configurations.

The weyl-stdenv family provides opinionated build environments for serious systems work.

How to use weyl-std in your projects.

These patterns are explicitly prohibited in Weyl Standard Nix to avoid common pitfalls and maintain code quality.

Every package. Every library. Every time. RelWithDebInfo for the entire dependency closure.

Configure your environment to use shared infrastructure for faster builds.

Nix has multiple module systems that share syntax but differ in semantics - flake-parts, NixOS, nix-darwin, and home-manager.

Standard nixpkgs idioms are fine, everything else gets spelled out. Optimize for grep and maintainability.

Every flake output must be built or checked by nix flake check. Untested code is broken code.

Modules should be self-contained with options and config together, using mkIf and mkMerge for lazy evaluation.

Packages should be callPackage-able functions using finalAttrs pattern for proper override support.

Practical guides for working with Weyl Standard Nix, covering getting started, patterns, and advanced topics.

Advanced topics for experienced Nix users.

Start here to set up your first Weyl Standard Nix project.

Coding patterns for Weyl Standard Nix.

We do not use what is approved

Understanding why Nix is essential for reproducible infrastructure

Understanding overlays as universe transformers

Naming conventions and the shibboleth

The philosophical foundations of Weyl Standard Nix

weyl-std library functions, available via weyl-std.lib.

Module configuration options for weyl-std.

API reference and option documentation.

This RFC establishes Weyl Standard Nix, a specification for writing Nix code within the weyl-ai organization.

This RFC specifies wsn-lint, a static analysis tool that mechanically enforces Weyl Standard Nix.

Request for Comments — the normative specifications for Weyl Standard Nix.