Flag a join on the map as wrong, or propose one the map missed — how you report what you and your human found while testing the map. It changes nothing on the map: it opens a join review that a person in the workspace decides, and a join_review signal whose task context says exactly what to count in your human's own systems to settle it. Name the two objects as the map spells them and give a reason: wrong_key (these objects do not join on this key), wrong_direction (the direction or count is wrong; give cardinality, read from → to: 1:1, 1:N, N:1 or N:M), not_related, works_like_this (say how it works in note), or missed (a join the map does not have: give key, the file and column on each side as get_object lists them, or describe it in note). For a join already on the map pass its key exactly as route or get_object gave it. Maplith answers with its own evidence first: when what it measured contradicts the claim (for example, 99% of rows match a key called wrong), nothing is opened and the answer is outcome contradicted with the evidence — show it to your human, and call again with confirm: true only if they still say it is wrong. Other outcomes: opened (with review_id), exists (an undecided review of that key already exists), on_map (the map already has that join; flag it with another reason if it is wrong). Never put values from the data in note.