a-new-capture-or-draft-is-matched-against-the-record-before

Summary

The design record for itd-2609212137116617: lexical matching at filing, a typed link, never a refusal.

Scope

1. The matcher (internal/core/record/match.go): tokenises the new text and each candidate's title, press release or body, scores overlap, returns candidates above and below the threshold (criteria 1, 2, 4).
2. The writers: capture and intent create call it before the write and add the link field; the print (criteria 1, 2, 3).
3. Configuration: match.threshold, match.fields through the layered resolver (criterion 4).
4. The discipline record itd-84 edited to mark the rung (criterion 5).

Out of scope

• Refusal; cross-repository; semantic matching.

Approach

The overlap function is the one the embark ranking uses, moved to the record package as the canonical primitive; both callers run it under their existing locks.

Footprint

• packages: internal/core/record, internal/core/capture, internal/core/intent
• tests: the scorer on fixtures; both writers with a planted double; the below-threshold json; the discipline edit

How the criteria are satisfied

Amendment (2026-09-26)

The Scope, Approach and Footprint above name a delivery that did not happen (iss-2609261631134401). No embark ranking held an overlap function to move: the embark ranking is scope 7 of the open reflect spec, spc-2609211751376504, and is not yet built. The primitive shipped new, as the package internal/core/record/match rather than a file in internal/core/record, because internal/core/record imports the capture and intent packages that call the matcher, and a matcher there would close an import cycle. The capture and intent writers import it directly, and the reflect spec's Approach names it as the primitive its embark ranking is to use.