How Collaboration Works

The Core Principle: Driver vs. Peer

Most AI coding assistants suffer from self-confirmation bias: an agent that misunderstands a specification will generate flawed code, write flawed tests that reflect the misunderstanding, and report that all tests passed green. Human developers are forced to manually audit every diff line-by-line.

Clavity breaks this confirmation bias by pairing two distinct model families in the same workspace directory:

• Claude Code (Driver): Formulates plans, edits code, executes builds, and tests implementations.
• Google Antigravity (Peer): Convenes expert review panels, audits specifications before coding starts, and runs adversarial capstone checks before code completion.

The 6-Stage Lifecycle

1. 1. Brainstorm Claude (driver)

   Interactive interview refining requirements into a structured design document before writing any code.

2. 2. Spec Review agy panel (peer) adversarial-panel-review

   Antigravity convenes independent expert seats (Architecture, Security, Performance) to challenge assumptions.

3. 3. Plan Review agy panel (peer) adversarial-panel-review

   Implementation plan tasks are audited for logical ordering, dependency risks, and measurable verification gates.

4. 4. Build Claude (driver)

   Claude implements code changes incrementally in thin slices, verifying locally via compiler and unit tests.

5. 5. Capstone agy (peer) agy-capstone

   Rounds-until-green adversarial review of committed diffs. Peer cites exact file:line proofs before human gate.

6. 6. Test Audit agy (peer) agy-test-audit

   Hardens test suites against vacuous assertions, ensuring test suites would catch future regressions.

Prompt Waivers & Fallbacks

Every review stage is fully optional. If Antigravity is offline or quota is exhausted, you can instruct Claude Code via prompt:

• "Waive agy for this step" — Claude proceeds solo without peer review.
• "Waive agy for this and use subagents" — Claude delegates review rounds to internal subagents.

Automatic Defect Capture

While navigating code, Claude automatically records pre-existing defects or anomalies discovered during the session. At the conclusion of any task, say "start the triage" to compile, rank, and organize those findings into a prioritized backlog.

Ready to Pair?

Evaluate Clavity in your own development workspace: