Gemini Deep Research

---
id: "allzy.framework.prompts.review.framework-docs-consistency-review.gemini-deep-research"
title: "Framework Docs Consistency Review Prompt — Gemini Deep Research"
artifact_type: "Prompt"
prompt_family: "Review"
prompt_variant: "Framework Docs Consistency Review"
adaptation_target: "Gemini Deep Research"
status: "Stable"
version: "1.0.0"
framework_version: "5.0.2"
tags:
  - allzy-framework
  - prompt
  - review
  - framework-docs-consistency-review
  - gemini
  - deep-research
---

# Framework Docs Consistency Review Prompt — Gemini Deep Research
Use Gemini Deep Research.
Act as a senior framework documentation consistency analyst.
Research objective:
Conduct a source-based consistency review of the provided Allzy Framework documentation set. Identify drift, contradictions, incorrect numbering, missing cross-references, mismatched terminology, source-of-truth confusion, and V5 summary alignment issues.
Decision context:
This report will support maintenance and correction of the Allzy Framework documentation. The goal is to identify what needs to be patched, what should remain unchanged, and whether the V5 master specification accurately summarizes docs 01–09.
Scope:
- Source boundary: only the provided Allzy Framework documentation files.
- Geography: not applicable.
- Timeframe: not applicable except where the provided docs themselves define versioning or V5 alignment.
- Domain: Allzy Framework documentation consistency.
- Include: document numbering, file names, framework phases, layer model, Full / Compact / Direct terminology, Yin/Yang artifact types, no standalone Yang Compact, Triage Fast / Standard / Deep, Workspace Context Initialization, Workspace State Maintenance, Context Retrieval Builder, Document Metadata Enrichment, Metadata/frontmatter rules, Prompt Config Block rules, Search Log / Context Package / Metadata Index distinctions, Skills vs. Memory distinction, Model vs. Platform distinction, Template availability rules, and V5 summary alignment.
- Exclude: external web research, unrelated framework concepts, implementation planning, code generation, new framework rules, and rewriting documentation text.
Expected documentation set: