You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**20/20 binary accuracy** — every scam detected, every safe call cleared. 0 false positives. 0 false negatives.
220
237
221
-
> 20 curated scenarios (10 scam + 10 safe), with expected verdicts, score ranges, and hard cases. See [`docs/EVALUATION.md`](docs/EVALUATION.md) for the full evaluation framework. Audio samples and results in [`demo/`](demo/).
238
+
> Full 20-scenario evaluation: 10 scam + 10 safe calls including 3 deliberate hard cases (legitimate IVR, angry customer, real bank fraud alert). See [`docs/EVALUATION.md`](docs/EVALUATION.md) for full methodology, scores, and analysis.
Copy file name to clipboardExpand all lines: docs/EVALUATION.md
+35-29Lines changed: 35 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -504,45 +504,51 @@ CallShield currently evaluates audio and transcript content only. It does not ha
504
504
505
505
## 9. Results Table
506
506
507
-
Use this template to record actual results when running the evaluation suite. Fill in the `Actual Verdict`, `Actual Score`, and `Match` columns after running each scenario through the CallShield pipeline.
507
+
Results recorded from a full evaluation run against the deployed CallShield API (`mistral-large-latest`, transcript mode). All 20 scenarios submitted via `/api/analyze/transcript`.
508
508
509
509
### Scam Scenarios
510
510
511
-
| ID | Category | Expected Verdict | Expected Score | Actual Verdict | Actual Score | Match |
511
+
| ID | Category | Expected Verdict | Expected Score | Actual Verdict | Actual Score |Binary Match |
Five scam scenarios scored SCAM where LIKELY_SCAM was expected (S03, S04, S06, S09, S10). In every case the model correctly identified the call as a scam — the scores were higher than expected, not lower. This is the desirable failure mode for a scam detector: over-detection on ambiguous scams is preferable to under-detection. No safe call was ever flagged as a scam.
0 commit comments