Glossary

Every 3AM term in one place, A to Z, with where to read more. Admin token, autonomy, Keychain, member, pack, proven, restore move, site key, System 1, Warden and the rest.

TermMeaning
AbandonedAn incident 3AM stopped investigating because it restarted; nothing after its last event was done
ActionEvaluatorThe deterministic rules that classify every fix as safe, needing approval, or forbidden (Resolution)
Admin tokenCreated at first start. Creates the first owner, then serves automation and break-glass; never a sign-in (Sign-in)
Advise / draftThe fix mode. advise gives advice when no pack fix exists; draft drafts a fix and may propose restore moves
At the alertA cause that can only be checked when its alert arrives (the alert names what to look at)
Audit log (ledger)Every event, hash-chained and signed, append-only (Logs and audit)
Autonomyoff, shadow, L1, L2, per service (Autonomy)
Break-glassSigning in with the admin token when e-mail can't be sent; logged
Bundle3am-<version>.tar: images, packs, installer, signed checksums (Air-gapped)
Causal discoveryPCMCI+ in 3am-causal, relating the series that shifted (Investigation)
ChronicA cause already true 30 minutes before the alert: not this incident's cause
Confidenceproven, linked, suspected, disputed, unproven, cleared
CoverageHow many of your services each kind of evidence reaches (Guide)
Digest3AM's call next to your team's, per service; readiness for L1 (Digest)
DisputedChecks prove it, but System 1 reads the evidence as refuting it: goes to a person
Drafted fixA fix 3AM drafts for a proven cause with no pack fix; two approvers by default
EpisodeOne investigation of one service's alerts, inside an incident
EstateThe map of your services, owners, dependencies and where each came from (Estate)
FingerprintA hash identifying an install for the licence (machine id, cluster UID)
Hand-overThe triage sent to people 90 s after the first alert when nothing is proven
HomeThe install a Keychain lives on (Keychain)
IncidentOne failure: every related episode, one ticket, one thread (Incidents)
Ingest tokenBearer token for POST /v1/events and alert webhooks
Install logThe hash-chained history of installs added to and removed from a licence
Investigator (System 2)The language model that reads through read-only actions and writes the note
KeychainOne setup for every install (Enterprise, Strategic)
L1 / L2L1 asks before every fix; L2 also runs safe fixes unasked
LinkedA symptom of another incident whose cause is proven
LookbackYour last 90 days of incidents read from ServiceNow or PagerDuty (Impact)
MCTSThe tree-search investigator (--investigator mcts)
MemberAn install that takes its setup from a Keychain's home
Mitigate firstAt L2, a safe fix before proof on a strong suspect with high impact
PackSealed knowledge of a technology: causes, checks, fixes (Packs)
PairingJoining a Keychain with six digits compared on two screens
ProvenA deterministic check passed on live data, not already true before, and (outside packs) a second line agrees
Readiness for L1≥ 5 judged proposals, ≥ 80% agreed, none policy would refuse
Restore moveWhen nothing is proven: undo the one change just before, start what stopped, or the declared failover
ResultHow an incident ended: resolved, restored, handed_over, linked, cleared, shadow
The ringEvery key (install) on a Keychain and how each is doing
Sealed fileThe Keychain in one file under a passphrase, for a site with no network to the home
ShadowProve, rehearse, record; change nothing. The default
Site keyA one-time key the home makes so a new site sets itself up (3AMSITE1.…)
StudyA read-only rehearsal of every cause, before anything breaks (Study)
System 1 (tev1)The small model that verifies causes, fixes and sentences, and can veto a fix
TierStarter, Enterprise, Strategic (Licensing)
Warden3AM's licence authority (warden.3am.si)