A semester is a map of explanations
Responsible AI education collapses when a school buys seats and hopes literacy appears. Map a semester as explanations a student can still give when the account is logged out.
Ask for human knowledge targets, refusal skills, teach-backs, and assessments that do not require a live model.
Weeks for noticing, explaining, transferring
Early weeks train stopping: limitation notes, separating claims from guesses, knowledge maps before model use. Mid-semester pairs short explanations with mentor questions about decorative words and remaining human decisions.
Later weeks carry habits into a STEM topic the student already studies. End with a portfolio of explanations and refusals, not a vendor certificate. No invented awards or placement statistics.
Operational checklist 1
Treat block 1 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 2
Treat block 2 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 3
Treat block 3 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 4
Treat block 4 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 5
Treat block 5 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 6
Treat block 6 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 7
Treat block 7 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 8
Treat block 8 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.