Chapter C93 · Interactive Course

Use it: diagnose a lost detail

Why a supplied fact went missing, and what to do about it.

Start chapter in web app

Core Learning Concept

Locate an ignored requirement and confirm it was present in the prompt. Test a focused repair by restating instructions near the query, then verify whether the output actually respects the requested constraint.

What You’ll Learn in This Chapter

  1. The detail that went missing

    Activity 1 of 7 · 5 min

    Locate the supplied fact that a response ignored.

    Start by verifying whether an ignored requirement was actually present in the model input context. A requirement documented elsewhere cannot guide generation unless it is explicitly supplied in the current prompt.

    Start activity →

  2. Distance is not the whole story

    Activity 2 of 7 · 5 min

    Reject “it was too far away” as a complete explanation.

    Long contexts can dilute attention across distant instructions or competing examples. When key constraints sit far from the generation prompt, models may overlook them in favor of more prominent local text patterns.

    Start activity →

  3. Repeat the detail where it is used

    Activity 3 of 7 · 4 min

    Choose a repair that puts the fact near the task.

    A reliable repair places critical instructions close to where generation begins, while pruning irrelevant background text. Moving vital constraints to prominent positions helps the model attend to them directly and accurately.

    Start activity →

  4. A heatmap is not a reason

    Activity 4 of 7 · 4 min

    Refuse an attention picture as proof of a cause.

    Testing an input modification provides causal evidence about whether that change improves prompt compliance. Compare before-and-after responses systematically across repeated runs rather than guessing internal motivations from a single lucky answer.

    Start activity →

  5. Explain it in two sentences

    Activity 5 of 7 · 4 min

    Give a causal account without equations.

    Document observed prompt failures alongside verified remedies using concrete before-and-after examples. Clear empirical evidence about what worked helps engineering teams maintain reliable and robust prompt designs over successive model updates.

    Start activity →

  6. Apply it: diagnose a lost detail

    Activity 6 of 7 · 7 min

    Carry out the whole diagnosis once: find the dropped fact, explain it with position and competition, choose a repair and say what the evidence supports.

    Start activity →

  7. Explain the Transformer without equations

    Activity 7 of 7 · 6 min

    Trace one attention operation on a translation diagram, place it inside the block, and say what the 2017 paper added.

    Start activity →