Example transcripts
What will appear here
Once the evaluation pipelines have run with real API keys, this page will publish 6–8 curated, verbatim transcripts from real runs — including at least one v1-baseline failure and one v3 success on the same case, side by side, so the difference in tutor behavior is visible. Every transcript will be labeled with:
- the test case ID and category from eval/test-cases.json;
- the prompt version it came from;
- the tutor model name, temperature and run date;
- the rubric scores it received, and from whom (human scorer and/or the blinded AI judge panel, labeled by method).
Why transcripts, not screenshots of a fake chat
This project's claim is about tutor behavior, and behavior evidence should be inspectable. Publishing real transcripts — including unflattering ones — is the honest version of a "before/after" demo. Publishing anything else would be fabrication. The live demo exists so you can exercise the v3 prompt yourself with your own key while the evaluation runs are pending.
Where the raw material lives
Raw run outputs are written to eval/results/<version>/ as JSON plus
readable Markdown transcripts (one file per case per run), with the model name, date
and parameters recorded in every file. When runs exist, they will appear in the
repository under eval/results/.
Until then that directory contains only a PENDING summary table.