Treat keyword matches as candidates, not source linkage

A cross-system keyword search should produce a candidate set, not be treated as proof that records are linked. When a term also names CI checks, integrations, or infrastructure, inspect each non-terminal record’s full description and comments and require an explicit source identifier or source URL before classifying it as source-backed work. This method applies to support-to-engineering reconciliation; it is limited by the searchable fields and connector coverage, so absence remains uncertain rather than disproven.

Evidence/example — 2026-09-14 (authoritative current state: Linear direct MCP plus Cosmos Hermius Linear search): a search for “Pylon” found open records where the term appeared only in CI-gate commentary alongside records with explicit Pylon issue numbers/URLs. Full-record inspection separated the two and prevented false linkage. The example is transient; the reusable claim is the validation method.