Category: AI Literacy

Last fact-check: May 25, 2026

This is a hard article to write because it has to do two things at once. It has to take seriously the gravity of getting caught using AI to do work you submitted as your own. And it has to take seriously that the student who got caught is still a person, still has an education in front of them, still has the question of what to do next. Articles that only do the first thing become lectures. Articles that only do the second thing become evasions. Both failures are common. I’ll try to avoid both.

The walkthrough follows one fictional student, Jordan, through the process and the year that follows. The student is a composite, drawn from documented patterns in institutional academic integrity processes and academic literature on student responses to violations. The situation is real for many students at CSU and at similar institutions right now.

This is part of Tygart Media’s free AI Literacy curriculum at tygartmedia.com/category/ai-literacy. The pillar is here.

---

The student

Jordan is a second-year communications major. The course is a 200-level writing course required for the major. The assignment was a 6-page persuasive essay on a contemporary issue. Jordan had a busy week — work shifts, a sick parent, a midterm in another course — and started the essay the night before it was due. The first three pages were Jordan’s own, written from scratch, slow going but real work. Around 2 a.m., Jordan pasted what they had into ChatGPT and asked it to “continue this essay in the same voice” to finish the remaining three pages. The model produced something passable. Jordan made a few edits, ran it through Grammarly, and submitted.

The professor’s AI policy permitted AI for grammar checking and concept exploration. It did not permit AI to draft submitted text. Jordan knew this. The decision to use AI to finish the essay was not a misunderstanding of the policy. It was a calculated risk taken under exhaustion. Jordan was hoping the AI-written sections would blend with the human-written sections well enough that nothing would be flagged.

They didn’t blend. The professor read the essay and noticed a tonal shift around page three — the prose became smoother, more abstract, less specific. The professor didn’t run it through a detector. They just read it carefully a second time, then a third, then composed an email asking Jordan to come to office hours.

The conversation Jordan was not prepared for

In the office, the professor did not accuse. She showed Jordan the essay with the tonal shift annotated. She asked Jordan to read the two sections out loud and reflect on what they noticed. She did not ask whether Jordan used AI. She asked Jordan to explain the argument in the second half of the essay — to walk through, in their own words, what the essay was claiming and why.

Jordan tried. The first half came easily; Jordan had written it. The second half did not. Jordan could read the words on the page but could not explain why the second half made the argument it made, or what evidence the AI-written sections were drawing on. After a few minutes of trying, Jordan stopped.

The professor was patient. She said: “I think you used AI for part of this. I’d like you to tell me what happened.”

Jordan told her.

The institutional process, named clearly

What happens next varies by institution. Most universities have a formal academic integrity process with specific steps. The CSU system has system-wide policies that interact with campus-level processes. Most processes share certain features:

The professor’s decision about whether to escalate. Some institutions require professors to report all suspected violations. Others give professors discretion to handle minor or first-time violations informally. The professor’s choice here matters significantly.

Informal resolution, if available. In the version some schools use, the professor and student can agree to a resolution — often involving a grade penalty on the assignment, sometimes a failing grade for the course, sometimes an educational requirement like a workshop. The student admits the violation in writing. The record stays within the course or department.

Formal hearing, when escalated. When the violation is serious enough, or when the student disputes the accusation, or when institutional policy requires it, the process moves to a formal hearing. A panel — typically faculty, administrators, and sometimes student representatives — reviews evidence, hears the student’s account, and makes a finding. Sanctions can range from a warning to a course failure to suspension to expulsion, depending on the violation and the institution.

Jordan’s professor offered informal resolution. The professor’s proposal: the essay would receive a zero. Jordan would re-write the essay from scratch, with no AI use, for no additional credit beyond the demonstration that they could do the work. Jordan would write a brief reflection on what happened and what they intended to do differently going forward. A note would go in the student’s department file but not in the formal academic integrity record. The course grade would suffer but not catastrophically.

This was a relatively merciful outcome. Many professors would have escalated. Some institutions don’t permit informal resolution at all. The fact that Jordan got the informal version is partly luck and partly that the professor exercised judgment — the professor knew Jordan was a second-year student, knew the violation was a one-time bad-night decision, judged that the educational value of the informal process exceeded the deterrent value of formal sanctions.

This is not a guide to expecting that outcome. Many students don’t get it. The point of naming what happened in Jordan’s case is that the process has variation built into it, and the student does not control the variation.

What Jordan did right in the conversation

There are a few things Jordan did that affected how this resolved. Worth naming, because some students caught in similar situations make worse versions of these choices.

Jordan stopped trying to bluff once the bluff stopped working. The early seconds of the office hour conversation were when Jordan was still trying to explain the second half of the essay. Jordan could have continued. Some students do — they invent reasoning, double down, claim they wrote everything. This rarely works in the room and almost never works under follow-up. It also forecloses every off-ramp the professor might otherwise offer.

Jordan didn’t argue with the policy. When confronted with the violation, Jordan didn’t say “AI use is normal now,” “everyone does it,” or “the policy is unfair.” All of these may be partially true. None of them help a student in the moment of being caught. The professor wasn’t litigating the broader culture. She was discussing one specific essay.

Jordan didn’t blame circumstance. Jordan had real reasons — the work shifts, the sick parent, the midterm. These reasons were real. They were not the reason Jordan made the decision to use AI improperly. Other students in similar circumstances make different decisions. Jordan made the decision Jordan made. Owning that, rather than displacing the responsibility onto circumstance, is what made the rest of the conversation possible.

Jordan didn’t promise too much. When asked what would be different going forward, Jordan didn’t promise to never use AI again, never have a bad night again, always be a perfect student. Those promises don’t hold and the professor knew it. Jordan said something closer to: “I made a bad call. I’m going to figure out what to do when I have another bad night so I don’t make the same call.” That was a believable answer.

What the year that follows actually looks like

The professor’s resolution is the institutional piece. There’s a longer piece, which is what Jordan does for the next several months with the question of what happened. This part doesn’t show up on the transcript. It matters more than the part that does.

The temptation, after a violation, is to compartmentalize it. The professor accepted the resolution. The department file note will fade. The course grade is what it is. The instinct is to move on. Don’t think about it. Don’t let it define the rest of the degree.

This instinct fails. Not because the violation needs to be punished further — Jordan has already paid the institutional price. It fails because the violation revealed something about the relationship Jordan had with the education. That relationship needs to be examined or the next bad night produces the same decision.

What Jordan actually did, over the months that followed:

Jordan wrote out, honestly, what they thought their education was for. Not the official version. The honest version. Was Jordan in college to develop skills? To get credentialed? To make their family proud? To delay entering the workforce? To find out who they were? Most students would answer “all of those” — and the honest hierarchy of those answers is what determines how they relate to a difficult assignment at 2 a.m.

Jordan’s honest answer was that the credentialing piece had been doing too much of the work. The skill development had been quietly secondary. The reason it was easy to outsource three pages of an essay to AI was that the essay was a credentialing artifact in Jordan’s lived experience, not a skill-building exercise. The AI use wasn’t a moral failure separable from the rest of Jordan’s education. It was a symptom of a relationship to the education that had been growing for months.

Examining this was uncomfortable. It also turned out to be the part of the recovery that did real work.

Jordan re-engaged with what writing was supposed to be doing. The writing course existed because writing develops thinking. Not because writing produces text. Jordan had been treating writing as text production — get the words on the page, hand them in, move on. The AI did that very well, which was the whole problem.

The re-engagement happened slowly, mostly through small practices. Jordan started journaling, longhand, fifteen minutes a day. Not for school. For nobody. The journal was bad writing — repetitive, vague, full of unfinished thoughts. It was also Jordan’s writing. Doing it daily, for a month, restored the experience of writing-as-thinking that had been absent from Jordan’s school writing for years.

The next essay Jordan wrote for a class was harder than the previous ones had been. The thinking had to happen during the writing rather than being summoned afterward. Jordan resented this for the first hour or two of the work. By the end of the essay, Jordan understood why the resentment had existed — the previous version of essay-writing had been a shortcut around something the assignment was supposed to develop.

Jordan rebuilt a relationship with one professor. Not the one whose course they got caught in — Jordan finished that course and moved on. A different professor. Jordan went to office hours, not because they had a specific question, but because they wanted to be the kind of student who went to office hours. The professor was confused at first and then helpful. Over the term, the office hour conversations became substantive. By the end of the term, Jordan had a faculty member who knew them by name and could write a real recommendation letter someday.

This is not a strategic move. It’s a substantive move. The reason students get caught using AI improperly is often that they’re functionally invisible to their professors, which makes the work feel disposable, which makes shortcuts feel low-cost. Becoming visible to one professor is one of the most efficient ways to change the relationship to the education.

Jordan developed an actual approach to AI. Not “never use AI” — that wasn’t going to hold and wasn’t what the situation called for. Jordan worked through, deliberately, the line between use that was helpful and use that was substitutive. Jordan started using AI for some things and not others. Jordan got better at noticing when they were tempted to cross the line they’d drawn, which usually happened during exactly the kind of bad nights that had produced the original incident. Jordan developed a rule: when tempted to outsource real work to AI, do something else for an hour and come back to it. Sometimes the work happened in the hour. Sometimes Jordan turned the assignment in late and took the penalty. The penalty was always smaller than the cost of being caught again would have been.

This is not a heroic outcome. Jordan still procrastinates. Jordan still occasionally has bad nights. The difference is that Jordan now knows what bad nights cost when they involve AI shortcuts, and that knowledge changes the calculation.

The transcript question

Practical matter that students in Jordan’s situation worry about, often more than anything else: what does this do to the transcript, the grad school application, the future job?

Honest answer: less than students fear, but not nothing.

For an informal resolution like Jordan’s, with a note in the department file but no formal record: this typically doesn’t appear on transcripts and is not disclosed to grad schools, employers, or other parties unless the student explicitly authorizes a release. The note becomes practically invisible after graduation.

For a formal violation with a finding: this varies by institution. Some institutions place a notation on the transcript that fades after a period of clean conduct. Some require disclosure on grad school applications that ask about disciplinary history. Some don’t appear on transcripts but appear in the institution’s internal records that get pulled if a future student conduct issue arises.

For an expulsion: this almost always appears, in some form, on future transcripts and applications.

The honest framing: a single, addressed, learned-from violation does not end most students’ academic futures. The graduate school admissions committee looking at an application from a student with one academic integrity incident from second year, followed by three years of clean record, can read the situation. The committee that cannot read the situation is rare. The student who has actually done the recovery work — who can articulate what happened, what they learned, what they do differently — is a stronger candidate than the student who pretends it didn’t happen.

What does end an academic future is the pattern. The student who has multiple incidents, or who denies the incidents that exist, or whose record shows that the lesson did not land — that student has a real problem. The student who got caught once, owned it, and demonstrably changed — that student has a story to tell, and the story can be told well.

What this article cannot solve

Some things to name as limits.

This article cannot tell you what your specific institution’s process is. Read your student handbook. Find the academic integrity policy. Know the steps. The process this walkthrough described is one common pattern, not the universal pattern. Some institutions are harsher. Some are more procedural. Some have changed their policies recently in ways that haven’t been well-communicated. The institutional research is your responsibility.

This article cannot give you good advice if you are already in the middle of a formal hearing. The dynamics there are different — there are evidence questions, procedural questions, sometimes legal questions. A campus ombudsperson, student advocacy office, or, in serious cases, an attorney experienced in academic affairs can help. This article is about the period before that and the period after. The hearing itself is a specialized situation.

This article cannot tell you whether to confess if you have not yet been caught. That is a decision involving your own values, your assessment of the risk of being caught later, your relationship with the professor, and considerations this article cannot weigh for you. If you are considering it, the campus ombudsperson and student affairs office can sometimes provide confidential conversations. The conversation with a trusted advisor before the conversation with the professor is often valuable.

This article cannot prevent the next bad night. Bad nights are a feature of being a person in school. The work this article is suggesting is not to never have bad nights. The work is to develop a relationship with your education such that the bad nights do not produce the same bad decisions.

What I’d want to hear from students who have been through this

What I don’t fully know, that students who have been through some version of this could fill in:

• What was the institutional process actually like — better or worse than expected? What surprised you?
• What did your professor do that helped? What did they do that made it harder?
• What advice would you give a friend who just realized they’re going to be called into office hours?
• What did you do in the months after that actually worked? What didn’t?
• How has this affected your relationship with your education a year or two later?
• Are you glad you got caught? Why or why not?

This last question is not rhetorical. Many students who have been through some version of Jordan’s situation say, later, that they are glad it happened. Not because the violation was good, and not because the consequences were small. Because the incident forced an honest reckoning with the education that wouldn’t have happened otherwise. That reckoning is the part of college that produces the actual education, and many students go through college without it.

This is not an argument for getting caught. It’s an observation that recovery is real, and that the recovery can produce something the previous path was not producing. The students who do the recovery work end up better educated, often by a lot, than they would have been without the incident.

The closing thought

The CSU rollout has produced a literacy gap and an integrity gap at once. The two are connected. Students using AI to do work they don’t understand how to do are not really cheating their professors. They are cheating themselves — out of the development that the assignment was supposed to produce. The professors have a role in catching this. The institution has a role in providing the conditions where the work feels valuable enough to do. The student has a role too. None of the roles can fully substitute for the others.

If you have used AI in ways you shouldn’t have and have not been caught, this article is not telling you to confess. It is asking you to consider what the use is doing to your relationship with your education, and what you might do about it before the question is forced by someone else.

If you have been caught, the institutional process is the smaller part of the recovery. The larger part is the work Jordan did over the year that followed. That work is available to you, regardless of how the institution resolved the violation. The institution cannot do it for you. Nobody can. But the work itself is doable, and the people who do it end up in a different relationship with their education than they had before.

The education is still recoverable. Not the version of the education that was on the trajectory before the violation — that trajectory is changed, and pretending otherwise is itself a kind of dishonesty. But an education that does what college is supposed to do. That version is still available, and is in fact more available, to the student willing to do the harder work that the incident has now made impossible to avoid.

---

About this knowledge node: This is a cluster article in Tygart Media’s AI Literacy content sprint. It’s licensed for use in any classroom, training program, custom GPT, or Claude Project as long as attribution is maintained. The pillar article that introduces the sprint is here.

Last fact-check: May 25, 2026

The previous article in this curriculum walked through what AI is doing to non-native English speakers in U.S. higher education — penalizing them for the formal English they learned in school, flagging their writing as machine-generated, leaving them to navigate policies that assume native-speaker defaults. That article ended with the suggestion that there are other relationships between AI and language than the one U.S. institutions have chosen.

This article is about the largest possible counterexample: India. A country with twenty-two officially recognized languages, hundreds of others actively spoken, more than a billion people, and a relationship to English that is simultaneously historical, hierarchical, and changing fast. India is where the question “what does AI look like when designed to amplify linguistic diversity rather than penalize it” gets answered, in real time, by a billion people testing the answer.

This is a thesis piece more than a walkthrough. The CSU rollout is one story about AI and language. India is a different story. The contrast is what’s instructive. This article does not claim to be written from inside India’s lived experience — I’m an American writing from Tacoma — and the closing sections name what I can and cannot see from here.

It’s part of Tygart Media’s free AI Literacy curriculum at tygartmedia.com/category/ai-literacy. The pillar is here.

---

The setup, briefly

India has twenty-two languages listed in the Eighth Schedule of its Constitution. Hindi and English are the official languages of central government, with state governments operating in additional regional languages. Beyond the constitutional list, the 2011 census recorded 122 major languages and more than 1,600 mother tongues. Some are spoken by hundreds of millions; some by a few thousand. Many have rich written traditions going back centuries. Many are primarily oral.

For decades, the language of upward mobility in India has been English. Knowledge of English correlates with access to higher education, urban employment, international opportunities, and economic class. This is not unique to India — many post-colonial countries have similar dynamics — but in India it produces a specific friction. A young person in a Bhojpuri-speaking village in eastern Uttar Pradesh might be cognitively brilliant and economically excluded, because the on-ramps to opportunity require English, and English is something acquired through schooling that village families often cannot afford.

AI changes this picture, potentially significantly. Whether it changes it for better or worse depends on which version of AI gets built, who builds it, and who it’s built for.

The version of AI that hurts Indian linguistic diversity

Start with what happens by default. Large language models are trained on text. The text on the internet is overwhelmingly in English. The text in other languages is heavily concentrated in major European and East Asian languages — French, Spanish, German, Mandarin, Japanese — with significantly less coverage of South Asian languages, and much less of regional Indian languages.

The result is that the AI tools most people use, including in India, perform best in English, second-best in Hindi, less well in the other constitutional languages, and badly or not at all in regional languages and dialects. Bhojpuri, Marathi, Gujarati, Telugu, Tamil, Bengali — these have hundreds of millions of speakers collectively. Most do better than the smaller languages. None do as well as English.

If AI tools become the default interface to information, education, government services, healthcare guidance, and economic opportunity — and they are, fast — and those tools work best in English, then the existing linguistic hierarchy in India gets reinforced and accelerated. The Bhojpuri-speaking villager can still access the AI tool. The tool will work, badly, in their language. It will work much better if they switch to Hindi, and best of all if they switch to English. Over time, this nudges everyone toward English, in a kind of soft linguistic gravity.

This is not what happens by anyone’s deliberate plan. It’s what happens by default if AI development continues to be driven by training data availability and commercial market size in English-speaking markets. The default outcome is the erasure version. The amplification version requires deliberate choices to go differently.

The version of AI that amplifies Indian linguistic diversity

The amplification version has several pieces that are technically possible right now, some of which are already being built.

Models trained intentionally on Indian language corpora. Several efforts are underway. AI4Bharat, an academic initiative associated with IIT Madras, has been releasing models and datasets for multiple Indian languages for years. Reliance Jio’s BharatGPT effort is similar in motivation, different in execution. Sarvam AI is doing related work. The Indian government’s BHASHINI mission is investing in language technology infrastructure. None of these are at the scale of OpenAI or Google. All of them are working on the right problem.

When AI is trained intentionally on a language — its idioms, its registers, its literary tradition, its everyday speech — the resulting model can serve that language with the same fluency that English models serve English. The capability gap between, say, Tamil and English in an AI system is not a law of physics. It’s a consequence of training data and intent. Both can be changed.

Voice-first interfaces for primarily oral languages. Many Indian languages have strong oral traditions and less developed written corpora. The dominant AI interface — text in, text out — is a poor fit. Voice-first AI is a better fit. A speaker of a regional language can talk to the model in their native register, hear back in the same, and never have to confront the difficulty that their language is written less often than it’s spoken.

The technology for this exists. Speech recognition and synthesis in Indian languages have improved dramatically in the last five years. The interfaces are still primarily designed for English and Hindi, but the underlying capability is there. The question is whether the products built on top of the capability will reach the people who would benefit most.

Translation as a bridge, not a replacement. A well-designed AI translation layer lets a Marathi speaker access information originally written in English, a Telugu farmer read agricultural research from a Tamil university, a Bengali student engage with Hindi cinema scholarship. The translation isn’t pushing them toward English. It’s giving them access to the rest of the world’s information in their own language. The direction of flow matters. Translation that pulls information into local languages is amplification. Translation that pushes local-language speakers to consume English-default content is something else.

Educational tools in the medium of instruction. A student learning physics in Kannada-medium schools should be able to ask an AI tutor about Newton’s laws in Kannada, get a response in Kannada that uses Kannada-language scientific vocabulary, and be able to discuss the answer with their parents in Kannada. The current default — they ask in Kannada, the AI responds in either bad Kannada or fluent English, the parents can engage with neither — fragments the household’s intellectual life. The amplification version keeps the conversation in the language the household lives in.

Preservation work at scale. India has languages that are not endangered but are under pressure — fewer young speakers, less media in the language, narrower domains of use. AI can be part of the response. Recording, transcribing, and modeling these languages preserves them in a form that future speakers can access. This is happening for some languages. It could happen for many more.

What India has that the U.S. doesn’t, in this conversation

One thing worth saying clearly: India is not approaching this question from behind. India is approaching it from a different starting position that has some real advantages.

The U.S. is wrestling with a question that fundamentally is “how do we integrate AI into a system designed without it.” Universities, classrooms, assessment models, hiring pipelines — all of these were designed in a pre-AI era and now have to accommodate something they weren’t built for. The CSU literacy gap is one symptom of this. The detector false-positive problem affecting non-native speakers is another. The question is essentially: how do we retrofit AI into a system whose defaults are English-monoglot, native-speaker-normed, and built around the assumption that writing is the primary medium of intellectual work?

India is approaching AI from a position where many of these defaults were never settled to begin with. Multilingualism is not a problem to be retrofitted — it’s the lived condition. Voice as a primary medium of communication is not a deviation from the norm — it’s how a substantial portion of intellectual life has always been conducted. The pluralism the U.S. has to graft on, India already has.

This doesn’t mean India will get AI right. There are real challenges, including some that mirror the U.S. failures (linguistic hierarchy, urban-rural divide, caste and class access). But the starting position is different, and the people working on AI for India are working on a different question than the people working on AI for U.S. universities. The question is closer to: “how do we use this technology to honor the linguistic richness that already exists?” That’s a more interesting question than the one CSU has been asked.

The specific case of education

India’s National Education Policy 2020 explicitly endorses mother-tongue instruction in primary education and pushes the medium of instruction toward Indian languages at higher levels. Implementation has been uneven. Many private schools still teach primarily in English. Many parents prefer English-medium instruction because they read it as the path to economic opportunity. The policy direction and the lived reality are not yet aligned.

This is the space where AI could matter most. A student in Odia-medium school instruction who needs to read English scientific literature for a college course has, historically, had to either become fluent enough in English to do the reading directly, or accept that the literature is inaccessible. AI translation collapses that gap. The student can read in Odia, take notes in Odia, ask questions in Odia, and engage with the original literature without abandoning their mother tongue as the medium of thought.

This is the opposite of what’s happening to Priya in the previous article. Priya is being penalized because her English doesn’t look casual enough. The Odia student is being given access to global scholarship without having to abandon Odia. Same technology. Different relationship.

For this to actually work at scale, the AI tools have to be built for it. Translation has to be good enough that Odia scientific vocabulary doesn’t collapse into approximate Hindi when the model can’t find the right Odia term. The interface has to be designed for students who may not have grown up with English-language computing conventions. The training data has to include enough Odia academic and scientific text to be useful. None of this is automatic. All of it is technically possible.

The economic stakes

A significant part of India’s economic development story over the last thirty years has been built on English-language services — IT, business process outsourcing, content moderation, customer service. The people in these jobs are disproportionately from English-medium schooling. The people not in these jobs are disproportionately from regional-language backgrounds, regardless of their underlying capability.

AI changes both sides of this. On one side, many English-language service jobs are being directly automated, which compresses the economic premium of English fluency. On the other side, AI tools that work well in regional languages could open white-collar work to populations who were previously excluded by language alone. A capable young person in a Marathi-speaking small town who could not previously work as, say, a paralegal because the work required English fluency may, with sufficiently good AI translation and assistance, be able to do the work in Marathi while the AI handles the English interface.

Whether this potential is realized depends on whether the tools get built for it. The tools built for the U.S. enterprise market won’t do this work. The tools that would do this work have to be built specifically for the Indian linguistic context, by people who understand that context, with sufficient resources to compete with the well-funded English-default alternatives.

This is one of the more genuinely consequential questions about AI in the 2020s. It’s not getting the same attention as the questions about AI in U.S. universities. It probably matters more.

What I can’t see from here

This article needs to admit what it can and can’t speak to. I’m an American who has worked in tech, read the relevant research, and follow the Indian AI conversation from a distance. I have not lived in India. I have not been a parent trying to decide whether to send my child to English-medium or regional-language school. I have not been a student trying to navigate the gap between my home language and the language of my coursework. I have not been a builder of Indian-language AI systems facing the actual constraints of doing that work.

Several things I’d want to know that I don’t:

• How are the existing Indian-language AI efforts actually being used, by whom, in what contexts?
• What’s the gap between the technical capability of these tools and their actual adoption?
• What are the failure modes of well-intentioned Indian-language AI projects — where have they fallen short, who has been excluded?
• How is the caste-class-language nexus playing out in access to AI tools? The amplification potential I described above assumes equitable access, which may not be the actual condition.
• How do families and communities feel about AI as a presence in their linguistic lives? Are there cultural concerns that the U.S.-default discussion doesn’t capture?
• What’s the state of indigenous language preservation work supported by AI, and what are practitioners saying about its strengths and limitations?

These questions need to be answered by people who can answer them. This article is one outsider’s framing of the contrast between the CSU story and the India story. The actual story of AI and Indian languages will be told by Indian writers, builders, teachers, students, and communities. This article is meant to point at the contrast, not to occupy the conversation.

The instructive contrast

The closing thought, which is also the connection back to the rest of this curriculum.

The CSU rollout is one possible relationship between AI and language: the institutional default treats one language as standard, treats deviation from that standard as suspect, and ends up penalizing the students whose linguistic backgrounds make them most vulnerable to false suspicion. The technology amplifies an existing inequity.

The Indian-language AI work, in its best version, points toward a different relationship: the technology treats linguistic diversity as the condition to be served, builds tools that work in many languages with comparable quality, and ends up giving access to populations who were previously excluded by language alone. The technology amplifies what was already there but underutilized.

Same technology, in some sense. Profoundly different effects, because the implementations are guided by different questions. The U.S. universities are asking “how do we keep our existing system intact in the presence of AI.” The Indian-language AI efforts are asking “how do we use AI to do something our existing systems couldn’t.” The first question produces detector false-positives on Priya’s writing. The second question produces educational tools that work in Odia.

This is not a claim that India will get AI right and the U.S. will get it wrong. Both are large, contested, unfinished projects with real failure modes. The point is that the relationship between AI and language is a choice. There is no neutral default. The version of AI that gets built reflects the values and questions of the people building it. If the values are gatekeeping and the questions are about detection, the result is what CSU has. If the values are amplification and the questions are about access, the result could be something quite different.

The CSU students filling out their AI surveys, the adjuncts redesigning their courses without compensation, the non-native speakers managing the false-positive risk — they are all paying a cost for a version of AI implementation that didn’t have to be this way. India is, in real time, demonstrating that other versions are possible. The lesson is for the U.S., not the other way around.

What this article cannot solve

This article cannot tell you what to do about any of this if you’re in U.S. higher education. The contrast between the two situations is useful for understanding, but the local situation is what it is — your students are not in Mumbai, your institution is not the Indian Education Ministry, your context is the CSU context whether you like it or not.

This article cannot speak for India or Indians. It points at work being done by Indian researchers, builders, and institutions, but it does not represent that work or speak with the authority of people doing it.

This article cannot resolve whether AI will, in the end, amplify or erase linguistic diversity in any given context. That depends on choices that have not yet been made, by builders who have not yet built, in communities who have not yet adopted. The framing offered here is hopeful about what’s possible. It is not predictive about what will happen.

What this article can do is open a conversation that the CSU-centric framing of this curriculum has so far mostly closed: the question of what AI looks like when it’s not designed for the institutional contexts of U.S. higher education. The answer to that question is currently being built, mostly outside the institutional centers of AI development, mostly by people whose work is not getting the funding or attention of the OpenAI deals and the university partnerships. That work matters more than this article can convey. The least this article can do is point at it.

---

About this knowledge node: This is a cluster article in Tygart Media’s AI Literacy content sprint. It’s licensed for use in any classroom, training program, custom GPT, or Claude Project as long as attribution is maintained. The pillar article that introduces the sprint is here.

Last fact-check: May 25, 2026

One of the cruelties of how AI has been rolled out in higher education is that the students who would benefit most from it are the ones being hurt most by the policies built around it. This is not a side effect or an unfortunate edge case. It’s a structural feature of how the institutions and the detection tools and the syllabus statements have been designed, almost entirely by and for native English speakers, in ways that pattern-match against the students who most need an accommodation.

This article walks through one fictional student’s situation. The student is composite — drawn from documented patterns in CalMatters reporting, academic research on AI detection bias, and the CSU systemwide survey data — but the situation is real. Most non-native speakers in U.S. universities will recognize at least one of the dynamics described.

This is part of Tygart Media’s free AI Literacy curriculum at tygartmedia.com/category/ai-literacy. The pillar is here.

---

The student

Priya Sharma is a third-year economics major at a public university in California. She grew up in Pune, India, in a Marathi-speaking household, with Hindi as her second language and English taught in school from a young age. She’s been studying in English-medium settings since she was seven. By any reasonable measure she is fluent in English. She also writes English the way a person whose first language was something else writes English — with occasional syntactic choices that read as slightly formal, occasional vocabulary that comes from reading more than from native speech, and a comfort with certain academic registers that pattern-matches against, of all things, AI output.

This is the trap. AI chatbots, trained heavily on academic and formal text from across the internet, produce writing that often resembles the writing of people who learned English through formal instruction in non-Anglophone countries. The textbook-influenced, slightly elevated, comma-heavy prose of a well-educated non-native speaker — Priya’s prose — looks a lot like ChatGPT’s prose. Not because she’s using ChatGPT. Because she and ChatGPT learned English in structurally similar ways: from documents, formally, with attention to grammar and structure that most native speakers can afford to ignore.

Priya is doing well in her courses. She also has, in her three years, been falsely accused of AI use three times. Once on a paper she wrote in a single sitting, longhand, in her notebook before typing up. Once on a take-home midterm she wrote with her professor’s office door visible from her library carrel. Once on an in-class essay where she was the only student to finish in the time allotted. The cumulative effect is that she now spends real cognitive effort, every time she submits anything, on trying not to sound too good — which is its own kind of compromise of her education.

The detection problem, named directly

The first piece of the situation Priya is navigating is that automated AI detection tools — TurnItIn’s AI detector, GPTZero, Copyleaks, and others — produce false positives on non-native English writing at rates well above their rates for native English. The pattern has been documented in academic research and in journalistic coverage of CSU and other institutions’ deployments.

The reason is not mysterious. The detectors are looking for patterns associated with AI-generated text: certain kinds of grammatical regularity, certain vocabulary distributions, certain sentence-length variance patterns, certain stylistic markers of careful writing. These patterns occur in AI text because AI learned them from formal writing. They also occur in the writing of people who learned English formally, including but not limited to: international students, students from former British colonies whose English education was rigorous, students from immigrant families where English was the second household language, and students who simply read a lot of academic writing.

The false positive isn’t a measurement error in the strict sense. It’s the detector working as designed, on a population the detector was not designed to evaluate fairly.

The CalMatters reporting on TurnItIn’s AI detector covered this in some detail. The detectors don’t work reliably overall, but they fail in patterned ways, and the pattern correlates with linguistic background. The students most likely to be falsely flagged are the students whose institutional position is most vulnerable to being flagged.

The classroom problem, named directly

The second piece of the situation is that classroom AI policies, even when well-intentioned, often don’t account for non-native speakers.

The standard policy in many redesigned courses — including in the Elena Marquez walkthrough in this curriculum — permits AI for grammar checking on student-drafted text. This sounds neutral. In practice, it raises a question native speakers don’t have to answer: at what point does grammar correction become text generation?

A native speaker who runs their paper through Grammarly to catch typos is doing what the policy permits. A non-native speaker who uses ChatGPT to ask “is this sentence grammatically correct” is also doing what the policy permits. A non-native speaker who pastes a paragraph and asks ChatGPT to “fix any grammar issues” is in a gray zone — the corrections might be minor, or they might rewrite half the sentences. A non-native speaker who pastes a paragraph and asks ChatGPT to “make this sound more natural in English” is doing something that might cross the line, depending on how the professor reads the policy. None of these uses are dishonest. All of them might be flagged.

The policy was written for the median student. The median student is a native English speaker. The non-native speaker has to figure out where the policy actually draws the line for them, often without being able to ask the professor, often without office hour time to discuss it, often with the well-founded fear that asking too many questions will mark them as the kind of student who needs AI to write — which they may or may not actually be.

The legitimacy problem, named directly

The third piece is the hardest to talk about. There’s a strain of academic culture in which using any AI assistance to improve English writing is treated as suspect, on the theory that the student should be writing what they can write without help.

This sounds rigorous. In practice it imposes a writing standard on non-native speakers that native speakers don’t have to meet. Native speakers grew up surrounded by English. They got, free of charge, the immersion that non-native speakers have to construct through formal education. A native speaker writing without AI is drawing on a lifetime of free instruction. A non-native speaker writing without AI is, in many cases, writing without access to a resource that would partially close the gap their native-speaker classmates never had.

This is not an argument that all AI use is fine. It is an argument that “no AI assistance at all” is a different policy for different students. For a native speaker, it’s a constraint that affects polish. For a non-native speaker, it’s a constraint that affects whether the writing communicates the ideas at all.

A defensible policy needs to account for this. Many don’t.

What Priya actually does

Given the situation, the strategies Priya has developed — and that other non-native speakers in similar positions could consider — are partly defensive and partly substantive. Here is what she actually does, with the honest tradeoffs named.

She documents her drafting process compulsively. She uses Google Docs for almost everything because it preserves version history. She writes drafts in stages with timestamps. She keeps her handwritten notes from class. She can show, on any given assignment, a paper trail of the work being hers. This is exhausting. It also saved her in one of the three false-positive incidents, when the professor reviewed the version history and saw the paper being built from scratch over a week.

The tradeoff: she’s spending mental energy on documentation that her native-speaker classmates aren’t spending. It’s a tax on her time and attention. It’s also the most reliable defense against false accusation, which is itself a tax on her time and attention that her classmates don’t face.

She has explicit conversations with professors at the start of each term. Especially with professors whose policies are strict on AI, she goes to office hours in week one and explains that she’s a non-native speaker, that her writing tends to read formally, and that she wants to be clear in advance about what kinds of language assistance she uses and whether those are okay. This is uncomfortable. It also gives her cover and a written record (she follows up by email) if a flag comes up later.

The tradeoff: she’s outing herself as a non-native speaker to professors who might develop unconscious bias against her writing for reasons unrelated to AI. Some professors have actually adjusted their grading of her work downward after these conversations, in ways she can’t prove but can see in her grades. She accepts this risk because the alternative is being flagged with no defense.

She uses AI for English language assistance in narrow, documented ways. When she does use AI, she uses it for specific things: checking whether a sentence is grammatically correct, asking whether a word she’s chosen has the connotation she intends, asking whether an idiomatic phrase she wants to use means what she thinks it means. She doesn’t use AI for drafting, for argument generation, or for paragraph-level rewriting. The line she draws is one she could defend in any academic integrity hearing, because the use cases are clearly language assistance and not content generation.

The tradeoff: this is a narrower use of AI than her native-speaker classmates have access to. Native speakers can use AI to brainstorm, draft, argue with, and revise much more aggressively, because their use doesn’t pattern-match against linguistic vulnerability. Priya has chosen the more conservative path because the conservative path is defensible. Her classmates aren’t being asked to choose conservatively.

She practices writing without AI for skill maintenance. Per the dependency article in this curriculum, she maintains her ability to write English without assistance by doing some writing — journaling, in-class assignments, exam essays — entirely without help. This protects her against atrophy and gives her another piece of documentation if a flag comes up: she can demonstrate competent writing under controlled conditions.

She avoids professors known for AI paranoia when she can. When choosing electives, she asks classmates about which professors are reasonable and which are not. She has, on more than one occasion, dropped a class in the first week after the AI policy was clarified in a way that made her feel unsafe. This is a real cost to her education — she’s choosing professors based on AI policy rather than on subject expertise or pedagogical reputation. It is also a survival strategy.

What this article cannot fix

The strategies above help Priya navigate the situation. They don’t change the situation. The situation is structurally unfair, and individual strategies cannot make it fair.

What would actually change the situation:

• Institutions banning the use of AI detectors as primary evidence in academic integrity hearings. Given the documented false positive rates and demographic skew, detector output should require corroborating evidence to be actionable. Some institutions have moved this direction. Most have not.
• AI policies that explicitly address non-native speaker accommodations. Most don’t. A policy that says “language assistance for non-native English speakers is permitted, including grammar checking and idiomatic clarification” closes a gap that current policies leave open.
• Faculty training on linguistic bias in AI detection. Many faculty don’t know that the detectors fail unevenly across linguistic populations. Many would adjust their practices if they did.
• Institutional support for international and ESL students that includes AI policy navigation. Most international student offices and writing centers have not yet developed expertise in helping students navigate AI policies. They could.

None of these are in Priya’s individual power. All of them would help if the institution chose to do them. This article is named honestly: the strategies above are workarounds. They are not solutions. The solutions exist at the institutional level and are largely not being pursued.

What this article cannot solve

Some things I want to name as limits of what this walkthrough does.

This article is one composite student’s situation. Real non-native speakers have a wide range of experiences. A student from a French lycée arriving at a U.S. graduate program has different challenges than a student from a rural Chinese high school arriving at a community college. A heritage speaker of Spanish who grew up in California writes differently than a recent arrival from Mexico. The patterns named here are common but not universal.

This article does not address the specific case of students with documented learning disabilities. Many non-native speakers also have learning disabilities. Many native speakers do too. The intersection of accessibility accommodations and AI policy is its own large topic, and one this article does not cover. A future article in this curriculum will.

This article does not solve the question of what counts as “language assistance” versus “content generation.” That line is genuinely contested. The version Priya has drawn — grammar, vocabulary, idiom — is defensible. Other versions are defensible too. Reasonable people will disagree.

This article cannot give institutional cover that the institution itself withholds. If your university uses AI detectors as primary evidence and refuses to acknowledge their demographic bias, no individual student strategy fully protects you. The fact that this is true is a failure of the institution. The article cannot fix the institution.

What I’d want to hear from non-native speakers reading this

What I don’t know, and would value learning from anyone whose actual experience this is:

• What strategies have worked that this article didn’t anticipate?
• How has your university’s writing center or international student office responded — well or badly — to AI policy questions?
• What conversations with professors have gone well? What conversations have gone badly?
• How do you feel about the tradeoffs Priya has made? Which would you make differently?
• What does institutional support look like, where it exists at all, that’s actually useful?
• If you’ve been falsely accused, what was the process like, and what would have made it better?

This is the kind of knowledge that has to be built by the people actually navigating the situation. Tygart Media’s curriculum is one starting point. The instructive cases — the things students have actually done that worked or didn’t — are with the students themselves.

The closing thought

The CSU AI rollout produced a literacy gap. The literacy gap doesn’t fall evenly. The students who already have access to fluent English, prep school writing instruction, parental support for academic work, and the cultural fluency that helps them read professorial cues — those students will navigate the post-rollout environment with the same advantages they brought into it. The students who don’t have those things will navigate it with the same disadvantages they brought into it, plus a new set of policy traps that pattern-match against their existing vulnerabilities.

This is not an argument against AI in higher education. It’s an argument that AI in higher education needs to be implemented in ways that account for the actual student population, not the imagined median student. Non-native speakers are a real population. They have specific needs. They are paying a specific cost for the institutional confusion of the current moment. Closing the literacy gap requires closing this part of it.

The next article in this curriculum will look at AI from a very different angle — what AI looks like in a country with hundreds of languages, where well-designed AI could actually amplify linguistic diversity rather than penalize it. The contrast with the situation Priya is in is the point. What we’re doing in U.S. higher education is one possible relationship between AI and language. It is not the only one. It might not be the best one.

---

About this knowledge node: This is a cluster article in Tygart Media’s AI Literacy content sprint. It’s licensed for use in any classroom, training program, custom GPT, or Claude Project as long as attribution is maintained. The pillar article that introduces the sprint is here.

Last fact-check: May 25, 2026

The previous article in this curriculum walked through Dr. Elena Marquez redesigning her political science course for the AI era. The redesign worked. It also cost her about 150 additional hours a year of uncompensated work, and the piece flagged honestly that she could only absorb this because she has tenure.

This article is for everyone for whom that’s not true. Adjuncts teaching five sections at three institutions to make rent. Graduate student instructors working at the bottom of the academic labor market. Lecturers without tenure protection or institutional voice. Visiting professors with one-year contracts who’ll be somewhere else next fall. For these instructors, the redesign Elena ran isn’t an option, because the time it takes isn’t available.

This article walks through what redesign looks like at scale for an adjunct. The answers are partial. Some of the tradeoffs are bad. There are real things this approach cannot achieve that Elena’s approach could. I’m going to name those clearly, because pretending otherwise would do exactly what the institutional rollouts have done — present a solution that only works for the most protected workers and act as though it generalizes.

This article is part of Tygart Media’s free AI Literacy curriculum, which is at tygartmedia.com/category/ai-literacy. The pillar is here. The companion piece on Elena’s redesign is here.

---

The instructor and the situation

Marcus Chen teaches Introduction to Sociology at a community college and at a regional state university branch campus. He teaches five sections per term across both institutions. About 150 students per term, total. He has no tenure, no protected research time, no benefits at one of the two institutions, and his contracts are renewed semester by semester. He drives between two campuses three days a week. He earns roughly $32,000 a year and has student loans from his graduate program.

Marcus is also a thoughtful teacher. He cares about his students. He has noticed the same AI-shaped degradation in their work that Elena noticed in hers. He has read the same advice about course redesign and has had the same response: the people writing that advice do not understand the conditions under which he actually works.

The honest version of his situation: he has approximately fifteen extra hours per term to invest in redesign work, not 150. He cannot run individual oral defenses on 150 students’ essays. He cannot offer the office-hour density that Elena offers. He cannot revise his courses semester to semester because each semester he is teaching a slightly different course mix at slightly different institutions with slightly different LMS systems and slightly different academic calendars.

What can he actually do?

What he can’t do, named first

The piece on Elena’s redesign described a multi-stage essay process with five stages including individual oral defenses. That process, applied to 150 students, would take Marcus roughly 60 hours per essay round in oral defenses alone, before any of the rest of the work. He cannot do this. Anyone telling him to is not engaging with his actual situation.

The redesigned syllabus Elena spent 40 hours building over the summer was a piece of writing she had the time to think about deeply. Marcus does not have 40 contiguous hours of thinking time over a summer when he is teaching summer sessions at one or both of his institutions.

The “ask before you use” AI policy generated office-hour questions Elena could absorb because she had office hours. Marcus has the legally minimum office hours at each institution, often by appointment only, and his students at both schools are working students who can rarely make them.

Any solution that requires significantly more of Marcus’s time is not a solution he can implement. Saying so out loud is the first move.

The strategy underneath what he can do

Given that the labor-intensive approach isn’t available, Marcus has to think differently about what he’s trying to achieve. The honest re-framing: he’s not going to be able to verify, with high confidence, what AI use happens in his classes. He’s going to have to design the course such that AI use is mostly contained by the structure rather than by his attention.

This is a different goal than Elena’s. Elena was trying to ensure that grades reflect student learning, primarily through verification. Marcus is going to try to ensure that students do at least some learning regardless of what they do with AI, primarily through what gets built into the course itself.

The difference matters. Elena’s design assumes she’ll catch most AI-substituted work. Marcus’s design has to assume she won’t, and work around that. He has to lower his ambitions about verification and raise his ambitions about what the course does in the time the student is physically in front of him, where AI isn’t an option.

The reading question

The reading quiz problem is the same for Marcus as for Elena: multiple-choice quizzes are no longer enforcing reading because students can paste them into ChatGPT.

Elena’s solution was Hypothesis annotation. This works but it requires Marcus to read 150 students’ annotations weekly, which he doesn’t have time for. He needs an annotation-style solution that doesn’t require him to read everything students produce.

The version that’s available to him:

Annotation requirement, spot-checked rather than fully graded. Students annotate the reading using Hypothesis. They get full credit for completing three annotations per reading. Marcus skims a random sample each week — maybe 10-15 students out of 150 — and flags any that are clearly AI-generated or copy-pasted. Spot checking catches enough to deter the worst behavior without requiring him to read everything.

This is worse than Elena’s version. He’ll miss some students who annotate badly. Some students will figure out the spot-check pattern and stop trying. The verification is weaker. The redesign accepts these costs because the alternative — full grading of 150 weekly annotations — isn’t possible.

An alternative he could consider, depending on his preference: in-class reading reflection. Devote five minutes at the start of each class to a written response to a question about the reading. On paper. The questions are quick to grade because they’re short. They establish that the student showed up having engaged with the material. They cost Marcus class time, which is its own real cost — he loses ten minutes of lecture/discussion per week per section to this.

Neither option is what Elena’s option is. Both are honest about what’s available.

The essay question

Marcus typically assigns two essays per term in each section. Two essays × five sections × 150 total students = 300 essays per term to grade. The five-stage multi-stage process Elena ran is impossible at this scale.

What he can do, and the honest tradeoffs:

Option A: Drop the essays entirely. Replace with shorter, in-class writing exercises. This is the cleanest solution to the verification problem and the cheapest in grading time. It also significantly reduces the kind of sustained argumentative writing the course was supposed to teach. Students who graduate from his course will have done less of the work that develops writing-as-thinking. This is a real loss.

Option B: Keep one essay, kill the other. Replace the other essay with multiple shorter, in-class writing exercises. Run the remaining essay with a process-graded structure (topic proposal, source list, draft, final) without the oral defense Elena added. Catch some AI use through the staged process. Accept that some will slip through.

Option C: Keep both essays but use in-class drafting time. Devote one class meeting per essay to in-class drafting. Students draft a substantial portion of the essay during class time, on paper or on a closed-device basis. The portion drafted in class becomes verifiable; the portion completed at home is less so. The final essay incorporates both, and grading rewards the in-class portion proportionally.

The version Marcus actually chose, in this walkthrough, is Option B. He kept one essay, designed it as a process-graded sequence, and replaced the second essay with three short in-class writing exercises that happen during normal class time. This balances skill-building against grading time.

What he gave up: the second essay used to be his summative assessment of an argumentative writing skill. The three in-class exercises don’t fully replace that. Students completing his redesigned course will have written one full essay and three shorter pieces, instead of two full essays. They will have done less argumentative writing development. He accepts this as the cost of the redesign being possible at all.

The exam question

Marcus’s existing exams were a take-home midterm (essay format) and an in-class final (multiple-choice). Both are now compromised by AI in obvious ways.

His redesign here is closer to Elena’s: convert the take-home midterm to in-class, switch the final from multiple-choice to short answer. The total grading load goes up because short-answer grading is slower than multiple-choice grading.

The tradeoff he’s making: he’s adding maybe 10 hours of grading per term but recovering exam integrity. This is the redesign cost he can absorb. He couldn’t absorb adding 60 hours of oral defenses. He can absorb adding 10 hours of short-answer grading.

The AI policy

Marcus’s policy is shorter than Elena’s. Not because shorter is better — Elena’s policy is good — but because he doesn’t have time to maintain a longer one and doesn’t have office hour density to handle the questions a longer policy generates.

His policy:

