Part 1 of 5

Introduction & System Overview

โฑ 15 minutes 9:00 โ€“ 9:15 Presenter-led
Right now ยท 15 minutes
Listen. You'll need these ideas in Part 2, when you work as a student.
  1. Cognitive bypass: the problem
  2. Piaget and Vygotsky: why the struggle and the talk matter
  3. Four design principles, roles, and turn-taking
  4. Accept or revise: how the AI responds
  5. The epistemic trace: same answer, different reasoning
Not logged in yet? Connect to Wi-Fi and log in at colearn-ai.com with the student account on your card now.
The Problem

Cognitive Bypass

When a student asks an LLM "what does range(1, 5) print?", the model answers immediately and correctly. The student copies the answer. Their assignment is done, but the confusion that would have driven learning never happened.

Definition: Cognitive Bypass A correct result appears without the learner engaging in the reasoning the result is meant to reflect. The assessment signal weakens, and the learning process may disappear entirely.

Cognitive bypass is not cheating in the traditional sense. It is a structural property of LLMs that removes the need to resolve uncertainty before getting an answer. This is fundamentally different from a textbook or a search engine, both of which still require the student to identify what they need and synthesize it.

Why it matters for computing education specifically: prediction, explanation, debugging, and reflection are the core cognitive acts that build durable programming knowledge. Each of these can now be bypassed.


Learning Theory

Why the Cognitive Work Matters

Piaget: Learning Requires Productive Struggle

Learners build understanding by revising mental models that no longer fit experience. The discrepancy between what was expected and what actually happened is productive, but only when the learner must explain it themselves.

A Classic CS1 Example

A student sees for i in range(1, 5): and predicts it will print 1 2 3 4 5. They run the code. It prints 1 2 3 4. Conflict! The discrepancy is productive: if the student must explain why 5 is missing, they restructure their mental model of how range() works.

An instant answer from an LLM removes the need to resolve the uncertainty. The struggle, and the learning, never occurs.

Vygotsky: Learning Develops Through Social Interaction

Students can reach understanding through peer dialogue and mutual scaffolding that they may not reach alone. When one student says "I think range runs five times" and another says "I ran it and it stopped at 4, so let's change the numbers and see," the conversation is the learning.

The Risk

When a single student prompts an LLM and shares the answer, the social construction of meaning collapses. AI becomes the reasoning partner, and peer dialogue, Vygotsky's engine of learning, is reduced or eliminated.

Both Mechanisms Are Bypassed by LLMs

Piaget

What learning requires: Difficulty creates cognitive conflict and restructuring.

What bypass removes: AI resolves the difficulty before the learner must make sense of it.

Vygotsky

What learning requires: Peers explain, challenge, and scaffold one another.

What bypass removes: AI becomes the primary reasoning partner, reducing peer dialogue.


Design Response

System Design Can Make Reasoning Necessary

The solution is not to ban AI. It is to design environments where AI cannot remove the cognitive and social processes that make learning happen.

Preserve Productive Struggle

Require predictions, explanations, and revisions before progress is possible.

Preserve Social Reasoning

Structure participation so students construct answers together: roles, turn-taking, shared submissions.

Constrain AI Feedback

Use prompts and questions that guide reasoning without supplying complete solutions. One nudge at a time, never the answer.

Preserve the Process

Retain attempts, feedback, code, output, and participation history in an append-only epistemic trace.

These four principles become interaction rules enforced by the platform, not left to individual students to follow voluntarily.


Pedagogy

POGIL: Roles That Distribute Responsibility

coLearn-AI is built around Process Oriented Guided Inquiry Learning (POGIL): students work in small groups with defined, rotating roles on a structured inquiry activity. Roles rotate so every student develops all four skill sets over time.

๐ŸŸข

Facilitator

Keeps the group on task. Watches the clock. Makes sure every voice is heard.

๐Ÿ”ต

Spokesperson

Speaks for the group: reports its answers and questions to the instructor and the room.

๐ŸŸฃ

Quality Control

Checks accuracy and understanding before submission. Catches errors the group misses.

๐ŸŸก

Process Analyst

Reflects on group process and dynamics. Reports on how the team worked together.

In coLearn-AI, only one student at a time can type. That student holds the turn. After each submission the turn passes to the next member, so everyone takes a turn at the keyboard. The rest of the group takes part by discussing, not by typing. The platform enforces this.

The platform also assigns roles, in this order: Facilitator, Process Analyst, Quality Control, and then Spokesperson. A group of three therefore has no Spokesperson. Roles are about how each person contributes. They are separate from who holds the typing turn.

