Anomaly & edge-case triager
Packaged know-how that tells an agent how to do a job well.
You might say…
“I either ignored odd data points or over-escalated them — having a structured triage call means I know which edge cases actually matter.”
What it does
Examines an observation outside the method's standard assumptions and judges whether it is benign variation, an ambiguity needing a routing call, or a true anomaly to escalate.
Trigger: Use mid-execution the moment an observation doesn't fit the rubric cleanly; provide the observation and the method's handling guidelines.
I/O: Anomalous observation + method assumptions → triage verdict (benign / ambiguity to route / escalate) with brief rationale
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation