memai-linklisted

# memai-link — stitching the memory graph Creates the edges that make the store navigable. It **only relates**: when a pair is the **same thing**, that is a merge and goes to [[memai-distill]]. ## 1. Relation vocabulary (keep it consistent) | `relation_type` | When it applies | |---|---| | `supersedes` | A replaces or retires B — a new version → the old one, a kept checkpoint → the archived one. Lineage. | | `relates_to` | Complementary, the same subject, or the same phenomenon from another angle. The default. | | `contradicts` | A and B claim incompatible things — pair it with the `contradicted` confidence of [[memai-confidence]]. | | `links_to` | A generic pointer when none of the above fits. | > `link_memories` takes `relation_type` as **free text** — nothing rejects a > fifth spelling. Write one of those four. ## 2. What is worth linking - **Materialize `[[wikilinks]]`.** A body that cites `[[slug]]` and has no edge in the graph gets a `relates_to`: a note on the queue drain whose text points at `[[cache-warmup-cold-start]]` reads as a link and is not one until the edge exists. - **Complementary memories under one domain.** Two notes filed in `acme/x100`, one on the batch retry and one on the queue drain it re-enqueues into, that nobody ever connected. - **checkpoint → note lineage.** A kept checkpoint → the canonical note for the mechanism (`relates_to`); an **archived** checkpoint from a finished `proj-1042` → the note that inherited its durable cont