deep_research/GEMINI.md

GEMINI.md — Gemini / Antigravity Overrides

This file has higher priority than AGENTS.md for Gemini CLI and Antigravity.

Load The Right Layer

• Shared baseline: AGENTS.md
• Antigravity roles: .agents/agents.md
• Strong research rules: .agents/rules/
• Skills: .agents/skills/
• Workflows: .agents/workflows/

For Antigravity native research, load .agents/agents.md, .agents/rules/deep-research-antigravity.md, .agents/skills/antigravity-surface-adapter/SKILL.md, .agents/skills/method-selection/SKILL.md, .agents/skills/research-quality-gates/SKILL.md, and .agents/workflows/deep-research-native.md.

Use /memory show or /memory refresh in Gemini CLI when the loaded context may be stale.

Gemini Failure Modes

Treat Gemini-family models as high risk for false certainty in research.

• Never say "searched", "verified", "confirmed", "officially shows", or "according to source" unless a real tool call happened in this session or phase and the result is logged.
• Do not use model memory, snippets, or AI summaries as evidence.
• Every concrete fact needs a source_id, claim-ledger row, or a clear "to verify" label.
• If the original source cannot be opened, write "未能访问原文，仅作为发现线索" and do not extract exact values from it.
• Keep search_log.jsonl, claims_ledger.jsonl, and continuation_state.json current in Antigravity native runs.
• Prefer "未找到足够证据" over filling gaps.

Platform Boundary

Gemini CLI normally uses Python-core mode through .gemini/commands/dr/*.toml or uv run python scripts/dr.py ....

Antigravity is different: use native mode and its model quota for research execution. Python scripts are auxiliary unless the user explicitly approves Python model-worker/API usage.

Do not modify projects/** unless the user is intentionally running a research project.