On this page

Tasks & Assignment Specifications

Companion to the Fall 2026 Syllabus — full instructions and rubrics for every graded task. The syllabus itself only summarizes each task in one line.

For any Mission or Major where you build something in GeoGebra, CODAP, or an AI chat tool, submit the tool's public share link whenever one is available, alongside or instead of a screenshot — a link lets me actually open and interact with your work. Before you submit, open the link in a private/incognito browser tab (or a browser where you're logged out) to confirm it's really viewable without your account — a link that only works while you're signed in isn't public yet.

Deadlines at a Glance

Deadlines are 08:00 (Istanbul time) on the Monday shown for every Mission and Major from Mission 3 on (Missions 1–2 were due at 23:59 on their Thursday), except the Dec 17 defense, which happens in person. The next deadline is highlighted; past ones are greyed out.

Why Monday 8:00 am and not Sunday 23:59? This is intentional. A Sunday-midnight deadline rewards staying up late. Monday 8:00 am gives the night owls among you a real weekend and a good night's sleep, then a fresh-eyed final read before you submit. Same weekend, better work.
DueWeekTask
Thu, Sep 24Wk 1Mission 1Philosophy of Technology Integration
Thu, Oct 1Wk 2Mission 2GeoGebra Micro-Build
Mon, Oct 12 · 08:00Wk 3Mission 3AI Worksheet Critique
Mon, Oct 19 · 08:00Wk 4Mission 4CODAP Mini-Investigation
Mon, Oct 26 · 08:00Wk 5Major 1Digital Toolkit Portfolio
Mon, Nov 9 · 08:00Wk 7Mission 5Differentiation Mini-Task
Mon, Nov 16 · 08:00Wk 8Mission 6AI Formative-Assessment Mini-Task
Mon, Nov 23 · 08:00Wk 9Major 2AI Professional Ethics & Practice Portfolio
Mon, Nov 30 · 08:00Wk 10Mission 7Computational Thinking Mini-Task
Mon, Dec 14 · 08:00Wk 12Major 3Capstone unit plan + Philosophy Bookend
Thu, Dec 17Wk 13Major 3Capstone defense (Showcase)

Subscribing keeps your calendar in sync with any date changes; a downloaded .ics is a one-time copy. Need more time? You have two Grace Tokens (48 hours each, not for the Capstone); see the syllabus.

Task Index

TaskDueCategoryXPEst. Student TimeRubric
Mission1 — Philosophy of Technology Integration (Reflective Essay)Thu, Sep 24 · 23:59
Wk 1
Weekly Mission3030–45 min3-item checklist
Mission2 — GeoGebra Micro-BuildThu, Oct 1 · 23:59
Wk 2
Weekly Mission3045 min3-item checklist
Mission3 — AI Worksheet CritiqueMon, Oct 12 · 08:00
Wk 3
Weekly Mission3045 min3-item checklist
Mission4 — CODAP Mini-InvestigationMon, Oct 19 · 08:00
Wk 4
Weekly Mission3045 min3-item checklist
Mission5 — Differentiation Mini-TaskMon, Nov 9 · 08:00
Wk 7
Weekly Mission3045 min3-item checklist
Mission6 — AI Formative-Assessment Mini-TaskMon, Nov 16 · 08:00
Wk 8
Weekly Mission3045 min3-item checklist
Mission7 — Computational Thinking Mini-TaskMon, Nov 30 · 08:00
Wk 10
Weekly Mission3045–60 min3-item checklist
Major1 — Digital Toolkit PortfolioMon, Oct 26 · 08:00
Wk 5
Major Assignment150~2–3 hrs (built from Missions 1/2/4)4-criterion rubric
Major2 — AI Professional Ethics & Practice PortfolioMon, Nov 23 · 08:00
Wk 9
Major Assignment (signature AI task)180~3 hrs, built up across the semester5-criterion rubric
Major3 — Capstone: AI-Integrated Unit & Public DefenseMon, Dec 14 · 08:00 (plan + Bookend)
Thu, Dec 17 (defense)
Wk 12 / Wk 13
Major Assignment (capstone)180~4–5 hrs across Weeks 10–12, plus the Week 13 defense6-criterion rubric + defense checklist

Presence & Engagement (250 XP), the Growth Loop (20 XP), and Peer Feedback (10 XP) are scored directly wherever the gradebook is kept, not as standalone tasks — see Syllabus Section 3.

