Docs
Four commands. Start with ask.
Install
Python 3.10 or newer. An Anthropic API key. The key stays on your machine; Aition makes calls from there and nowhere else.
$ git clone REPO_URL aition $ cd aition $ pip install -e . $ export ANTHROPIC_API_KEY=... $ aition setup --project /path/to/repo
setup builds the structural index once. It's fast (2.9s on Django, 8.3s on PX4) and reruns on demand.
Commands
aition ask "<question>" --project . Finds every file that could be affected, sends only those to the model, returns a verdict per file with a reason and a confidence. Prints a cost estimate before spending. Run it before you make the change.
Flags: --max-cost 1.00 caps the spend. --json for machine output.
aition plan "<migration>" --project . Returns a dependency-ordered sequence of waves: change these first, these next, these together. Free, no API call.
aition audit --project . Keeps a ledger of every assumption every agent session has made, re-checks all of them against the current code, and names the ones that just went false.
aition triage Give it an agent's diff and transcript, get the four-bucket classification of the agent's own work plus a repair plan. Also runs as a post-commit hook and a GitHub Action.
Verdicts
- DISCARDThrow the file away. The only verdict that requires unanimity across samples.
- REWORKThe file depends on the invalidated assumption and needs changes.
- REVIEWPossibly affected, or confidence was too low to say. Low confidence always lands here, never in SAFE.
- SAFEExamined and unaffected. Files not examined are listed separately with a reason; they are never counted as safe.
Every examined file says how it got into the set: "imports order-service", "shares the event name order.created with subscriptions.py, no import", "implicitly implements the Go interface Gateway". When expansion stops at a hub file, the output says so.
Everything else
Config, the GitHub Action, the post-commit hook, and the JSON schema live in the repo README. The repo is private for now. Ask for access.