"The studio asks you to produce a small but serious hidden-string toolkit. This is the point where the module should start resembling real design work rather than lecture replay.\n"
" Build a compact notebook that recovers several secrets, defends a stable reporting convention, and compares at least two builder styles for auditability. Your aim is not maximal code. Your aim is a reliable family artifact.\n"
" Build a secret-recovery helper that you would actually trust next week. The test is whether another reader can tell which secret bits induce which oracle interactions.\n"
"editable_code = '\\nfrom qiskit import QuantumCircuit\\n\\ndef bv_oracle(secret: str = \"110\") -> QuantumCircuit:\\n oracle = QuantumCircuit(4, name=f\"bv_{secret}\")\\n ancilla = 3\\n for index, bit in enumerate(reversed(secret)):\\n if bit == \"1\":\\n oracle.cx(index, ancilla)\\n return oracle\\n\\ncircuit = QuantumCircuit(4, 3)\\ncircuit.h([0, 1, 2])\\ncircuit.x(3)\\ncircuit.h(3)\\ncircuit.compose(bv_oracle(\"110\"), inplace=True)\\ncircuit.h([0, 1, 2])\\n# Change the measurement order only if you can explain the reporting contract.\\ncircuit.measure([0, 1, 2], [0, 1, 2])\\n'\n",
"## Studio Prompt 3: Compare Two Builder Styles\n",
"\n",
"\n",
" Compare a lean and a more structured candidate. The point is not that one style is always correct. The point is to learn how to justify the tradeoff in review language.\n"
"quiz_block([{'prompt': 'What is the best studio target for this module?', 'options': ['A small secret-recovery library where the oracle contract and reporting order are both reviewable', 'The shortest possible BV code cell', 'A notebook that uses only barriers and screenshots'], 'correct_index': 0, 'explanation': 'Studio work should promote reusable, auditable design rather than compression alone.'}, {'prompt': 'Why is it useful to compare two secrets of different Hamming weights?', 'options': [\"It shows how the oracle body's density changes while the global motif stays stable\", 'It changes the number of required classical bits', 'It removes the need for a final Hadamard layer'], 'correct_index': 0, 'explanation': 'Different secret densities stress the same design pattern in different ways.'}], heading='Studio Design Check')\n"
" A good studio notebook in this module makes hidden structure feel ordinary and reviewable. If the secret still feels like a mysterious label rather than implemented structure, keep refining the builders and the prose until the structure is obvious.\n"
"A strong studio notebook is compact, explicit, and reviewable. It does not hide behind volume. It makes clear what family of circuits was explored, what invariant mechanism survived across the variants, what evidence justified the final recommendation, and what tradeoffs remained open. If your notebook cannot answer those questions yet, keep refining it. That refinement is the studio.\n"
"The finished notebook should feel like a small engineering artifact rather than a scrapbook. A reviewer should be able to open it, understand the task, inspect the candidate circuits, see the evidence, and understand why one recommendation won. If that standard is met on these small modules, later capstone work becomes much more realistic.\n"