# Discovery Reconstruction

Use this note when changing Workflows, Search, Runbook Index, Role Paths, Site Map, Start Here, page guidance, or navigation. The goal is to keep the large content library easy to roam without deleting useful material.

## Navigation Model

- Workflows is the lane-first hub.
- Search is the term-first hub.
- Runbook Index is the situation-first hub.
- Role Paths is the role-first hub.
- Site Map is the full-inventory hub.
- Start Here is the beginner and returning-user orientation.
- Visual Route Map is the output-first visual lobby.
- Games And Quizzes is the practice lobby.
- Tool Chains is the multi-tool workflow lobby.
- Report Gallery and Report Builder Path are the reporting/output lobbies.

Workflows and Site Map now include route chooser sections before their larger
inventories. The chooser pattern answers what the user knows first: term,
situation, role, output, practice goal, trust question, or full inventory. Keep
that pattern in these hubs instead of adding more dropdown links.

## First-Screen Switchboard

These pages must expose first-screen hero actions so users can switch modes without scrolling:

- `pages/search.html`: Workflows, Search Workflow Examples, Runbook Index, Role Paths.
- `pages/runbook-index.html`: Workflows, Search, Role Paths, Site Map.
- `pages/role-paths.html`: Workflows, Runbook Index, Search, Site Map.
- `pages/site-map.html`: Workflows, Search, Runbook Index, Role Paths.

`scripts/check-site.ps1` enforces these hero links. `scripts/audit-content-quality.ps1` reports the same state as a planning aid.

## Top Navigation Rule

Top navigation uses a seven-door model:

- Home
- Workflows
- Intel
- Tools
- Learn
- Games
- Status

Top dropdowns are curated, grouped entry points, not full inventories. Keep them short enough to scan without scrolling:

- Home should expose only first-use routes.
- Workflows should group links by choosing a route, doing the work, and following up.
- Intel should group links by today's signal and pressure views.
- Tools should group links by workbench and output surfaces, not every individual utility.
- Tools should expose Tool Chains before deep individual utilities when the user needs a workflow rather than a single parser.
- Learn owns the Learn Hub, Training drills, Research references, scenario practice, and playbooks.
- Learn should point toward Games And Quizzes as the friendly Training lobby rather than filling the dropdown with every drill.
- Games owns the app-facing practice loop: Games Hub, App Home Preview, Training Coach, Practice Packs, Daily Challenge, Progress, Training Report, Scenario Library, and Arcade.
- Learn can expose a few high-value Research references such as Product Lab, Evidence Library, Priority Model, Affected Range Examples, and Exploit Maturity Explainer, but the dropdown should stay curated rather than becoming the full Research inventory.
- Status owns health, trust, privacy, and limitations.
- The full catalog belongs in Workflows, Search, Runbook Index, Role Paths, Site Map, Tools Hub, and page guidance.
- Do not duplicate the same deep guide across several dropdowns just because it is useful in several contexts.

If a user needs everything about an area, send them to Site Map, Search, or the area hub instead of extending a dropdown.

Grouped dropdown headings should explain intent in two words or fewer, such as First Click, Choose Route, Do Work, Follow Up, Today, Pressure, Workbench, Output, Practice, Build And Report, Health, and Public Trust.

## Shared Taxonomy

Keep workflow lane definitions in `js/workflow-taxonomy.js`. Do not create another lane map in Search, Site Map, Role Paths, Runbook Index, page guide, page-family guidance, or documentation.

Current lanes:

- Intake
- Validate
- Decide
- Act
- Communicate
- Govern
- Practice
- Reference

## Content Rules

- Prefer linking into Workflows before adding another Core routing page.
- Prefer Training for drills, quizzes, and practice.
- Prefer lobby pages such as Visual Route Map, Games And Quizzes, Tool Chains, Report Gallery, and Report Builder Path when a content area grows too broad for dropdown navigation.
- Prefer Research for source comparison, proof quality, methodology, and slower interpretation.
- Prefer Tools for input/output helpers.
- Prefer Status for health, trust, privacy, limitations, diagnostics, and release readiness.
- Keep Search default discovery guided; do not show the full route index before a term or filter is chosen.
- Keep Search result badges aligned to the content governance categories: Tool, Workflow, Training, Intel, Threat, Research, and Trust.
- Keep broad Search suggestions pointed at workflow routes that produce a next action, not just more inventory.
- Keep Role Paths job-based; lane hints should support the role path, not replace it.
- Keep chooser cards short and intent-based. They should route to hubs and
  lobbies, not duplicate the full catalog.

## Review Routine

Before staging a broad discovery or IA batch:

- Run `scripts/audit-content-quality.ps1`.
- Run `scripts/production-build.ps1 -BaseUrl https://main-9et.pages.dev`.
- Run `scripts/final-review.ps1 -BaseUrl https://main-9et.pages.dev`.
- Manually open Workflows, Search, Runbook Index, Role Paths, Site Map, Start Here, Visual Route Map, Games And Quizzes, Tool Chains, Report Builder Path, Quality Center, and What's New on desktop and mobile.