commit 40942ae9e0c6f8c7f3ccefd837d9bfaf918d8f29
parent a135290a9196c63abe72eb2f63b81a1607b87cf4
Author: triesap <tyson@radroots.org>
Date: Mon, 22 Jun 2026 00:56:59 +0000
docs: remove misplaced nix guide
Diffstat:
3 files changed, 6 insertions(+), 120 deletions(-)
diff --git a/AGENTS.md b/AGENTS.md
@@ -25,7 +25,9 @@ This file exists for compatibility with tools that look for AGENTS.md.
Before editing code:
-- Read this file, `AGENT_INSTRUCTIONS.md`, `README`, `docs/nix.md`, and `spec/README.md`.
+- Read this file, `AGENT_INSTRUCTIONS.md`, `README`, and `spec/README.md`.
+- When touching Nix behavior, read `flake.nix` and the active Nix implementation files under
+ `nix/` until the approved `build/nix/` migration lands.
- Enter the canonical environment with `nix develop` or `direnv allow` before targeted cargo work.
- Discover commands from checked-in repo surfaces; do not invent ad hoc workflows.
- Read the current implementation and nearby tests before designing a change.
diff --git a/AGENT_INSTRUCTIONS.md b/AGENT_INSTRUCTIONS.md
@@ -40,7 +40,9 @@ Before editing code:
- Read `AGENTS.md`.
- Read this file.
-- Read `README`, `docs/nix.md`, and `spec/README.md` when the change touches workflow, exports, or public surfaces.
+- Read `README` and `spec/README.md` when the change touches workflow, exports, or public surfaces.
+- When touching Nix behavior, read `flake.nix` and the active Nix implementation files under
+ `nix/` until the approved `build/nix/` migration lands.
- Read the relevant crate manifest, implementation files, and nearby tests before proposing a new structure.
- Check `git status --short`.
diff --git a/docs/nix.md b/docs/nix.md
@@ -1,118 +0,0 @@
-# Nix
-
-This workspace uses Nix as the canonical development and CI environment contract.
-
-## Install Nix
-
-macOS:
-
-```bash
-sh <(curl --proto '=https' --tlsv1.2 -L https://nixos.org/nix/install) --daemon
-```
-
-Linux with systemd:
-
-```bash
-sh <(curl --proto '=https' --tlsv1.2 -L https://nixos.org/nix/install) --daemon
-```
-
-Enable flakes for your user:
-
-```bash
-mkdir -p ~/.config/nix
-cat > ~/.config/nix/nix.conf <<'EOF'
-experimental-features = nix-command flakes
-accept-flake-config = true
-EOF
-```
-
-## Optional direnv
-
-Install `direnv` and `nix-direnv` if you want the shell to load automatically when you enter the repo.
-
-```bash
-brew install direnv
-echo 'eval "$(direnv hook zsh)"' >> ~/.zshrc
-nix profile install nixpkgs#nix-direnv
-mkdir -p ~/.config/direnv
-echo 'source $HOME/.nix-profile/share/nix-direnv/direnvrc' >> ~/.config/direnv/direnvrc
-```
-
-After that:
-
-```bash
-direnv allow
-```
-
-## Enter The Shell
-
-Default shell:
-
-```bash
-nix develop
-```
-
-Coverage or release shell:
-
-```bash
-nix develop .#coverage
-nix develop .#release
-```
-
-The shells provide:
-
-- Rust `1.92.0` with `wasm32-unknown-unknown`
-- pinned nightly cargo for coverage from `rust-toolchain-coverage.toml`
-- `cargo-llvm-cov`
-- `pkg-config`
-- `clang` and `libclang`
-- `libsodium`
-
-## Command Map
-
-Pure flake checks:
-
-```bash
-nix flake check
-```
-
-Repo-aware command apps:
-
-```bash
-nix run .#fmt
-nix run .#check
-nix run .#contract
-nix run .#coverage-report
-nix run .#release-preflight
-```
-
-`nix flake check` is intentionally limited to pure surfaces:
-
-- Nix, shell, and TOML formatting through `treefmt`
-- Rust formatting through `cargo fmt --check`
-- pure cargo check/test derivations for the contract crate set
-- repo guards that can run without cargo registry network access
-
-Repo-aware flows stay behind `nix run` apps because they need a real checkout:
-
-- coverage refresh and release preflight produce repo-local artifacts derived from measured per-crate gate reports
-- publish commands read runtime tokens and the live checkout state
-
-## First Verification
-
-After installation:
-
-```bash
-nix flake check
-nix run .#contract
-nix run .#release-preflight
-```
-
-## Notes
-
-- Flakes only see tracked files when the source is treated as a git checkout. If Nix appears to miss a new file, `git add` it first.
-- Do not put secrets in `flake.nix`.
-
-## Deferred Infrastructure
-
-Public binary-cache support is intentionally deferred until repository infrastructure is ready to own it. The next infrastructure-backed follow-up is to provision a public cache, publish its trust key in `flake.nix`, and wire CI to write to it.