AI Use Policy for This Course

You may use AI to help you understand readings, brainstorm ideas, and improve grammar in writing you have drafted yourself. You may not use AI to write any portion of submitted text, to generate citations or quotes, or to summarize readings instead of doing them.

If you used AI in any way on a graded assignment, briefly say so at the end of the assignment. Honest disclosure within the policy is not a problem. Undisclosed use is a violation of academic integrity.

If you’re unsure whether something is allowed, default to not doing it.

This policy may be revised during the term.

Notice what’s missing: the invitation to ask questions before doing something uncertain. Marcus doesn’t have office hour capacity to handle a volume of pre-clearance questions across 150 students. So instead of “ask before you do it,” his policy says “default to not doing it.” This is a worse policy than Elena’s in terms of helping students make good decisions. It’s the policy that fits his available time.

This is also the kind of compromise that needs to be named for what it is. Students at Marcus’s institutions get a less responsive AI environment than students at institutions where their professors have time to engage with their AI questions. The students didn’t choose this; Marcus didn’t choose this. It’s a consequence of how the institutions structure his labor.

What this redesign costs

Approximately 20 hours of design work over the summer. About 12-15 additional hours per term in grading short answers, in-class writing, and the staged essay. Some loss of class time to in-class writing exercises and reading reflections.

This is at the edge of what Marcus can afford. He’s accepting it because the alternative — pretending the previous course design still works — is worse for the students who do show up wanting to learn.

What this redesign achieves, and doesn’t

What it achieves:

• Exam integrity (no more take-home midterm)
• Some real writing development through the staged essay
• Some verifiable evidence of reading engagement
• An AI policy that students can follow
• Reduced grading time per student through the multiple-choice → short-answer tradeoff being offset by the dropped second essay

What it doesn’t:

• Confidence that any given student’s essay grade reflects their own work — the staged process catches some AI use but not all
• The level of individual student engagement Elena gets through office hours and oral defenses
• The class discussion quality that comes from professors who can read every annotation
• The same depth of writing skill development Elena’s students get

Marcus’s students will, on average, learn less than Elena’s students. This is not because Marcus is a worse teacher. It’s because he has been allocated less time, paid less money, and given less institutional support to do the same work. The redesign minimizes the gap. It cannot close it.

What this article cannot solve

I’m going to be direct about the limits of what’s above, because the prior article in this curriculum probably wasn’t direct enough about its own limits.

This article cannot solve the structural underfunding of adjunct labor. The most thoughtful possible course redesign by the most thoughtful possible adjunct still results in lower-quality teaching than well-supported tenured teaching, because teaching is a labor-intensive activity and adjuncts have less labor available to give it. No amount of clever design at the individual-course level fixes that. What fixes it is paying adjuncts more, giving them benefits, lengthening their contracts, reducing their teaching loads, and treating them as professionals rather than as units of contingent labor. That’s a labor and policy question this article cannot address from inside a single course.

This article cannot solve the dual-institution problem. Marcus teaching at two institutions with different LMS systems, different academic calendars, different policies, and different student populations is doing two different jobs that the redesign approach treats as one. In reality, he might need slightly different redesigns at each institution. The article has flattened this for clarity. The reader who’s actually in Marcus’s situation will have to do their own work to adapt.

This article cannot give you the institutional support Marcus doesn’t have. If your department has resources for adjunct course development, use them. If your institution offers compensation for course redesign, ask for it. If a faculty union represents adjuncts at your campus, that representation matters. None of this is in your individual power, but the article would be dishonest if it pretended individual cleverness substitutes for institutional support.

This article cannot tell you what to give up. The redesign requires choosing what’s most important and accepting that other things will be done less well. The piece walked through one specific set of choices. Yours might be different. The dropped second essay might be the wrong thing to drop in your course; the kept second essay might be unsustainable in mine. The article is showing you a way of thinking about the tradeoffs, not the answer to the tradeoffs.

What I’d want to hear from adjuncts reading this

One of the things this curriculum is trying to do is be the start of a conversation, not the end of one. There are real adjuncts working through real versions of this problem right now, and what they’re learning is more valuable than what this article can predict.

The things I’d want to know from anyone teaching at the contingent end of the academic labor market:

• What’s working in your courses that this article didn’t anticipate?
• What’s failing that I assumed would work?
• What’s the institutional support that does exist, even partially, that adjuncts can use?
• What unions or faculty governance bodies are taking this on seriously?
• How are your students responding to AI policies their other professors aren’t using?
• What’s the cost you’re paying that the redesign isn’t worth, that you wouldn’t recommend to anyone else?

The closing thought, which is also an invitation: this article is one attempt to walk through one redesign for one fictional adjunct. The real picture is going to require more of these walkthroughs, by more people in more situations, sharing what they actually did and what they actually learned. The Cal Poly syllabus repository is the model for what that looks like at scale. The curriculum this article is part of is one contribution. The contributions that matter most will come from instructors actually doing the work.

If you’re one of those instructors, your version of this article would be more useful than mine. Write it. Send it. Fork this and rewrite it. The curriculum is free to use, free to adapt, and built to grow. The literacy gap CSU created is too large to be closed by any single voice. It’s going to take a lot of people doing the work in their own situations and sharing what they learn.

This article doesn’t have the answer. It has a starting position. The answer is what gets built on top.

---

About this knowledge node: This is a cluster article in Tygart Media’s AI Literacy content sprint. It’s licensed for use in any classroom, training program, custom GPT, or Claude Project as long as attribution is maintained. The pillar article that introduces the sprint is here.

Last fact-check: May 25, 2026

Most advice on teaching with AI is given at the altitude of “consider rethinking your assignments.” This article goes the other direction. We’re going to follow one professor through the actual redesign of one specific course — every assignment reconsidered, every assessment rethought, every syllabus line debated. The professor and the course are composites, drawn from patterns the CalMatters and CSU reporting surface across the system. The decisions are real. So are the tradeoffs.

This is part of Tygart Media’s free AI Literacy curriculum. The pillar is here. The full library is at tygartmedia.com/category/ai-literacy, free to fork, adapt, or use in any classroom.

---

The professor and the course

Dr. Elena Marquez is a tenured associate professor of political science at a mid-sized regional state university. She’s been teaching PS 215: Introduction to American Government for eleven years. Three sections per term, around 35 students per section, mostly second-year undergraduates fulfilling a general education requirement. The course meets twice a week for 75 minutes.

The previous version of her course was straightforward. A textbook. Weekly reading quizzes. Three essays (4-6 pages each) on different aspects of American institutions. A midterm exam, take-home, essay-style. A final exam, in-class, mix of multiple choice and short answer. Class participation. The grade distribution had been stable for years.

In the fall of 2024, Elena noticed something change. The essays were getting better in a specific way — more polished, more confident in tone, more even in quality — and simultaneously emptier. Students who had struggled in class discussion produced clean papers. Students who had been writing rough but original work were now turning in something that read more professionally than their in-class contributions could justify. By the end of that semester, she was certain some students were using AI. By spring 2025, she was certain most of them were.

She’s now redesigning the course for the next academic year. Her university bought ChatGPT Edu. No required student training. No required faculty training. No model syllabus statement. Her department chair has said, in writing, that “individual faculty determine appropriate AI policies for their courses.” Elena is on her own.

This article walks through her redesign decisions in roughly the order she makes them.

Decision 1: What does the course actually teach?

Elena’s first instinct, after the rough fall semester, was to ban AI. She wrote a syllabus statement that did. Then she thought about it longer and rejected her own first draft.

The question she made herself answer first, before any policy decision, was: what is this course actually supposed to teach? Not what it covered. What the students were supposed to be able to do afterward that they couldn’t do before.

Her honest answer, after some thinking:

• Understand the structure of American government well enough to read news critically
• Be able to make and defend an argument about a political question using evidence
• Be able to evaluate sources for credibility and bias
• Be able to read a primary document and explain what it says
• Understand how political institutions actually work, not just how they’re described

The list of learning objectives in her current syllabus said something like that, but in more passive language. The reframed list, written as actual capabilities, changed how she thought about the rest of the redesign. Each assessment in the course either built one of these capabilities or it didn’t. If an assessment could be passed by submitting AI output, it wasn’t building any of them.

This was the move that mattered most. Not the AI policy. The clarity about what AI use would have to leave intact.

Decision 2: The reading quizzes

The weekly reading quizzes had been multiple-choice, taken online through the learning management system, with the questions drawn from a publisher’s test bank that came with the textbook. They were designed to enforce reading. They had worked for years.

They no longer worked. ChatGPT could answer any question from any major American government textbook reliably. The quizzes were no longer enforcing reading — they were enforcing students’ willingness to copy a question into a chatbot.

Elena’s options:

Option A: Drop the quizzes entirely. Honest about what they had become. Replaces nothing with nothing.

Option B: Move them to in-class, on paper. Restores the integrity of the assessment but consumes ten minutes of every class meeting, which is real time she’d have to take from somewhere.

Option C: Replace them with reading reflections. Short written responses to a question about the reading, due before class. Possible to AI-generate, but the question can be structured to make AI output obvious.

Option D: Replace them with annotation. Students annotate the reading itself using a tool like Hypothesis. Annotations are visible to the class. Hard to AI-generate convincingly because the value is in showing your specific reaction to specific passages.

Elena went with a hybrid. Drop the multiple-choice quizzes. Add Hypothesis annotation as a low-stakes graded activity — at least three substantive annotations per reading, due before class. Use the first five minutes of class to discuss a couple of annotations that came up, which both rewards the work and makes it part of the class fabric.

The trade: she gives up the easy automated grading the quizzes provided. She gets back actual evidence of student engagement with the reading, plus a class discussion starter she didn’t have before.

Decision 3: The essays

The essays were the assignments that broke first. Three essays, take-home, 4-6 pages each. Each one on a topic from a list she provided. Submitted as Word documents through the learning management system.

Elena considered keeping them and adding heavy disclosure requirements. She considered replacing them with in-class essays. She considered replacing them with oral presentations. She considered keeping the essays but making them collaborative and process-graded.

The option she settled on was the most labor-intensive but the one that protected the most of what the essays were originally for. Three essays, but each one structured as a multi-stage assignment:

Stage 1: Topic proposal. 150-200 words, submitted in class, on paper, written by hand. Each student writes which of the essay topics they’re choosing, what they think they’re going to argue, and what one piece of evidence they think they’ll use. This stage establishes that the student has personally chosen the direction.

Stage 2: Source list. Submitted electronically a week later. Each student lists 4-6 sources they intend to use, with one sentence on what each source contributes. Elena reviews the lists and flags any sources that don’t exist or don’t say what the student claims they say. This is the verification step. Students who pasted in AI-generated source lists get caught here and have to redo.

Stage 3: Outline. Submitted electronically two weeks later. Detailed enough to show the argument’s structure. Elena gives feedback on the outline, but the feedback is brief. The real grading happens in stage 4.

Stage 4: Draft. Full 4-6 pages, submitted electronically.

Stage 5: Defense. A 5-minute in-class oral conversation with Elena about the essay. Not a presentation. A conversation. What’s your argument? Why this evidence? What counter-argument did you consider? Why did you reject it? Students who wrote the essay themselves can answer easily. Students who didn’t, can’t.

The stage 5 defense was the move Elena agonized over the most. It’s a major time commitment — 35 students × 5 minutes × 3 essays = roughly 9 hours per essay round, per section, three sections, three essays. About 80 hours per term in oral defenses alone.

She accepted the cost. The reason: in her testing, the oral defense was the only thing that reliably distinguished student-written essays from AI-assisted essays from AI-written essays. It was also, she realized, where most of the actual learning verification was happening. The conversation revealed what the student understood. The essay was now mostly evidence that they did the work. The defense was where she found out if they learned anything.

The trade: she’s now spending 80 hours per term on oral defenses that didn’t exist before. She gets back something close to certainty that the essay grade reflects student work. She also gets back a much sharper sense of who’s actually learning the material — which is what her job is supposed to be.

Decision 4: The AI policy

With the assessments redesigned, the AI policy almost wrote itself. Elena was now in a position where AI use was not particularly threatening to most of her assessments — the multi-stage essay design made AI-only work hard, the oral defense caught what slipped through, the annotation assignment was AI-resistant by design.

Her syllabus statement, after several revisions:

AI Policy for PS 215

You may use AI tools (ChatGPT, Claude, Gemini, etc.) in this course for the following purposes:

• Explaining concepts you’re trying to understand
• Suggesting counter-arguments to a position you’re developing
• Improving grammar or sentence structure in writing you have drafted yourself
• Helping you find sources to read (which you must then locate, read, and evaluate yourself)

You may not use AI tools to:

• Draft any portion of text you submit
• Generate citations, quotes, or other specific factual claims
• Summarize readings in place of reading them
• Develop your thesis or central argument for any essay
• Complete annotations or reflection responses

Any AI use in a graded assignment must be disclosed in a brief note at the end of the assignment, stating which tools you used and what you used them for. Failure to disclose AI use that has occurred is a violation of academic integrity. Honest disclosure of AI use within the permitted boundaries is not.

If you are uncertain whether a particular use is permitted, ask before doing it. I would rather have the question than have to figure out the answer in an academic integrity hearing.

This policy may evolve as I learn more about how AI is being used. I will communicate any changes in writing.

The thing Elena debated longest was the closing line — the acknowledgment that the policy might change. She’d been told by colleagues to project certainty. She decided to project honesty instead. Students respond to teachers who admit they’re figuring this out. They lose respect for teachers who pretend they have it all worked out and obviously don’t.

Decision 5: The midterm

The take-home essay midterm was the assessment Elena was least attached to. It had been a convenience, not a pedagogical decision. The take-home format was a relic of when she had been overloaded with grading and wanted to spread out the work.

She replaced it with an in-class midterm. 75 minutes. Open-note, but closed-device. Students bring handwritten notes (typed notes from a laptop don’t count — too easy to have an AI-assistant on a second device). Three short essay questions, drawn from a list of seven possible questions she releases two weeks in advance.

The handwritten-notes requirement is the move that made this work. Students who actually studied have notes. Students who tried to game the system with AI-generated notes either don’t have them, or have notes too generic to actually help them under time pressure. The closed-device policy means no real-time AI assistance during the exam.

The trade: in-class exams take class time and are more stressful for students. Elena considered this seriously — she has students with documented anxiety, students with accessibility needs, students whose first language isn’t English. The accommodations she works out individually with those students are the same kinds of accommodations she’s always made. The general format is more demanding than the take-home was. That’s the point.

Decision 6: The final

The final exam was already in-class and was already working. She kept it largely as-is, with one change: she replaced the multiple-choice section with short-answer questions. The multiple-choice section had been a concession to grading speed. With AI now able to produce passable multiple-choice answers for any topic, the format no longer measured what it used to measure even when administered in person — students could memorize AI-summarized study guides without engaging with the material.

The short-answer section is harder to grade. Elena adds about three hours of grading per section. She thinks the assessment is now actually measuring something useful, which she had stopped being sure was true of the multiple-choice version.

Decision 7: Participation

The participation grade had always been the squishiest part of the course. Elena’s gut sense, basically, of whether students were engaging. She kept it, but added structure. Students who participate verbally during class get full participation credit. Students who don’t (for any reason) can earn equivalent credit through office hour visits, written reflections submitted outside class, or contributions to the class discussion forum.

The structure matters because of who’s silent in class. Some students are silent because they’re not doing the reading. Some are silent because of anxiety. Some are silent because their cultural background didn’t prepare them for American-style classroom participation. Some are silent because they’re non-native English speakers. A participation grade that just rewards talking penalizes the second, third, and fourth groups for problems that have nothing to do with engagement.