Task Continuity FAQ

Can I reuse a previous Mission for this task?

Only when the task says so. Mission 5 explicitly asks you to reuse Mission 2, 3, or 4; Major 1 explicitly revises Missions 1, 2, and 4. Every other task is a fresh topic — though reusing the same underlying math concept across missions for your own coherence is always fine.

Does every task have to be different?

The tool and topic change each week; the deliverable format (a short artifact + a short note) stays deliberately similar, so you're never learning a new submission format — only new content.

Does it have to be math-related?

Yes, always. Every Mission, Major, and the Capstone must be built around a specific mathematics concept.

What grade level should I use?

Your choice — elementary, middle, or high school. This course defaults to middle/high school, but elementary is completely fine if you prefer it. State your chosen grade band in each submission.

I'm a master's/graduate student — is the Capstone the same for me?

Talk to me in the first two weeks of the course. If you're pursuing a graduate degree, Major 3 (the Capstone) can be adapted into a paper or a component of your own research or manuscript instead of the standard K–12 unit plan. Missions and Majors 1–2 stay the same for everyone.

Should I submit screenshots or links for GeoGebra/CODAP/AI work?

Submit the tool's public share link whenever one is available, alongside or instead of a screenshot — a link lets me actually open and interact with your work. Before submitting, check it in a private/incognito browser tab to confirm it's really public and not just viewable while you're logged in.

I'm adding this course during add/drop — will I be penalized for missing Week 1?

No. See the Add/Drop Grace policy in Syllabus Section 3 — Week 1's Presence & Engagement points are simply left out of your denominator, not counted against you as zeros.

Each Mission/Major block below also carries its own Builds on: line so the dependency is visible at the task itself, not just here.

Weekly Missions (M1–M7)

Detailed instructions and rubrics for the seven 30–60-minute weekly Missions. Each Mission is worth 30 XP, graded on the same 3-item checklist shape: Meets (10) / Partial (5) / Not Yet (0) per criterion. Submit through the Mission document in your shared Google Drive folder.

Mission1 — Philosophy of Technology Integration (Reflective Essay)

Due Thu, Sep 24 · 23:59 Week 1

Time: ~30–45 min

Builds on: — fresh start, no prior work needed. You'll revisit this exact essay in Week 12 (Philosophy Bookend, due Mon, Dec 14 · 08:00).

Objective: Put into words, before any tool training begins, what you actually believe about technology's role in math teaching and learning. There are no right or wrong answers here — this is a starting point, not a test.

Instructions:

  1. Write a 300–500 word reflective essay on your personal philosophy of technology integration in mathematics education. Consider: What role should technology play in a math classroom? What excites you about it? What worries you? What experiences — as a student or observer — shaped this view?
  2. Be honest and specific rather than diplomatic. A genuinely uncertain or even skeptical essay is scored the same as an enthusiastic one — this is about depth of self-examination, not the "correct" stance.
  3. Submit your essay. Keep a copy for yourself — you'll be asked to reread and respond to it in Week 12, as a "bookend" to your Capstone.
CriterionMeets (10)Partial (5)Not Yet (0)
Essay is substantive and complete (300–500 words)
Reflects specific personal beliefs, not generic statements
Shows genuine self-examination, not a surface-level answer

Mission2 — GeoGebra Micro-Build

Due Thu, Oct 1 · 23:59 Week 2

Time: ~45 min

Builds on: — independent; pick any concept.

Objective: Build one small dynamic-geometry object illustrating a single concept from your chosen grade band (elementary, middle, or high school).

Instructions:

  1. Pick a concept (e.g., slope, angle bisector, function transformation).
  2. Build a GeoGebra sketch with at least one slider or draggable point.
  3. Write a 3–4 sentence "what should a student notice" note: what should they see happen as they drag or move the slider, and what mathematical idea does that reveal?

Submit your GeoGebra sketch's public share link (File → Share → Copy link), not just a screenshot — check the link works in a private/incognito tab first.

CriterionMeets (10)Partial (5)Not Yet (0)
Sketch runs and illustrates the concept
At least one interactive element (slider/drag)
Noticing note is specific and accurate

Mission3 — AI Worksheet Critique

Due Mon, Oct 12 · 08:00 Week 3

