Centralizes telemetry event execution and documentation for Cairnloop.

Cairnloop emits telemetry events for all major operations. You can attach to these events to capture metrics, logs, and traces.

Conversation Events

The following events are emitted using :telemetry.span/3:

• [:cairnloop, :conversation, :resolve, :start]

• [:cairnloop, :conversation, :resolve, :stop] - Metadata includes :business_duration_seconds

• [:cairnloop, :conversation, :resolve, :exception]

• [:cairnloop, :conversation, :reply, :start]

• [:cairnloop, :conversation, :reply, :stop]

• [:cairnloop, :conversation, :reply, :exception]

Feedback Events

• [:cairnloop, :feedback, :csat, :start]
• [:cairnloop, :feedback, :csat, :stop] - Metadata includes :rating
• [:cairnloop, :feedback, :csat, :exception]

Retrieval Events

• [:cairnloop, :retrieval, :search]
• [:cairnloop, :retrieval, :draft_grounding]

Retrieval metadata is bounded to low-cardinality fields such as :surface, :source_mix, :result_bucket, :grounding_status, :diagnostic_class, :reason, :canonical_hit_count, :assistive_hit_count, and :ranking_outcome.

Knowledge-Maintenance Events

• [:cairnloop, :knowledge_automation, :gap_candidate]
• [:cairnloop, :knowledge_automation, :suggestion_outcome]
• [:cairnloop, :knowledge_automation, :review_decision]
• [:cairnloop, :knowledge_automation, :publish_outcome]
• [:cairnloop, :knowledge_automation, :reindex_outcome]

Knowledge-maintenance metadata is bounded to coarse workflow fields such as :surface, :entrypoint_type, :outcome, :reason, :publish_status, :reindex_status, :canonical_evidence_count, and :assistive_evidence_count.