Skip to main content

Documentation 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.

A.D.A.M. does not route by reading intent or detecting high-stakes topics. It routes by reading message shape. The structural kernel — defined in section S of the protocol — computes a set of boolean flags from each user message and maps those flags to routing and audit decisions.
Write naturally. Structural detection operates on message shape, not phrasing. A simple sentence stays LOW. A message with multiple option blocks, numbers, and criteria items will trigger DEEP candidacy automatically.

​
The structural kernel

The structural kernel is the single source of truth for AUDIT_ON, DEEP_CANDIDATE, MINI_TABLE_TRIGGER, and RETROGRADE_HARD. It is computed fresh from the current user message on every turn. Structural booleans do not persist across turns, except where a mapping explicitly depends on prior state (such as prev_commit in NEW_CONSTRAINTS_AFTER_COMMIT).
Commas, slashes, and backslashes are not structural triggers. High-stakes semantics alone do not trigger DEEP. Use the manual override DEEP if you need full decision support on a message that lacks structural signals.

​
Primitives

Structural detection operates on a small set of line-level primitives:
PrimitiveDefinition
Line-startFirst non-whitespace character of a line
Criteria itemLine-start - or *, excluding option blocks and step blocks
Option blockLine-start A) / B) / … or 1) / 2) / …
Step blockLine-start 1. / 2. / 3. / …
The distinction between option blocks (1)) and step blocks (1.) matters: they map to different structural booleans.

​
Structural booleans

Each boolean is computed independently from the current message surface. None are inferred from tone, topic, or prior turns (except NEW_CONSTRAINTS_AFTER_COMMIT).
BooleanTrue when
HAS_NUM2+ digits, a digit range, a comparator with any digit, or a percent with any digit. Dates count.
HAS_INLINE_3PLUS_ALTS_PARENSAt least 3 inline parenthetical alternatives: >=3 (, >=3 ), and >=2 ), in the message.
HAS_2PLUS_OPTIONSAt least 2 line-start option blocks.
HAS_3PLUS_OPTIONSAt least 3 line-start option blocks.
HAS_STEPS_OR_TIMELINEAt least 3 line-start step blocks, or at least 2 date/time patterns (YYYY-MM-DD or HH:MM).
HAS_3PLUS_CRITERIAAt least 3 criteria items, or at least 2 semicolons in one message.
STRUCTURED_LIST_MARKERSAny criteria item, option block, or step block present.
NEW_CONSTRAINTS_AFTER_COMMITprev_commit is true AND the current message contains HAS_NUM, HAS_3PLUS_CRITERIA, or STRUCTURED_LIST_MARKERS.
prev_commit is true when the immediately previous assistant reply contained an explicit COMMIT — a concrete recommendation or actionable conclusion. If the previous reply is unavailable or ambiguous, prev_commit is not inferred as true.

​
Kernel mappings

The booleans feed four derived signals that control routing, audit, and gating: 
MINI_TABLE_TRIGGER  = HAS_3PLUS_OPTIONS
                      OR (HAS_2PLUS_OPTIONS AND (HAS_NUM OR HAS_3PLUS_CRITERIA))

RETROGRADE_HARD     = NEW_CONSTRAINTS_AFTER_COMMIT

DEEP_CANDIDATE      = (HAS_2PLUS_OPTIONS OR HAS_STEPS_OR_TIMELINE
                        OR HAS_INLINE_3PLUS_ALTS_PARENS)
                      AND (HAS_NUM OR HAS_3PLUS_CRITERIA OR RETROGRADE_HARD)

AUDIT_ON            = (MODE==DEEP)
                      OR DEEP_CANDIDATE
                      OR RETROGRADE_HARD
                      OR (STATE in {DECIDE, VERIFY}
                          AND (HAS_2PLUS_OPTIONS OR HAS_STEPS_OR_TIMELINE
                               OR HAS_NUM OR HAS_3PLUS_CRITERIA))
