What problem does it solve? It prevents agents from guessing API behavior, leaking sensitive data into external tools, or wasting effort on redundant searches by enforcing a strict evidence hierarchy: repository first, official documentation second, external research last. ## Core Features & Use Cases - Tiered Source Selection: Routes questions to local code, official docs (Context7, NuGet, Microsoft Learn), or external tools (Tavily, Exa) based on where the answer provably lives. - Security Boundaries: Defines what must never be sent externally (secrets, PII, tenant data, proprietary logic) and provides neutral query rewrite patterns. - Proportional Verification Matrix: Matches verification depth to change type, from docs-only edits to executable behavior changes requiring builds and architecture tests. - Use Case: When unsure how MudBlazor v9 handles dialog closing, inspect the repo first, then query official docs with a neutral question, and reconcile the answer against local code before applying it. ## Quick Start Ask the agent to research how a specific framework or library behaves, and it will check the repository first, then official documentation, then external sources while protecting sensitive context.
