Description
Exact-ID Search recognizes a complete Dots human ID such as a row handle and resolves it directly to an authorized search result. The resolved item appears at rank zero ahead of ordinary relevance results, even when the hybrid pipeline misses it or the rest of the response comes from L2 cache. Recognition and lookup use the authoritative Dotabases seam rather than a second prefix grammar inside search.
The feature preserves privacy and pagination semantics around that shortcut. Lookup is scoped by company and readable Dotabases, failures return no pin, an active Playbook row wall disables pinning, and a Dotabase filter admits only an owner that is explicitly in scope. The pin is resolved per request and never stored in L2, preventing one actor's readable exact match from entering another actor's cached response.
Selling Points
- Known IDs become a dependable navigation path instead of competing with fuzzy relevance scoring.
- Search shares the platform's authoritative ID recognizer, avoiding drift as prefixes and normalization rules evolve.
- Authorization failure produces no result rather than revealing that a protected row exists.
- Rank-zero insertion works on both fresh pipeline responses and safe shared-cache hits.
- Cursor re-keying keeps displaced results reachable, so the convenience shortcut does not silently skip content.
User Story
A support lead receives a Task identifier in a message and pastes it into Universal Search. The matching readable row appears first immediately, while related full-text and semantic hits remain below it. If the user cannot read the Task, the search behaves like an ordinary query and discloses nothing about the hidden row.
Extension Surface
Extensible is the first true rung. packages/search/src/internal/contracts/exact-id-match.ts defines ExactIdMatchLike, and SearchServiceConfig in packages/search/src/internal/service.ts accepts the composition-supplied recognizer and resolver. A different authoritative row system can implement that structural seam in-repo, but there is no external registration marketplace for exact-match resolvers.
Capabilities & Limits
- Recognizes authoritative human IDs and maps readable rows into the common search-hit shape.
- Prepends one deduplicated rank-zero result while respecting the requested page size.
- Re-keys continuation state from the final pipeline item actually shown.
- Limits: only a full ID accepted by the injected recognizer qualifies; partial handles remain ordinary search text.
- Limits: pinning is disabled when a Playbook
rowIdsscope is present and is constrained by non-empty Dotabase filters.
Implementation Map
packages/search/src/internal/contracts/exact-id-match.tspackages/search/src/internal/exact-pin.tspackages/search/src/internal/service.tsapps/web/src/composition/runtime.tspackages/search/src/internal/stages/analyze.ts