Skip to content
Freyja Labs

Professional Development for Carmel Clay Schools

Customized. Hands-on. Built for your teachers and your students.

Carmel, IN · 16,500 students

Map data © OpenStreetMap contributors

What we've been reading

From outside, what we notice

Carmel Clay is ranked the #1 district in Indiana by Niche, in one of the most educated communities in the Midwest. The PD bar is high in a specific way: substance over sloganeering. Anything that smells of marketing language gets dismissed quickly. Indiana's CS graduation requirement (Class of 2029) and the Next Level CS Fund are the policy frame. We co-design with Carmel teachers — substance over slogans, grounded in research, built for sustained practice rather than seasonal initiative.

If any of this resonates, you might also like

Next ↓ 02 · Sample lessons

Sample lessons — artifacts, not deliverables

We don't deliver lesson plans.

We deliver change for your teachers. The lessons below are the receipts.

These two examples were built for Carmel Clay Schools — but what we'll actually do together depends on what you tell us about where you are and where you want to go. We custom-build with your teachers around what your students, your community, and your district leadership are actually navigating: AI integration, CS/STEM integration, IN policy, the local context only your educators can read. The artifacts you'll see below are one shape that capability can take.

Tech lesson / with devices
micro:bit + AI · Evidence vs. pattern matching

The Standard of Evidence: Scientists vs. AI

8–10 · Science · 90 minutes

Kit: micro:bit + sample lesson plan — "The Standard of Evidence: How Scientists and AI Analysts Differ" (grades 8-10, science). Students conduct a micro:bit-based investigation, compare their evidence-based conclusions with AI analysis, and evaluate which approach produces more trustworthy results. Embedded AI literacy: the difference between pattern-matching and understanding.

What's new — what wouldn't have happened before this PD

Without the PD, AI analysis reads as analysis. After: students compare evidence-based scientific conclusions with AI pattern-matching and evaluate which approach produces more trustworthy results — exactly the substance-over-slogan bar Carmel families set.

Show full lesson plan objectives · procedure · materials · assessment · teacher pack

Content Objectives

  • Conduct a complete evidence-based scientific investigation
  • Document a chain of reasoning from data to conclusion
  • Compare investigation with pattern matching

AI Literacy Objectives

  • Distinguish pattern matching from understanding
  • Apply a structured verification practice with rigor
  • Articulate why evidence-based reasoning produces more trustworthy conclusions

What Students Do

Phase 1 · 30 min Investigate

Teams of 3+ conduct a micro:bit-based scientific investigation. Reach evidence-based conclusions; document the chain of reasoning from data to conclusion.

Facilitation focus

Don't standardize sensor placement across teams. Different microclimates make Phase 2 richer. Move between teams every 5 minutes; check that students are recording observations *and* numerical readings. The qualitative notes are the wedge they'll use to challenge AI in Phase 3.

Watch for

Teams logging only numbers. Push them to write at least one observation per reading ("breeze picked up", "cloud passed over"). If the campus has visibly varied environments — shade vs. sun, paved vs. planted — push teams to spread out.

Phase 2 · 30 min Compare

Teams query an AI tool to analyze the same data and reach a conclusion. Document where AI pattern matching produced something that resembled understanding and where it fell short.

Facilitation focus

Frame the AI tool as a teammate, not an authority. When the AI prediction is wrong, students often default to "we'll fix our data." Interrupt that — the goal is to surface where AI and ground-truth diverge, not to reconcile.

Watch for

Teams that find zero divergence. Either they're smoothing data unconsciously, or the AI is generic enough to match anything. Have them pick a single 5-minute window and compare in extreme detail.

Phase 3 · 30 min Evaluate

Apply the verification protocol. Class debates: which approach produces more trustworthy results, evidence-based investigation or AI pattern matching? Connect to Carmel's substance-over-slogan culture.

Facilitation focus

The class trust guidelines are the deliverable. Push for specificity: not "AI is bad at humidity" but "AI underestimates humidity in conditions like ours when [specific local condition]." Local knowledge + data = the trust criteria.

Watch for

Generic statements ("AI is sometimes wrong"). Reject these gently — every guideline must reference a specific divergence the team observed.

A four-step verification protocol your teachers will build with us

A practice students learn once and apply to any AI output, in any subject, for the rest of their lives.

