Cross-cutting agent

Exception routing agent

Not a separate product — the trust layer under the other three. You define what counts as an exception; it routes each one to a named owner with full context and a clock, instead of guessing quietly.

See this on your workflow

Commonly connects to

Slack
Teams
email
your ticketing tool
+ your in-house OMS

This is a starting point

Nothing here ships as-is.

Your field names, your SKU resolution rules, your approval thresholds, your escalation owners, your systems. What's reused from build to build is the reliability machinery underneath — idempotency, retries, audit, tenant isolation — which is exactly the part you shouldn't be paying to reinvent.