norm-spec 0.1.0-rc.1

High-level Rust API for collecting and validating .norm files
Documentation
  • Coverage
  • 100%
    14 out of 14 items documented0 out of 0 items with examples
  • Size
  • Source code size: 98.2 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 846.0 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 18s Average build duration of successful builds.
  • all releases: 18s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • CyanoOrg/norm-spec
    0 0 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • bravetwo

norm-spec

The .norm project-convention format, implemented as a Rust library and a portable norm CLI.

The project starts with one deterministic semantic engine. Its specification, schemas, templates, fixtures, and machine contracts live in this repository; framework adapters consume those contracts without becoming format authorities.

Status: 0.1.0-rc.1 release-preparation candidate. Gate C, Gate D, and the Gate E distribution implementation are complete, including standalone and canonical Skill adoption, Rust 1.97 MSRV verification, and four native archive targets. The RC still requires exact-candidate hosted verification; public visibility, tagging, GitHub Pre-release, crates.io publication, and stable v0.1.0 remain maintainer checkpoints.

Crates

  • norm-spec: packaged, filesystem-aware collect and validation facade.
  • norm-spec-core: deterministic parsing, collection rules, Schema and semantic validation, and versioned response models.
  • norm-spec-cli: arguments, presentation, exit codes, the norm command, and the independent norm-spec-conformance runner; filesystem semantics and release-owned assets are delegated to norm-spec.

Rust API

Until registry publication, pin an exact Git revision:

[dependencies]
norm-spec = { git = "https://github.com/CyanoOrg/norm-spec", rev = "<exact-commit>" }
use std::path::Path;
use norm_spec::{CollectRequest, ValidateRequest, collect, validate};

fn main() -> Result<(), Box<dyn std::error::Error>> {
    let root = Path::new(".");
    let inherited = collect(CollectRequest::new(root, Path::new("docs")))?;
    let checked = validate(ValidateRequest::all(root))?;
    assert!(!inherited.norms.is_empty());
    assert_eq!(checked.summary.errors, 0);
    Ok(())
}

See docs/RUST-API.md for request, failure, compatibility, and packaging boundaries.

Development usage

Run directly from the checkout:

cargo run -p norm-spec-cli -- --version
cargo run -p norm-spec-cli -- parse path/to/.norm --pretty
cargo run -p norm-spec-cli -- collect --root . --target path/to/directory --pretty
cargo run -p norm-spec-cli -- validate --all --strict
cargo run -p norm-spec-cli -- init --profile module --output path/to/.norm
cargo run -p norm-spec-cli -- scan --root . --text
cargo run -p norm-spec-cli -- compatibility --pretty

Or install the current development binary from this checkout:

cargo install --path crates/norm-cli --locked
norm parse path/to/.norm --pretty
norm collect --root . --target path/to/directory --pretty
norm validate --all --strict
norm init --profile module --output path/to/.norm
norm scan --root . --text
norm compatibility --pretty

cargo install also installs norm-spec-conformance. It verifies an explicit candidate against an exact exported or release-provided contract bundle:

norm-spec-conformance \
  --candidate "$(command -v norm)" \
  --contract-dir path/to/exact-contract-bundle \
  --pretty

This is an unpublished RC candidate install. The five initial commands, compatibility discovery, Rust facade, arbitrary-candidate conformance, packaged standalone adoption lane, canonical Skill, and target-specific self-verifying archives are functional. CI artifacts remain review evidence until a maintainer approves public release actions.

See docs/INTEGRATION.md for plugin-free project adoption, canonical Skill installation, failure behavior, and downstream host-adapter boundaries.

See docs/INSTALLATION.md for release archives, checksums, source installation, MSRV, upgrades, rollback, and uninstall.

See ROADMAP.md, docs/ARCHITECTURE.md, and docs/planning/v0.1-execution.md before contributing.

License

MIT © 2026 Wade