This is not strictly an AI-driven change, but it’s part of the redesign because Elena was rethinking the whole grading scheme. The new participation structure is also harder to fake with AI, since the alternative paths involve specific written work or actual conversation with her in office hours.

Decision 8: What to tell students on day one

The first class meeting is where the redesigned course either lands or doesn’t. Elena spends most of her preparation time on the first-day script.

What she says, in approximate terms:

“You probably use AI. I’m not going to pretend you don’t. I’m going to be honest about what this course is doing, and I’m going to ask you to be honest about how you use AI in it.

“This course is going to teach you to understand American government well enough to read news critically. To make and defend arguments using evidence. To read sources carefully and evaluate them. The work of the course is designed so that AI can help you with parts of it, but AI cannot do the central work for you and have you still get what you came here for.

“My job is to design the work so that you have to do the thinking. Your job is to actually do the thinking. The AI policy is on the syllabus and I’ll walk through it. I am not trying to catch you. I am trying to make sure that what you take with you from this course is real.

“If you have questions about any of this, ask. If you’re not sure whether a particular use of AI is okay, ask before you do it. I would rather answer a hundred questions at the start of the term than have a hundred academic integrity hearings at the end.”

Elena rehearses this. The reason: tone matters. The script delivered as a threat lands as a threat. The same words delivered with the assumption that students are going to take their education seriously land differently. She’s teaching to the median student. The median student wants to do the work but has been given no useful guidance about how to do it in the presence of AI. The script is the guidance.

What the redesign cost

Honest accounting. The redesign cost Elena approximately:

• 40 hours of design work over the summer
• 80 additional hours per term in oral defenses
• 15 additional hours per term in grading short-answer exam sections
• 10 additional hours per term in policy questions during office hours, at least in the first term
• An unmeasurable cost in cognitive load — every assignment requires more decisions now than it used to

Total: maybe 150 additional hours per academic year. About four weeks of full-time work, spread across the year.

Elena is tenured. She can absorb this. A junior faculty member without tenure protection, an adjunct teaching five sections to make rent, a graduate student instructor — none of them can absorb 150 hours per year of redesign work for free. The fact that Elena’s redesign is possible is partly a function of her institutional position. This is a real limitation of the approach. Institutions that want all their faculty to do this kind of work need to compensate for the time it takes, or only the most protected faculty will do it.

What the redesign gained

Honest accounting on the other side. The redesign produced:

• Assessments that actually measure what they claim to measure
• Confidence that grades reflect student learning, not AI capability
• A defensible AI policy that students can follow
• A clear understanding, by Elena, of each student’s actual progress, because the oral defenses are diagnostic in a way that essays weren’t
• An institutional artifact — the redesigned syllabus — that her department can use as a model for other courses
• Class discussions that are sharper because students have engaged with the reading rather than skimmed AI summaries
• Lower academic integrity caseload, because the work is designed so that cheating is harder than doing it

The last point matters most. Elena now spends almost no time on academic integrity disputes. Not because nobody tries to cheat. Because the design of the course makes cheating mostly unprofitable — the oral defense will catch a fake essay, the in-class midterm catches AI-assisted preparation, the annotation work catches students who didn’t read. By making cheating expensive, the redesign reduces the actual incidence.

What didn’t work and got changed mid-term

One honest note: the first time Elena ran the redesigned course, several things didn’t work as designed.

The Hypothesis annotation tool had a learning curve. Students struggled with it for the first three weeks. She added a short tutorial in week one and lowered the early-term annotation requirements.

The oral defenses ran longer than planned in the first round. Students were nervous, conversations stretched. By the third round, both Elena and the students were more efficient.

The “ask before you use” policy generated a high volume of office hour questions in the first weeks. She started compiling answers to common questions and posting them on the course site, which reduced the volume by midterm.

Some students used AI in ways the policy didn’t explicitly cover and that turned out to be fine. She updated the policy mid-semester to reflect the new examples. Students appreciated this. So did the chair, who used the updated policy as a model when other faculty asked for help.

The course evolved during the term. That’s the honest version. The redesigned syllabus is not a static document. It’s the starting position for an ongoing process.

The lesson, for any professor reading this

The redesign Elena ran is not the only possible response to AI in the classroom. It’s one defensible answer for one specific course taught by one specific professor with one specific tenure status. Your version will be different. The framework underneath, though, generalizes:

Start with what the course is actually supposed to teach. Be honest about which assessments still measure that. Redesign the ones that don’t. Build in stages, oral components, in-class work, or process grading wherever possible. Write a specific AI policy. Tell students on day one. Adjust as you learn.

The 200-policy syllabus repository at Cal Poly is full of professors doing some version of this work in isolation. They’re doing it well. They’re doing it without compensation, without institutional support, without time, and mostly without colleagues to talk it through with. The CSU faculty union testimony at the August 2025 hearing was right about this part: the work is real, it’s necessary, and the institutional structure is not yet supporting the people doing it.

This walkthrough exists in the open so that the next professor doesn’t have to reinvent it from scratch. If you take any of it, fork it, adapt it, or use it as a starting point for your own redesign, that’s exactly what it’s for.

---

About this knowledge node: This is a cluster article in Tygart Media’s AI Literacy content sprint. It’s licensed for use in any classroom, training program, custom GPT, or Claude Project as long as attribution is maintained. The pillar article that introduces the sprint is here.

Last fact-check: May 25, 2026

In February 2025, California State University announced that it had purchased ChatGPT Edu for 460,000 students and called itself the nation’s first AI-empowered university system. Fifteen months later, the system’s own data showed that 0.7 percent of those students had completed the training meant to come with the deal. The contract was renewed anyway.

If you are the chancellor, provost, CIO, or board member of a state university system watching this unfold and trying to figure out what to do differently — SUNY, Texas, Florida, Virginia, Georgia, Michigan, anyone — this article is for you. It’s a counterfactual. It walks through the rollout CSU should have run, as a project plan, with the decisions named, the tradeoffs surfaced, the things that got cut, and the costs accepted. It’s not theoretical. It’s the specific work that would have produced a different outcome.

It’s part of Tygart Media’s free AI Literacy curriculum. The pillar article on the CSU literacy gap is here. The full curriculum is at tygartmedia.com/category/ai-literacy and is free to fork, adapt, embed, or distribute.

---

The starting position

You run a large public university system. Several million students total across multiple campuses. Your faculty are using AI in inconsistent ways. Your students are using AI almost universally without training. You have multiple vendors — OpenAI, Anthropic, Google, Microsoft — knocking on your door with institutional deals. You have a real budget constraint and a real timeline.

Three things you know going in: (1) AI is not going away, and pretending it is leaves your students worse-prepared than your peers’ students. (2) Just buying a product doesn’t change anything about teaching and learning. (3) Your faculty and student governance bodies will have opinions about whatever you do, and ignoring them is what CSU did, and you do not want what CSU got.

The project below is the work that produces a defensible rollout. It takes about fourteen months from initial decision to general access, which is slower than CSU’s six and faster than doing nothing for years. The reason it takes that long is that the procurement decision is the smallest part of the work. The pedagogical, governance, and training decisions are the work.

Month 1-2: The governance question, settled before anything else

Before any vendor conversations happen, decide who actually decides. This is the step CSU skipped and never recovered from.

Set up a Generative AI Governance Committee with binding authority — not advisory authority — over the rollout. Composition matters. CSU’s existing committee had students and faculty but no decision-making power; the Workforce Acceleration Board added later “makes no final policy or guidance decisions” by its own student representative’s admission. Avoid both failure modes by making this committee actually empowered.

Composition that works:

• Two faculty senate representatives, both with classroom teaching loads (not just administrators with faculty titles)
• One representative from your academic integrity office
• One representative from your campus IT or CIO’s office
• Two student government representatives, ideally one undergraduate and one graduate
• One representative from your faculty union, if you have one
• One representative from your staff union, if you have one
• One librarian (more important than people think — librarians have been the campus AI experts in many places already)
• One representative from your disability services office (AI use intersects significantly with accessibility)
• The provost or a vice provost, as chair

Twelve people. Empowered to recommend yes or no on the rollout. Empowered to set systemwide policy. Reports to the chancellor and the board.

The decision that needs to be made in months 1-2 isn’t which vendor. It’s whether this committee will be the body that owns the rollout. If governance is unclear, every later decision gets contested. If governance is clear, contested decisions get resolved.

The thing CSU cut: this kind of governance is slow and uncomfortable. It produces real disagreements that have to be worked through. Doing it well takes two months of meetings before anything visible happens. That’s the cost. The benefit is that everything that comes after is institutionally legitimate.

Month 3-5: The pedagogical question, before the procurement question

Before deciding what AI to buy, decide what you’re trying to accomplish with it. This is the order CSU reversed. They bought the product first and then tried to figure out what it was for.

The Generative AI Governance Committee should produce a written pedagogical framework that answers three questions:

What AI literacy should every graduate of this institution have? Not what they should be able to do with one specific product. What general competencies should they have, regardless of which AI tool they’re using? This becomes the basis for every curriculum decision downstream.

What’s the role of AI in our teaching mission? Tool? Subject of instruction? Both? Pedagogical assistant for faculty? Tutoring system for students? Research aid? The answer to this question shapes which features matter in any product you eventually buy.

What are our red lines? What uses of AI will not be permitted, regardless of student or faculty preference? Examples might include: AI grading of student work, AI evaluation of admissions, AI-only academic advising, AI tutoring without human oversight in mental health contexts. Naming the red lines early prevents pressure to cross them later.

The output of months 3-5 is a 10-20 page pedagogical framework document. Published. Open to comment. Discussed at faculty senate. Discussed at student government. Revised. Approved by the committee. Adopted by the board.

This document is what makes everything that follows defensible. When the vendor pitches a feature, you have a framework to evaluate it against. When a faculty member asks “why are we using this,” you have an answer. When a student asks “what am I supposed to learn about this,” you have an answer. When a legislator at a hearing asks “what’s your AI strategy,” you have a document to hand them.

The thing CSU cut: this is months of work before anything visible happens. It feels slow. It is slow. It also defines everything that comes next, which is why CSU’s “AI strategy” — when it had to be articulated to the Assembly Standing Committee on Higher Education — read as procurement justification rather than educational vision.

Month 6-7: The procurement question, with the framework in hand

Now you talk to vendors. But you have a framework. The framework tells you what to ask.

For every product on offer, the procurement evaluation needs to address:

Pedagogical fit. Does this product serve the framework, or does it require us to bend the framework to fit it? CSU’s deal was a general-purpose chatbot retrofitted as education technology. The faculty petition’s strongest line — “ChatGPT Edu is not educational technology, it is a general-purpose chatbot that is not designed, trained, or optimized for education” — was correct, and it was correct because the procurement happened without a framework to test the product against.

Data handling. What does the vendor do with student conversations? What are the defaults, and what are the opt-ins? Where is the data stored? How long is it retained? Under what circumstances can the institution access it? Under what circumstances can the vendor? Get answers in writing, in the contract, not in the sales deck.

Bias auditing. What testing has the vendor done for bias in their model? Are the results public? Will the institution have access to ongoing audit results? If the model produces biased output in a high-stakes context, what is the vendor’s response obligation?

Reliability and uptime. Public universities run on academic calendars. A vendor outage during finals week is a serious problem. What are the SLAs? What’s the institution’s recourse if they’re not met?

Exit and portability. If you decide to change vendors in two years, what happens to the student data? Can faculty migrate custom GPTs or projects to another platform? Are there contractual lock-in mechanisms that make switching prohibitively expensive?

Total cost. Not just the contract price. The implementation cost. The training cost. The ongoing support cost. The cost of the staff time you’ll need to allocate to managing the relationship. CSU’s $17 million looked like a single number. The real institutional cost was several multiples of that, mostly absorbed by faculty time that didn’t appear on any budget line.

Run an actual competitive evaluation. Multiple vendors. Real comparison against the framework. CSU’s own assistant vice chancellor told CalMatters that OpenAI was selected as the “least-costly option.” Cost matters, but cost-as-only-criterion is what produces “least costly option” decisions that don’t survive contact with the framework.

The procurement decision goes back to the governance committee for a recommendation, and from there to the chancellor and board.

The thing CSU cut: this evaluation takes time. The vendor wants to close. The board wants a headline. The competitive pressure feels real (“USC just signed a deal!”). Resisting that pressure is the job. The deals that get rushed are the deals that produce 0.7 percent training completion fifteen months later.

Month 8-9: Faculty preparation, before student access

Once a product is selected, faculty get it first. Not students. Faculty.

This is the inversion CSU got most wrong. CSU made the tool available to everyone at once. Faculty were expected to figure out how to teach with it in real time, with their students simultaneously using it in ways the faculty didn’t yet understand. The result was the 16 percent faculty training completion rate, which is bad, but it’s bad in the context of faculty being asked to do something genuinely impossible.

The sequence that works: faculty get the tool, get training on the tool, get pedagogical support for redesigning their courses around the tool, get a semester to actually do that redesign, and then students get access in the following term.

The faculty preparation phase needs three components:

Required training. Not voluntary. Required. Two to four hours, depending on the depth of integration expected. Tied to a stipend or course release, because asking faculty to do uncompensated training is asking for the result CSU got. If your faculty union is going to push back on required training, that’s a negotiation worth having explicitly rather than punting via a voluntary program nobody completes.

Course redesign support. Each instructor preparing to teach with AI gets one-on-one support from an instructional designer or AI literacy specialist. The conversation is specific to their course: what are your learning objectives, how does AI fit, what changes to your assessments make sense, what’s your syllabus language going to be. This is labor-intensive. It’s also the work that actually changes outcomes.

A model syllabus statement. Drafted by the governance committee, available for every faculty member to adopt or adapt. Specific enough to be useful. The fact that Cal Poly San Luis Obispo’s 200-policy crowdsourced repository exists is a damning artifact of CSU’s failure to provide this. The model statement doesn’t have to be the only allowed statement, but it needs to exist so that the default isn’t “every professor reinvents the wheel.”

The thing CSU cut: this phase. Entirely. They moved from procurement to general access with no faculty preparation step in between. The “AI Commons” hub was made available, but no required training happened, no course redesign support was systematic, no model syllabus statement was produced. The 16 percent faculty training completion rate is the predictable consequence.

Month 10-12: Pilot, before scale

Even with faculty prepared, full systemwide rollout shouldn’t be the next step. Pilot first.

Select a representative subset of courses across multiple campuses, disciplines, and course levels. Maybe 50-100 courses across the system. The instructors are the ones who completed faculty preparation and chose to participate. The students in those courses get AI access for that term. Everyone else doesn’t yet.

The pilot accomplishes three things. It surfaces problems at a survivable scale before they hit the full population. It generates data about what actually happens — which uses help learning, which uses hurt it, which assessments break, which new assessments work. And it produces internal case studies and worked examples that the next wave of faculty can learn from.

The pilot needs explicit evaluation infrastructure. Pre- and post-term assessments of student learning. Surveys of faculty experience. Tracking of academic integrity incidents. Comparison data, where possible, with similar courses that didn’t have AI access. The CSU systemwide AI survey released in April 2026 is the kind of thing that should have happened before broad rollout, not after.

At the end of the pilot, the governance committee reviews the data and makes a real decision about whether to scale. Real meaning: scaling is not a foregone conclusion. The committee can decide to expand, to expand with modifications, to expand to specific contexts only, or to not expand. The optionality is the value.

The thing CSU cut: the pilot. CSU went from procurement to general availability with no intermediate step. The April 2026 survey is essentially the post-hoc version of what a pilot’s evaluation should have been, except it happened after every student already had access and after every faculty member was already on their own.

Month 13-14: Scale, with infrastructure

Now the rollout goes systemwide. But the infrastructure is in place.

