Trigger
A group chat, email or bot reports an unstructured exception such as supplier delay, failed shipment booking, equipment downtime, reconciliation difference or missing file.
SCENARIO-DETAIL / LOCALIZED DECISION BRIEF
Message Exception to Resolved System Task
Business trigger: A group chat, email or bot reports an unstructured exception such as supplier delay, failed shipment booking, equipment downtime, reconciliation difference or missing file.
REFERENCE_ARCHITECTURE · READBACK_VERIFY
DECISION RECORD / C.31
What this route helps you decide
Source-traceable reference · pp.66–67
Goal
Extract facts, business object, evidence and Owner from the message, deduplicate against existing system events, then enter the formal exception state machine.
Risk / exception
A verbal reply cannot override system facts. If no unique object matches or the formal system remains in exception, do not close; continue collecting evidence, escalate or hand over to a person.
Close condition
The message binds a real business object; system events are deduplicated; the exception has an Owner and SLA; execution enters the formal system; readback verifies closure.
Next safe action
Choose one message exception and define object matching, event deduplication, escalation and readback closure rules.
KNOWLEDGE → COMPARISON → DIRECTION → OPTIMIZATION
Evidence stays attached to the decision.
The full-detail canonical evidence record remains available in Chinese. IDs, Truth classes, boundaries, and source references stay unchanged across languages.
Knowledge
Source-traceable reference
Comparison
Compare the same operating fields before choosing a direction.
Direction
Confirm the owner, authority, human gate, and readback rule.
Optimization
Define a baseline, target, owner, and observation window before claiming impact.