> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scoutqa.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Knowledge Base

> Centralized insights from your testing sessions, organized and accessible.

The Knowledge Base is where Scout stores and organizes insights gathered from your testing sessions. As you run explorations, Scout builds a comprehensive understanding of your application that helps improve future test runs.

<Note>
  **New in v0.10.1:** The Knowledge Base now includes Application Graph, Project Summary, and automatic issue pattern detection.
</Note>

## Knowledge tabs

Access the Knowledge Base from the **Knowledge** tab in your project. It contains three main sections:

### Application Graph

The Application Graph visualizes your application's structure based on Scout's explorations. It shows:

* Pages and routes discovered during testing
* Navigation paths between screens
* User flows and common journeys

This helps you understand how Scout perceives your application and identify areas that may need more exploration.

### Project Summary

Get a high-level overview of your project's testing history:

* Total executions and issues found
* Issue trends over time
* Most frequently discovered issue types
* Coverage of your application

### Critical Issue Path Graph

<Note>
  Visualize the paths that lead to critical issues in your application.
</Note>

The Critical Issue Path Graph shows you exactly how users might encounter bugs:

* Traces the steps leading to critical and high-severity issues
* Helps prioritize fixes based on how easily users can trigger them
* Identifies bottlenecks where multiple issues converge

## How the Knowledge Base helps

### Smarter future explorations

Scout uses Knowledge Base data to:

* Avoid re-testing stable areas unnecessarily
* Focus on sections that historically have more issues
* Recognize when new issues are related to previously found problems

### Automatic issue linking

When Scout finds a bug that's similar to a previous issue, it automatically links them together. This helps you:

* Understand patterns across multiple test runs
* Identify regressions when fixed bugs reappear
* Track issue frequency over time

### Observation-to-issue pipeline

Scout automatically converts observations into trackable issues. During exploration, Scout notes interesting behaviors. After analysis, significant observations become formal issues with:

* Severity assessment
* Reproduction steps
* Suggested fixes

## Best practices

<AccordionGroup>
  <Accordion title="Run regular explorations">
    The more you test, the smarter Scout becomes. Regular explorations build a richer Knowledge Base that improves issue detection and reduces false positives.
  </Accordion>

  <Accordion title="Review the Application Graph">
    Check the Application Graph periodically to ensure Scout has discovered all important areas of your application. If something is missing, run a targeted exploration.
  </Accordion>

  <Accordion title="Use Critical Issue Paths for prioritization">
    When planning fixes, check the Critical Issue Path Graph. Issues on frequently-traveled paths should be prioritized over those in rarely-used features.
  </Accordion>

  <Accordion title="Track linked issues">
    Pay attention to issues that Scout links together. Multiple linked issues often indicate a systemic problem that needs architectural attention rather than individual fixes.
  </Accordion>
</AccordionGroup>