Why POGIL + AI? POGIL gives structure. Roles distribute accountability. The AI then operates within that structure, nudging the group's reasoning rather than bypassing it. This is what coLearn-AI enforces: fixed group roles, rotating submission control, questions before solutions, constrained AI feedback, and an append-only interaction history.

The Platform

How coLearn-AI Scaffolds a Group

When a group submits an answer, the AI does one of two things: it accepts the answer, or it sends it back for revision with one focused question. It never gives the answer. Here is the same question answered three different ways.

The Question
Write a range() call that produces the values 3, 6, 9, 12, 15, 18.
Starter code given to the group: for value in ___________:
    print(value)
โœ… Accept

Group submits:

CoLearn-AI responds:

"That works: range(3, 19, 3) starts at 3, steps by 3, and stops before 19, so 18 is the last value printed. Move on to the next question."

The response is correct. The group advances.

๐Ÿ’ฌ Revise: Almost There

Group submits:

CoLearn-AI responds:

"Your start and step look right. Does range(3, 18, 3) include 18 in the output? Try it and check."

Off by one: stop is exclusive. One question, no answer given. The group must figure it out.

โš ๏ธ Revise: Wrong Approach

Group submits:

CoLearn-AI responds:

"The question asks for a range() call. Can you rewrite this so range() generates those values instead of a literal list?"

Wrong approach entirely, so the answer is sent back. The author sets how many tries a group gets. After those, the group may press Continue, and the trace records that it moved on without acceptance.

The AI's job is not to grade. It is to keep the group thinking. It targets one issue at a time and never gives the answer.

Not just for computer science The same accept-or-revise cycle works in any field: economics, chemistry, history, biology, digital humanities, and more. See examples from other disciplines โ†—

Key Feature

The Epistemic Trace

Every interaction (submissions, AI feedback, revisions, code runs, and optional follow-up) is appended to a per-group, per-question record. Nothing is overwritten. The AI sees the full reasoning path when evaluating each new submission. Instructors see the process, not just the product.

Every interaction is recorded in sequence: submissions, AI responses, revisions, code runs, follow-up. The trace grows however the group's work actually unfolds; there is no prescribed structure. Some common patterns:

Pattern 1: Direct Accept
Submit range(1, 6)
Accept "Correct: range(1, 6) produces 1 through 5, stopping before 6."

Two events. The group understood the concept, submitted a correct answer, and moved on. The trace is short by design, and that is informative too.

Pattern 2: Sent Back, then Revised
Submit range(1, 5)
Sent back "Does range(1, 5) include 5 in the output? Try it and check."
Revise range(1, 6)
Accept "Yes, the stop value is excluded, so 6 is needed to include 5."

The classic off-by-one path. The AI's question kept the group thinking; the trace records exactly where the misconception was corrected.

Pattern 3: Predict then Submit
Predict "We think it prints 1 2 3 4 5, five numbers."
Run Output: 1 2 3 4
Revise "range(1, 5) stops before 5. Output is 1 2 3 4."
Accept "Correct. And did the output match your prediction?"

The prediction was wrong; running the code created Piaget's productive conflict. The trace shows the exact moment the mental model was revised.

Pattern 4: Several Rounds of Revision
Submit [1, 2, 3, 4, 5]  (literal list, not range)
Sent back "The question asks for a range() call. Can you rewrite this?"
Revise range(5)
Sent back "range(5) starts at 0. How do you make it start at 1?"
Revise range(1, 6)
Accept "Yes, range(1, 6) gives 1 through 5."

Three separate misconceptions surfaced and resolved. No single final answer would show any of this. The trace is the evidence of learning.

Any combination is possible: questions without predictions, questions with code execution before submission, questions with follow-up commentary after acceptance. The trace captures all of it.


Same Answer, Very Different Reasoning

The trace's power is clearest when two groups arrive at the same final answer by completely different paths.

Group A
Predict "Prints 1 to 5."
Submit range(1, 5)
Sent back "Check if 5 appears in the output."
Revise range(1, 6)
Accept "Correct."
Group B
Predict "Stops at 4 or 5? Not sure, so let's use 6 to be safe."
Submit range(1, 6)
Accept "Correct."
Final answers: identical. Traces: completely different. Group A held a confident misconception, had it surfaced when the AI sent the answer back, and corrected it. Group B guessed correctly without fully resolving the question. Grading the output reveals nothing. The trace reveals everything.

Feedback from this workshop matters. Your experience today (what works, what confuses, what feels off) is exactly the kind of signal that shapes the next iteration. Please share it.