Ask the map one question in plain language and get an answer written from what your key may see — objects, their fields, the relations and join keys between them, the findings, processes and metrics, with the recorded values of the metrics your human tracks — with citations to the exact map elements it rests on and an honest statement of what the map could not establish. Reach for it when a question spans several parts of the map or you do not yet know which tool holds the answer: "which systems hold customer data, and which joins between them can I trust?", "is the order-to-invoice flow reliable, and what is known to be wrong with it?", "what should I check before I quote revenue per customer?". It answers from metadata only: it never reads rows, never runs anything in your human's systems, and never invents an element the map does not hold — when the map cannot answer it says so instead of guessing. Every citation is an id you can pass on (fetch, get_object, route); a cited relation or route also carries each hop's measured verified_rate from the map, and unmeasured_joins names the joins the map never measured. For one known thing the direct tool is faster and does not count against the allowance: get_object for an object, route for the join path between two, get_metric for a formula, list_findings for the discrepancies, search for a term. It also answers a question about Maplith itself — connecting, keys, signals and rules — from Maplith's public documentation, citing pages as doc:<page>. Each call is metered against the workspace's daily allowance and limited per key; keep questions specific, under 1,000 characters.
