" Prefer answers that separate mechanism, evidence, and conclusion. Reject answers that use the word noise or mitigation as if they explained themselves.\n"
"quiz_block([{'prompt': 'Which invariant is useful for a Bell-style correctness check?', 'options': ['Support concentrated on correlated outcomes with limited imbalance between 00 and 11', 'Only total shot count', 'The number of markdown cells'], 'correct_index': 0, 'explanation': 'A good invariant captures the intended structure of the state.'}, {'prompt': \"Why is 'looks entangled' weak evidence?\", 'options': ['Because verification needs explicit criteria, not aesthetic impressions', 'Because entanglement can never be visualized', 'Because only hardware data matters'], 'correct_index': 0, 'explanation': 'A professional verifier states what will count as passing evidence.'}], heading='Invariants')\n"
"quiz_block([{'prompt': 'What is the strongest sign that a result reflects a design bug rather than modest noise?', 'options': ['The ideal circuit already fails the intended invariant', 'The noisy histogram is not perfectly sharp', 'The transpiler changed gate names'], 'correct_index': 0, 'explanation': 'If the clean mechanism is broken, noise is not the primary story.'}, {'prompt': 'Why run both ideal and noisy variants of the same circuit?', 'options': ['To separate structural correctness from robustness', 'To avoid writing explanations', 'To guarantee mitigation works'], 'correct_index': 0, 'explanation': 'The comparison reveals which failure mode you are actually facing.'}], heading='Bug Versus Noise')\n"
"quiz_block([{'prompt': 'What is a strong mitigation sentence?', 'options': ['Postselection raised the correlated-support rate, which suggests leakage was a major issue, but it did not repair the underlying circuit if the ideal invariant already failed', 'Postselection fixed quantum computing', 'Filtering makes every circuit correct'], 'correct_index': 0, 'explanation': 'Mitigation claims should stay bounded and mechanism-aware.'}, {'prompt': 'Why keep mitigation local-first in this project?', 'options': ['Because diagnosis and repair habits should be learnable without cloud dependencies', 'Because real hardware never matters', 'Because noise cannot be simulated locally'], 'correct_index': 0, 'explanation': 'Local-first makes the reasoning loop short and reproducible.'}], heading='Mitigation Reasoning')\n"
"quiz_block([{'prompt': 'Which review note is strongest?', 'options': ['The notebook compares noisy data to no stated invariant, so the diagnosis is under-specified', 'The histogram is ugly', 'Please remove the baseline because it is redundant'], 'correct_index': 0, 'explanation': 'The real issue is the missing diagnostic standard.'}, {'prompt': 'What should support a final verification claim?', 'options': ['Ideal reference, noisy comparison, explicit invariant, and a reasoned distinction between defect and distortion', 'Only a single noisy run', 'Only intuition about what should happen'], 'correct_index': 0, 'explanation': 'Verification requires a multi-layer evidence chain.'}], heading='Review Language')\n"
" Many weak notebooks reach for the word noise too quickly. Something went wrong, the histogram looks imperfect, therefore the explanation must be noise. That move is dangerous because it can hide design defects behind physical-sounding language. These problems are designed to slow you down and make you earn every diagnostic conclusion.\n"
"The multiple-choice format is only the surface. Underneath it, the notebook is testing whether you can preserve the right burdens while the wording shifts. If your understanding is strong, a changed phrase still points you back to the same structure, constraint, invariant, or recommendation logic. If your understanding is weak, the wording change will tempt you into vague or prestige-based answers. That is why these problem sets matter.\n"
"A common failure mode in advanced notebook work is broad correctness with local vagueness. A learner says something true at a high level, yet still fails to name what this particular workflow, redesign, diagnosis, or recommendation is actually doing. The problems notebook is meant to squeeze that vagueness out. It prefers circuit-specific or review-specific sentences over vague correctness.\n"
"The written prompts at the end of this notebook are not filler. They are where you prove that the right distinctions are surviving contact with your own prose. Multiple-choice blocks can tell you whether a distinction still feels recognizable. A written answer tells you whether you can actually deploy that distinction in a design note, verification memo, or review comment. Professional skill depends on that second ability.\n"
"feedback_iteration_panel(title='Noise-Aware Verification and Mitigation Problem-Set Review Loop', prompt='After the quizzes, write the claim you now trust most, the evidence pattern behind it, the phrasing that still feels weak, and the next rewrite you owe yourself.')\n"