For Google Antigravity, Paqad is advisory: onboarding writes ANTIGRAVITY.md at the project root, telling the AI how to load your project's rules and workflows. Nothing in Antigravity makes the AI follow it. Onboarding also writes a file called .antigravity/hooks.json, but that file is only a list and Antigravity never runs it.
What Paqad can enforce in Antigravity
Nothing, during the session. Antigravity is at the advisory level: the tool is given the rules but nothing stops it ignoring them.
- No edit is refused by Paqad.
- No verification runs when the AI finishes.
- Paqad's evidence files are only written if the AI runs Paqad's commands itself.
Paqad's source records Antigravity as advisory because it wires no hook that the tool actually runs.
Files onboarding writes
| File | What it is |
|---|---|
ANTIGRAVITY.md | The entry file. It tells the AI to open .paqad/framework-path.txt and follow the installed framework, or to act as a normal assistant if Paqad is missing or off. An existing file keeps its text; Paqad's lines go in a marked block. |
.antigravity/hooks.json | A bookkeeping list of the hook files Paqad selected for the project. It is not in any format Antigravity runs, so it enforces nothing. |
.antigravity/mcp.json | The MCP servers Paqad suggests for your stack. MCP (Model Context Protocol) lets AI tools connect to extra information sources. The file names servers but holds no start commands, so it connects nothing by itself. |
.antigravity/cache.json, .antigravity/memory.json | Paqad bookkeeping. Not Antigravity settings. |
Paqad writes ANTIGRAVITY.md, but whether Antigravity loads a file with that name on its own depends on the Antigravity version you use. If the AI does not seem to know about Paqad, point it at ANTIGRAVITY.md at the start of the session.
Getting evidence without hooks
Paqad's instructions ask the AI, on advisory tools, to record each stage of feature work by running Paqad's commands in the terminal:
npx paqad-ai stage start planning
npx paqad-ai stage end planning --artifact <plan file>These write to the ledger, Paqad's evidence files under .paqad/ledger/. Nothing checks that the AI runs them. Look in .paqad/ledger/paqad.stage-evidence/ after a change to see what was recorded.
Independently of the AI, git post-commit and post-merge hooks link commits to their feature, and you can add Paqad's verification script to your CI pipeline. See Adapters overview.
Setting it up
- Run
paqad-ai onboard --providers antigravity, or tick Antigravity when onboarding asks. - Open the project in Antigravity and check that the AI has read
ANTIGRAVITY.md.
If you need edits to be refused when the process is skipped, use Claude Code or Codex CLI.