Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Guru Meditation Codes

Inspired by the Amiga’s iconic error screens, every failure mode in Gaius gets a unique identifier — a Guru Meditation Code. These codes create a traceable link from error messages to diagnostics and remediation.

Format

#<COMPONENT>.<SEQUENCE>.<MNEMONIC>

  • Component: Two or three letter abbreviation for the subsystem
  • Sequence: Zero-padded number unique within the component
  • Mnemonic: Human-readable description of the failure mode

Components

CodeComponent
DSDatasetService
NFNiFi
ENEngine
EPEndpoints/Inference
EVEvolution
DBDatabase
QDQdrant
GRgRPC
ACPAgent Client Protocol
ACFArticle Curation Flow
HLHealth
XBX Bookmarks

How They’re Used

Every error message includes the guru code and remediation path:

DatasetService not initialized.
  Guru: #DS.00000001.SVCNOTINIT
  Try: /health fix dataset
  Or:  just restart-clean

Design Rules

  1. One code per failure mode: Each code maps to exactly one failure
  2. Unique across the system: No two failure modes share a code
  3. Stable: Codes are never renumbered once assigned
  4. Documented: Each code has a KB heuristic with symptom, cause, and fix

KB Heuristics

Each guru code has a corresponding heuristic document in the knowledge base at build/dev/current/heuristics/gaius/<category>/<name>.md containing:

  • Symptom: What the user sees
  • Cause: Root cause analysis
  • Observation: How to detect programmatically
  • Solution: Remediation steps, including /health fix command

See Guru Meditation Codes Reference for the complete catalog.