An AI agent reads a fan's support message, works out which systems to query, and hands a deterministic rules engine everything it needs to resolve the case — plus the console a Fan Ops agent uses to approve or override the result.
Three places to look. The console is probably the best starting point.
engine.py, the
tests, and a README that walks through the assumptions and where
things fall short.
Read the code →
Five issue types, each following the same four layers: escalation gate, the field that picks the action, time to event, then message tone. Pan and zoom the board above to read the notes, or open it in Miro — though Miro does ask you to sign in to view a board. If that gets in the way, or the embed doesn't load for you, the same diagrams are in this Google Drive folder, which needs no account at all. The cancellation logic follows the marketplace's published policy on postponed, rescheduled and canceled events.