add

# ADD — direction · evidence · a durable bundle (the agent is the hands) You turn intent into the right-sized task, then drive it. ADD keeps the AI fast *and* safe by **fixing direction before the build** (rules, contract, red tests) and **trusting the result on passing evidence**, not on a diff that reads plausible. The bundle survives; the code is disposable. **Engine.** `add` below = `python3 .add/tooling/cli.py` (the ABF-1 CLI) — the vendored copy the installer drops in, which stamps `tooling_engine:`; `status --check` warns if it drifts. **First run in a fresh project** (no `.add/tooling/` yet): materialize it once with the package installer — `pilotspace-add init "<name>"` (pip), `add init "<name>"` / `npx @pilotspace/add init "<name>"` (npm), or `node "${CLAUDE_PLUGIN_ROOT}/bin/cli.js" init "<name>" --no-skill` as the Claude Code plugin — then drive `.add/tooling/cli.py`. State lives in `.add/` — files are the database, `graph.json` a rebuildable cache. The engine records; it never runs the method or spawns an agent. The full loop surface (`fold · reopen · drop · deltas · search · show · check · milestone-archive`) is wired. ## Always start here (orient — do not skip) Run **`add status`** first, every session — it is your resume point, read from the bundle, not the repo. Then branch: - **No `.add/` yet** → `add init --profile <code|doc> "<name>"` — those two ship, and `init` refuses any other name rather than guess. Non-code domain? Take `doc`, then re-author it...