Education Technology

Schools and their vendors carry duties that most software teams never meet. A tutoring assistant handles a minor, a grade, and sometimes a disciplinary note in one session. This starter puts identity and student data checks in front of the model, and puts accuracy checks behind it.

Every call must carry a verified identity, because authentication is on by default even though no role names are listed. Add your roles to separate a teacher, a guardian and a learner. A student privacy constraint then applies to the request. Masking hides student or pupil identifier shapes, grade record wording and disciplinary record wording.

Answers face a demanding combined floor of 0.85, with relevance at 0.78 and accuracy at 0.80. A reply under 120 characters or a single sentence is refused. Citation checking records how well an answer is grounded, and it flags weak grounding rather than blocking it. A teacher still reads the result.

The bias check runs with its built-in signal and raises an escalation rather than a refusal. The keyword screen carries no terms of your own, so a built-in list applies until you add age appropriate wording. The review point is empty, so an escalation path exists only after your team switches it on.

FERPA and COPPA questions about access, parental consent and age gating are policy decisions, not gateway settings. What you get here are refusals and evaluation markers that show how each request was handled. Decide directory information rules, retention and consent capture in your own systems.