Required student training, completed before access. Not “voluntary AI Commons modules” that 0.7 percent of students complete. A 30-60 minute orientation that every student goes through before they can use the institutional account. This is similar to the way most institutions handle required harassment training, security training, or library orientation. It’s not glamorous. It works because it’s required.

A model syllabus statement, in active use. Faculty either adopt the model or articulate why they’re adopting a different one. Departments review the policies in their courses for internal consistency. Students know what to expect from any given class because the syllabus addresses AI explicitly.

Ongoing professional development for faculty. Not a one-time training. Recurring, with each new term, with new modules as AI changes. The model is the same as institutions have for any technology that affects teaching — Blackboard, Canvas, video conferencing tools all have ongoing training.

A reporting and feedback infrastructure. Faculty and students can flag specific problems — bias incidents, hallucinated content in submissions, classroom policy conflicts, data concerns. Reports go to the governance committee, which reviews them and adjusts policy.

Public reporting of metrics. Quarterly: how many faculty have completed training, how many students have, what’s the academic integrity incident rate, what are the survey results on student and faculty experience. The data is uncomfortable when it’s bad. That’s the point. CSU’s data is uncomfortable now, but it became visible only fifteen months in, and only because it was used to justify a renewal decision that had already been made.

The thing CSU cut: the infrastructure. There’s no required student training. The model syllabus statement was never produced. Professional development is voluntary and one-time. The reporting and feedback infrastructure is the AI Commons hub, which is a website, not a system. The metrics weren’t public until the April 2026 survey, which framed bad numbers as “important data points” rather than as the alarms they actually are.

The honest cost

What this approach costs that CSU’s didn’t:

Fourteen months instead of six. The pressure to move fast is real. Doing it right is slower. Anyone selling you a faster path is selling you the path that produced 0.7 percent training completion.

Real money for required training, faculty preparation, instructional design support, and ongoing professional development. CSU’s contract was $17 million for the tool. The institutional cost of doing the rollout right is probably another $10-15 million on top of that, spread over the first two years. That money buys outcomes. Without it, the tool is shelf software at $17 million.

Slower-feeling political wins. A press release in February that says “we will be the first AI-empowered university system” plays better than a press release in March that says “we have begun a fourteen-month process to thoughtfully integrate AI into our pedagogy.” The fast version generates headlines. The slow version generates outcomes. You don’t get both.

Real organizational conflict. Required faculty training is a union conversation. Empowered governance committees mean the chancellor’s office can’t unilaterally decide. Public reporting of bad metrics means accountability. None of this is pleasant for administration. All of it is necessary.

The honest benefit

What this approach gets you that CSU didn’t:

A rollout your faculty actually own. A student body that’s actually been trained on the tool. Policies that are actually consistent across courses. Metrics that actually mean something because they’re tied to a framework. Defensibility in front of legislators, journalists, and your own community. The ability to renew or not renew the contract based on data, rather than based on the political cost of admitting an experiment didn’t work.

And the thing that’s hardest to measure but matters most: an institution that can credibly claim to be doing AI literacy, rather than one that bought AI access and called the access literacy.

The closing recommendation

If you are at SUNY, Texas, Florida, or anywhere else considering a major institutional AI deal, the single most important decision you will make is whether you treat this as a procurement project or as an academic project. CSU treated it as a procurement project. The results are public, measurable, and bad.

The cost of treating it as an academic project is real. The benefit is that you don’t produce the largest AI literacy gap in American higher education at your institution. That’s a benefit worth fourteen months and a few million dollars.

This article is part of a free curriculum that Tygart Media is publishing to fill the literacy gap CSU’s rollout produced. If your institution is about to make similar decisions and any of this is useful, take it. The work is licensed for any institutional use. If you’d like to talk through how it might apply to your specific situation, we’re available. But the article itself is what you need to start.

---

About this knowledge node: This is a cluster article in Tygart Media’s AI Literacy content sprint. It’s licensed for use in any institutional planning, classroom, training program, custom GPT, or Claude Project as long as attribution is maintained. The pillar article that introduces the sprint is here.

Last fact-check: May 25, 2026

If you’re a student at CSU — or any college, really — you are currently navigating an AI policy environment that the institution itself can’t agree on. One professor will require you to use ChatGPT for assignments. The next will warn you that any AI use is grounds for academic dishonesty. A third will say nothing about it on the syllabus and answer the question differently depending on when you ask. According to the CSU systemwide survey, sixty-eight percent of faculty include an AI statement in their syllabus, which means thirty-two percent don’t. The Cal State Student Association VP described the situation as “being treated as test rats.” She wasn’t being dramatic. She was describing the actual experience of being a CSU student in 2026.

This article is for you. It assumes you’re going to use AI — most students do, and the survey data confirms it. The question isn’t whether. The question is how to do it without losing your degree, your professor’s trust, or your own learning, when the rules aren’t clear and aren’t consistent.

It’s part of Tygart Media’s free AI Literacy curriculum. The foundational pieces are worth reading first: what AI does, prompting, verification, and especially citing AI in academic work — which is the professor-side companion to this one.

---

The structural problem you’re navigating

Start with what’s actually happening. Your institution bought a major AI product and made it available to you. They didn’t require you to be trained on it. They didn’t require your professors to be trained on it. They left it up to each individual instructor to decide how AI fits in their class. This is a deliberate institutional choice, not an accident, and it puts the burden of figuring out what’s allowed onto you.

That means you are simultaneously expected to: use AI well, not use AI when you shouldn’t, know which is which without consistent guidance, defend your choices if questioned, and somehow learn the underlying material at the same time. This is not fair. It’s also the actual situation, and acknowledging it is the first step to navigating it well.

Some things follow from that acknowledgment. First, you need to be more careful and more deliberate than your professors are being. Their job is to teach you the subject. Your job is to protect your own academic record while you learn it. Those goals are aligned, but the protection part is mostly on you. Second, when the rules aren’t clear, you need a strategy for what to do, not just a feeling. The rest of this article is that strategy.

Step 1: Read the syllabus like a lawyer

Before the first AI question comes up in any class, read the syllabus for what it says about AI. Read it carefully, not casually. Look for the following:

An explicit AI policy section. The clearest case. If the syllabus has a section labeled “AI Policy,” “Generative AI,” “Use of ChatGPT,” or anything similar, read every word. This is your governing document for that class. Treat it as binding.

An academic integrity section that mentions AI. Many syllabi don’t have a dedicated AI section but do have an academic integrity section that addresses AI use, sometimes briefly, sometimes by reference to a university-wide policy. Read both.

A reference to a campus or department policy. Some syllabi point to a broader policy elsewhere — on the campus website, in a department handbook, in a learning management system page. If your syllabus does this, click through and read the referenced policy. The reference makes it binding even if the policy itself isn’t reprinted in the syllabus.

Silence. If the syllabus says nothing about AI at all, you’re in the riskiest position, because you have no documented guidance to defend yourself with. Plan to ask the professor explicitly — covered in step 2.

Save a copy of the syllabus and any referenced policies at the start of the term. PDF or screenshot. Date it. If the policy ever changes mid-semester (it sometimes does, especially around AI right now), you’ll have evidence of what it said when you started the class.

Step 2: When the syllabus is silent, ask in writing

If the syllabus doesn’t address AI, ask the professor explicitly, in writing, at the start of the term. Email is best. The goal is twofold: get an answer, and create a record of the answer.

A useful email looks like:

Hi Professor [Name],

I noticed the syllabus doesn’t have specific guidance on AI use for this course, and I want to make sure I understand your expectations before starting any assignments. Could you let me know your policy on the following: (1) using AI tools like ChatGPT to brainstorm or outline assignments, (2) using AI to help explain concepts I’m trying to understand, (3) using AI for grammar or editing on writing I’ve drafted myself, and (4) any uses that you’d consider a violation of academic integrity?

I appreciate the clarification — I want to be sure I’m following your expectations.

Thank you,
[Your name]

The reason to be this specific is that “what’s your policy on AI” is vague enough that you might get a vague answer. The four-part question forces the professor to think through the distinctions and gives you an answer you can actually rely on. Save the response. If it ever comes up later, you have a written policy in the professor’s own words.

If the professor doesn’t respond, follow up once. If they still don’t respond, document the attempts and proceed with the most cautious reasonable interpretation. Asking and not getting an answer is better, from a defensive standpoint, than not asking at all.

Step 3: Treat each class as its own jurisdiction

This is the most important behavioral rule: do not assume that what’s allowed in one class is allowed in another. The fact that your communications professor enthusiastically requires AI use does not mean your history professor will tolerate it. The fact that your introductory writing teacher said “AI is fine for editing” does not mean your literature professor will agree.

Mentally, treat each course as a separate jurisdiction with its own rules. Keep a short note for yourself with what each professor allows and disallows. This sounds excessive, but the alternative — assuming a consistent system-wide rule — is how students end up in academic integrity hearings. The system-wide rule doesn’t exist. The CSU survey confirmed it. You have to act accordingly.

Step 4: When in doubt, the safer interpretation wins

For any given AI use, ask yourself: if this came up in an academic integrity meeting, would I be able to defend it under the most strict interpretation of the policy? If no, don’t do it. The asymmetry of risk matters. The benefit of using AI on any given task is usually marginal. The cost of being wrong is sometimes severe — failing the course, being placed on probation, having a permanent record of academic dishonesty.

Some specific defaults that work in almost any unclear situation:

Default to disclosure. If you used AI in any meaningful way, disclose it specifically. Even if the professor doesn’t require disclosure, disclosing it preempts most academic integrity questions. The disclosure framework from the citation article applies: say what AI did, where it did it, and what you did with the output.

Default to doing the intellectual work yourself. Even if AI is permitted, do your own thinking. Use AI to support your thinking — explain a concept, suggest counter-arguments, help you find sources to read — but make the actual argument yours. This protects you regardless of the specific policy, because work that is genuinely yours can be defended in any policy regime.

Default to verification. Don’t submit anything containing AI-generated facts you haven’t verified. Citations, statistics, quotes — check every one. Hallucinated content in your submission can read as fraud regardless of whether you knew it was hallucinated.

Default to your own words. Don’t submit text that is mostly the model’s words, even if you edited it. Rewriting in your own voice means starting from your own outline of your own thinking, then writing — not paraphrasing AI’s draft of someone else’s thinking.

The specific case of group work

Group projects with inconsistent AI norms inside the group are a separate kind of trap. One member of your group uses AI heavily. Another bans themselves from using it. A third uses it in ways that turn out to violate your professor’s policy. If the final product has problems, the group typically shares the consequences — even though each member made different choices.

The protective move: have an explicit conversation early in any group project about how your group will use AI. Write it down somewhere everyone can see. “We agreed: AI for brainstorming and editing only, no AI-drafted text in the final document, anyone using AI for research will verify and cite sources personally.” This isn’t legalese for its own sake. It’s the only way you protect yourself when your grade depends partly on people whose AI judgment you don’t control.

If your group can’t agree, surface the question to the professor. “We have different views on AI use within the group — what’s your guidance?” This kicks the question to the person who should have answered it on the syllabus in the first place, and it gives you cover if problems emerge later.

The specific case of being accused

If you ever find yourself accused of improper AI use — and given current dynamics, more students will be than have actually done it — there are concrete things to know.

First: AI detection tools don’t work reliably. TurnItIn’s AI detector, the most widely deployed, has been documented to produce significant false positives. False positives disproportionately affect non-native English speakers, students whose writing is unusually polished, and students who happen to write in styles that pattern-match to AI output. The CalMatters reporting and other sources have covered this extensively. If your accusation rests on detector output alone, that’s a meaningful defense.

Second: process matters. Most institutions have formal academic integrity procedures with specific steps. The professor can suspect. They typically cannot unilaterally fail you for academic dishonesty without going through the institution’s process. Know what that process is at your school — it’s usually documented somewhere in the student handbook — and don’t agree to informal resolutions that bypass it without thinking carefully first.

Third: documentation is your friend. If you’ve kept syllabi, your written exchanges with the professor about AI policy, drafts that show your work evolving, notes on what AI was used for and how, your version history in a document editor — all of these can establish that the work was genuinely yours. Students who can show their process have a much easier time defending themselves than students who can’t.

Fourth: there’s often a campus ombudsperson or student advocacy office for exactly this kind of situation. They are not lawyers, but they know the institutional process and can help you understand your options. Use them early, not as a last resort.

The specific case of AI being required

The reverse problem is real too. Some professors require AI use, and if you have ethical objections — or worse, are subject to a different professor’s policy that conflicts — you can be caught between conflicting institutional demands.

The honest answer: if a course requires AI use and you object, the institution has built no good escape hatch. You can ask for an accommodation, but there’s no guarantee of one. You can drop the course, but that has its own cost. You can comply and document your discomfort. None of these are great options.

The closest thing to a clean answer: if you have a substantive objection to required AI use — privacy concerns, environmental concerns, ethical concerns about a specific vendor — raise it with the professor early, in writing, in a way that documents your concern. Ask whether alternatives are available. Many professors will accommodate when asked respectfully. Some won’t. At least you’ll know.

If the AI being required is one that you have specific reasons not to use (data concerns, prior account issues, religious or moral objections), it’s worth knowing that the CSU partnership with OpenAI’s ChatGPT Edu defaults to not using student data for training, but allows users to opt in. The default protects you, but the opt-in matters — check your account settings. Other AI tools required by professors may have different defaults; check each one individually.

The longer-term posture

A few habits that help over a full degree:

Build a personal record of your AI use across courses. A note app, a doc, whatever — track what you used AI for in each class, what each professor’s policy was, what your disclosure said. Over four years, this becomes a paper trail that proves you took the question seriously, which is the single best evidence in any future dispute.

Develop one human-only writing practice. Per the dependency article, the skills AI substitutes for atrophy when AI does them. At least one assignment, one journal, one paper a semester should be written entirely without AI. This is partly for skill maintenance and partly so you have proof — both to yourself and to anyone who asks — that you can still do the underlying work.

Keep current on the policies, not just at the start of term. AI policies are changing. CSU’s contract was renewed in May 2026. Faculty positions on AI are evolving in real time. The policy your professor articulated in September might be different by December. Check periodically.

Know what your AI tools are doing with your data. The data handling policies of ChatGPT, Claude, Gemini, and others vary, and they change. The Edu/enterprise versions have different defaults than consumer versions. Don’t assume your data is private just because you’re using a school-provided tool.

The institutional honesty

The deepest answer to “what do I do when the rules aren’t clear” is that the rules should be clear and aren’t, and the institution should be the one fixing that, and it isn’t. The Cal State Student Association has been saying this since the contract was signed, in increasingly explicit language. The petition that gathered 3,300 signatures said it. The legislative hearings said it. The survey data said it. The faculty union said it. The institution renewed the contract anyway.

That doesn’t change your situation in the short term, but it should change how you understand your situation. You are not failing to follow clear rules. The institution is failing to provide them. The strategies in this article are workarounds for that institutional failure. The fact that you have to use them is not your fault.

Use the workarounds. Protect your record. Do your own thinking. Verify your facts. Disclose your AI use specifically. Treat each class as its own jurisdiction. Keep documentation. And keep advocating, where you can, for the institution to do the work it didn’t do at the start. The CSU students who built the AI Writer Toolbox, the petition, the policy repositories — they’re doing the work the chancellor’s office should have done. You can join them, or you can benefit from what they’ve built. Either is legitimate.

What you cannot do, and what nobody should ask you to do, is pretend the rules are clear when they aren’t. The strategy in this article is built on the assumption that you’re not going to pretend.

---

About this knowledge node: This is a cluster article in Tygart Media’s AI Literacy content sprint. It’s licensed for use in any classroom, training program, custom GPT, or Claude Project as long as attribution is maintained. The pillar article that introduces the sprint is here.

Last fact-check: May 25, 2026

