# edgequake - 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: `raphaelmansuy/edgequake` - capability: EdegQuake 🌋 High-performance GraphRAG inspired from LightRag written in Rust; Transform documents into intelligent knowledge graphs for superior retrieval and generation - expected_user_outcome: EdegQuake 🌋 High-performance GraphRAG inspired from LightRag written in Rust; Transform documents into intelligent knowledge graphs for superior retrieval and generation ## 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. - **Overview & System Architecture**: importance `high` - source_paths: README.md, edgequake/Cargo.toml, edgequake/src/main.rs, edgequake/crates/edgequake-core/src/lib.rs, edgequake/crates/edgequake-api/src/lib.rs - **Core Pipeline & Data Flow**: importance `high` - source_paths: edgequake/crates/edgequake-pipeline/src/pipeline/mod.rs, edgequake/crates/edgequake-pipeline/src/extractor/mod.rs, edgequake/crates/edgequake-pipeline/src/chunker/mod.rs, edgequake/crates/edgequake-pipeline/src/merger/mod.rs, edgequake/crates/edgequake-pipeline/src/lineage.rs - **Configuration, Deployment & Operations**: importance `high` - source_paths: edgequake/crates/edgequake-llm/src/lib.rs, edgequake/models.toml, edgequake/crates/edgequake-api/src/state/bundled_models.rs, edgequake/crates/edgequake-api/src/state/provider_setup.rs, edgequake/crates/edgequake-api/src/providers/resolver.rs - **SDKs, APIs & Integrations**: importance `medium` - source_paths: edgequake/crates/edgequake-api/src/routes.rs, edgequake/crates/edgequake-api/src/server.rs, edgequake/crates/edgequake-api/src/openapi.rs, edgequake/crates/edgequake-api/src/handlers/websocket.rs, edgequake_webui/src/lib/api/edgequake.ts ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `2882651e7e396f02af21da647f52148719654d63` - inspected_files: `README.md`, `docs/CHANGELOG.md`, `docs/OBSERVABILITY.md`, `docs/README.md`, `docs/api-reference/document-upload-quick-reference.md`, `docs/api-reference/extended-api.md`, `docs/api-reference/index.md`, `docs/api-reference/lineage-endpoints.md`, `docs/api-reference/rest-api.md`, `docs/architecture/crates/README.md`, `docs/architecture/crates/index.md`, `docs/architecture/data-flow.md`, `docs/architecture/index.md`, `docs/architecture/lineage-tracking.md`, `docs/architecture/overview.md`, `docs/comparisons/edgequake-vs-lightrag-superiority-analysis.md`, `docs/comparisons/index.md`, `docs/comparisons/vs-graphrag.md`, `docs/comparisons/vs-lightrag-python.md`, `docs/comparisons/vs-traditional-rag.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: Installation risk requires verification - Trigger: Project evidence flags a installation 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: identity.distribution | https://github.com/raphaelmansuy/edgequake - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Installation risk requires verification - Trigger: Project evidence flags a installation 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: community_evidence:github | https://github.com/raphaelmansuy/edgequake/issues/252 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Installation risk requires verification - Trigger: Project evidence flags a installation 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: community_evidence:github | https://github.com/raphaelmansuy/edgequake/issues/255 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Installation risk requires verification - Trigger: Project evidence flags a installation 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: community_evidence:github | https://github.com/raphaelmansuy/edgequake/issues/251 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Configuration risk requires verification - Trigger: Project evidence flags a configuration 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: community_evidence:github | https://github.com/raphaelmansuy/edgequake/issues/259 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Configuration risk requires verification - Trigger: Project evidence flags a configuration 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: community_evidence:github | https://github.com/raphaelmansuy/edgequake/issues/250 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: Configuration risk requires verification - Trigger: Project evidence flags a configuration 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: community_evidence:github | https://github.com/raphaelmansuy/edgequake/issues/253 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: 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/raphaelmansuy/edgequake - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: Runtime risk requires verification - Trigger: Project evidence flags a runtime 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: packet_text.keyword_scan | https://github.com/raphaelmansuy/edgequake - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: 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/raphaelmansuy/edgequake - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.