Mastery: your playbook

Your mastery artifact is a teaching packet with target alignment map, vetted materials, misconception plan, accessibility review, and teacher sign-off. It should let a competent colleague repeat design a differentiated fraction mini-lesson while keeping assessment judgment with the teacher without inheriting unstated assumptions. Include the job card, source requirements, prompt contract, examples, rubric, privacy boundary, escalation rule, and recovery steps.

Use target → draft → differentiate → solve → review → teach as the spine. For every stage, name the input, action, output, owner, check, and stop condition. Include the concrete prompt:

Learning target: compare fractions with unlike denominators. Create a three-minute explanation using a pizza model, one worked example, four practice items from easy to challenging, and an answer key naming likely misconceptions. Use fictional learners only. Keep the target fixed and do not make grading or placement decisions.

Then include a specimen response: An age-appropriate explanation, a correctly solved example, practice that measures the same target, and a misconception note about comparing denominators directly. Label it as an example, not a guaranteed result. Attach proof from the independent check: you must solve every item, confirm support versions assess the same target, check reading load and cultural assumptions, and have the teacher approve classroom use.

Run the same playbook on a second case that differs in one meaningful way. Keep the quality bar fixed. Explain which context fields and constraints changed. If the workflow only succeeds on the memorized example, it is not mastered.

Teach the method in five minutes to someone who has not read this chapter. Ask them to identify the source of truth, the riskiest failure, and the human decision. Their answers reveal whether your playbook is explicit.

Score yourself:

1. Framing: I can reject work outside the stated job.
2. Context: I distinguish evidence, assumptions, and untrusted input.
3. Prompting: I constrain output and request inspectable artifacts.
4. Verification: I use an external check, not model confidence.
5. Safety: I enforce this boundary: never submit names, grades, disability details, behavior records, private writing, or any identifiable student information to an unapproved system.
6. Operations: I can recover from wrong answer keys; difficulty changed by changing the target; accidental answer reveal in hints; biased examples; automated grading or discipline recommendations.
7. Communication: I disclose limitations and ownership clearly.

A weak score is a practice target, not a reason to pad the playbook. Adapt the route to learning, not the destination. AI drafts examples and supports; the teacher remains responsible for accuracy, context, and consequential decisions.

Package the project as create a mini-lesson with two support levels, a hint ladder, exit ticket, answer audit, and teacher-use notes. Show the before state, constraint decisions, failed case, correction, measured result, and reflection. Remove sensitive inputs and avoid claiming impact you did not measure. Professional credibility comes from showing judgment under constraints.