"This studio asks for protocol design. You are no longer just interpreting prepared examples. You are choosing how to prepare, how to probe, and how to report. That is exactly the kind of ownership a professional circuit designer needs.\n"
"Every answer should separate three layers explicitly: preparation, measurement basis, and reporting. If those layers remain fused in your language, the design is not yet under control.\n"
"Build a one-qubit protocol that produces a deterministic result in one basis and a non-deterministic result in another. The point is not novelty. The point is to justify why the contrast is caused by a changed question rather than by hand-waving.\n"
"editable_code = '\\ncircuit = QuantumCircuit(1, 1)\\n# [1] Try changing the preparation gate sequence.\\ncircuit.x(0)\\ncircuit.h(0)\\n# [2] Optionally add Z or another H before measurement.\\n# circuit.z(0)\\n# circuit.h(0)\\n# [3] Measure the result.\\ncircuit.measure(0, 0)\\n'\n",
"Start from the Bell preparation and decide which basis or readout change best tests the story you want to claim. Write your explanation as if another engineer had to review it.\n"
"editable_code = '\\ncircuit = QuantumCircuit(2, 2)\\n# [1] Prepare the correlated state.\\ncircuit.h(0)\\ncircuit.cx(0, 1)\\n# [2] Change the basis of the first measurement question.\\ncircuit.h(0)\\n# [3] Measure both qubits into the matching classical bits.\\ncircuit.measure([0, 1], [0, 1])\\n'\n",
"Use swapped or altered classical wiring deliberately. The point is to produce a circuit whose quantum preparation is fine but whose reporting layer could mislead a careless reader. Then write the warning note that a reviewer should leave.\n"
"quiz_block([{'prompt': 'What does the measurement studio demand that the lecture does not?', 'options': ['Deliberate protocol design and explicit justification of why a chosen measurement reveals what you claim', 'Less writing', 'No circuit edits'], 'correct_index': 0, 'explanation': 'The studio is where you own the protocol rather than merely understand it.'}, {'prompt': 'What is the hallmark of a good studio answer?', 'options': ['It separates preparation, basis choice, wiring, and evidence instead of blurring them together', 'It uses the most gates possible', 'It avoids comparison between alternatives'], 'correct_index': 0, 'explanation': 'Review language should make the protocol legible and falsifiable.'}], heading='Measurement Studio Check')\n"
"reflection_box('Which part of measurement reasoning now feels reliable, and which part still feels too dependent on the exact example in front of you?')\n"
"Use a strict rubric on yourself here. A good studio answer makes the preparation explicit, makes the basis choice explicit, makes the classical mapping explicit, and says what evidence would count as success or failure. It also admits uncertainty honestly. If you are unsure whether your chosen probe actually distinguishes two candidate explanations, write that uncertainty down and propose the next check. That is not weakness. That is proper review culture.\n",
"\n",
"This rubric is intentionally demanding because measurement notebooks are where many people learn bad habits: overclaiming from too little evidence, blurring protocol choices together, or treating a nice-looking plot as proof. The studio exists to train the opposite behavior. Clear protocol, explicit evidence, and disciplined interpretation. Nothing less will scale to professional work.\n"
"A strong studio result is not the most elaborate circuit. It is the clearest protocol. If you can prepare, question, report, and defend the evidence chain cleanly, the module has done its job.\n"