Configuring Sigh Thresholds
The Sigh Calibration System produces a contextual exasperation signal with every response. This tutorial explains the levels and how to configure the threshold.
The Sigh Calibration System (SCS) produces a contextual exasperation signal with every response. The threshold controls the minimum intensity of this signal that is emitted to the caller. It does not affect the internal sigh state.
Sigh levels
| Level | Code | Trigger condition | Example |
|---|---|---|---|
| None | SILENT |
Exceptional query quality | A perfectly scoped, conventional-commit-formatted query with all context provided |
| Mild | MILD |
Standard queries | Most things |
| Moderate | MODERATE |
Commit message without scope, or a diagram committed without the export workflow | "fix: corrected the thing" |
| Deep | DEEP |
A wip commit. A big-bang PR. Markdown in an Antora repo. |
A single commit touching auth, rate limiting, and the README |
| Existential | EXISTENTIAL |
Commit message is wip |
The system enters a brief reflective state |
Configuration
Add the following block to your wraas.yml to configure sigh threshold behaviour:
# wraas.yml
sigh:
threshold: MILD # minimum intensity to emit
emit_on_pass: false # suppress sigh on fully valid queries
log_triggers: true # log what triggered the sigh
Setting threshold: SILENT suppresses the sigh signal but does not suppress
the sigh. WRAAS still sighs internally. This is documented in the audit log.
The Exasperation Subsystem's output is capped at MODERATE — escalation
beyond that point was evaluated and rejected under DME-3000.