Teacher material · Page · Unpublished in Canvas

Facilitator Guide: AI Ethics Council Day 10 — Test the Code

Canvas state
Unpublished

TEACHER ONLY · LESSON GUIDE

AI Ethics Council Day 10 — Test the Code

Run the lesson here; the student item below remains the independent and absence route.

Daily Learning Contract

Topic: Policy stress-testing and revision

Objective: Students will evaluate whether an AI policy handles new cases, apply peer feedback to revise a weak rule, and justify the final verdict with evidence.

TEKS:
  • §126.19(c)(11)(B) — share and seek feedback on files in various formats, including text, raster and vector graphics, video, and audio files.
  • §126.19(c)(12)(A) — integrate use of appropriate technology terminology in scholarly inquiry and dialogue such as classroom discussion and written samples;

Demonstration of learning: Peer-feedback record, one documented rule revision with its evidence, individual synthesis, and final group code.

Before class

Time: One class period
Student route: Day 10: Test, Revise + Final Verdict
Use what already exists: Casebook and completed group code.

Lesson flow

  1. Launch: Launch with a concrete question or failure that makes feedback and revision matter.
  2. Model: Model one current example or tool move before students begin.
  3. Do: Guide the first decision together, then release students to the existing Canvas task.
  4. Check + support: Check for the named evidence, not completion alone; keep a visual sequence, sentence stems, and purposeful partner roles available.
  5. Close + handoff: Collect or verify the evidence and name the next lesson's connection.

Check before students leave

Ask students to point to the specific evidence above and explain one choice, test, or revision. Completion alone is not evidence of understanding.

Support + troubleshooting

Scaffold: Keep the visual task sequence visible, assign purposeful partner roles, and use the sentence stems on the student page before simplifying the task.

When students get stuck: Ask for the exact step where the tool, code, or task stopped. Check setup, inputs, and saved work before replacing the task or lowering the thinking.