1. Check the source

Where did the AI get its data? Is it the same data we used or generated?

2. Check the reasoning

How did the AI reach its conclusion? Can we follow the logic?

3. Check against reality

Does the output match what we observed with our own senses, instruments, or knowledge?

4. Check yourself

What might we have missed? What would we want a second opinion on?

More on the thinking behind this — the framework we built it from.

Materials

  • micro:bit with sensors (included in kit)
  • USB cables and student devices
  • AI analysis tool access
  • Evidence-vs-pattern reference card
  • Investigation-design worksheet

Assessment

Each team produces a one-page artifact: their findings, the AI output they evaluated, and a written verdict on when this kind of AI work is worth trusting.

Final debate position cites at least two specific differences between the team conclusion and the AI conclusion, with reasoning about which is more trustworthy.

Teacher pack — everything you need to teach this

For the Facilitator

Prior Knowledge Required
  • Read and create simple data tables and bar/line graphs
  • Distinguish between an observation (what we measured) and an inference (what we conclude)
  • Familiarity with one-step variable assignment in block-based or text-based code
Exit Ticket

"Describe one moment today when your direct measurement told you something the AI missed. What did you measure, and what should the AI have done differently?"

Look for
  • Specific reference to a measurement (number + unit + location)
  • Specific reference to what the AI output said
  • A concrete claim about what the AI should have changed (input, comparison, caveat)
Anticipated Misconceptions

"If the AI says it, it must be right — it has access to all the data."

Show the AI a deliberately wrong dataset and have students predict the (wrong) output. Reinforce: AI confidence ≠ AI correctness. The AI processes whatever input it receives, including noise and bias.

"Our sensor data is wrong because it doesn't match the AI."

Have students re-measure with a second device or different location. Direct measurement is the ground truth — divergence with AI is a signal worth investigating, not an error to "fix."

"The AI is broken if it gives a different answer to the same question twice."

This is a feature, not a bug. Use it to discuss probabilistic vs. deterministic systems. Two valid outputs can describe the same data — students should learn to ask "what stayed the same?"

Differentiation
Slide Cues — 6 slides
Standards Alignment — 9 frameworks
Family / Guardian Letter — copy & paste, edit to fit

Dear families, This week your student is learning a skill that will matter for the rest of their lives: how to decide when to trust an AI system. In this lesson, students used real sensors to measure conditions around our school and compared what they measured with what an AI predicted. The point is not that AI is bad — the point is that AI works best when paired with someone who knows the real situation. Your student is learning to be that someone. We call the protocol the verification protocol. It has four steps: check the source the AI used, check the reasoning, check the result against reality, and check yourself for what you might have missed. You can use this with your student at home — every time an AI assistant gives you an answer, ask: "How would we check this?" Questions? hello@freyjalabs.com — Freyja Labs (working with Carmel Clay Schools)

Unplugged lesson / no screens
No screens · Courtroom evidence standards for AI

The Standard of Evidence: Courtroom vs. Algorithm

8–10 · ELA / Social Studies · 60 minutes

The Standard of Evidence: Courtroom vs. Algorithm — Teams apply courtroom evidence standards (beyond reasonable doubt, preponderance of evidence) to AI-generated claims. They discover that different standards of evidence lead to different conclusions. Designed for Carmel's intellectual rigor.

What's new — what wouldn't have happened before this PD

Without the PD, "evidence standards" is an English-class topic. After: students apply courtroom evidence standards (beyond reasonable doubt, preponderance of evidence) to AI claims — and discover that different standards lead to different conclusions, every time.

Show full lesson plan objectives · procedure · materials · assessment · teacher pack

Content Objectives

  • Apply legal evidence standards to written claims
  • Compare standards and their implications
  • Construct a context-appropriate evidence framework

AI Literacy Objectives

  • Apply formal evidence standards to AI output
  • Distinguish standards by stakes and consequences
  • Articulate when AI claims must clear which bar

What Students Do — No Screens, No Devices

Phase 1 · 15 min Examine

Teams of 3+ read printed AI-generated claims. Document what each claim asserts and what evidence (if any) supports it.

Facilitation focus

Print the artifact packets in color so detail is preserved. Don't tell students which AI claims are "right" — let them notice divergence on their own. Their lived knowledge of the topic IS the comparison standard. Treat it that way explicitly.

