Use exact provenance links, not keyword hits, in workflow audits

Keyword searches over work-item text can badly overcount provenance because integration names often appear in CI summaries, containment checks, documentation, or release notes. For request-to-delivery audits, classify origin only from exact source URLs, structured relationships, or explicit source identifiers in the full record. Treat the resulting count as a lower bound because links may exist only in comments or the source system. This preserves precision while making missing provenance visible instead of filling gaps with lexical guesses.

Applies when: measuring how meetings, support conversations, or customer requests become engineering work. Keywords: workflow audit provenance exact links source correlation traceability