Outline sketch
Audience: support / ops.
Steps:
1) Deterministic pre-checks in code (closed tickets, missing fields).
2) State: message, sender, open orders, policy lists — omit secrets.
3) Parallel: Choice intent/topic; Score complexity; optional Nouls (needs_human, requests_credentials).
4) Gate: high confidence → route; mid → suggest; low → human.
Expected effect: closed-label routing with confidence-aware escalation.
Do not let Jev mutate tickets or send mail.
Needs access to: typesafe-sdkyour-ticketing
Who it's for
Support / ops engineers owning queues
Steps / how it's set up
Map queues to Choice criteria (what / not_for / examples). Call System One once per ticket; compose the route in application code. Cross-link: Hands-on support routing. Sources: intent-routing · how-to-build-with-system-one · awesome-jev-usecases · Routing.
Include an other / exception Choice option so unknown intents are not forced into a wrong queue. Optional speculative Nouls can branch follow-up questions in one round-trip. Production-scale routing claims from community repos are author-reported — calibrate on your ticket mix.
Sources (wave-2 deepen)
Expected effect
Canonical first System One shape: closed answer space, high repeat rate, judgment instead of brittle rules.
Unofficial outline for learning. Paraphrased from public docs and tutorials — not a production recipe. Review sources before you automate anything.