Review queue

Required review loop

• Reviewer identity and role: Every decision identifies an accountable teacher, subject expert, safeguarding reviewer or curriculum lead.
• External or real-world attestation: The accepted validation record confirms evidence is external or real-world and not synthetic-only.
• Full UK education scope: Review coverage spans all MVP stages and subjects from EYFS through A-Level, with age-scoped expectations intact.
• Concept accuracy and fundamentals: Objectives, explanations, worked examples and representative problems accurately teach the core of the subject.
• Prerequisite sequence: Prerequisites, progression links and extension paths form a coherent learning route for the stated age group.
• Misconceptions and remediation: Common errors, feedback, remediation and stretch work are specific enough for Aristotle to respond safely.
• Assessment rubric: Rubric dimensions, mastery signals and evidence prompts can measure understanding rather than completion alone.
• Blocked content triage: Blocked and revision-needed concepts are repaired or kept out of production-trusted teaching until re-reviewed.
• Validation registry acceptance: A subject-expert review record is accepted with no open handoff gaps before a production trust claim is made.

Next actions

• Send 768 pending concept(s) to subject experts in traceable batches.
• Start with A-Level / Mathematics, where 8 concept(s) remain open.

Acceptance rules

• Structural curriculum audit: The EYFS-to-A-Level curriculum map has no missing metadata for concepts, prerequisites, rubrics or progression links.
• Live expert review coverage: Every concept in the claimed scope has a latest approved CurriculumReview decision.
• Accepted validation evidence: The validation registry contains an accepted subject-expert review record with external or real-world attestation.
• Production trust gate: Expert-reviewed-only teaching is enabled in the target environment before production trust claims are allowed.

Return protocol

• Inspect each concept: Check objective, age scope, prerequisites, misconceptions, representative problem, mastery signals, remediation, extension and progression links.
• Record a decision: Use approved only when the concept can support trusted teaching for the stated stage and subject; otherwise use needs_revision or blocked.
• Write traceable notes: Every decision needs reviewer_name, reviewer_role, confidence and alignment_notes; correction_notes should explain what to repair.
• Return the decision JSON: Return the completed decision_import_template with the batch_reference intact so Aristotle can validate the whole batch before saving.
• Create validation evidence after coverage: After all concepts in scope are approved, create subject-expert validation evidence with external or real-world attestation.

Required attestation

• Reviewer identity and role: Every decision identifies an accountable teacher, subject expert, safeguarding reviewer or curriculum lead.
• External or real-world attestation: The accepted validation record confirms evidence is external or real-world and not synthetic-only.
• Validation registry acceptance: A subject-expert review record is accepted with no open handoff gaps before a production trust claim is made.

The work order contains curriculum map content, review status and decision fields only; it excludes learner profiles, names, raw answers, guardian details, emails, session keys and access codes.