DEEP mode in A.D.A.M. is consent-gated. When the structural kernel detects aDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/xxyoudeadpunkxx/a.d.a.m.-adaptive-depth-and-mode/llms.txt
Use this file to discover all available pages before exploring further.
DEEP_CANDIDATE — a message with complex multi-option structure combined with numeric constraints or multiple criteria — the protocol proposes DEEP and waits for an explicit yes before running the full decision-support analysis. You are never dropped into DEEP without agreeing to it first.
How DEEP Gating Works
User sends a structurally complex message
You send a message that the structural kernel evaluates as a
DEEP_CANDIDATE. This means the message has at least two option blocks (or step blocks, or three inline parenthetical alternatives) and at least one of: numeric content (HAS_NUM), three or more criteria items (HAS_3PLUS_CRITERIA), or a hard retrograde condition.Structure beats wording. High-stakes language alone does not trigger DEEP_CANDIDATE. The kernel reads message shape — option blocks, step markers, criteria bullets, numbers — not meaning.Protocol emits a POSSIBLE DEEP reply
The protocol opens with Nothing appears after
MODE: MID -> POSSIBLE DEEP on the first line, followed immediately by the automatic structural classification overlay (if any structural chip threshold is met), then a useful MID-level answer, and ends with exactly the gating question as the final line:Switch to DEEP? (yes/no). If AUDIT_ON is true, the AUDIT block is placed immediately before the gating line.You reply yes, no, or anything else
Reply Reply
yes (exactly): The protocol enters DEEP mode. The next reply opens with MODE: DEEP, includes the full decision-support analysis, and always has an AUDIT footer. The reply language follows the language of the preceding POSSIBLE DEEP reply — sending exactly yes alone does not reset the reply language. Example:no (exactly): Gating is discarded. The protocol continues normally on the next turn.Reply anything else: Treated as no. Gating is discarded. The protocol continues in AUTO routing. The gating question is not automatically repeated.One-Turn Validity
Pending gating is valid only for the immediately following user turn. If you reply to a gating question with any other content first — even a simple question or comment — the gating reference is consumed or discarded, and a strayyes in a later turn does not trigger DEEP. Only an exact yes on the very next turn after a POSSIBLE DEEP reply enters DEEP mode.
The Automatic Structural Overlay
When the protocol emitsMODE: MID -> POSSIBLE DEEP or MODE: DEEP, a structural classification overlay may appear as the second line of the reply, immediately after the mode tag. This overlay is a presentation-only mirror of the structural kernel’s reading of your message shape — it classifies structure, it does not extract or paraphrase your content.
The overlay takes the form of structural chips mapped directly from the struct primitives:
| Chip | Threshold | Meaning |
|---|---|---|
[confronto tra opzioni] | opt >= 2 | Two or more line-start option blocks detected |
[vincoli da rispettare] | crit >= 3 | Three or more criteria items (or two semicolons) |
[numeri, date o limiti] | num = Y | Numeric content, date patterns, or comparators detected |
[passi o ordine] | step >= 3 | Three or more line-start step blocks detected |
Example Exchange
User message (structurally complex — 3 option blocks, 3 criteria bullets, a numeric constraint):POSSIBLE DEEP):
yes
Protocol reply (DEEP):
Manual DEEP Override
If you already know you want DEEP — or if your request is semantically complex but structurally simple — prefix your message withDEEP:
DEEP_CANDIDATE because the message lacks options, steps, or criteria in its shape, even though the content is genuinely complex.
See the Manual Override guide for full override syntax and boundary rules.
Anti-loop rule: If you reply to a
Switch to DEEP? (yes/no) gating question with anything other than exactly yes or exactly no, the protocol treats it as no, discards the pending gating, and continues in AUTO routing. The gating question is not automatically repeated. A new POSSIBLE DEEP will only appear if a new DEEP_CANDIDATE message triggers it, or you manually use the DEEP override.