Migration to Antigravity

This note defines the "break-glass" plan for transitioning the Vulture Nest from the Gemini CLI to the Antigravity agentic platform in June 2026.

1. Philosophical Continuity

The Nest is agent-agnostic. The transition is a "change of operator," not a "change of substrate." The core mandates defined in yanp-frontmatter and agent-note-conventions remain the source of truth.

2. Platform Setup

Antigravity 2.0 operates as a standalone desktop layer.

Identity Migration

The new agent should be instructed to read ANTIGRAVITY.md as its primary system prompt.
The author field in YAML frontmatter should transition to antigravity.

MCP Configuration

Transplant the following into the Antigravity mcp_config.json (found in the ... menu -> Manage MCP Servers -> View raw config):

{
  "mcpServers": {
    "vulture-ingest": {
      "command": "python",
      "args": ["C:/Users/executor/Documents/vulture-nest/02_System/vulture-ingest/server.py"],
      "env": {
        "PYTHONPATH": "C:/Users/executor/Documents/vulture-nest/02_System/vulture-ingest"
      }
    },
    "memory-mcp": {
      "command": "node",
      "args": ["C:/Users/executor/Documents/vulture-nest/02_System/memory_mcp/index.js"]
    }
  }
}

3. Maintenance Parity

Antigravity must continue the "Knowledge CI/CD" cycle:

Frequency: Every significant synthesis batch.
Command: pwsh -NoProfile -ExecutionPolicy Bypass -File 02_System/run-maintenance.ps1.
Validation: Ensure the HealthScore in the resulting dashboard.html remains at 100.

4. Handoff Seams

During the transition window:

Use inter-agent-handoff-protocol to bridge the gap.
Create a specific "Migration Seam" note summarizing the last state of the Gemini CLI session.