diff --git a/docs/specs/2026-09-27-m5c-honcho.md b/docs/specs/2026-09-27-m5c-honcho.md
index d546ea6..5a4815c 100644
--- a/docs/specs/2026-09-27-m5c-honcho.md
+++ b/docs/specs/2026-09-27-m5c-honcho.md
@@ -199,7 +199,10 @@ The agent's own workspaces are not searched: the local index holds every turn an
 agent with exact labels, and would return the same text twice. Each source runs on its own thread
 with its own limit (the local index as today; 5 s for each Honcho source); `recall` answers with
 what arrived, and a source that did not answer is one line, `<source>: unavailable`. Hits are
-ranked within their source and interleaved to `k`, the local index first. Text from Honcho is
+ranked within their source and interleaved to `k`, the local index first. Honcho's search has no
+relevance cutoff (a query with no match still returns the nearest messages, recorded 2026-09-28),
+so a Honcho hit is kept only when it shares a search term with the query, as the local index's
+full-text match requires. Text from Honcho is
 neutralised on arrival and size-capped like every recall snippet. Any `memory-tainted` hit marks
 the session untrusted, and every hit raises the session's class to its label, as local hits do.
 
@@ -220,12 +223,14 @@ telemetry, a `secret` session's queries must stop going to Honcho without the ow
 
 ## 9. `ask_memory`
 
-A new core tool, `ask_memory { question, workspaces?, reasoning? }`:
+A new core tool, `ask_memory { question, workspaces? }`:
 
 - `workspaces`: at most two names from `[honcho]`: `own` (default), `untrusted`, `fleet`, or
   another agent's name from `[[honcho.read]]` (owner, 2026-09-28: two, so that both chats run at
   once inside `brokerd`'s wait; the model asks again for more);
-- `reasoning`: `minimal` (default: one search, then the answer) or `low`;
+- Honcho's reasoning level is always `minimal` (one search, then the answer). A `low` chat,
+  recorded from rift on 2026-09-28, returned the dialectic model's raw tool-call markup as its
+  answer; the choice comes back when rift answers it;
 - `question`: at most 2,000 characters.
 
 One workspace chat (`POST /workspaces/{w}/chat`) per named workspace, both at once; workspace chat searches every conclusion and message of the workspace without the model