Student guide: Contradictions in Context

Use invented, low-stakes prompts. The purpose is to notice unresolved conflicts before they turn into confident-looking work.

1. Predict before you run

Write what you think the tool might do: ask a question, choose one instruction, blend them, ignore one, or invent a reconciliation.

2. Create one labeled conflict

Try a conflict in facts, goals, tone/format, audience assumptions, or a long thread. Example: “The event is Tuesday” followed by “The event is Thursday.” Keep the conflicting phrases visible.

3. Record the visible result

Note exactly what happened. Did the tool ask? Which side did it choose? Did it quietly blend incompatible instructions? Do not call a polished answer a repair.

4. Diagnose the risk

Write which phrase conflicts, what a busy reader might accept too quickly, and who must resolve the conflict.

5. Repair the context

State the authoritative fact, the audience, the required length, and when the tool may ask a question. Run again and compare the two outputs.

Completion check

Keep the original prompt, prediction, result, diagnostic note, repaired prompt, revised result, and warning sign. You are done when you can explain why the original response looked acceptable while remaining unresolved.

Recovery tips

If you cannot identify the contradiction in words, make a two-column table. If a tool asks a good question, record that as a useful behavior—not a guarantee. Never test real emergencies, health, legal, employment, or client decisions.

---

Source: labs/contradictions-in-context/companions/student-step-by-step.md