2

Known Event

Phase 1 · LiveLive

Matches the complaint to a known event and returns an id, a rationale, and a confidence.

Reads
Error code, notes, product, diagnosis, failure analysis
Decides
Which known event fits best, if any
Returns
Known Event ID, rationale, confidence

Processing flow

  1. 1
    Classify the complaint
    System service complaint, returned-product complaint, or other.
  2. 2
    Stop early when there is nothing to match
    System service returns N/A. Returned product without material number returns a blank id and "Pending material part number and description."
  3. 3
    Retrieve
    Walk the decision tree and pull a short list of known events from the knowledge base.
  4. 4
    Score and adjudicate
    Rank the short list. A model picks among the ranked events. If the model fails, keep the ranked order.
  5. 5
    Return
    Known Event ID, rationale, confidence, and human review required. Does not create known events or choose investigation depth.
  6. 6
    Hand back to orchestration
    The result is stored. The orchestrator decides the next agent. This agent does not call the next one.

Example on PR 1842201

Known Event ID
KE-4412
Confidence 0.91 · Human review required
See this on the complaint