find_related_claims
Association search over published claims: what else does the graph already know that bears on THIS claim. Searched by the claim's OWN stored vector, so it is like-for-like and costs no embedding call — this is the by-EXAMPLE sibling of methodist_search_semantic, which searches by free TEXT. Use it before creating a claim (is this already established?), when building on prior work, and at cycle closeouts where the methodology already requires citing rather than re-minting. FIELDS: score_gemini / score_qwen are per-space scores, and when a space is queried EVERY hit gets its score (a hit missing from that space's own top-K is scored directly, so a blank is never a hidden low score). similarity_agreement="both_spaces" means two INDEPENDENT vector spaces agree the two claims are SIMILAR; "single_space" means both were queried and only one cleared the floor — a real disagreement; ★ "not_measured" means only one space was queried (the default), so agreement was NEVER TESTED — read it as the absence of a question, never as a negative answer. Pass vector="both" to actually test agreement. None of this says whether the found claim is TRUE; its verification status is the separate verification_outcome field. ownership="own" | "foreign" | "unknown": self-corroboration is weaker evidence, and "unknown" (provenance not establishable) counts as NEITHER — it earns no independence credit and no right to supersede, and you must record in your journal that the origin could not be established. SAME_AS: when a cluster is collapsed the returned representative is the BEST-MATCHING member, NOT the §7.6 identity-canonical (which is the earliest and is returned alongside as same_as_canonical_id). LINKING: cite/link link_target_id, not the hit id — it is the canonical mapped to its current version. When link_target_followed_chain is true the target was superseded-forward and its CONTENT may differ from the hit that matched. If link_target_ambiguous is true, TWO OR MORE records supersede the same one — there is no single current version; read link_target_candidates and choose deliberately rather than citing either as the answer. you matched: read it before linking. Read-only: never merges, never proposes a merge, never writes.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| run_id | No | Optional. The active methodist run_id (as returned by the methodist diagnose / get_current_dose door). Pass it whenever you call this tool while working inside a run, so the call is attributed to that run for the §8 usage crosscheck — attribution is run-anchored, so it stays correct even if your access token refreshes mid-run. Must be YOUR run: a run_id owned by a different principal, or a non-existent run_id, is rejected. | |
| vector | No | search space — default gemini (primary); qwen = the alt space; both = fused (NOT the default) | |
| claim_id | Yes | ||
| min_score | No | raise the similarity floor above the codified 0.62; it can only be raised, never lowered | |
| latest_only | No | exclude superseded claims (DEFAULT OFF since A0-3b, aligned with methodist_find / _search / _search_semantic). Every returned claim carries is_superseded, so filtering here is optional: you can always drop stamped records, but you cannot recover records a door hid from you. | |
| exclude_same_as | No | drop members of the ANCHOR's own same_as cluster — they are the same claim (default TRUE). The response reports how many were dropped in excluded.same_as_members. | |
| collapse_same_as | No | represent each same_as cluster once, by its best match (default TRUE) |