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.

This lexicon is the single source of truth for A.D.A.M. terminology. Use these exact forms when editing the protocol, writing documentation, or building tooling around A.D.A.M. Using synonyms outside this list creates ambiguity that propagates into the protocol, documentation, and any tooling built on top of it — stable terminology reduces protocol drift.

Most-used terms

TermOfficial FormAllowed VariantsAvoidNotes
A.D.A.M.A.D.A.M.ADAM (only in commands, filenames, paths)Adam (as a person)Project/protocol name.
modeMODEmodedepth levelPublic reply state label.
LOWLOWLiteFast, low-overhead response mode.
MIDMIDNormalDefault structured mode.
DEEPDEEPDeep modeFull decision support.
POSSIBLE DEEPPOSSIBLE DEEPMODE: MID -> POSSIBLE DEEPmaybe deepDEEP candidate state; requires gating.
manual overridemanual overrideoverrideforce (as a general synonym)LOW / MID / DEEP as first token; case-sensitive.
public core commandspublic core commandscore commandsmain controlsADAM PING, ADAM REMOUNT, ADAM PERSIST, ADAM OFF, ADAM ON.
operator commandsoperator commandsdebug commandsADAM SELF TEST, TRACE INPUT, SYS STATUS, UNSUPPORTED WHY.
BOOTSTRAP_CLASSBOOTSTRAP_CLASShost classPublic source-side bootstrap state established by ADAM PING in TRANSPORT.
TEXT_ONLYTEXT_ONLYtext modeProtocol operable, but execution not tentable or no stable physical bind proved.
BOUND_ROBOUND_ROread-only boundSource-side physical bind established; read-only at source side.
BOUND_RWBOUND_RWread-write boundSource-side physical bind established; source-side write/readback verified.
GHOSTGHOSTghost modePhysical bootstrap ran, but no sufficient classification basis remained.
PERSISTENCE_CLASSPERSISTENCE_CLASSpersist classDestination-side result of ADAM PERSIST; does not replace BOOTSTRAP_CLASS.
structural kernelstructural kernelkernel, section Sswitch logicSSOT routing layer driven by input structure, not wording.
AUDIT footer`AUDIT` footerAUDIT blockepistemics blockStrict 4-line bounded audit block.
ACTION/RISK/BASISACTION: / RISK: / BASIS:A/R/VCanonical lines inside the AUDIT footer.
DEEP gatingSwitch to DEEP? (yes/no)deep promptExact last-line consent gate to enter DEEP.
ADAM PINGADAM PINGCanonical visible bootstrap trigger. In TRANSPORT: strict 4-line bootstrap output. In ACTIVE: strict 2-line liveness output.
TRACE INPUTTRACE INPUTRX receiptStrict forensic/operator input trace command.
ADAM_UNSUPPORTEDADAM_UNSUPPORTEDFail-closed output when strict invariants cannot be satisfied reliably.

Runtime and state terms

These terms describe runtime, state, and matching rules.
TermOfficial FormMeaning
rule-ordered runtimerule-ordered runtimeExplicit priority, parsing, and output rules constrain behavior, even though execution remains probabilistic.
grammargrammarThe recognized command vocabulary and its matching rules.
exact matchexact matchCanonical command matching rule for strict commands and probes.
first tokenfirst tokenThe first whitespace-delimited token of the user message; used for manual override.
priority orderpriority orderREMOUNT_REPLAY > TRANSPORT_GATE > OFF_GATE > ACTIVE_CONTROL_COMMANDS > MANUAL_OVERRIDE > STRUCTURAL_KERNEL > STATE_DEFAULT > OUTPUT_CONTRACT.
TRANSPORTTRANSPORTFile present but not yet activated; only exact ADAM PING and exact remount replay are available.
ACTIVEACTIVEProtocol is active and normal routing applies.
OFFOFFProtocol is temporarily off; ADAM ON is required to return to ACTIVE.
state machinestate machineFinite state model for TRANSPORT / ACTIVE / OFF, plus a separate internal reasoning overlay.
fail-closedfail-closedIf a strict invariant cannot be satisfied reliably, output only the strict fallback instead of approximating.
liveness-onlyliveness-onlyExact ADAM PING while already ACTIVE; confirms activity but does not rerun G0.
prev_commitprev_commitRuntime input derived from whether the immediately previous assistant reply contained an explicit COMMIT. It is not a structural boolean computed from the current user message.

Modes and gating terms

TermOfficial FormMeaning
mode tagMODE tagRequired first line on normal replies while ACTIVE.
LOWLOWMinimal, fast replies with low overhead.
MIDMIDDefault rigorous mode.
DEEPDEEPFull decision support mode.
POSSIBLE DEEPMODE: MID -> POSSIBLE DEEPCandidate state indicating DEEP may be needed.
DEEP gatingSwitch to DEEP? (yes/no)Exact last-line consent question used to enter DEEP.
hard stophard stopIf gating is used, the gating question must be the exact last line.
anti-loopanti-loopIf user reply is not exactly yes or no, treat it as non-entry and do not repeat the gate automatically.
DEEP_CANDIDATEDEEP_CANDIDATEStructural kernel result indicating DEEP may be warranted.
MINI_TABLE_TRIGGERMINI_TABLE_TRIGGERStructural kernel result that triggers a compact comparison table in MID.
RETROGRADE_HARDRETROGRADE_HARDStructural kernel result indicating a hard retrograde condition after new constraints.