Watch for

Teams that pick a "winning" artifact immediately. Slow them down — every artifact reflects the AI's best guess given its inputs. The question is not which is right but how anyone could have known in advance.

Phase 2 · 25 min Apply

Teams apply two evidence standards to each claim: would it survive "preponderance of evidence"? Would it survive "beyond reasonable doubt"? Document the reasoning.

Facilitation focus

Distinguish three error types: factual (X is asserted but isn't true), framing (the description emphasizes one thing while ignoring others), absence (something important is left out entirely). Most AI artifacts fail in framing and absence, not facts.

Watch for

Teams that only catch factual errors. Push deeper — what story is the AI telling? Whose perspective is implicit? What did it not have access to?

Phase 3 · 20 min Argue

Each team produces a position: in which contexts should AI claims face which evidence standard? Connect to Carmel's intellectual rigor expectations.

Facilitation focus

Frame the argument as advice to a real decision-maker who will act on it. Students must commit to a recommendation AND name specifically what would change their mind.

Watch for

Hedging ("we can't really know"). True — but the decision still has to be made. Push students to commit to a recommendation AND explain what new information would flip it.

Materials

  • Printed AI-generated claims (PDF at landing page)
  • Evidence-standard reference cards (beyond reasonable doubt, preponderance of evidence)
  • Standards-application worksheet
  • Chart paper and markers

Assessment

Each team produces a one-page artifact: their findings, the AI output they evaluated, and a written verdict on when this kind of AI work is worth trusting.

Position cites at least three claims and the standard applied to each, with reasoning grounded in the evidence-standard reference.

Teacher pack — everything you need to teach this

For the Facilitator

Prior Knowledge Required
  • Read and discuss informational text in small groups
  • Cite evidence to support a claim — written or verbal
  • Familiarity with the difference between a prediction and a confirmed result
Exit Ticket

"An AI tool gives someone you care about a recommendation. What three things should they check before they accept it?"

Look for
  • At least one item references the source or input data the AI used
  • At least one item references the AI's reasoning or comparison with known facts
  • At least one item references checking with a person, lived experience, or independent source
Anticipated Misconceptions

"AI is just like a calculator — if you give it the right numbers, you get the right answer."

Use a worked example where two students give the same prompt and get different outputs. AI is more like a human reader making a judgment call than a calculator computing a formula.

"If we can't see the math, we just have to trust it."

Pivot the protocol — "Check the reasoning" — to focus on what we CAN check: source, comparison to known facts, internal consistency. You don't need the math to evaluate a claim.

"AI hallucinations only happen with chatbots."

Show a printed AI example that contains a confident but factually wrong statement. Hallucinations are a property of how generative models work, not a chatbot quirk.

Differentiation
Slide Cues — 6 slides
Standards Alignment — 6 frameworks
Family / Guardian Letter — copy & paste, edit to fit

Dear families, This week your student practiced something most adults haven't been formally taught: how to evaluate an AI-generated claim before accepting it. In this lesson, students worked from printed artifacts — no screens — and applied a four-part verification protocol: check the source, check the reasoning, check the result against reality, and check yourself. They learned that the right answer to "should I trust this AI?" is almost always "let me check first." At home, you can use the same protocol. The next time an AI assistant gives your family information, ask your student: "What would we need to check before we acted on this?" Questions? hello@freyjalabs.com — Freyja Labs (working with Carmel Clay Schools)

Worth saying again: the lessons above are receipts, not the goal. The point of the engagement is change for your teachers — their confidence to design the next ten lessons themselves, for whatever Carmel Clay Schools faces next. We don't deliver lesson plans. We deliver capability.

More on how we think about this work

Next ↓ 03 · How we'd work together

Engagement Options

How We Can Work Together

We don't sell a packaged curriculum — every engagement is shaped around what your district tells us it needs. The options below are starting shapes; the actual work gets co-designed with your team. Click any that look promising and tell us what you're thinking.

Click any option below to mark it as interesting — then use the form to send a quick note.

Next ↓ 04 · Reach out

We do not provide generic materials. We provide the empowerment and support for teachers to build lessons like these — tailored to their students, grounded in their community's experience.

Mike Borowczak, Ph.D.

Andrea C. Burrows Borowczak, Ed.D.

Where growth begins.

hello@freyjalabs.com