Project intelligence

What it maps

Project intelligence builds an inspectable working view of routes, symbols, dependencies, test signals, reports and likely change impact. The Agent uses this signal to choose a smaller, more relevant context for each turn.

• Relevant files and symbols.
• Dependency paths and affected boundaries.
• Test coverage and recent test signals.
• Working set and change impact before editing.

How to use it

Ask the Agent to map the project or explain the impact of a proposed change before implementation. Use the graph and file list to challenge the plan when an important dependency is missing.

What it does not do

The map is an aid to reasoning, not a guarantee that every runtime dependency is known. Generated files, dynamic imports, external services and stale indexes still require a focused test and human review.