recall_iterative
Performs multi-hop memory recall: retrieves round-one results and outputs an ask prompt plus prior_ids so a follow-up call can retrieve the answer through a bridging entity.
Instructions
MULTI-HOP recall, PHASE 1 of 2 — use this instead of recall when the answer needs a fact that is
reachable only THROUGH another one ("who manages the person who signed off on X", "what did the vendor we
switched to in March charge us"). One-shot top-k systematically misses that second hop: the record holding
it is similar to the BRIDGE entity, not to your question, so no amount of ranking brings it back.
HOW THIS WORKS, AND WHY YOU ARE IN THE LOOP. The fix is to read round-1, name what is missing, and search
again — which needs a model. inspeximus does not have one and will not grow one: no LLM on the write path
and none inside the read path either. You ARE the model. So this returns round-1 hits plus ask (the
instruction) and prior_ids (the continuation token), you decide what the bridge is, and you hand it back
to recall_followup. Your model stays yours; the retrieval, dedup and merge stay deterministic and ours.
Returns {k, max_followups, round, hits, prior_ids, ask, next_call, bounds} — your query is not echoed
back (you sent it, and a memory server should not reflect caller text into a model's context). If hits
already answer the question, stop here — the second call is optional and costs a retrieval.
BOUND: exactly ONE recall() and at most k records back (k hard-capped at INSPEXIMUS_MAX_K). The
response size is a function of k alone and does NOT grow with the store — unlike this server's
contradictions surface, whose all-pairs output reached ~150 MB at n=2,000.
Honours the active project scope, like recall; all_projects=True searches every project. A multi-hop
walk must not be a side door out of the scope its first hop respected.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| k | No | ||
| full | No | ||
| query | Yes | ||
| user_id | No | ||
| agent_id | No | ||
| session_id | No | ||
| all_projects | No | ||
| trusted_only | No | ||
| max_followups | No | ||
| snippet_chars | No |