Rubric Versioning
Version Stamping
How versions are permanently linked to interviews and scorecards.
What Gets Stamped
| Event | Version Stamped | Stored On |
|---|---|---|
| Interview starts | interviewer_version | transcripts table |
| Interview scored | interviewer_version + scorer_version | scorecards table |
Why This Matters
Every scorecard is permanently linked to the exact rubric versions used:
- Interviewer version — the prompt that guided the interview
- Scorer version — the methodology that scored the transcript
This enables:
Version Comparison
"Did changing the ownership rule in scorer v2.1.0 affect average scores?" → Query scorecards by scorer_version and compare.
Regression Detection
If scores suddenly drop, check if a new rubric version was deployed. The trends dashboard surfaces this automatically.
Legal Defensibility
If an employer's hiring decision is challenged, you can reproduce exactly what prompt was used and what scoring rules applied.
Scorer Model Changes
Dev uses Claude Haiku, prod uses Claude Sonnet. If scoring quality differs, version stamps let you isolate whether it's the rubric or the model.