Skip to main content
Glama
Antigravity Truth Guard

Antigravity Truth Guard

by bushold-dev

πŸ›‘οΈ Antigravity Truth Guard v2.0

Global Multi-Project Anti-Hallucination MCP Guard for Autonomous AI Coding Agents with Zero-Runaway-Cost Protection

English | Π£ΠΊΡ€Π°Ρ—Π½ΡΡŒΠΊΠ° вСрсія (README.uk.md)

MCP Protocol License: MIT Node.js Version Google Cloud

Antigravity Truth Guard is an open-source autonomous architectural governance system (MCP server) that guarantees AI coding agents (Google Antigravity, Claude Code, OpenAI Codex, Cursor, etc.) write code strictly grounded in verified facts and architecture contracts. It eliminates database schema hallucinations, prevents architectural layer contamination, and protects project owners from runaway API costs caused by infinite loops.


πŸ“– Table of Contents

  1. The Problem: Why Do AI Coding Agents Hallucinate?

  2. How Truth Guard Works (Plain English for Non-Programmers)

  3. Financial Safety Architecture: Zero-Runaway-Cost Protection

  4. Technical Architecture & In-Memory RAM Mirroring

  5. The 5 Universal Engineering Laws

  6. MCP Tools Reference

  7. Quickstart & Deployment Guide

  8. Connecting to Antigravity, Claude, Codex, and Cursor

  9. AI Agent Prompts Library

  10. How Verification and Scoring Work (Detailed Guide)


Related MCP server: guardian-mcp

🧩 The Problem: Why Do AI Coding Agents Hallucinate?

Autonomous AI coding agents operate with superhuman speed, but in commercial repositories, they exhibit three critical failure modes:

  1. Schema & Contract Hallucinations: When an agent lacks grounded context for a database table or business rule (e.g. β€œmonetary values must be stored strictly as integer cents, never floating-point numbers”), it guesses or extrapolates. This causes production outages, silent financial drift, and corrupted database states.

  2. Architectural Cross-Segment Contamination: An agent often tries in a single prompt to modify calculation formulas in the domain core, add a button to the UI, and alter database schemas simultaneously. The result is tangled spaghetti code that breaks Clean Architecture.

  3. The "Financial Abyss" (Runaway Agent Loops): If an agent encounters an unexpected error while operating autonomously (especially overnight), it can trap itself in infinite self-correction loops. It burns tens of thousands of LLM API calls, resulting in unexpected, massive billing charges.


πŸ›οΈ How Truth Guard Works (Plain English for Non-Programmers)

Imagine you are constructing a high-rise building, and the AI agent is an ultra-fast construction crew.

          [ User Request: "Build new inventory feature" ]
                                β”‚
                                β–Ό
                  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                  β”‚   AI Coding Agent         β”‚
                  β”‚   (Claude, Codex, etc.)   β”‚
                  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                                β”‚ 1. Drafts technical plan
                                β–Ό
              β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
              β”‚   πŸ›‘οΈ ANTIGRAVITY TRUTH GUARD      β”‚
              β”‚   (Chief Compliance Notary)       β”‚
              β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                            β”‚ 2. Audits against Ground Truth Laws
             β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
             β–Ό                             β–Ό
       [ Plan INVENTED Facts ]       [ Plan 100% GROUNDED ]
             β”‚                             β”‚
             β–Ό                             β–Ό
      ❌ STAMP: REJECTED             βœ… STAMP: APPROVED
      Job site remains locked!       Receipt generated:
      Agent must fix errors.         .truth-receipt.json
                                           β”‚
                                           β–Ό
                                     Construction/Code edit
                                     permitted to execute!

The "Notary & Blueprint" Principle:

  • The Blueprint (Ground Truth): Your project specifications, schema contracts, and domain rules stored in .md specification files (safe from self-poisoning). Truth Guard indexes them into a high-speed knowledge base.

  • Mandatory Fact-Check (truth_search): The AI agent is strictly forbidden from writing code blind. It must first ask Truth Guard: β€œWhat are the exact, verified rules for this subsystem?”.

  • The Independent Verification Gate (truth_verify_plan): Before modifying any code, the agent submits its implementation plan along with the intended target_files. An independent AI auditor cross-references every single table, column, enum, and arithmetic operation against the Ground Truth facts. If the agent invented anything, the plan is instantly rejected.

  • Cryptographic Verification Receipt (.truth-receipt.json): Only when the plan is 100% faithful does Truth Guard issue a time-stamped, cryptographically signed receipt bound to target_files (15-minute TTL, single-use per git commit). The repository verification harness (npm run verify and Git pre-commit hooks) rejects any commit or test run if code changes exist without an authentic, fresh receipt!


πŸ’³ Financial Safety Architecture: Zero-Runaway-Cost Protection