Time: ~45 min

Builds on: — independent; a new concept of your choice.

Objective: Practice directing AI rather than accepting its first answer — and see how a general-purpose model compares to a purpose-built teaching tool.

Instructions:

  1. Write one prompt asking for a short, two-tier differentiated worksheet for a math concept of your choice. Run that exact same prompt in both a general AI chat tool (e.g., ChatGPT, Gemini) and coteach.ai.
  2. Check both tiers of both outputs for mathematical accuracy.
  3. Write a short comparison: how did the two outputs differ in accuracy, differentiation quality, and usefulness to you as a teacher? Then write 3 specific edits you made (or would make) to the version you'd actually use, and why.

Share the link/export of both AI conversations if the tool supports it — check it's viewable in a private/incognito tab before submitting.

CriterionMeets (10)Partial (5)Not Yet (0)
Both AI outputs included (general LLM + coteach.ai)
≥ 3 specific, correct edits identified, with a real comparison of the two tools
Edits show pedagogical reasoning, not just wording

Mission4 — CODAP Mini-Investigation

Due Mon, Oct 19 · 08:00 Week 4

Time: ~45 min

Builds on: — independent; a new dataset.

Objective: Ask one data question and let CODAP help answer it.

Instructions:

  1. Open a provided (or self-chosen) small dataset in CODAP.
  2. Build one graph.
  3. Write one data-based claim and the specific evidence for it: what exactly in the graph supports your claim, and what would change your mind?

Submit your CODAP document's public share link, not just a screenshot — check the link works in a private/incognito tab first.

CriterionMeets (10)Partial (5)Not Yet (0)
Graph correctly represents the data
Claim is specific and data-based
Evidence correctly cites the graph

Mission5 — Differentiation Mini-Task

Due Mon, Nov 9 · 08:00 Week 7

Time: ~45 min

Builds on: Mission 2, 3, or 4 — required; pick one of those to extend.

Objective: Use AI to generate two tiers of one task, then verify them.

Instructions:

  1. Pick a task you built in Mission 2, 3, or 4.
  2. Prompt AI for a scaffolded version and an extension version.
  3. Verify both mathematically. For each version, answer: which UDL principle (representation, action & expression, or engagement) does it reflect, and specifically how?

Share the AI conversation link alongside your two versions if possible — check it's viewable in a private/incognito tab.

CriterionMeets (10)Partial (5)Not Yet (0)
Both tiers present and mathematically correct
UDL principle correctly named for each tier
Scaffolding/extension choices are pedagogically sound

Mission6 — AI Formative-Assessment Mini-Task

Due Mon, Nov 16 · 08:00 Week 8

Time: ~45 min

Builds on: — independent; a new concept of your choice.

Objective: Generate and vet a short formative check with AI.

Instructions:

  1. Prompt AI for a 3-question exit ticket on a concept of your choice.
  2. Solve all 3 yourself; flag and fix any AI errors.
  3. Write specifically what the results would tell a teacher to do next: if most students missed question 2, what's the concrete next instructional move?

Share the AI conversation link if possible — check it's viewable in a private/incognito tab.

CriterionMeets (10)Partial (5)Not Yet (0)
3 relevant, correctly-leveled questions
Your solutions are correct; AI errors caught
Next-step response is instructionally specific

Mission7 — Computational Thinking Mini-Task

Due Mon, Nov 30 · 08:00 Week 10

Time: ~45–60 min

Builds on: — independent; a new procedure.

Objective: Translate one mathematical procedure into an algorithmic, step-based form.

Instructions:

  1. Pick a procedure (e.g., long division, the quadratic formula).
  2. Write it as a numbered algorithm or a simple GeoGebra/CODAP script.
  3. Name one computational-thinking practice it uses — decomposition, abstraction, pattern recognition, or algorithm design (Weintrop et al., 2016).

If you build this in GeoGebra or CODAP, submit the public share link — check it's viewable in a private/incognito tab.

CriterionMeets (10)Partial (5)Not Yet (0)
Steps are correct and complete
CT practice correctly named and justified
Representation is clear enough for a peer to follow

Major1 — Digital Toolkit Portfolio (150 XP)

Due Mon, Oct 26 · 08:00 Week 5 (work session Thu, Oct 22)

Est. time: ~2–3 hours (built from Missions 1, 2 & 4, not from scratch)

