Provenance before dashboards
Operations reads only completed live Router dispatches and Evaluation results already stored in the current browser. It does not imply site-wide traffic, production infrastructure access, or provider billing authority.
Observe what happened.
Claim nothing more.
A transparent explanation of the dataset, calculations, alerts, portability, and limits behind AXON//RADAR Operations.
OPEN OPERATIONS ↗Consistent operating measures
Request count, success rate, latency, input plus output tokens, provider-reported cost, model distribution, and fallback usage are derived from individual recorded traces. Missing history produces an empty state—not invented values.
Thresholds are decision aids
Latency, budget, error-rate, and fallback-rate limits are user-controlled comparisons against the visible dataset. Alerts indicate a threshold crossing; they are not incident diagnoses, SLA guarantees, or billing notifications.
Portable evidence
JSON exports preserve the version, export timestamp, and trace records. CSV exports reflect the active source filter. Imported JSON exists only in the current view and is not silently merged into Router or Evaluation history.
Known limits
Browser storage is device- and profile-specific. Clearing site data removes local history. Provider cost and token reporting may vary. A production deployment should stream equivalent trace events to durable storage and connect real billing, authentication, retention, privacy, and alert-delivery systems.