Skip to content

docs(tutor-quality): record the conformance audit and no known deviations #158

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ttbombadil merged 1 commit into from
Oct 3, 2026
Merged

docs(tutor-quality): record the conformance audit and no known deviations #158

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 17 additions & 8 deletions ssot/ssot_function_definition_TutorQualityEvaluation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,16 +1,14 @@
# Tutor Quality Evaluation – Corpus, Execution, Checks, Judge, Report

Status: normative target model for Tutor quality evaluation.
Status: normative model for Tutor quality evaluation.
Supersedes: the earlier execution-runner specification and the earlier
semantic-layer design (see the historical glossary entries in §2). Implementation
plan: `docs/UNOSIM_TUTOR_QUALITY_AUTOMATION_PLAN.md` (not normative).

> **Target state, not current runtime.** This document partly describes the
> NORMATIVE TARGET STATE of an ongoing migration. The current `main` can
> therefore contain known, temporary deviations. Appendix A lists these known
> deviations and assigns each to a planned PR. No statement in this document
> may be read as claiming that a known, not yet implemented item is already a
> current runtime invariant.
> **Conformance.** `main` implements this document; Appendix A records the
> conformance status and lists no known deviation. A deviation found later is
> listed there with its owner until it is fixed. While it is listed, the
> affected statement must not be read as a current runtime invariant.

Rules carry stable IDs (for example `R-EXP-1`) so that code, tests, and
reviews can cite them.
Expand Down Expand Up @@ -773,7 +771,18 @@ the Judge-credential preflight (`missing-judge-credential`) in PR G; the weekly
schedule was later deactivated (Appendix B). R-ATT-2 followed last: every
deterministic check record carries `outcome` (`pass`, `fail`, or
`not-applicable` with a `reason`), and every check that cannot be interpreted
uses it, not only `expected-phase-after`. Remaining known deviations: none.
uses it, not only `expected-phase-after` (#155).

A full audit on 2026-10-03 checked every MUST/SHALL and `R-*` rule of this
document, `ssot_function_definition_TutorQuality.md`,
`ssot_function_definition_CourseContent.md`, and
`ssot_function_definition_LearningQuestions.md` against code and tests; the UI
rules of LearningQuestions §10 and §16.1 were taken from their existing test
suites rather than re-verified one by one. It closed R-ATT-2 and found two further deviations, both closed: the corpus
contract test capped the Strategy cases per phase at three (R-AUT-1, #156),
and the Stage-1 scenario runner let scenarios fake the planner
(`ssot_function_definition_TutorQuality.md` §5, #157). Remaining known deviations:
none.

Intentional historical identifiers that stay in code and artifacts (§11.4):
the report field `stageAStatus`, internal type names `TutorQualityStageA…`, and
Expand Down
Loading