Overview
The Findings Explorer is a unified dashboard for browsing all memory items in your project — both from Genesis Scan analysis and from session enrichment. It replaces the older layer-specific views with a single, searchable interface organized by knowledge category.
Navigate to Findings Explorer from the sidebar.
Data sources
The Findings Explorer aggregates items from two pipelines:
| Source | Badge | Description |
|---|---|---|
| Genesis Scan | Scan | Items produced by running a full codebase analysis |
| Session Enrichment | Session | Items captured from coding sessions via VS Code extension, CLI, or MCP |
| Manual | Manual | Items created or imported manually |
Each finding card displays a colored source badge so you can tell at a glance where the knowledge came from.
View modes
Toggle between two views using the switcher in the top-right corner:
Highlights
The default view shows a summary dashboard with several panels:
- Scan Summary — Total findings, category count, security issue count, and average confidence
- Knowledge Sources — Distribution of items by source (Scan, Session, Manual) with counts and percentage bars
- Category Heatmap — Top categories ranked by item count, with orange intensity scaling to show knowledge concentration
- Top 10 Findings — The highest-importance findings across all categories, ranked by importance and confidence
- Module Map — A visual breakdown of which parts of your codebase have the most findings
- Security Highlights — A preview of the top security findings (only items tagged as real vulnerabilities)
Click Explore All Findings at the bottom to switch to the full list.
All Findings
The full list view includes:
- Search bar — Filter findings by title or content
- Confidence slider — Set a minimum confidence threshold (0–100%)
- Category tabs — Filter by knowledge category (see below)
Category tabs
Findings are organized into 27 categories derived from the schema key taxonomy. Tabs only appear when they have items — empty categories are hidden.
Core categories
| Category | Schema Key | Description |
|---|---|---|
| Product | root/product | Business logic, user flows, feature boundaries |
| Architecture | root/architecture | Tech stack decisions, patterns, structure |
| Conventions | root/conventions | Coding style, naming, organization rules |
| Decisions | root/decisions | Architectural decision records |
Domain categories
| Category | Schema Key | Description |
|---|---|---|
| Stack | root/stack | Dependencies, frameworks, configs |
| Auth | root/auth | Authentication, sessions, tokens |
| Security | root/security | Real vulnerabilities (OWASP-style issues tagged security) |
| Risks | root/security | Technical debt and improvement suggestions (security-adjacent items not tagged as vulnerabilities) |
| Data | root/data | Database schema, migrations, seed data |
| Performance | root/perf | Indexes, caching, query optimization |
| Infrastructure | root/infra | CI/CD, Docker, deployment |
| Testing | root/testing | Tests, mocks, fixtures |
| Docs | root/docs | README, guides, documentation |
Code area categories
| Category | Schema Key | Description |
|---|---|---|
| Frontend | root/frontend/* | UI, components, routes, hooks, state |
| Backend | root/backend/* | API endpoints, services, business logic |
| Data Flow | root/dataflow | Schemas, types, API contracts |
| Entry Points | root/entrypoints | Routes, pages, middleware |
| Dependencies | root/dependencies | Packages, versions, usage |
Package categories
| Category | Schema Key | Description |
|---|---|---|
| CLI | root/cli | CLI package findings |
| MCP | root/mcp | MCP server package findings |
| VS Code | root/vscode | VS Code extension package findings |
Activity categories
| Category | Schema Key | Description |
|---|---|---|
| Journal | root/journal | Implementation journal entries |
| Bugs | root/bugs | Bug fixes, workarounds |
| Todo | root/todo | Pending tasks, known issues |
| Code Map | root/codemap | Codebase structure from scan |
Security vs Risks
The Findings Explorer distinguishes between Security and Risks:
- Security — Genuine vulnerabilities detected during Genesis Scan's security audit layer (items tagged
security). These are OWASP-category issues like injection, authentication flaws, and XSS. - Risks — All other items under the
root/securityschema key that are not tagged as vulnerabilities. These include technical debt, configuration concerns, and improvement suggestions.
This split ensures the Security tab only shows actionable vulnerabilities, while Risks captures the broader analysis. For a dedicated security workflow, use the Security Center.
Finding cards
Each finding card displays:
- Title and expandable details
- Source badge — Scan (blue), Session (green), or Manual (gray)
- Freshness indicator — Relative time since the item was last updated (e.g., "2 days ago", "3 weeks ago")
- Confidence score — AI confidence as a percentage
- Importance — Star rating (1–5)
- Tags — Category labels and custom tags
Click a card to expand it and see:
- Full description with all facts
- Rationale — Why this finding matters
- Impact — What areas of the codebase are affected
- Related files — Source file paths (linked to GitHub when a repository is connected)
Loading behavior
Findings load progressively in pages of 50 items. A progress bar shows loading status when there are more items than the initial page. All filtering and searching work on the fully loaded dataset.
Prerequisites
The Findings Explorer requires memory items in your project. Populate them by:
- Running a Genesis Scan to analyze your codebase
- Capturing coding sessions via the VS Code extension or CLI
- Saving context via the MCP server
Without any items, the page shows an empty state prompting you to run a scan.
Next steps
- Genesis Scan — Run or re-run a codebase analysis
- Security Center — Focused view of security vulnerabilities and risks
- Brain Explorer — Interactive knowledge graph and category browser
- Schema Keys — How knowledge is organized in the taxonomy