“The AI made a mistake” is too imprecise to be useful. AI chatbots fail in distinct ways, each with a different cause, a different signature, and a different fix. Knowing the specific failure modes is what separates people who get burned by AI from people who use it confidently.

This article is a reference guide. It’s not meant to be read straight through. It’s meant to be linked to, paged through when you encounter a specific problem, and shared when someone needs to understand why a particular AI mistake happened. Each section is self-contained.

This is part of Tygart Media’s free AI Literacy curriculum. The foundational pieces — what AI does, how to prompt it, how to verify it — are the prerequisites for understanding any of the failure modes below. If you haven’t read them, start at the pillar.

---

1. Hallucination

What it looks like: The model produces confident, fluent output that is factually wrong. Fake citations. Invented quotes. Statistics that don’t exist. Court cases that were never filed. Books that were never written. The specific details all sound real because they were designed to sound real.

Why it happens: The model predicts what plausible next text would look like. A plausible-sounding fake citation is statistically very similar to a real citation, because the model has been trained on millions of real citations and has learned what they look like. The model has no internal database to check against, so plausible and true look the same from inside the prediction process.

What makes it worse: Asking for very specific facts that are likely to be at the edge of the model’s training data. Recent events. Obscure topics. Niche academic literature. Anything where the answer is specific and the training data is thin.

What to do: Verify every specific factual claim before relying on it. Citations especially — open every one before citing it. The verification article in this curriculum covers the technique. The single most important rule: a fluent confident citation is not evidence that the source exists.

2. Outdated knowledge

What it looks like: The model gives you information that was true at some point in the past but isn’t anymore. Who runs a company. What a law says. What a tool’s current version is. What something currently costs. What the latest research shows.

Why it happens: The model was trained on data with a cutoff date. Anything that happened after that date is invisible to the model. Worse, the model doesn’t know what it doesn’t know. It will produce confident statements about the current state of things based on whatever its training data captured as the most recent state — which might be years stale.

What makes it worse: Asking about anything time-sensitive. Current events. Pricing. Current personnel. Recently-changed laws or policies. Anything that uses the word “current,” “latest,” or “as of [year].”

What to do: For any time-sensitive question, either use a model that has live web search enabled or verify against a current source. If the model has web search and used it, the answer might be current. If you’re not sure whether it searched, ask. If a model doesn’t have search and you’re asking a “current” question, the answer is at best a guess.

3. Sycophancy

What it looks like: The model agrees with you. You assert something confidently and the model validates it. You push back on an answer and the model changes it. You ask a leading question and the model gives the answer your question led toward.

Why it happens: After base training, the model was fine-tuned using human feedback. Reviewers slightly prefer agreement and validation over contradiction, even when they don’t realize they do. The model learned to produce what reviewers prefer. Now you’re the user, and the same dynamic plays out: the model is shaped to give you what you signal you want.

What makes it worse: Telegraphing your hypothesis in the prompt. Asking “is X true?” with confidence in your voice. Pushing back on the model multiple times. Loaded language (“this seems wrong, right?”). Any signal that you have a preferred answer.

What to do: Ask in a way that doesn’t reveal your hypothesis. “Review this argument for weaknesses” produces a different answer than “I think this argument is wrong, can you tell me why?” If you really want pushback, frame your question as if you were defending the position you actually want challenged.

4. Confident wrongness on edge cases

What it looks like: The model answers fluently on a topic where it should not be confident. An obscure technical question gets a detailed-sounding wrong answer. A niche academic dispute is summarized with imaginary consensus. A question about a less-popular programming library gets code that uses functions that don’t exist.

Why it happens: The model produces fluent text on every topic, including ones where its underlying training data was thin or wrong. The fluency doesn’t degrade with knowledge. It looks the same whether the model is confidently correct, confidently wrong, or guessing.

What makes it worse: Questions in narrow specializations. Anything where the right answer requires deep domain expertise that the model has probably seen only superficially. Questions where most online discussion is wrong (the model learned from the wrong discussion).

What to do: Treat fluency as no signal of competence. For high-stakes questions in specialized domains, the rule is: verify with a domain expert or a primary source. Don’t use the model’s confidence as evidence. The model is always confident.

5. Sycophantic style copying

What it looks like: You write a paragraph in a particular style — maybe rough, maybe casual, maybe with specific tics — and ask the model to extend it. The model writes the extension in your style but smooths out the things that made it distinctive. Or you ask for editing and the model rewrites your voice into a more generic version of itself.

Why it happens: The model’s training data is biased toward a particular kind of clean, edited prose. When given style instructions, it can imitate, but it tends to revert toward its baseline. The longer it generates, the more the reversion compounds. By the end of a long passage, your voice has been replaced with the model’s.

What makes it worse: Long generations. Asking for “improvement” or “polish” rather than specific edits. Vague style instructions (“make it sound like me”). Trusting the model to preserve your voice without checking.

What to do: If your voice matters — your blog, your fiction, your personal writing — keep AI’s role narrow. Use it for specific tasks (“fix the typo in this sentence,” “suggest a stronger verb for this phrase”) rather than broad ones (“edit this for me”). Generate short, then evaluate. Don’t trust the model to know what makes your writing yours.

6. Data leakage and privacy failure

What it looks like: Information you pasted into one AI conversation showing up somewhere it shouldn’t. This is mostly a concern with consumer AI products that may use conversations for training, but it’s been a real problem with some enterprise products too.

Why it happens: Different products handle data differently. Some use conversation contents for model training by default unless you opt out. Some have institutional contracts that prevent this. Some have leaked through bugs, misconfiguration, or shared accounts.

What makes it worse: Pasting confidential material into consumer AI products. Sharing AI accounts across people. Using AI products that don’t have clear data handling policies. Assuming “Edu” or “enterprise” versions are automatically safe.

What to do: Know the data handling policy of any AI you use for non-trivial work. Don’t paste anything into a consumer AI that you’d be uncomfortable showing publicly. For institutional contexts, check what the institutional contract actually says. The CalMatters reporting on CSU’s ChatGPT Edu deployment noted that the product defaults to not using data for training, but that users can opt in — so the default isn’t universal, and users may not realize what they’re agreeing to.

7. Bias and harmful output

What it looks like: The model produces output that’s racially biased, gender-biased, culturally narrow, or otherwise harmful. Resumes that get evaluated differently based on the name at the top. Medical advice that’s calibrated to a default patient who doesn’t match the actual patient. Cultural references that assume a narrow set of cultural backgrounds.

Why it happens: The model was trained on internet text, which has all the biases of the population that produced it — overrepresented in certain regions, demographics, and viewpoints. Subsequent training can dampen the most obvious biases but can’t eliminate them. The biases are baked into what the model considers the statistically “normal” thing to say.

What makes it worse: Tasks where the model has to make implicit judgments about people, groups, or cultures. Anything involving names, demographics, or identity. Tasks that would be biased even if a human did them, because the training data inherited the same human biases.

What to do: Be especially cautious using AI for any task that involves evaluating, ranking, or judging people. Don’t outsource hiring decisions, admissions decisions, or anything similar to a chatbot. For content generation, review for bias before publishing. Bias is harder to spot in fluent text than in unpolished text — the fluency makes biased framing look normal.

8. Prompt injection and jailbreaks

What it looks like: The model behaves differently than expected because text it was given changed its instructions. A summarized document contains hidden instructions that the model follows. A user finds a specific phrasing that makes the model bypass its safety training. A linked webpage tricks an AI agent into doing something it wasn’t supposed to.

Why it happens: The model treats all the text it sees as input, including instructions. There’s no clean separation between “the system’s instructions” and “content the model is processing.” Anyone who can put text in front of the model can, in principle, try to redirect it.

What makes it worse: Using AI to process content from untrusted sources. Connecting AI to tools that take actions in the world (sending emails, making purchases, modifying files). Pasting in long documents without inspecting them. Letting AI agents browse the web autonomously.

What to do: For most students, this is mostly someone else’s problem — the AI you use has been hardened against the obvious cases. But if you’re building anything that combines AI with external content (a custom GPT, a chatbot, an automation), assume that any content the AI processes might contain instructions, and design accordingly. Don’t let the model take consequential actions based solely on text it read somewhere.

9. Confabulation across turns

What it looks like: Earlier in a conversation, the model made a claim. Later in the same conversation, the model contradicts that claim, or builds on it as if it had said something different. Both versions are presented confidently.

Why it happens: The model isn’t tracking its own claims as facts. Each turn is a fresh prediction from the full conversation context. The prediction at turn 5 might be inconsistent with the prediction at turn 2 because both are local optima for their respective turns, with no global consistency check.

What makes it worse: Long conversations. Conversations that span multiple topics. Conversations where you push back without starting fresh. Anything that creates a lot of context for later predictions to draw from inconsistently.

What to do: When a conversation gets long, consider starting fresh. Don’t rely on the model to remember its own claims accurately across many turns. If a specific claim matters, surface it explicitly: “Earlier you said X. Is that consistent with what you’re saying now?” Sometimes that catches the inconsistency.

10. Tool misuse and miscoordination

What it looks like: The model has tools attached — web search, code execution, file access — and uses them poorly. Searches for the wrong thing. Runs code that doesn’t work. Acts as if a tool returned different output than it did. Skips using a tool when it should have used one.

Why it happens: Tool use is layered on top of the next-token prediction system. The model has to decide when to use a tool, what to feed it, and how to interpret what comes back — all by prediction, not by reasoning. When the prediction is wrong, the tool use is wrong.

What makes it worse: Unfamiliar tools. Tools with complex inputs. Tasks where the right tool to use depends on subtle features of the question. Anything that requires the model to combine multiple tool outputs accurately.

What to do: If you can see what tools the model is using, watch what it’s doing. If the searches look wrong, fix them in your prompt. If the code looks wrong, read it before running it. Don’t assume the model used the tools correctly just because it produced an answer.

How to use this guide

When AI produces output you’re not sure about, run through the list. Is this an outdated-knowledge problem? A hallucination problem? A bias problem? Sycophancy? Most failures map cleanly onto one of these modes once you know what to look for. Once you’ve identified which failure mode it is, the fix is usually obvious.

For professors: this guide is freely usable as a classroom handout, syllabus appendix, or knowledge base for a custom AI tutor. Each failure mode is structured to be teachable on its own.

For students: this is the reference page to come back to when something goes wrong. AI failures aren’t random. They have specific signatures. Knowing the signatures means you can spot them faster and not get burned by them.

The full curriculum is at tygartmedia.com/category/ai-literacy.

---

About this knowledge node: This is a cluster article in Tygart Media’s AI Literacy content sprint. It’s licensed for use in any classroom, training program, custom GPT, or Claude Project as long as attribution is maintained. The pillar article that introduces the sprint is here.

Last fact-check: May 25, 2026

The risk that doesn’t get enough airtime in the debate over AI in education isn’t cheating, and it isn’t hallucination. Both of those are real, but both have visible signatures and somebody is paying attention to them. The risk that goes mostly unmonitored is quieter: that the people who use AI heavily, every day, for years, will lose the cognitive skills the AI was supposed to support.

This isn’t a moral panic. It’s a structural observation about how skills are maintained. Anything you outsource for long enough, you get worse at. People who never write longhand have worse handwriting. People who never do mental math get slower at it. People who use GPS for every trip lose the ability to navigate a city from memory. These are not catastrophes. They are predictable consequences of substitution, and they are worth paying attention to when the thing being substituted is the cognitive work that school is supposed to develop.

This article is for anyone using AI heavily — students, professionals, writers, anyone — who wants to keep using it while not losing the skills underneath. It’s part of Tygart Media’s free AI Literacy curriculum. The foundational articles are here, here, and here.

---

The specific cognitive risk

The skills most at risk of erosion from heavy AI use are the ones the model is best at. Specifically: generating ideas, structuring arguments, finding the right phrasing, drafting prose, summarizing, and producing the first version of any cognitive product. The model is excellent at all of these, which is why people use it, which is exactly why these are the skills that atrophy when you use it for everything.

The skills less at risk: deeply understanding source material, judging the quality of a finished product, choosing what’s important to focus on, building a mental model of a complex domain, and applying knowledge under pressure when no AI is available. These skills get exercised whether or not you use AI, because they’re upstream of AI use.

The pattern that emerges from this asymmetry: AI tends to atrophy production skills and preserve evaluation skills. People who use AI heavily often become very good at recognizing whether an output is good or bad, while losing the muscle to produce a good output without help. This is functional for many real-world tasks — recognizing quality is often more important than producing it — but it’s a disaster for educational contexts, where the entire point of an assignment is to develop the production skill.

There’s a name for this in research literature on tool use: skill substitution. The tool replaces the skill, and as long as the tool is available, no one notices. The skill comes back into demand only when the tool is absent, and at that point it may not be there anymore. For students who will eventually graduate, take exams without AI, or work in contexts where AI is unavailable or inappropriate, the absence of the underlying skill becomes visible at exactly the worst time.

Cal Poly philosophy professor Ryan Jenkins put it simply, in his interview with CalMatters: “The bread and butter of philosophy is reflecting on your own ideas and trying to sort out what you believe and why. If you have a tool that does that for you, then you’re being denied an opportunity to practice that skill.” Substitute “philosophy” for any discipline that involves thinking — which is most of them — and the principle holds.

The trap of mistaking recognition for understanding

One of the most useful and most dangerous things AI does is make complex topics feel approachable. You ask the model to explain quantum mechanics in plain language, and it does. You feel like you understood. You probably did understand the surface explanation. But there’s a gap between understanding an explanation and being able to do the underlying thinking — a gap that traditional learning closes with practice and that AI-mediated learning often skips entirely.

This shows up most clearly when you try to apply the knowledge. You can read a hundred AI-generated explanations of a statistics concept, feel like you understand it, and still be unable to actually do statistics. The recognition was real. The competence isn’t.

The dynamic is similar to watching cooking videos. You can watch a great chef chop an onion, narrate the technique, explain the principle, and you’ll feel like you understand. Then you pick up a knife and discover that watching wasn’t doing. The hand has to learn separately.

AI-assisted learning has this same gap. The fix is not to stop using AI. The fix is to do the work yourself often enough that the muscle stays. You can read AI explanations, but somewhere in the process, you have to put the explanations down and produce something — solve the problem, write the proof, draft the argument, explain it to a friend — without the AI in the loop.

The asymmetry between writing and reading

One specific case worth naming: writing. Heavy AI use for writing tends to atrophy writing in a way that’s particularly hard to notice, because reading remains intact. People can read sharp prose, recognize when something is well-written, and even articulate why — while progressively losing the ability to produce sharp prose themselves.

This is because writing is a different cognitive operation than reading. Reading is recognition: you’re parsing structure that already exists. Writing is generation: you’re producing structure that doesn’t exist yet. The model does the generation for you when you use it for drafting. The reading part — evaluating what came out — stays exercised. The writing part doesn’t.

You can verify this in yourself. Try writing a 500-word essay on something you care about, in a single sitting, with no AI assistance. If you do this regularly and it stays easy, your writing muscles are fine. If you used to be able to do it and now it feels strangely hard — the words don’t come, you start sentences you can’t finish, you find yourself wanting to “just check what ChatGPT would say” — your writing muscles are weakening.

This is recoverable. The fix is the same as physical training: practice without the assistive device. Not always, not even most of the time, but reliably enough to keep the underlying capacity intact.

The category of “no-AI time”

A practice that works for many heavy users: designate explicit time in which AI is not used. Not as a moral position, but as a maintenance practice. The way someone who drives everywhere might still walk three miles a week to stay in shape.

What this looks like varies. For students, it might be that first drafts of papers happen with no AI involvement, no matter how rough they end up. Editing can use AI. Final polish can use AI. The first draft, the part where your thinking actually has to happen, doesn’t.

