What the tools send
Nothing. No shipped file under src/ or hooks/ opens a socket
or calls fetch. There is no telemetry, no analytics, no crash reporting, no
update check, and no API key to give it, because there is nothing to authenticate to.
The package has no runtime dependencies, so nothing arrives with it that could.
The git hooks, the command line tools and the MCP server all run as local processes on your machine. The MCP server speaks stdio to whatever started it and does not listen on a port.
What the tools write
Everything the gates record stays inside the repository you run them in, under
.adg/:
.adg/test-diff.json, the baseline recording what a repository already held when the gates were adopted, so old work is not reported as new weakening..adg/prose-rules.txtand.adg/prose-baseline.txt, used only when the optional prose check is turned on..adg/induced/, holding the failures an induced-failure run declares.
adg init also writes hook configuration into your project for whichever
agents you ask it to set up. Those files are yours, they are readable text, and they are
the only things the tools create.
adg census checks out your own base commit into a scratch git worktree in
the system temporary directory and removes it when it is done. Nothing is copied out of
the repository, and nothing survives the run.
This website
These pages are static files. They load no JavaScript, no fonts, no images from anywhere else, and no analytics. They set no cookies and use no browser storage. Opening this page makes exactly one request, for this page.
It is served by GitHub Pages. Like any web host, GitHub receives the request and can log it, which is outside this project's control. GitHub's own privacy statement covers what it does with that.
Installing it
Installing from npm is a request to npm, and npm sees it. That is true of every package and has nothing to do with this one. After the install, the code does not go back.
Questions and changes
Every claim here is a claim about code you can read. If you find one that does not hold, that is a bug, and an issue is the place for it. Changes to this page arrive the way everything else here does, as a commit in the repository.