Teacher material · Page · Unpublished in Canvas

Facilitator Guide: AI Ethics Council Day 1 — Case Intake + Source Trail

Canvas state
Unpublished

TEACHER ONLY · LESSON GUIDE

AI Ethics Council Day 1 — Case Intake + Source Trail

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

Daily Learning Contract

Topic: Traceable AI ethics cases

Objective: Students will evaluate an AI ethics claim by defining the system and decision, separating evidence from opinion, and verifying the claim with a traceable source trail.

TEKS:
  • §126.19(c)(5)(B) — apply appropriate search strategies, including keywords, Boolean operators, and limiters, to achieve a specified outcome that includes a variety of file formats.
  • §126.19(c)(9)(D) — evaluate the bias of digital information sources, including websites.

Demonstration of learning: Casebook case intake and a two-source trail with publisher, title, link, supported fact, and evidence-versus-opinion distinction.

Before class

Time: One class period
Student route: Day 1: Case Intake + Source Trail
Use what already exists: AI Ethics Council Casebook PDF/DOCX; existing source links.

Lesson flow

  1. Launch: Launch with a concrete question or failure that makes traceable ai ethics cases 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.