# AGENTS.md

Heavy work runs on folknet hardware, never on the development box. Builds, tests, model
batches, corpus and ground-truth building, and oracle and conformance-suite runs all go to
the build lanes and the machines behind them; the development box only coordinates
(edits, git, starting and watching runs). A script that does heavy work routes itself to a
lane, and a model batch fails rather than fall back to a local run when no lane answers.

How: `docs/infrastructure.md` → "Build lane" (`bench/on-lane.sh`, `bench/remote-lane.sh`,
`bench/verify.sh`), and `bench/batch-lane.sh` for model batches.

Pushing `main` to this repo's remotes needs no confirmation.

Never use the word `seam` in prose; say "generated function" (or a plainer phrase that fits
the sentence). `crates/harness/tests/no_seam_word.rs` enforces it for `README.md`,
`roadmap.md`, `docs/*.md` and this file; code identifiers and paths in backticks are
exempt.