triage

Error deduplication uses fingerprint-based hashing of structured record fields to compute stable hashes, ensuring identical errors yield the same ticket fingerprint across entry points. This eliminates noisy, duplicate error reports during triage cycles.

Run a single-environment triage cycle that ingests watchdog entries, applies deduplication, evaluates promotion rules using trust thresholds and escalation signals, then sends notifications. One pass processes the complete flow for a named environment.

Trust-aware noise filtering applies low-trust filters to raw watchdog errors before promoting tickets to lane-ready status. It uses trust thresholds, velocity boosts, and cross-environment escalation signals to decide which errors become actionable tickets.

After fingerprinting, deduplication, and promotion rules apply, the triage cycle sends notifications for promoted tickets. It also enforces Beads ticket label and lane transitions based on trust and thresholds, updating the checkpoint state.

The triage cycle runs one complete pass for a named environment at a time. It applies to monitoring and error-routing workflows for multiple configured environments, typically invoked by a watcher or manual run for debugging.

Duplicates may appear if structured record fields differ between entry points, altering the fingerprint hash. The deduplication requires matching stable hashes from identical structured fields to successfully group the same error.