AI literacy basics
Generative AI Without the Hype
Learn the basic mechanics, strengths, limitations, and system controls of generative AI across text, images, audio, code, and multimodal products.
By the end you can
- Distinguish generative models from discriminative and retrieval systems
- Describe prompts, context, model inference, decoding, tools, and validation at a high level
- Explain why fluency and format compliance do not establish factual correctness
- Use a practical routine for safer, evidence-aware generative AI work
Comparison
Separate three operations that assistants often combine
A conversational interface can hide several distinct mechanisms. Identifying them helps you diagnose errors and choose the right evidence.
Discriminate
Score, classify, extract, or rank among defined possibilities.
- Output is constrained or comparative
- Useful for detection and routing
- Can provide inputs to generation
- Example: classify user intent
Retrieve
Select existing records, passages, images, or examples from a collection.
- Returns source material
- Depends on indexing and ranking
- Can be checked against the collection
- Example: find a policy paragraph
Generate
Compose a new sequence, image, sound, or structured candidate from learned patterns and context.
- Flexible and open-ended
- Can synthesize across inputs
- May create unsupported details
- Example: draft a reply using the policy
Generation produces candidates from learned patterns
A text generator estimates plausible next tokens given instructions, context, and prior generated tokens; image, audio, and video generators use different representations and procedures, but they too create outputs by modeling patterns in training data.
“Plausible” is not the same as “true.” The training objective rewards pattern fit, while factual reliability depends on evidence, system design, evaluation, and the conditions of the request.
That gap is not only an engineering shortfall; part of it is provable. Adam Tauman Kalai and Santosh S. Vempala posted “Calibrated Language Models Must Hallucinate” on 24 November 2023. It was published in 2024. They derive “an inherent statistical lower-bound on the rate that pretrained language models hallucinate certain types of facts”. That bound has “nothing to do with the transformer LM architecture or data quality.” Some facts are “arbitrary”: their veracity cannot be determined from the training data. For those, a model satisfying a calibration condition generates a hallucination. The probability is “close to the fraction of facts that occur exactly once in the training data”. This holds “even assuming ideal training data without errors.” Their result is bounded in a useful way. It gives no statistical reason to expect the same behavior for facts that appear more than once. Nor does it for systematic facts such as arithmetic. That is one reason post-training, retrieval, and tools are the usual places to look for a remedy.
A generator is optimized to produce a likely or useful candidate, not to certify every claim it contains.
Visual
What happens between a prompt and a product action
A robust application adds context, controls, and validation around the model call. Stakes decide how many of those steps survive. Skip several for low-risk creative work; keep all of them for anything consequential.
Whether those steps exist is not only a design preference. It can settle who is answerable. In Moffatt v. Air Canada, decided on 14 February 2024, British Columbia’s Civil Resolution Tribunal held the airline responsible. A support chatbot had told a passenger booking travel after a death in the family that a bereavement fare could be claimed retroactively. The airline’s own policy page contradicted that. The tribunal recorded the airline’s defense and rejected it. “Air Canada argues it cannot be held liable for information provided by one of its agents, servants, or representatives – including a chatbot. It does not explain why it believes that is the case. In effect, Air Canada suggests the chatbot is a separate legal entity that is responsible for its own actions. This is a remarkable submission.” It found that Air Canada “did not take reasonable care to ensure its chatbot was accurate”. It added: “While a chatbot has an interactive component, it is still just a part of Air Canada’s website.” The generated sentence was the organization’s sentence.
- 1
Interpret the request
Classify intent, permissions, language, required format, and whether the task is allowed.
- 2
Assemble context
Add instructions, conversation state, retrieved evidence, user data, examples, or tool results.
- 3
Generate candidates
The model produces tokens, pixels, audio, code, or structured fields under decoding settings.
- 4
Validate output
Check schema, citations, calculations, policy, safety, and consistency with available evidence.
- 5
Request or execute tools
The application may authorize search, databases, calculators, or external actions with limited permissions.
- 6
Present and record
Show uncertainty and sources where useful, capture user edits, and log decisions for monitoring.
Example
Generative AI is larger than chat
Generative products create or transform many types of data. Each modality has different evaluation and misuse concerns.
Those misuse concerns already have regulators attached to them. The United States Federal Communications Commission adopted a Declaratory Ruling on 2 February 2024. It was released on 8 February. It confirmed “that the TCPA’s restrictions on the use of ‘artificial or prerecorded voice’ encompass current AI technologies that generate human voices”. Calls using a cloned voice therefore require the prior express consent of the person called. Commissioner Geoffrey Starks described the trigger in a statement attached to the same document. “In January, potential primary voters in New Hampshire received a call, purportedly from President Biden, telling them to stay home and ‘save your vote’ by skipping the state’s primary. The voice on the call sounded like the President’s, but of course it wasn’t. Those were voice cloning calls.” One modality, one product category, one law that already applied.
- Text: drafting, summarization, translation, extraction, dialogue, and transformation of style or structure.
- Images: concept exploration, editing, inpainting, layout, synthetic scenes, and visual variation.
- Audio: speech synthesis, voice conversion, music, sound effects, restoration, and dubbing.
- Video: storyboard generation, editing, motion synthesis, scene extension, and simulation assets.
- Code and structured outputs: candidate programs, queries, tests, plans, and records that require execution or schema validation.
- Multimodal systems: interpret combinations of text, image, audio, and video, then generate responses across modalities.
Analogy
An improviser with a reference packet
A skilled improviser can continue a scene from a character brief, recent dialogue, and a folder of facts, and the performance can be coherent and responsive even when the actor has no direct knowledge of the real event.
Prompts and retrieved context resemble the brief and the folder. An improviser has intentions and a life to draw on; a model has neither, and will blend supplied evidence with unsupported patterns without noticing the seam.
That limit has been measured on products sold precisely on the promise that the folder fixes it. Varun Magesh, Faiz Surani, Matthew Dahl, Mirac Suzgun, Christopher D. Manning and Daniel E. Ho posted a preregistered study on 30 May 2024. It is called “Hallucination-Free? Assessing the Reliability of Leading AI Legal Research Tools”. It was accepted on 14 March 2025 and published in the Journal of Empirical Legal Studies. The authors note that providers had touted retrieval-augmented generation as “eliminating” or “avoid[ing]” hallucinations, or as guaranteeing “hallucination-free” legal citations. Testing them told a different story. The tools “made by LexisNexis (Lexis+ AI) and Thomson Reuters (Westlaw AI-Assisted Research and Ask Practical Law AI) each hallucinate between 17% and 33% of the time.” The strongest of the four, Lexis+ AI, answered 65% of their queries accurately. Retrieval improved the odds against a general chatbot. It did not convert the answer into something a lawyer could file unread.
Context can guide generation, but guidance does not become a proof of factual grounding.
Key idea
Fluency, citations, and JSON can all create false confidence
A polished paragraph can be wrong. A citation can point to a source that does not support the claim. Valid JSON can contain invented values, and a tool call can request an unauthorized action.
Each layer requires its own validation: semantic claims against evidence, structures against schemas, calculations through reliable tools, and actions through permissions and policy.
A correct surface form is evidence only about form.
Case
Mata v. Avianca: six citations that did not exist
The case that put this on a court record is Mata v. Avianca, Inc., 22-cv-1461 (PKC) in the Southern District of New York. In an Opinion and Order on Sanctions filed on 22 June 2023, Judge P. Kevin Castel found that two attorneys and their firm “abandoned their responsibilities when they submitted non-existent judicial opinions with fake quotes and citations created by the artificial intelligence tool ChatGPT, then continued to stand by the fake opinions after judicial orders called their existence into question.” Six of the cited decisions did not exist. One was “Varghese v. China Southern Airlines Co., Ltd., 925 F.3d 1339 (11th Cir. 2019)” — a real reporter, a plausible circuit, a plausible year, and no such case. Asked afterwards whether Varghese was real, the chatbot replied that it “does indeed exist” and said it could be found on Westlaw and LexisNexis. Note what each validation layer would have caught here and what it would not: the prose was fluent, the citation format was valid, and only a lookup in the reporter itself settled the question. The judge drew the boundary carefully: “Technological advances are commonplace and there is nothing inherently improper about using a reliable artificial intelligence tool for assistance. But existing rules impose a gatekeeping role on attorneys to ensure the accuracy of their filings.”
Position
Fluency is not evidence, and retrieval does not fix it
The most expensive beginner mistake with generative systems is reading a well-formed answer as a checked one. Nothing in the objective rewards truth; it rewards plausible continuation. Kalai and Vempala's result matters precisely because it says some rate of confident error is a property of the setup rather than a defect awaiting a patch.
Grounding helps, and is worth building. It does not close the gap: the legal-research study in this lesson measured invented output from products sold specifically on the promise that retrieval had solved this. The lawyer in Mata v. Avianca did not lack intelligence or diligence. He lacked one step that checked whether the cited cases existed. Build that step into the application, before the output reaches a person who will act on it, and do not build it out of a firmer instruction to the model.
If your only defence against a false answer is asking the model to be accurate, you have no defence.
Steps
A safe-use routine for generative work
The routine changes with stakes. Creative brainstorming may tolerate uncertainty; medical, legal, financial, or security decisions require much stronger controls.
The step “Limit tool authority” has a specific attack behind it. OWASP’s Top 10 for Large Language Model Applications ranks prompt injection first, as LLM01. Its 2025 edition separates two forms. Direct prompt injections “occur when a user’s prompt input directly alters the behavior of the model in unintended or unexpected ways”. Indirect prompt injections “occur when an LLM accepts input from external sources, such as websites or files”. That content redirects the model once it is read. The class was named and demonstrated on 23 February 2023. The paper is “Not what you’ve signed up for: Compromising Real-World LLM-Integrated Applications with Indirect Prompt Injection”. Its authors are Kai Greshake, Sahar Abdelnabi, Shailesh Mishra, Christoph Endres, Thorsten Holz and Mario Fritz. They showed that processing retrieved prompts “can act as arbitrary code execution, manipulate the application’s functionality, and control how and if other APIs are called.” It is not a thought experiment. Microsoft published CVE-2025-32711 on 11 June 2025, under the title “M365 Copilot Information Disclosure Vulnerability”. It describes “Ai command injection in M365 Copilot allows an unauthorized attacker to disclose information over a network.” Least privilege matters here for one reason. The attacker may be a document your assistant was asked to read.
- 1
Classify the task
Separate creative, informational, analytical, and action-taking requests.
- 2
Provide bounded context
Supply relevant evidence, clear instructions, and explicit scope without exposing unnecessary sensitive data.
- 3
Ask for inspectable output
Request sources, assumptions, structured fields, alternatives, or uncertainty where they improve review.
- 4
Verify consequential claims
Check original sources, calculations, identifiers, and policy rather than trusting fluency.
- 5
Limit tool authority
Use least privilege, confirmations, sandboxing, and reversible actions for external tools.
- 6
Keep a recovery path
Allow editing, rejection, escalation, and non-AI completion when the output is unsuitable.
What Path 16 will add later
A later course examines tokenization, transformers, pretraining, post-training, decoding, retrieval engineering, tool use, evaluation, safety, serving, memory, and multimodal design in depth.
For now, keep the boundary. Generative AI produces candidates from learned patterns and supplied context; product reliability comes from the system that grounds, validates, authorizes, presents, and monitors those candidates.
Generation expands what software can propose; it does not remove the need to decide what should be trusted or executed.
Key takeaways
- Discrimination, retrieval, and generation are different operations that may appear behind one conversational interface.
- Generative models create plausible candidates from learned patterns and context rather than certifying truth.
- A production assistant may interpret requests, retrieve evidence, generate, validate, use tools, and record outcomes.
- Fluency, citations, valid schemas, and tool calls each require separate verification.
- Consequential actions need least privilege, confirmation, logging, and recovery outside the model.
- Path 16 will cover generative systems deeply; this lesson provides the safety and system boundary needed beforehand.