Builds on: Missions 1, 2, and 4 — required; this task revises and compiles them.

Objective: Show growth across GeoGebra, CODAP, and AI-assisted design by revising and curating your best work so far.

Instructions:

  1. Choose your strongest artifact from Mission 2 (GeoGebra), Mission 4 (CODAP), and one AI-assisted piece (Mission 1 or 3).
  2. Revise each using at least one piece of feedback you received.
  3. Write a ~400-word rationale: what each tool contributes that the others don't, and how you'd sequence all three in a real unit.
  4. Submit one entry in your shared Google Drive folder: 3 revised artifacts (public share links where applicable) + the rationale.

Rubric (150 XP total — enter the number that fits each row, then add):

CriterionExemplaryProficientDevelopingIncomplete
GeoGebra artifact quality & visible revision4030200
CODAP artifact quality & visible revision4030200
AI-assisted artifact quality & visible revision3526170
Rationale compares all three tools with genuine understanding3526170

Major2 — AI Professional Ethics & Practice Portfolio (180 XP)

Due Mon, Nov 23 · 08:00 Week 9

Est. time: ~3 hours, built up across the semester (not written the night before)

Builds on: your cumulative AI Usage Log since Week 1, plus any prior AI-assisted artifact you choose to formalize.

This is the course's signature AI assessment — it exists specifically to show that a student can use GenAI as a math-teaching collaborator professionally, transparently, and ethically, not just competently.

Components (submit as one entry in your shared Google Drive folder):

  1. AI Usage Log — a running table kept since Week 1: tool used · purpose · one key prompt · what you changed or verified afterward. Update it weekly rather than reconstructing it at the end.
  2. Annotated AI-Assisted Lesson Artifact — one lesson resource (activity, assessment, or task) that is clearly AI-co-created, with annotations showing exactly which parts came from AI, which you changed, and why. Share the AI conversation's public link alongside the artifact where possible.
  3. Professional Ethics Reflection (~1 page) answering:
    • a) One place the AI's output was wrong or biased, and how you caught it.
    • b) One ethical boundary you would set for your own future students' AI use.
    • c) How you would explain your AI-assisted planning to a parent or principal.

Rubric (180 XP total):

CriterionMeetsPartialNot Yet
AI Usage Log is complete and specific across the semester40200
Lesson artifact is instructionally sound and mathematically accurate40200
AI's contribution vs. your own editing is clearly, honestly annotated40200
Reflection identifies a real AI error/bias and how it was caught30150
Reflection sets a concrete, defensible ethical boundary30150

Major3 — Capstone: AI-Integrated Unit & Public Defense (180 XP)

Due Mon, Dec 14 · 08:00 unit plan + Philosophy Bookend, Week 12 Defense Thu, Dec 17 Week 13

Est. time: ~4–5 hours across Weeks 10–12, plus the Week 13 defense

Builds on: the Weeks 10–12 backward-design work and the Week 11 Guild Critique peer feedback — required. Also builds on Mission 1 for the Philosophy Bookend component (required — revisit and compare).

Pursuing a master's or other graduate degree? Talk to me in the first two weeks — this Capstone can be adapted into a paper or a component of your own research or manuscript instead of the standard K–12 unit plan.

Objective: Independently design, and publicly defend, a short (2–3 lesson) AI-integrated mathematics unit that treats GenAI as a genuine collaborator.

Components:

  1. A unit plan: learning goals, lesson sequence, at least one GeoGebra resource and one CODAP-or-AI-generated resource.
  2. An AI-usage statement (per Syllabus Section 5).
  3. Incorporation of the peer feedback received at the Week 11 "Guild Critique."
  4. A Philosophy Bookend (~1 page): reread your Mission 1 reflective essay from Week 1, then write about how — and whether — your philosophy of technology integration has changed across the semester. Be specific about what shifted and what didn't.
  5. An 8–10 minute public defense/presentation with Q&A on Week 13, Thursday (Dec 17).

Rubric (180 XP total):

CriterionPoints
Unit coherence & standards alignment0–35
Integration quality of GeoGebra/CODAP0–30
AI used as collaborator — documented, ethical, verified use0–30
Incorporation of Week 11 peer feedback0–25
Philosophy Bookend — genuine, specific revisiting of Mission 10–25
Defense: clarity + handling of Q&A0–35