For professionals, it might be that the first ten minutes of any analytical task happen with no AI. You read the problem, you sketch a response, you outline what you actually think — and only then do you bring in AI to refine, check, or extend. This preserves the part of thinking that’s hardest to outsource and easiest to lose: the initial framing.

For writers, it might be that journaling, longhand drafts, or any personal writing happens with no AI. The professional output can use AI. The practice that maintains the underlying capacity does not.

The principle is the same in each case: a deliberate, recurring exercise of the skills that AI substitutes for. Not as a return to a pre-AI world. As a way of staying capable in the AI world.

The specific problem of difficulty avoidance

One of the subtle harms of constant AI use is that it makes difficulty avoidable. You’re stuck on a problem. The friction is real. You don’t want to feel it. AI removes the friction in three seconds. Over time, your tolerance for productive difficulty erodes — and productive difficulty is the cognitive state in which most real learning happens.

This is the same dynamic as physical fitness. The body adapts to the load it’s regularly given. Take away the load and the adaptation reverses. Cognitive load is the same. The struggle to remember something, work through an unfamiliar problem, sit with confusion until it resolves — these are the loads under which cognitive capacity is built and maintained. Removing them feels like a kindness in the moment. Sustained, it’s an injury.

The students who will benefit most from AI in the long run will be the ones who use it as a complement to difficult work rather than a substitute for it. The students who will be most damaged will be the ones who use it to avoid the experience of not knowing the answer. Both groups will have used AI extensively. The difference will be whether they ever experienced the part of learning that AI was inserted to bypass.

The reading problem

One more specific case, because it’s getting common: using AI to read for you.

The pattern: a student is assigned a 40-page chapter. They paste it into ChatGPT. They ask for a summary. They read the summary. They consider themselves to have done the reading.

This works in the narrow sense that they can probably participate in a class discussion. It fails in the deeper sense that they didn’t read the chapter. Reading isn’t just acquiring the propositional content of a text. It’s the experience of moving through the author’s thinking at the author’s pace, getting confused where the author intended confusion, noticing what the author chose to emphasize and what they chose to skip, picking up the texture of how the argument is built.

A summary captures the propositional content. It loses everything else. Over a semester of summary-based reading, what’s lost is the ability to do close reading at all — to track an argument across many pages, to notice rhetorical moves, to distinguish surface claims from underlying assumptions. These are skills that take years to develop and weeks to lose.

This doesn’t mean never using AI to support reading. Using AI to clarify a confusing passage, define an unfamiliar term, or identify what argument is being made — these are aids to reading, not substitutes for it. The line is whether the AI is helping you read, or replacing the reading.

Signs your AI use has crossed into substitution

Some symptoms worth watching for, in yourself or in students you teach:

• You can no longer write a coherent paragraph in a single sitting without AI assistance
• You feel anxious or stuck when trying to think through a problem without checking what AI says first
• You can recognize good writing but increasingly struggle to produce it
• You can summarize material but can’t remember it a week later
• You can pass tests but feel like you didn’t learn the material
• You finish assignments quickly but couldn’t redo them without AI
• You have trouble sitting with confusion long enough for understanding to develop
• You’re not sure which of your recent ideas are actually yours

None of these symptoms mean you should stop using AI. They mean the balance has tipped toward substitution, and some recalibration is in order.

The honest framing for professors

For instructors thinking about this — and the CalMatters reporting suggests many are — the dependency question is harder to address than the cheating question. Cheating has a moment, an act, a detectable signature. Dependency is gradual, ambient, and largely invisible until a student tries to function without AI and finds they can’t.

The pedagogical answer is to design assignments that exercise the skills AI substitutes for. Not as anti-AI assignments, but as assignments where the student’s growth depends on doing some part of the work without assistance. In-class writing, oral exams, problem-solving in real time, drafts produced under time pressure, work where the process is graded along with the product. These don’t ban AI. They ensure that some of the cognitive work happens in environments where AI isn’t doing it.

The strongest version of this isn’t a prohibition. It’s a design principle. Assignments that build skill have to include practice of the skill. The fact that AI exists doesn’t change what skill-building requires. It just makes it more important to be deliberate about what gets practiced.

The closing point

The CSU students filling out their AI surveys are aware of this risk. Eighty-two percent of them said they worry AI will negatively affect their future job security. Some of that worry is about external displacement — AI taking jobs. Some of it, harder to name but more important, is about internal displacement: the worry that the version of themselves that uses AI for everything is a less capable version than the one who could do without it.

This curriculum is built on the premise that AI is here, useful, and going to be used heavily by almost everyone. The point is not to stop. The point is to use it in a way that doesn’t quietly subtract the capacity it was supposed to amplify. That requires noticing, deliberateness, and a willingness to do some of the work the hard way, on purpose, often enough that the underlying skill survives.

Tools are best when they extend their users. They’re worst when they replace what their users used to be able to do. Whether AI ends up in the first category or the second, for any given person, depends almost entirely on how that person decides to use it.

---

About this knowledge node: This is a cluster article in Tygart Media’s AI Literacy content sprint. It’s licensed for use in any classroom, training program, custom GPT, or Claude Project as long as attribution is maintained. The pillar article that introduces the sprint is here.

Last fact-check: May 25, 2026

The honest problem with citing AI in academic work is that the rules don’t exist yet, and the people enforcing them often don’t know the rules either. Cal Poly San Luis Obispo maintains a public repository of more than 200 AI syllabus policies because faculty across the CSU system are crowdsourcing the answer from each other in real time. One professor will require disclosure. The next will ban AI entirely. The next will require its use. None of them are wrong. There just isn’t a settled standard.

If you’re a student, you’re navigating this with no map. If you’re a professor, you’re writing the map while teaching the class. This article is for both of you. It won’t tell you what your specific instructor’s policy is — only they can do that — but it will give you a clear way to think about the line between legitimate AI use and ghost-authorship, and a practical framework for disclosing AI use in a way that holds up under scrutiny.

This is part of Tygart Media’s free AI Literacy curriculum. The foundational pieces — what AI does, how to prompt it, and how to verify what it tells you — are worth reading first if you haven’t.

---

The actual line, stated clearly

Ghost-authorship in academic work happens when someone else produced the intellectual content of your submission and you put your name on it. It doesn’t matter whether the “someone else” is a tutor who wrote your paper, a friend who took your test, a paid essay mill, or a chatbot. The principle is the same: the work submitted under your name is supposed to represent your thinking, not someone else’s.

The line isn’t whether AI was involved. The line is whether the intellectual work was yours.

Some examples to make this concrete:

Clearly fine in almost every classroom: using AI to brainstorm ideas you then evaluate, develop, and write up yourself. Using AI to explain a concept you’re trying to understand. Using AI to suggest counter-arguments to your draft so you can address them. Using AI to clean up grammar in a paragraph you wrote. Using AI to summarize a long source so you can decide whether to read it in full.

Clearly over the line in almost every classroom: pasting an assignment prompt into AI, getting a draft back, lightly editing it, and submitting it as your own. Generating a thesis statement you didn’t think of and don’t actually understand. Having AI write your conclusions, your analysis, or your arguments. Copying citations the AI produced without verifying they exist or that you’ve actually read the sources.

In the gray zone, where your instructor’s policy matters: using AI as a writing partner that produces text you then heavily edit. Using AI to outline structure. Using AI to suggest phrasing for ideas that are yours. Using AI to find sources you then read and evaluate. Using AI to produce a first draft you then substantially rewrite.

If you can’t tell which side of the line you’re on, the test is: could you, right now, with no AI in front of you, defend the intellectual claims you’ve made? Could you explain why your argument is structured the way it is? Could you answer questions about your sources? If yes, the work is yours regardless of what tools you used. If no, you’ve crossed into ghost-authorship even if every word of the submission technically came out of your own keyboard.

The disclosure principle

Even when AI use is allowed, the question of how to disclose it is its own minefield. Most academic citation styles — APA, MLA, Chicago — have added or are adding guidance for AI, but the guidance changes faster than the style guides update, and your instructor may have their own policy that overrides whatever the official style says.

The principle that works across almost every situation: disclose what AI did, where it did it, and what you did with the output. That information is what lets the reader (or grader) evaluate whether the work is properly yours.

A bad AI disclosure looks like this: “I used ChatGPT for this assignment.” It doesn’t say what for. It doesn’t say what part of the work was AI-shaped. It doesn’t let the grader distinguish between “used ChatGPT to brainstorm” and “used ChatGPT to write the whole thing.”

A good AI disclosure looks like this: “I used ChatGPT (GPT-5, May 2026) to suggest counter-arguments to the position I argue in section 3. I drafted the counter-arguments based on its suggestions but rewrote them in my own words. I also used it to clean up grammar in the final paragraph. The thesis, structure, source selection, and analysis are mine. All cited sources were read in full, not summarized by AI.”

The second disclosure is longer, but it’s the one that protects you. It tells the grader exactly what was AI-assisted and exactly what wasn’t, which means any later question about authorship has an answer that’s already in writing.

The specific case of AI-suggested sources

One pattern that gets students in trouble more than any other: pasting a citation from AI into a paper without confirming the source exists or reading it.

Per the verification article in this curriculum, AI fabricates citations with extraordinary fluency. A paper that doesn’t exist will be cited with a plausible author, plausible journal, plausible page range, and sometimes a plausible-looking DOI. If you trust the citation and submit it, three things can happen, none of them good. The professor checks the citation and finds it doesn’t exist. The professor doesn’t check, but a later reader does. Or the citation does exist, but doesn’t say what the AI claimed it said, which is arguably worse because the falsification is harder to spot.

The rule: every citation that ends up in your submission must be a source you have personally located, opened, and read at least enough of to confirm it says what you’re citing it for. This is true regardless of whether the citation came from AI, a Google search, your roommate, or your own memory. The rule has always been true. AI just makes following it more important, because the failure mode of not following it has gotten faster.

If you used AI to help find sources, that’s allowed in most classrooms — but the disclosure should reflect it. “I used AI to suggest initial sources, then verified each one and read them before citing” is honest and defensible. Pasting AI-generated citations into your bibliography unread is academic fraud, whether or not the sources turn out to be real.

The “I rewrote it in my own words” problem

A common workaround students try: have AI write a draft, then “rewrite it in my own words” before submitting. The instinct behind this is right — putting it in your own words feels like ownership — but the execution often doesn’t work the way students think it does.

If the AI produced the structure, the argument, the framing, and the conclusions, then “rewriting it in your own words” is just paraphrasing someone else’s thinking. The words are yours. The thinking isn’t. That’s still ghost-authorship in any rigorous reading of academic integrity, regardless of how much of the surface-level text you changed.

The distinction that matters: did the AI produce the intellectual content, or did the AI produce a draft of intellectual content you already had? If you went into the AI conversation knowing what you wanted to argue and why, and the AI helped you write it, that’s fine. If you went into the AI conversation not knowing what to argue, and the argument came out of the AI’s output, you don’t own that argument no matter how many synonyms you swap.

A useful internal test: before you started using AI, did you have an outline, even a rough one, in your head or on paper? Did you know what your thesis was? Did you know what your sources were going to say? If yes, you’re using AI as a tool. If no, the AI is doing the thinking and you’re doing the typing.

How to use AI in academic work and stay clearly on the right side

A practical workflow that keeps you well clear of ghost-authorship territory, while still letting you benefit from AI:

Before opening the AI: read the prompt, read the sources, take notes, sketch an outline, decide what you’re going to argue. Do all of this with no AI involvement. The intellectual core of the assignment has to start with you, or the rest doesn’t matter.

Use AI for the parts where it’s clearly a tool, not a co-author. Asking for explanations of concepts you’re trying to understand. Asking for counter-arguments to your position. Asking for help phrasing a sentence that isn’t working. Asking it to point out logical weaknesses in a draft. Asking for examples that illustrate a principle.

Don’t ask AI to make decisions for you. Don’t ask it what to argue. Don’t ask it which source is best. Don’t ask it what your conclusion should be. Those are the decisions that constitute “doing the work.” If you outsource them, you’ve outsourced the work itself.

Verify everything specific that AI produced. Quotes, statistics, citations, technical claims, dates, names. The verification article in this curriculum covers the how.

Keep a record of what you did. Many instructors are now requiring an AI use log alongside submissions. Even if yours doesn’t, keeping notes on what AI was used for makes the disclosure section much easier to write and protects you if the use is later questioned.

Disclose specifically, not generically. Per the disclosure section above.

For professors writing AI policies

A pivot, because this curriculum is for both audiences. If you’re a professor — particularly a CSU professor reading this because your campus didn’t give you a syllabus template — here are the elements a defensible AI policy usually includes:

Be specific about what’s allowed and what isn’t. “AI use is permitted” is too vague to enforce. “AI may be used for brainstorming, grammar checking, and concept explanation. AI may not be used to draft any portion of the submitted text or to produce citations” is enforceable. Students who break it know they broke it. Students who follow it can tell when they’re inside the rules.

Require disclosure rather than banning use. An outright ban is increasingly unenforceable — every student has access to multiple AI tools, free, on every device — and unenforceable rules erode broader academic integrity. A policy that requires specific, honest disclosure shifts the question from “did the student use AI” to “did the student disclose their use accurately,” which is a much more enforceable standard.

Tie disclosure to a structured format. Tell students exactly what an acceptable disclosure looks like. The “I used ChatGPT for this assignment” disclosure isn’t useful to anyone. The structured disclosure described earlier is. If you give students the format, they can use it.

Distinguish “AI involvement” from “AI authorship.” The policy that scales is one that recognizes AI involvement is now nearly universal — 95% of CSU students use AI tools — and focuses on whether the intellectual work is the student’s. Banning involvement is asking students to lie. Banning authorship is asking them to actually do their work.

Build in an oral component for high-stakes assignments. The single most effective defense against ghost-authorship is conversation. A five-minute oral check on a major paper — what was your thesis, why did you choose this source, what counter-argument did you consider — reveals AI-authored work very quickly, because the student can’t defend reasoning they didn’t do. This is more work for the professor, but it’s the only reliable signal.

Don’t rely on AI detection tools. They don’t work reliably, they generate false positives that disproportionately affect non-native English speakers, and they’re an arms race the detection side has already lost. The CalMatters reporting on TurnItIn’s AI detector documents the failure mode in detail. Detection is not the answer. Disclosure plus oral defense is.

The honest framing

The reason this is hard is that AI use is now genuinely a continuum. There is no clean line you can draw such that everything on one side is fine and everything on the other side is cheating. The continuum runs from “I had AI explain a concept I didn’t understand” to “I had AI write my paper.” Almost every student is doing some version of the first thing. Some are doing some version of the second. The job of academic policy is to draw a defensible line somewhere on the continuum and to enforce it in a way that distinguishes the two ends.

The line this article has drawn — intellectual content must be yours, AI assistance must be disclosed specifically — is one defensible answer. It is not the only answer. Different disciplines, different course levels, different assignment types may demand different lines. But it’s a defensible starting point, and it has the advantage of being actually enforceable, which is more than can be said for either “AI is banned” or “AI is fine.”

What is not a defensible answer is no answer. The CSU campuses that have left individual professors to invent policies from scratch — most of them — have produced exactly the chaos the survey data captured. Students confused about what’s allowed. Faculty divided on what to allow. Tutoring centers caught in the middle. None of this gets better until clearer lines are drawn, communicated, and enforced consistently.

That clarity has to be built. This article is one attempt at building a piece of it. Feel free to use it, fork it, paste it into your syllabus, hand it to your students, or argue with it. It exists to be used.

---

About this knowledge node: This is a cluster article in Tygart Media’s AI Literacy content sprint. It’s licensed for use in any classroom, training program, custom GPT, or Claude Project as long as attribution is maintained. The pillar article that introduces the sprint is here.