Truth Guard features an automated Emergency Safety Circuit Breakerβ€”just like an electrical circuit breaker in your house:

                          [ Daily API Call Stream ]
                                     β”‚
      β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
      β–Ό                              β–Ό                              β–Ό
  [ Calls 0 - 1,400 ]       [ Calls 1,400 - 5,000 ]       [ Calls > 5,000 (LOOP) ]
      β”‚                              β”‚                              β”‚
      β–Ό                              β–Ό                              β–Ό
  ⭐ TIER 1: FREE TIER        ⚑ TIER 2: PAY-AS-YOU-GO       🚨 TIER 3: CIRCUIT BREAKER
  Google AI Studio            Secondary Paid Fallback        EMERGENCY SHUTDOWN!
  1,500 free calls/day.       (costs a few cents,            All paid APIs blocked.
  Cost: $0.00 / day.          prevents work stops).          Forces LOCAL_FALLBACK.
                              Cost: ~$0.05.                  Cost: $0.00 (100% Safe).
  1. Tier 1 (Free Tier, 0 – 1,400 calls/day): Utilizes the Google AI Studio / Gemini API Free Tier (1,500 free requests per day). Operating comfortably within 1,400 calls/day, your daily operational cost is $0.00.

  2. Tier 2 (Paid Backup / Pay-as-you-go, 1,400 – 5,000 calls/day): If the daily free quota is exhausted or temporary 429 Rate Limits occur, the server does not crash. It automatically escalates to a linked Google Cloud Pay-as-you-go backend (Gemini / Vertex AI). Verification continues seamlessly at a cost of only a few cents per month.

  3. Tier 3 (Emergency Safety Circuit Breaker, > 5,000 calls/day): If an agent goes rogue or is trapped in an infinite script loop, the circuit breaker trips:

    • All paid external cloud API calls are immediately hard-blocked.

    • The server switches to LOCAL_FALLBACK_MODE (in-memory keyword BM25 search + deterministic TypeScript schema & rule auditing).

    • Your funds and credit card are 100% protected against runaway charges.


βš™οΈ Technical Architecture & In-Memory RAM Mirroring

