Global Search · Prototype v0.1

Omnisearch across Projects, Contracts, Suppliers & Documents

This prototype extends the AA-8022 contract search foundation into a unified global search experience. Two result-grouping models are testable side by side: Container view (projects as parents with nested children) and Peer view (entity-grouped sections). Results use the scripted "CalFresh" scenario so the demo flow is consistent.

Context 1

Dashboard

Default global search. No project context, so results span all entities. Shows live dropdown with view-mode toggle.

Open demo → Context 2

Inside a Project

Scoped search demo. Search is biased to the current project with a "Search everywhere" escape hatch. Tagged as future phase.

Open demo → Full results

Results Page

Enter-to-search destination. Filter rail modeled on the existing Authorium tag filter. Entity tabs, snippets, and match highlighting.

Open demo →

What's implemented

Omnibox in the top nav with ⌘K shortcut
350 ms debounce matching the AA-8022 pattern
Top 3 results per entity type in the dropdown
Yellow highlight on title matches
"Matched in [field]" snippet hints for non-title matches
Container/Peer view toggle — persists via localStorage
Project-scoped search (when inside a project) with escape hatch
Enter-to-full-results page with entity tabs and filter rail
Collapsible breadcrumb that converts to magnifying-glass icon
"Did you mean?" suggestions on empty state

Try these searches

CalFresh — matches projects, contracts, and documents
MOU-24 — prefix match on contract family
Gartner — supplier match surfaces related contracts
22-4037 — exact contract ID lookup

Open questions for stakeholders

Does Container view reduce cognitive load vs Peer view, or add it?
Is "surfaced because items inside match" a clear enough label?
Should scope be sticky across pages or reset on each query?
Are the "matched in" snippets specific enough to build trust?