Files
maraphon-app/src/Marathon.Application/Reporting/OutcomeBucketKeys.cs
T
alexei.dolgolyov 292223174c feat(insights): anomaly outcome validator — hit-rate calibration page
Adds a calibration dashboard that joins persisted SuspensionFlip anomalies
with EventResult rows and reports whether the post-flip favourite actually
won — the single metric that says whether the detector is doing its job.

Domain:
- AnomalyEvidenceData + AnomalyEvidenceParser to read the JSON written by
  AnomalyDetector without re-implementing the schema.
- AnomalyOutcomeEvaluator: pure function returning Hit / Miss / Unresolved.
  Tennis-style two-way markets with a Draw winner are downgraded to
  Unresolved rather than silently counted as Miss.
- AnomalySeverityThresholds: shared Low/Medium/High constants so the UI
  badge and the report buckets cannot drift.

Application:
- EvaluateAnomalyOutcomesUseCase orchestrates the join + aggregation.
- AnomalyOutcomeReport carries totals, hit rate, three breakdowns
  (severity / sport / score bins) and a per-event title lookup so the UI
  needs no second pass over IEventRepository.
- Score bins extend below 0.30 automatically when the operator lowers the
  detector threshold so the histogram total always equals ResolvedCount.

UI:
- Insights page at /anomalies/insights — hero header, 4-card KPI strip
  (hit rate tinted by tone), three breakdown grids with bar visualisation,
  drill-down tables for resolved and unresolved anomalies. Honors
  prefers-reduced-motion. RU + EN localisation.
- Nav entry under Analysis section + chip button on the Anomaly Feed.

Tests: +42 across Domain + Application (evaluator boundary cases including
tennis two-way and Draw guard, score-bin edges, dynamic floor when
threshold is lowered, event-title pass-through). All 324 tests pass.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-16 13:53:31 +03:00

24 lines
988 B
C#

namespace Marathon.Application.Reporting;
/// <summary>
/// Canonical, culture-invariant <see cref="OutcomeBucket.Key"/> prefixes and
/// literals. Used by the use case to emit keys and by the UI to localise them
/// — both sides reference these constants so a rename can never produce silent
/// "key not found" rendering on the page.
/// </summary>
public static class OutcomeBucketKeys
{
/// <summary>Prefix for sport-grouped buckets, e.g. <c>Sport.6</c>.</summary>
public const string SportPrefix = "Sport.";
/// <summary>Prefix for score-bin buckets, e.g. <c>Bin.0.30-0.40</c>.</summary>
public const string BinPrefix = "Bin.";
/// <summary>Prefix for severity buckets, e.g. <c>Severity.High</c>.</summary>
public const string SeverityPrefix = "Severity.";
public const string SeverityLow = SeverityPrefix + "Low";
public const string SeverityMedium = SeverityPrefix + "Medium";
public const string SeverityHigh = SeverityPrefix + "High";
}