1. In-Memory RAM Cache Mirror (local-mirror.json) β€” $0 Database Read Costs

  • At server boot, all knowledge chunks for the active project and global space are loaded into process memory (ramMirror) and cached locally in local-mirror.json.

  • All truth_search requests execute entirely in RAM using hybrid scoring:

    • Vector Cosine Similarity over 768-dimensional embeddings (gemini-embedding-001).

    • BM25 Keyword Matching over section titles and body content.

  • Zero Firestore read charges during developer/agent conversations! (Comfortably inside Firestore's 50,000 free daily reads).

2. Multi-Project Isolation with Priority Boosting

  • Truth Guard automatically detects the active project from the git repository name or package.json.

  • Search runs concurrently across two namespaces: project_id == currentProjectId and project_id == "global".

  • Project-specific facts receive a [HIGH (PROJECT OVERRIDE)] priority tag and rank boost over global defaults ([BASE (GLOBAL)]).

3. Background Smart Watcher (Zero Quota Waste)

  • Powered by chokidar, Truth Guard continuously monitors **/*.md, **/*.schema.ts, and **/*.types.ts.

  • Sections are tracked via SHA-256 hashes in .truth-hashes.json.

  • Embeddings are generated only for sections whose text has genuinely changed.


πŸ“œ The 5 Universal Engineering Laws

Defined in global-rules.md and seeded automatically into project_id: "global":

  1. Grounded Context (global-no-guessing): Agents are forbidden from guessing codebase architecture, database schemas, or API contracts. Every task starts with truth_search.

  2. Cross-Segment Isolation (global-surgical-scope): Strict Clean Architecture boundaries. Never blend changes across Domain, Application, Infrastructure, and UI in a single monolithic edit.

  3. Verification Honesty (global-verification-honesty): Never bypass compiler diagnostics (@ts-ignore) or mock test passes. Every plan must cite authentic cited_fact_ids.

  4. Ledger-First Accounting (global-defensive-code): All currency values must use integer cents (integer cents). Balances must never be directly overwritten; every inventory change must be an immutable ledger delta (+ / -).

  5. Hierarchy of Truth (global-project-priority): Project-specific rules always take absolute precedence over global defaults when conflicting.


πŸ› οΈ MCP Tools Reference

The server exposes 4 standard Model Context Protocol (MCP) tools:

Tool

Purpose

Key Arguments

truth_search

In-memory semantic & BM25 search (0 database reads)

query (search text), include_global (boolean)

truth_verify_plan

Multi-tier LLM verification gate & receipt generator

proposed_plan, cited_fact_ids, target_files (optional), project_dir (optional)

truth_upsert_rule

Create or update a spec rule (Human-in-the-Loop protected)

scope, file_path, section_title, content, user_confirmed, confirmation_token

truth_status

Comprehensive status report: active tier, RAM chunks, circuit breaker

target_project (optional)


πŸš€ Quickstart & Deployment Guide

1. Clone & Install Dependencies

git clone https://github.com/bushold-dev/antigravity-truth-guard.git
cd antigravity-truth-guard
npm install

2. Configure Environment Variables

Copy .env.example to .env:

cp .env.example .env

Fill in your configuration:

# Free Gemini API Key (Get free key at https://aistudio.google.com/app/apikey)
GEMINI_API_KEY="your-gemini-api-key-here"

# Google Cloud Project ID with Firestore Native database
GCP_PROJECT="your-google-cloud-project-id"
FIRESTORE_DATABASE="(default)"

3. Create Firestore Composite Vector Index (Run Once)

gcloud firestore indexes composite create \
  --collection-group=truth_chunks \
  --query-scope=COLLECTION \
  --field-config=field-path=project_id,order=ASCENDING \
  --field-config=field-path=embedding,vector-config='{"dimension":"768","flat":{}}'

4. Run Verification Self-Test

npm test

Verifies RAM mirror preloading, semantic search, plan verification, and the circuit breaker safety system.


πŸ”Œ Connecting to Antigravity, Claude, Codex, and Cursor

For Google Antigravity

Add to ~/.gemini/config/mcp_config.json or ~/.gemini/antigravity/mcp_config.json:

{
  "mcpServers": {
    "antigravity-truth-guard": {
      "command": "node",
      "args": ["/absolute/path/to/antigravity-truth-guard/server.mjs"]
    }
  }
}

For Claude Code (claude.json)

{
  "mcpServers": {
    "truth-guard": {
      "command": "node",
      "args": ["/absolute/path/to/antigravity-truth-guard/server.mjs"]
    }
  }
}

For OpenAI Codex (~/.codex/config.toml)

[mcp_servers.truth_guard]
command = "node"
args = ["/absolute/path/to/antigravity-truth-guard/server.mjs"]

Enforce in Your Project's CI/CD or Build Script (package.json)

{
  "scripts": {
    "verify": "node /path/to/antigravity-truth-guard/check-receipt.mjs && npm run lint && npm test"
  }
}

If an AI agent modifies code in src/ without obtaining an authentic .truth-receipt.json from truth_verify_plan, this script immediately halts the build!


πŸ€– AI Agent Prompts Library

We provide ready-to-use copy-paste prompts in PROMPTS.md (Π£ΠΊΡ€Π°Ρ—Π½ΡΡŒΠΊΠ° вСрсія):

  1. Autonomous Setup Prompt: Directs any AI agent to prepare Google Cloud, install Truth Guard, and connect it to your IDE.

  2. Repository Enforcement Prompt: Directs any AI agent to enforce mandatory verification receipts and the 3 Laws of Truth inside an existing project.


πŸ“„ License

Released under the open-source MIT License. Contributions, issues, and forks are welcome!

Available Tools

4 tools
truth_statusA

Get operational status of antigravity-truth-guard: tier, RAM mirror count, circuit breaker, and quota usage

Inputs: target_project.

truth_upsert_ruleB

Create or update a ground-truth rule or spec both locally on disk, in RAM mirror, and in Firestore (requires human confirmation)

Inputs: content (required), file_path (required), section_title (required), scope, +2 more.

truth_verify_planB

Anti-hallucination verification gate: checks proposed plan against ground truth facts using multi-tier LLM engine

Inputs: target_files (required), proposed_plan (required), cited_fact_ids (required), project_dir.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a clearly distinct operation: semantic search, plan verification, rule upsert, and status reporting. There is no meaningful overlap between them, and an agent can easily select the right tool.

    Naming Consistency4/5

    All tools share a consistent truth_ prefix and snake_case style. Three use verb-based names (search, verify_plan, upsert_rule) while truth_status is noun-based, a minor deviation.

    Tool Count5/5

    Four tools is a well-scoped set for a truth-guard service: search, verify, upsert, and status each earn their place without redundancy.

    Completeness4/5

    The surface covers reading, verifying, creating/updating, and monitoring rules. However, there is no explicit delete/remove operation for rules and no dedicated list-all tool, leaving minor lifecycle gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI coding agents with an embedded knowledge graph and architecture governance tools, enabling blast radius analysis, compliance checks, and smart context extraction from codebases.
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to avoid irreversible mistakes by intercepting risky deletions, overwrites, and commands before execution, applying path, pattern, and blast-radius safeguards with quarantine backups.
      3
      13 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables autonomous agents to enforce financial guardrails by tracking real-time token burn and cost velocity, automatically throttling or freezing execution when budgets are exceeded. It also blocks destructive shell commands, prompt injections, and runaway planning loops while sanitizing outputs before they are returned.
      7
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents such as Claude Code and Cursor to check a team's learned decisions from pull requests, reviews, and docs before writing code, showing whether breaking them is blocking or advisory. It also provides locally computed symbol impact/blast-radius analysis so source code never leaves the machine.
      67 npm
      2
      MIT