The meta-gem, and the way a Terret is composed. Bundles ship ordered config rows, profiles stack bundles, patches adjust rows by id, and Terret.boot hands the result to the Hames loader -- so which plugins run, in what order, with what config is a question YAML answers rather than Ruby. Ships terret-base (the log, the harness, the model seam, the execution world sandboxed with the network denied, the standard tool roster, and a policy floor that starts closed), the headless profile template, and trt: boot, dump-config, doctor.

Claude Code's tool names, verbatim wherever it has one: Read, Write, Edit, Glob, Grep, Bash, WebFetch, Task and TodoWrite, plus snake_case terminal_* and job_* for the seams it has no equivalent for — all registered on ctx[:tools] with honest mutating/approval/concurrency metadata. Every handler reaches the world only through a seam, so swapping the sandbox row moves the whole roster into a container untouched. Zero runtime dependencies beyond stdlib; ripgrep is used as a fast path when it is present.