Module 2 · Mastering Context Threads · 20 min
Detect and Correct Instruction Drift
Is lesson ke baad tum
Identify the violated requirement, request a concrete correction, and validate the result. A promise to remember is not evidence of a repair.
In this lesson
Repair an answer that breaks a stated rule, then check the repair yourself. “Instruction drift” describes the observable problem: a response no longer follows an earlier instruction. It does not establish why the failure happened.
Make the Failed Requirement Visible
“Wrong tone” can be hard to act on. “The reply promised Friday delivery when the source gives no date” identifies something you can fix.
Use a short correction loop:
- Quote the requirement.
- Point to the violating text.
- Request the corrected output, not a promise about future behaviour.
- Validate the result against the source.
- If a clear retry still fails, simplify the task, use a checked handoff, or complete it manually.
For a word limit, count words. For a table, inspect its columns. For factual claims, compare each one with the approved source. A model's own “all checks passed” statement is not an independent check.
Worked Example
Fictional source: A shop has packed a wallet. Courier collection is pending. No delivery date is confirmed.
Required output: A table with columns “Confirmed” and “Still unknown.” Use only source facts.
Illustrative failed answer:
Your wallet has shipped and should arrive on Friday.
Both the format and the facts fail. A useful correction is:
The required output is a table with Confirmed and Still unknown columns.
Your answer is prose, and "shipped" and "Friday" are not supported.
Source: Wallet packed; courier collection pending; delivery date unknown.
Return the corrected table using only that source.A passing result would be:
| Confirmed | Still unknown |
|---|---|
| Wallet packed; courier collection pending | Delivery date |
The table is the evidence that the correction worked. “I will remember the rule” would leave the original problem unresolved.
Hands-On Exercise
Use this different fictional source:
Workshop: Saturday, 11 am, Room B, Lahore.
Fee: PKR 1,000.
Payment method: not decided.
Requirement: Exactly two bullets; no invented details.The failed draft is:
Join us Saturday at 10 am in Room B. Pay PKR 1,000 through our website. Only two seats remain!
Write a correction request. Then produce the corrected output in an assistant or manually, and check it.
Check your work: The problems are 10 am instead of 11 am, an invented website payment route, invented scarcity, and the missing two-bullet format. One acceptable repair is:
- The workshop is on Saturday at 11 am in Room B, Lahore.
- The fee is PKR 1,000; the payment method has not yet been decided.
Your result must fix all four problems. Correcting the time while retaining “two seats remain” is an incomplete repair.
Know When to Change Approach
A rule can be clear and still be missed. Long context, conflicting instructions, product behaviour, or ordinary model variability may contribute. Record the failure without claiming you know the internal cause.
If the same material error survives a clear retry, stop repeating “follow instructions.” For this short workshop reminder, writing the two bullets yourself is a useful fallback. For a larger task, move the checked facts and requirement list into a fresh conversation using Lesson 2.2.
For bilingual work, check names, dates, PKR amounts, and the requested script separately. An answer can sound natural while still reporting the wrong fee.
Completion Rubric
Practice quiz
Check yourself
4 questions · practise what you just learned
1 / 4 · sequence
The required output is a Confirmed/Still unknown table, but the answer says 'shipped, arriving Friday' although only packing is confirmed. Which correction request best addresses the failure?
Apna kaam check karo.
Practice complete ki? Result ko example aur lesson ke checks se compare karo.
This is your own completion record, not a graded assessment.