plastic-intent-linking

# Linking Intents ## When to Use - During intent creation (automatic: ask about related intents) - User says "link", "connect", "relates to" - Agent discovers a relationship between intents during work ## Discovery and ranking are separate Two distinct steps, do not conflate them: 1. **Discovery** (finding candidate related intents) may use any tool: grep, find, ripgrep, or QMD/Serena when present (QMD-first per the project rule). Discovery casts a wide net. 2. **Ranking** the candidates is a CONTEXT-INFLUENCE judgement: read each candidate's `## Intent` and `## Context` and ask whether that context actually informed this intent. Ranking is NOT a structural metric (no shared-file or shared-symbol grading: on intent 90, matching whole files flagged 35 intents because ~20 touch `bridge.rb`). It is NOT a similarity score either (QMD relevance measures topic proximity, not influence). A script cannot make this call; an agent does. ## The three tiers (by context influence) - **sources:** the foundational context that shaped this intent's CREATION (a split, an idea born during development, a merge). Earns an edge. Decided by origin, never inferred. - **chain:** the context that materially helps DELIVER this intent. HIGH bar: only the genuinely delivery-moving intents, not everything in the same area. Earns an edge, reflected in `## Links`. Worked example (intent 90): 79 created it so 79 is a source; 80 deferred the exact fix 90 makes, so its context ...