Verification needs sprints
STEM without verification becomes unverified polish. A student verification sprint includes a hypothesis that becomes a protocol, a test students can run, a pass/fail rule written in advance, and a log line a reviewer could audit.
Failed tests count when the test was written first. Mentors make claims more attackable; they do not take over the apparatus.
Weekly rhythm
Monday protocol draft; midweek run and log; Friday review of what the claim may now say. Lights and paint are not measurements. AI-assisted work needs a prompt log and checks against known cases. Polish comes after the pack exists.
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.