SignalEffect
MINI_TABLE_TRIGGERMID reply includes a compact comparison mini-table and a “when to use what” conclusion
RETROGRADE_HARDForces the overlay state back to EXPLORE; prior COMMIT is explicitly invalidated
DEEP_CANDIDATETriggers the DEEP gating flow: MODE: MID -> POSSIBLE DEEP + Switch to DEEP? (yes/no)
AUDIT_ONAppends the exact 4-line AUDIT footer to the reply

​
Normative examples

These examples are normative — they define correct structural interpretation:
InputBooleanResult
v10HAS_NUMtrue
v2HAS_NUMfalse
1-2HAS_NUMtrue
>=5HAS_NUMtrue
5%HAS_NUMtrue
A (10), B (20), C (30)HAS_INLINE_3PLUS_ALTS_PARENStrue
A (10), B (20)HAS_INLINE_3PLUS_ALTS_PARENSfalse
Line-start A) + line-start B)HAS_2PLUS_OPTIONStrue
Bullets onlyHAS_2PLUS_OPTIONSfalse
Line-start 1) + 2) + 3)HAS_3PLUS_OPTIONStrue
Line-start 1) + 2) onlyHAS_3PLUS_OPTIONSfalse
Line-start 1. + 2. + 3.HAS_STEPS_OR_TIMELINEtrue
Line-start 1. + 2. onlyHAS_STEPS_OR_TIMELINEfalse
2026-03-05 aloneHAS_STEPS_OR_TIMELINEfalse
2026-03-05 14:30 plus another date/timeHAS_STEPS_OR_TIMELINEtrue
3 criteria bulletsHAS_3PLUS_CRITERIAtrue
2 criteria bulletsHAS_3PLUS_CRITERIAfalse
A; B; CHAS_3PLUS_CRITERIAtrue
A; BHAS_3PLUS_CRITERIAfalse
prev_commit=true plus new list markerNEW_CONSTRAINTS_AFTER_COMMITtrue
prev_commit=false plus same markerNEW_CONSTRAINTS_AFTER_COMMITfalse
Criteria-only message, no options, no stepsDEEP_CANDIDATEfalse
2 option blocks + 3 criteria + a numberDEEP_CANDIDATEtrue

​
AUTO routing

When no manual override is present, A.D.A.M. selects a routing path automatically:
1

AUTO_LIGHT → MODE: LOW

Selected when the turn is a factoid, brief definition, trivial calculation, micro-procedure, explicit brevity request, or banter with no analysis demand.
2

AUTO_STANDARD → MODE: MID

Selected for explanation requests, moderate evaluations or comparisons, and requests for rigor, pros/cons, confidence, or sources — provided DEEP_CANDIDATE is not true.
3

DEEP gating flow → MODE: MID → POSSIBLE DEEP

Selected when DEEP_CANDIDATE is true. A.D.A.M. delivers a complete MID-level answer and appends the exact final line Switch to DEEP? (yes/no). Entering DEEP requires an exact yes reply.
Manual override (LOW, MID, or DEEP as the first token followed by whitespace) wins over all automatic routing. See Modes for override syntax and the boundary strictness rule.

​
RETROGRADE_HARD and commit invalidation

RETROGRADE_HARD fires when a previous assistant reply contained an explicit COMMIT and the current message adds new structural constraints. When this happens:
  • The overlay state resets to EXPLORE
  • The prior COMMIT is explicitly invalidated — A.D.A.M. must state what changed and why the prior conclusion no longer holds
  • Silent revision or silent preservation of the old COMMIT is not permitted
A micro-edit exception applies: if the follow-up is purely textual and contains none of HAS_NUM, list markers, step markers, or 2+ semicolons, the COMMIT remains stable and RETROGRADE_HARD does not fire.
MessageClassification
for clarity, I mean the second pointMicro-edit — COMMIT stable
by fast I mean responsive, not powerfulMicro-edit — COMMIT stable
I meant 150 euroNot micro-edit — HAS_NUM present
consider option CNot micro-edit — option block present
it must stay under 200 euroNot micro-edit — HAS_NUM present
also add speed and priceNot micro-edit — list marker present

Build docs developers (and LLMs) love

Get started for freeTalk to us