# graphrag - Doramagic AI Context Pack

> Purpose: pre-work context for the user's host AI. This pack does not prove that the project has been installed, run, or validated.

## Project

- canonical_name: `microsoft/graphrag`
- capability: A modular graph-based Retrieval-Augmented Generation (RAG) system
- expected_user_outcome: A modular graph-based Retrieval-Augmented Generation (RAG) system

## Operating Boundaries

- Do not claim that the project has been installed, run, called through an API, or used on local files unless separate evidence proves it.
- Project facts must come from repo evidence, Claim Graph, or explicit source references.
- When a capability is not verified, mark it as unverified instead of completing it as fact.
- publish_status: `publishable`
- blocking_gaps: none

---

## Doramagic Context Augmentation

The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints.

## Human Manual Outline

Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph.

Host AI hard rules:
- Do not treat page titles, section order, summaries, or importance values as factual project evidence.
- When explaining the Human Manual outline, state that it is only a reading route or salience signal.
- Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph.

- **GraphRAG Overview and Architecture**: importance `high`
  - source_paths: README.md, docs/index.md, docs/index/overview.md, docs/index/architecture.md, docs/get_started.md
- **Indexing Pipeline, Data Flow & Incremental Updates**: importance `high`
  - source_paths: docs/index/default_dataflow.md, docs/index/inputs.md, docs/index/outputs.md, packages/graphrag/graphrag/api/index.py, packages/graphrag/graphrag/cli/index.py
- **Query Engine and Search Methods**: importance `high`
  - source_paths: packages/graphrag/graphrag/api/query.py, packages/graphrag/graphrag/cli/query.py, packages/graphrag/graphrag/query/factory.py, packages/graphrag/graphrag/query/structured_search/local_search/search.py, packages/graphrag/graphrag/query/structured_search/global_search/search.py
- **Configuration, LLM Integration, Storage & Extensibility**: importance `high`
  - source_paths: docs/config/overview.md, docs/config/models.md, docs/config/yaml.md, docs/config/init.md, docs/index/byog.md

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `6d02c2355c3fed4c49007572fbe951d73258a37f`
- inspected_files: `README.md`, `pyproject.toml`, `uv.lock`, `docs/blog_posts.md`, `docs/cli.md`, `docs/config/init.md`, `docs/config/models.md`, `docs/config/overview.md`, `docs/config/yaml.md`, `docs/data/operation_dulce/ABOUT.md`, `docs/data/operation_dulce/Operation Dulce v2 1 1.md`, `docs/developing.md`, `docs/examples_notebooks/inputs/operation dulce/ABOUT.md`, `docs/examples_notebooks/inputs/operation dulce/Operation Dulce v2 1 1.md`, `docs/get_started.md`, `docs/index/architecture.md`, `docs/index/byog.md`, `docs/index/default_dataflow.md`, `docs/index/inputs.md`, `docs/index/methods.md`

Host AI hard rules:
- Without repo_clone_verified=true, do not claim that the source code has been read.
- Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts.
- Without quick_start_verified=true, do not claim that the Quick Start path has run successfully.

## Doramagic Pitfall Constraints

These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes.

### Constraint 1: Capability evidence risk requires verification

- Trigger: README/documentation is current enough for a first validation pass.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: capability.assumptions | https://github.com/microsoft/graphrag
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 2: Maintenance risk requires verification

- Trigger: Project evidence flags a maintenance risk. Review the linked source before relying on this workflow.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/microsoft/graphrag
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 3: Security or permission risk requires verification

- Trigger: no_demo
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: downstream_validation.risk_items | https://github.com/microsoft/graphrag
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 4: Security or permission risk requires verification

- Trigger: no_demo
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: risks.scoring_risks | https://github.com/microsoft/graphrag
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 5: Maintenance risk requires verification

- Trigger: issue_or_pr_quality=unknown。
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/microsoft/graphrag
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 6: Maintenance risk requires verification

- Trigger: release_recency=unknown。
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/microsoft/graphrag
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.
