" Produce a local verification notebook that states the intended invariant, compares clean and noisy behavior, and writes a mitigation note that is useful precisely because it is limited and evidence-backed.\n"
"editable_code = '\\nfrom qiskit import QuantumCircuit\\n\\ndef bell_candidate(bug: bool = False) -> QuantumCircuit:\\n circuit = QuantumCircuit(2, 2)\\n # [1] Toggle only one potential design defect at a time.\\n if not bug:\\n circuit.h(0)\\n # [2] Correlate the second wire so the intended support is {00, 11}.\\n circuit.cx(0, 1)\\n # [3] Keep the reporting layer explicit and stable.\\n circuit.barrier()\\n # [4] Measure both outputs so invariants can inspect the evidence.\\n circuit.measure([0, 1], [0, 1])\\n return circuit\\n\\ncircuit = bell_candidate(bug=False)\\n'\n",
"quiz_block([{'prompt': 'What is a strong studio outcome for this module?', 'options': ['A verification notebook that states an invariant, compares clean and noisy behavior, and writes a bounded mitigation note', 'A notebook that only declares the result noisy', 'A notebook that assumes any deviation is a design bug'], 'correct_index': 0, 'explanation': 'The studio should culminate in disciplined diagnosis, not generic complaint.'}, {'prompt': 'Why does this module belong in the professional band?', 'options': ['Because serious circuit work requires debugging and falsification habits, not only construction skill', 'Because noise makes design impossible', 'Because ideal simulation is obsolete'], 'correct_index': 0, 'explanation': 'Professional competence includes knowing how to test and challenge a design.'}], heading='Studio Design Check')\n"
"evidence_checklist(['The notebook states the objective or decision clearly.', 'The relevant constraints are explicit and stable.', 'Evidence is tied to a concrete circuit, output, or metric.', 'At least one uncertainty or risk is named explicitly.', 'The notebook ends with a next action or defended judgement.'], title='Noise-Aware Verification and Mitigation Evidence Checklist')\n"
" A strong studio notebook in this module reads like a careful case file. It says what should happen, what actually happened ideally, what changed under noise, and why any mitigation claim remains bounded by explicit evidence.\n"
"A strong studio notebook is compact, explicit, and reviewable. It does not hide behind volume. It makes the objective clear, the candidate or case structure visible, the evidence traceable, and the final judgement conditional in the right way. If those things are not yet present, the notebook is not finished no matter how many cells it contains.\n"
"The finished notebook should feel like something another engineer could open and use. They should be able to understand what the notebook is trying to decide, how the circuits were compared, what evidence was gathered, and why the recommendation or diagnosis ended where it did. That is the practical definition of \"world-class\" in this project: not theatrical polish, but concentrated clarity under real engineering burdens.\n"
"Before you leave a studio notebook, ask one last question: if another engineer disagreed with my conclusion, would the notebook give them enough material to locate the disagreement precisely? If the answer is yes, the studio is doing its job.\n"
"feedback_iteration_panel(title='Noise-Aware Verification and Mitigation Studio Revision Loop', prompt='Write the decision or diagnosis the studio currently supports, the evidence carrying that weight, the main remaining uncertainty, and the next revision that would sharpen the notebook.')\n"