Output contract terms

TermOfficial FormMeaning
Action LaneAction LaneMain answer body.
AUDIT footer`AUDIT` footerStrict bounded block appended only when AUDIT_ON is true.
boundedboundedHard cap on meta output; AUDIT must remain exact and compact.
audit compressionaudit compressionKeep AUDIT short and grounded; use - when a line cannot be grounded.
ACTIONACTION:Dominant operational next step, or -.
RISKRISK:Dominant downside/failure mode, or -.
BASISBASIS:One compact grounding basis: check, visible source, or observable verification basis, or -.
decision-completedecision-completeIn DECIDE / VERIFY, ensure at least one meaningful guardrail exists unless mode/contract forbids it.
comparison mini-tablecomparison mini-tableCompact table for multi-option comparisons in MID.
publish-boundary validationpublish-boundary validationDraft → validate → rewrite once → fail-closed if strict invariants still fail.
sparse local provenanceSparse Local ProvenanceC5 local signal layer for eligible DEEP blocks only.

Probes and diagnostics terms

TermOfficial FormMeaning
ADAM SELF TESTADAM SELF TESTRuns the external self-test file if available; otherwise returns SOURCE_FILE_UNAVAILABLE ADAM_SELF_TEST.md.
SYS STATUSSYS STATUSRuns the external system status probe if available; otherwise returns SOURCE_FILE_UNAVAILABLE SYS_STATUS.md.
TRACE INPUTTRACE INPUTStrict one-line forensic/operator trace on the last visible user message.
INPUT_TRACEINPUT_TRACE: ...Strict output shape returned by exact TRACE INPUT.
lenlen=<L>Raw character count in the traced user message as seen by the model; if unreliable, len=0.
headhead="<H>"First 16 characters of the traced user message after required normalization.
tailtail="<T>"Last 16 characters of the traced user message after required normalization.
structstruct=[opt:<n> step:<n> crit:<n> num:<Y|N>]Structural summary used by strict TRACE INPUT.
structural classification overlayTRACE INPUT: overlayAutomatic presentation-only structural overlay in MODE: MID -> POSSIBLE DEEP and some DEEP replies.
UNSUPPORTED WHYUNSUPPORTED WHYStrict one-line diagnostic probe after ADAM_UNSUPPORTED.
CAUSECAUSE <CLASS>Strict output for UNSUPPORTED WHY.

Host and compatibility terms

TermOfficial FormMeaning
hosthostThe chat UI/platform where you load and run A.D.A.M.
system prompt hostsystem prompt hostA host that lets you load the protocol as active instructions.
upload is transport onlyupload is transport onlyFile presence does not count as activation. Exact ADAM PING is still required.
local contextlocal contextThe visible/mounted context the protocol can actually inspect.
host artifactshost artifactsUI banners, wrappers, or formatting inserted by the host, outside protocol control.
bootstrap boundarybootstrap boundaryThe bounded activation check run through exact ADAM PING in TRANSPORT.
protocol operability checkprotocol operability checkLevel 1 visible-context check that runs before physical classification in G0.
physical classificationphysical classificationG0 phase that determines public BOOTSTRAP_CLASS beyond TEXT_ONLY.
source-side classsource-side classPublic meaning of BOOTSTRAP_CLASS; it does not describe destination durability.
destination-side classdestination-side classPublic meaning of PERSISTENCE_CLASS; it does not replace BOOTSTRAP_CLASS.

Errors and strict outputs

TermOfficial FormMeaning
ADAM_UNSUPPORTEDADAM_UNSUPPORTEDOutput-only fail-closed fallback when a strict invariant cannot be satisfied reliably.
SOURCE_FILE_UNAVAILABLESOURCE_FILE_UNAVAILABLE <FILENAME>Strict one-line fallback when an external source file is unavailable in current host context.
strict outputstrict outputA response format that must match exactly, with no extra prose or extra lines.
ADAM_PING_OKADAM_PING_OKStrict success line emitted by exact ADAM PING.
ADAM_REMOUNT_OKADAM_REMOUNT_OKStrict success line confirming exact remount replay and return to ACTIVE.
ADAM_PERSIST_OKADAM_PERSIST_OKStrict success line for ADAM PERSIST when a destination copy is written and classified.
PERSIST_BLOCKEDPERSIST_BLOCKED: ...Strict blocked output when source or destination gate prevents ADAM PERSIST.
ADAM_PERSIST_FAILADAM_PERSIST_FAILStrict failure output when persist write fails.
VERIFIEDVERIFIEDDestination copy written, re-opened, and matched to source.
WRITTEN_ONLYWRITTEN_ONLYDestination write appears to have happened, but readback or strict verification is incomplete.
MISMATCHMISMATCHDestination copy exists but does not match source.
CAUSECAUSE <CLASS>Strict output for UNSUPPORTED WHY. <CLASS> is one of HARD_STOP, AUDIT_FORMAT, HOST_FORMAT, CONTROL_STRICT, CONFLICT, UNKNOWN.
When in doubt about which term to use, check this lexicon. Avoid creating new synonyms — stable terminology reduces protocol drift and keeps the spec, documentation, and tooling aligned.

Build docs developers (and LLMs) love