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. operates a two-layer state model. The outer layer — transport/activity state — controls whether the protocol is active and what commands are available. The inner layer — reasoning overlay state — is an internal governor for long-session routing stability. Neither layer is stored by the protocol itself; both are recalculated from visible context on each turn.
Reasoning overlay state is ephemeral — it is recalculated from visible history each turn, not stored by the protocol. This means it cannot carry over after context loss.

​
Transport / activity states

StateDescription
TRANSPORTThe protocol file is present in context but not yet activated. Only exact ADAM PING and exact remount replay are available. All other non-empty turns return the fixed 2-line transport response.
ACTIVEThe protocol is active. Normal routing, manual overrides, commands, and probes are all available.
OFFThe protocol is temporarily off. Only ADAM ON can return to ACTIVE. Normal chat continues without A.D.A.M. mode tags.
Transport/activity state is inferred only from visible exact events — ADAM PING, ADAM OFF, ADAM ON, and exact remount replay. It is never presumed from apparent conversation continuity. If visible context does not establish ACTIVE or OFF, state defaults to TRANSPORT.

​
State transitions

1

Activation: TRANSPORT → ACTIVE

Send exactly ADAM PING while in TRANSPORT. A.D.A.M. runs the protocol operability check and G0 physical classification, then replies with the strict 4-line bootstrap output and enters ACTIVE.
2

Liveness check: ACTIVE → ACTIVE

Send exactly ADAM PING while already ACTIVE. A.D.A.M. confirms liveness with a strict 2-line reply. This does not re-run G0, does not clear pending gating, and does not alter overlay state.
3

Deactivation: ACTIVE → OFF

Send exactly ADAM OFF. A.D.A.M. replies with the strict 2-line off response. Normal chat continues without A.D.A.M. tags.
4

Reactivation: OFF → ACTIVE

Send exactly ADAM ON. A.D.A.M. replies with the strict 2-line on response and returns to ACTIVE.
5

Recovery: any state → ACTIVE

Paste the exact remount capsule body (delimited by REMOUNT_BEGIN and REMOUNT_END). A.D.A.M. confirms with ADAM_REMOUNT_OK and enters ACTIVE from any prior state.

​
Transition table

FromEventToNotes
TRANSPORTexact ADAM PINGACTIVERuns G0 bootstrap
ACTIVEexact ADAM PINGACTIVELiveness only; no reset
ACTIVEexact ADAM OFFOFF
OFFexact ADAM ONACTIVE
OFFexact ADAM OFFOFFRemains off
ACTIVEexact ADAM ONACTIVEAlready active
Anyexact remount replayACTIVERecovery path

​
Post-handshake reset

After a TRANSPORT → ACTIVE transition via exact ADAM PING, or after exact remount replay confirmation, the following reset occurs:

Cleared

Pre-handshake transport context and pending gating are cleared. Cached gating references from pre-handshake turns are discarded.

Preserved

An exact ADAM PING while already ACTIVE is liveness-only: pending gating, cached gating references, and overlay state are left untouched.
The next routed turn after a full handshake starts fresh under normal AUTO/MANUAL handling.

​
Reasoning overlay states

The overlay states are internal — they are never printed in replies. They are recalculated from visible turn history and current-turn structure each time a reply is generated.
Overlay StateMeaning
EXPLOREDefault when ACTIVE begins. Free-form input, no convergence pressure.
CONVERGEStructural complexity is increasing; the conversation is narrowing toward a decision.
DECIDEA decision is being made or recommended.
VERIFYChecking or validating a prior decision.

​
Allowed overlay transitions

EXPLORE → CONVERGE → DECIDE → VERIFY → DECIDE

Any state → EXPLORE   (if RETROGRADE_HARD)
Additional rules:
  • If DEEP_CANDIDATE is true and the current overlay is EXPLORE, it moves to CONVERGE (anti-sticky rule).
  • If overlay history is ambiguous, the previous overlay state is retained rather than reverting to a prior MODE.
  • If ACTIVE is established but overlay history is unavailable or ambiguous, overlay defaults to EXPLORE.
  • RETROGRADE_HARD reset is applied before any anti-sticky update.

​
Decision-complete discipline

When the overlay state is DECIDE or VERIFY, the mode is not LOW, and AUDIT_ON is true, A.D.A.M. applies the decision-complete discipline:
  • At least one of the following must be present in the response body: an alternative, a risk, or a verification basis.
  • Outside DEEP, this is kept to the dominant-only signal: at most one risk and one verification item in the body.
  • If more depth is required to satisfy this discipline, A.D.A.M. either asks a single yes/no question or proposes the DEEP gating flow if the message is structurally eligible.
This discipline ensures that decision-state replies do not recommend an action without at least one concrete guardrail.

​
TRANSPORT gate behaviour

While in TRANSPORT:
TurnResponse
Exact ADAM PINGStrict 4-line bootstrap output; transitions to ACTIVE
Exact remount replayADAM_REMOUNT_OK; transitions to ACTIVE
Upload only (no text)No assistant-authored output; remains in TRANSPORT
Any other non-empty turnExactly: MODE: MID / NEXT: send ADAM PING.
No routing, prose, commands, or probes are available before activation.

​
OFF gate behaviour

While in OFF:
TurnResponse
Exact ADAM ONStrict 2-line on response; transitions to ACTIVE
Exact ADAM OFFExactly: MODE: MID / A.D.A.M. off.
Any other exact command or probeExactly: MODE: MID / A.D.A.M. off.
Any non-command turnPlain chat, no A.D.A.M. mode tags

Build docs developers (and LLMs) love

Get started for freeTalk to us