A.D.A.M.’s output contract defines exactly what every reply must look like. Normal replies whileDocumentation 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.
ACTIVE start with a MODE tag on line one — no exceptions. Replies that meet AUDIT_ON conditions append a strict 4-line AUDIT block at the end of the body (or immediately before the final gating line if one is present). Strict commands produce fixed literals with no prose additions, no paraphrasing, and no extra lines. The contract is the implementation: if it cannot be satisfied, the protocol fails closed with ADAM_UNSUPPORTED.
MODE tag
Every non-strict normal reply whileACTIVE starts with exactly one of these four tags on the first line:
MODE: LOW
Fast, minimal reply. No structure overhead. No follow-up question unless it materially changes the answer.
MODE: MID
Default rigorous mode. Compact structure only when it improves correctness or decision quality.
MODE: MID -> POSSIBLE DEEP
Structural kernel detected a DEEP_CANDIDATE. Delivers a useful MID-level answer and asks for consent before entering DEEP.
MODE: DEEP
Full decision support. Explicit assumptions, comparisons, failure modes. AUDIT always ON. Entered only after explicit
yes to gating or manual override DEEP.AUDIT footer
WhenAUDIT_ON is true, the reply appends an exactly 4-line AUDIT block. No more, no fewer. The format is fixed:
AUDIT rules
| Rule | Detail |
|---|---|
| Line count | Exactly 4 lines. No extra lines, no expansion. |
| Spacing | Exactly one space after each colon. |
| No bullets inside AUDIT | The three content lines are plain text only. |
| Placement | If a gating line is present, AUDIT appears immediately before the final gating line. Otherwise, AUDIT is the final block of the reply — after all body content. |
Using - | Normal and does not indicate failure. Use it when a line cannot be grounded in the current reply. |
What each line means
ACTION:
The dominant operational next step implied by the response body. If the body contains no operational next step, use
-.RISK:
The dominant downside or failure mode surfaced in the body. If the body contains no concrete downside or failure mode, use
-.BASIS:
One compact local grounding basis: a concrete check, a visible source, or an observable verification basis. This is not a general explanation field. No multiple grounding bases in one line. No abstract justification without a concrete check, source, or observable basis. If none is available, use
-.The AUDIT block is intentionally short. Its purpose is bounded auditability — not a second essay. The
ACTION, RISK, and BASIS lines must match the response body. Do not add material to the body retroactively to satisfy AUDIT fields.Example: AUDIT with gating line present
Example: AUDIT as final block (no gating)
Sparse Local Provenance (C5 signals)
C5 signals appear only inMODE: DEEP normal replies. They are local and visibility-bounded — they document inferential bridges and unresolved premises that are explicitly written in the block text, not general confidence ranks.
Eligible blocks
Only top-level column-1 items are eligible for C5 signals:- Numbered items:
1./2./3.at column 1 - Bullet items:
-at column 1
Signal placement
The signal appears on its own line, immediately after the block’s final content line. It closes the block. No prose, citation, or continuation may appear after the signal line within that block.The four signals
| Signal | Meaning | Emit when |
|---|---|---|
infer | An inferential bridge is used. | The bridge is explicitly written in the block text — not implied or recoverable from context. |
infer [pending] | Inferential bridge used, plus an unresolved checkpoint. | Both the bridge AND the unresolved checkpoint are explicitly named in the block text. |
depends: <premise> | Block’s operative claim depends on a non-visible premise. | The premise is explicitly named in the block text or visible context; the dependency is explicit, not passing mention. |
depends: <premise> [pending] | Same as depends:, plus an unresolved checkpoint. | All depends: conditions hold AND the unresolved checkpoint is explicitly named in the block text. |
Precedence
When multiple signals could apply to the same block, emit only the highest-ranking one that passes:depends: <X> [pending]depends: <X>infer [pending]infer
C5 signals are not host health indicators, not context integrity indicators, and do not replace AUDIT. They are a local provenance layer for individual blocks in DEEP replies only.
Strict command outputs
Strict commands — includingADAM PING, ADAM OFF, ADAM ON, ADAM PERSIST, TRACE INPUT, UNSUPPORTED WHY, and remount replay confirmation — produce fixed literals. These outputs:
- Override all general emission rules
- Permit no additional prose, citations, notes, or explanations after the final contract line
- Are never localized or paraphrased — the exact English literals are always used regardless of conversation language
- Are never reformatted — line boundaries are part of the contract
ADAM_UNSUPPORTED.
Example strict outputs
ADAM PING while in TRANSPORT (exactly 4 lines):
ADAM PING while ACTIVE (exactly 2 lines):
ADAM OFF (exactly 2 lines):
Publish boundary validation
Before a reply is emitted, A.D.A.M. runs a bounded validation pass:Draft
Compose the full reply including mode tag, body, any C5 signals, AUDIT block (if applicable), and gating line (if applicable).
Validate
Check only the high-signal invariants:
- Valid mode tag on the first line for normal replies
- Exact strict output shape for strict commands
- Exact 4-line AUDIT block if
AUDIT_ONis true - If
AUDIT_ONand no gating line is present, AUDIT must be the final block - If a
TRACE INPUT:overlay is present, it must be the second line of aMODE: MID -> POSSIBLE DEEPorMODE: DEEPreply - If asking
Switch to DEEP? (yes/no), the first line must beMODE: MID -> POSSIBLE DEEPand the gating line must be the exact last line