\n",
"\n",
"# Course Blueprint\n",
"\n",
"This notebook is the first serious orientation notebook after `START_HERE.ipynb`. The earlier version of the project had ambition, interactivity, and a serious mastery model, but it still behaved too much like a set of topic notebooks. A world-class lecture series needs a stronger spine. The spine now comes from a hybrid design: textbook sequence for coherence, apprenticeship pressure for professional growth, and local-first Jupyter execution for sustained practice.\n"
],
"id": "92554a04"
},
{
"cell_type": "markdown",
"metadata": {},
"source": [
"\n",
"
\n",
"\n",
"\n",
"## Mainline Navigation\n",
"\n",
"Step 2 of 59. Follow the official walkthrough in order.\n",
"\n",
"Previous notebook: [Start Here](START_HERE.ipynb)\n",
"\n",
"Next notebook: [Principles and Circuit Literacy Lecture](foundations/module_01_principles_and_circuit_literacy/lecture.ipynb)\n",
"\n",
"Rule: complete the mandatory cells in this notebook before you open the next one.\n"
],
"id": "dcec697f"
},
{
"cell_type": "markdown",
"metadata": {},
"source": [
"\n",
"
\n",
"\n",
"## Why The Architecture Changed\n",
"\n",
"A beginner does not merely need more text. A beginner needs a trustworthy order. The PDF backbone that now informs this project moves from principles to qubits to gates to Qiskit engineering to optimization to simulation to algorithms and finally to workflow patterns. That sequence is strong because it makes later ideas feel earned rather than arbitrary.\n",
"\n",
"Our previous curriculum had a different strength: it was already clearer than most tutorials about the professional destination. It said that the end-state is not “ran some Qiskit notebooks” but “independent hardware-aware circuit designer.” That was the right ambition, but it was acting like a top-heavy staircase. The new architecture keeps the ambition and fixes the staircase.\n",
"\n",
"The result is a hybrid model:\n",
"\n",
"- the book-like spine provides canonical order\n",
"- the apprenticeship layer provides mastery gates and design pressure\n",
"- the notebook bundle pattern provides deliberate pedagogy instead of one giant mixed notebook\n",
"\n",
"This notebook is not here to motivate you vaguely. It is here to tell you exactly how the course is organized so the rest of the series becomes legible.\n"
],
"id": "23b60fdd"
},
{
"cell_type": "markdown",
"metadata": {
"ql_injected": "badge",
"ql_track": "meta",
"ql_role": "exercise"
},
"source": [
"\n",
"
\n",
"\n",
"## The Four Technical Bands\n",
"\n",
"The technical mainline now has four bands:\n",
"\n",
"1. **Foundations**: principles, qubits, gates, measurement, and the first disciplined understanding of circuits as arguments rather than raw syntax.\n",
"2. **Qiskit Engineering**: construction, analysis, transpilation, visualization, simulation, and noise models.\n",
"3. **Algorithmic Design**: foundational and applied algorithm families used as reusable circuit motifs, not just as curiosities.\n",
"4. **Professional Design**: workflow patterns, hardware-aware redesign, verification, mitigation thinking, and capstone review.\n",
"\n",
"Orientation still exists, but it is not the whole course. It is now treated like course navigation and diagnostic framing. Once that framing is clear, the course should feel like a real lecture series rather than a manifesto.\n"
],
"id": "46d3c062"
},
{
"cell_type": "markdown",
"metadata": {},
"source": [
"\n",
"
\n",
"\n",
"## The Bundle Pattern\n",
"\n",
"Every serious module will be rebuilt as a four-notebook bundle:\n",
"\n",
"- **Lecture**: deep explanation, canonical worked examples, misconceptions, and transfer language\n",
"- **Lab**: editable circuits, graphics, measurements, and representation shifts\n",
"- **Problems**: retrieval, prediction, debugging, and short written explanation\n",
"- **Studio**: open-ended design brief, comparison, critique, and review language\n",
"\n",
"The reason for this separation is simple. One notebook cannot cleanly teach, drill, diagnose, and evaluate design judgment all at once. Tutorials often collapse those roles into a single stream of cells, and the result feels busy but pedagogically blurry. The bundle pattern makes the burden of each notebook explicit.\n",
"\n",
"If you use the bundle correctly, you will move through four modes of learning:\n",
"\n",
"- understand\n",
"- manipulate\n",
"- retrieve\n",
"- design\n",
"\n",
"That sequence is closer to serious engineering education than a single mixed notebook could be.\n"
],
"id": "ca18ff10"
},
{
"cell_type": "markdown",
"metadata": {},
"source": [
"\n",
"
\n",
"\n",
"## Textbook Sequence And Apprenticeship Pressure\n",
"\n",
"The new architecture is easiest to understand if you separate two design questions that most learning platforms blur together. The first question is sequencing: in what order should ideas appear so that later ones feel intelligible rather than arbitrary? The second question is performance: what kind of work must the learner do so the ideas become capabilities instead of impressions? A textbook usually answers the first question well. An apprenticeship usually answers the second question well. This course is trying to answer both.\n",
"\n",
"The textbook influence can be seen in the chapter order that now sits underneath the curriculum. Principles come before qubits, qubits before gates, gates before serious Qiskit engineering, engineering before algorithmic reuse, and algorithms before professional workflow patterns. That order matters because it lets each stage inherit stable language from the stage before it. The apprenticeship influence can be seen in the mastery gates, the prediction prompts, the debugging emphasis, and the requirement to compare candidate designs instead of worshipping the first one that runs.\n",
"\n",
"If you remember only one phrase from this notebook, remember this one: the spine provides order, the apprenticeship provides pressure. Both are necessary.\n"
],
"id": "66fc3ce4"
},
{
"cell_type": "markdown",
"metadata": {},
"source": [
"\n",
"
\n",
"\n",
"## Why The Main Path Remains Local-First\n",
"\n",
"The source book includes IBM-platform tooling and cloud usage because it is written for a broad audience. That context is useful, but the main path in this repository remains local-first on purpose. Local-first is a teaching decision. It keeps the beginner loop short, reproducible, and under your control. When a circuit drawing fails, a dependency is missing, or a measurement plot looks wrong, the problem should be close enough that you can inspect it without a cloud account, network request, or moving API target getting in the way.\n",
"\n",
"This does not mean hardware awareness is optional. It means hardware awareness is introduced in the right place. First you build the clean story locally. Then you watch compilation, connectivity, or noise distort that story. That order is what protects conceptual clarity. If you begin inside distortion, you never get a clean enough picture of what the circuit was even trying to mean.\n"
],
"id": "44eb3632"
},
{
"cell_type": "markdown",
"metadata": {},
"source": [
"\n",
"
\n",
"\n",
"## What Counts As Progress\n",
"\n",
"Progress in this course is not “finished notebook.” It is:\n",
"\n",
"- explained a mechanism cleanly\n",
"- predicted behavior before running\n",
"- modified a circuit without losing the story\n",
"- debugged a mismatch without hand-waving\n",
"- compared two designs with explicit criteria\n",
"\n",
"This is why the course keeps the mastery model. The mastery model is not being replaced; it is being placed where it belongs. The textbook spine tells you what order to learn things in. The mastery gates tell you whether the capability is actually landing.\n"
],
"id": "fd0ee441"
},
{
"cell_type": "markdown",
"metadata": {
"ql_injected": "badge",
"ql_track": "meta",
"ql_role": "test"
},
"source": [
"\n",
"
\n"
],
"id": "913c755d"
},
{
"cell_type": "code",
"execution_count": null,
"metadata": {
"jupyter": {
"source_hidden": true
},
"tags": [
"hide-input"
]
},
"outputs": [],
"source": [
"quiz_block(\n",
" [\n",
" {\n",
" \"prompt\": \"What is the main function of the new bundle pattern?\",\n",
" \"options\": [\n",
" \"To split one topic across several notebook types that each carry a different pedagogical burden\",\n",
" \"To make the repository look larger\",\n",
" \"To avoid using long-form writing in notebooks\",\n",
" ],\n",
" \"correct_index\": 0,\n",
" \"explanation\": \"Lecture, lab, problems, and studio are intentionally different forms of training.\",\n",
" },\n",
" {\n",
" \"prompt\": \"Why is the textbook spine important?\",\n",
" \"options\": [\n",
" \"Because beginners need a canonical order so later topics feel earned and coherent\",\n",
" \"Because it removes the need for mastery gates\",\n",
" \"Because it guarantees all chapters are equally important\",\n",
" ],\n",
" \"correct_index\": 0,\n",
" \"explanation\": \"The spine supplies sequence and legibility; the apprenticeship layer supplies performance pressure.\",\n",
" },\n",
" {\n",
" \"prompt\": \"What is the purpose of the professional-design band?\",\n",
" \"options\": [\n",
" \"To defer all serious engineering until the end\",\n",
" \"To convert earlier circuit knowledge into review, redesign, mitigation, and capstone decision-making\",\n",
" \"To replace algorithms with workflow prose\",\n",
" ],\n",
" \"correct_index\": 1,\n",
" \"explanation\": \"The final band is where competence becomes engineering judgment.\",\n",
" },\n",
" ],\n",
" heading=\"Blueprint Quiz A\",\n",
")\n"
],
"id": "abe18ae3"
},
{
"cell_type": "markdown",
"metadata": {},
"source": [
"\n",
"
\n",
"\n",
"## What To Open Next\n",
"\n",
"The full technical mainline is now rebuilt. Start with **Principles and Circuit Literacy**, continue through the rest of the foundations modules, then move into **Circuit Construction and Analysis**, **Transpilation and Visualization**, and **Simulation and Noise Models**, then continue into **Deutsch Family and Oracle Thinking**, **Bernstein-Vazirani and Structured Oracles**, **QFT and Periodic Structure**, and **Grover and Amplitude Amplification**, and finally complete the professional band with **Qiskit Patterns and Workflow Design**, **Hardware-Aware Redesign Studio**, **Noise-Aware Verification and Mitigation**, and **Capstone Circuit Design Review**. Inside each module, finish the mandatory lecture cells first. Then finish the mandatory lab cells, then the mandatory problems cells, then the mandatory studio cells. Facultative cells never replace that order.\n",
"\n",
"The sequence matters. If you jump straight into the studio, you may produce activity without comprehension. If you stop after the lecture, you may feel recognition without control. The four-notebook loop is the point.\n"
],
"id": "dce35113"
},
{
"cell_type": "markdown",
"metadata": {
"ql_injected": "badge",
"ql_track": "meta",
"ql_role": "test"
},
"source": [
"\n",
"
\n"
],
"id": "2be36c91"
},
{
"cell_type": "code",
"execution_count": null,
"metadata": {
"jupyter": {
"source_hidden": true
},
"tags": [
"hide-input"
]
},
"outputs": [],
"source": [
"quiz_block(\n",
" [\n",
" {\n",
" \"prompt\": \"What is the intended first complete rebuilt module?\",\n",
" \"options\": [\n",
" \"Principles and Circuit Literacy\",\n",
" \"Capstone Circuit Design Review\",\n",
" \"Noise-Aware Verification and Mitigation\",\n",
" ],\n",
" \"correct_index\": 0,\n",
" \"explanation\": \"The foundations band is the correct place to establish the new standard.\",\n",
" },\n",
" {\n",
" \"prompt\": \"What should happen after you finish a lecture notebook?\",\n",
" \"options\": [\n",
" \"Move directly to the next lecture so momentum stays high\",\n",
" \"Use the lab, problems, and studio notebooks to convert explanation into capability\",\n",
" \"Treat the rest of the module as optional\",\n",
" ],\n",
" \"correct_index\": 1,\n",
" \"explanation\": \"The bundle is designed as a full cycle, not as four unrelated files.\",\n",
" },\n",
" {\n",
" \"prompt\": \"Where does the mastery model now sit in the architecture?\",\n",
" \"options\": [\n",
" \"It is replaced by the textbook sequence\",\n",
" \"It operates as the assessment and apprenticeship layer on top of the textbook sequence\",\n",
" \"It appears only in the capstone\",\n",
" ],\n",
" \"correct_index\": 1,\n",
" \"explanation\": \"The hybrid design keeps both sequence and performance standards.\",\n",
" },\n",
" ],\n",
" heading=\"Blueprint Quiz B\",\n",
")\n"
],
"id": "da5dae16"
},
{
"cell_type": "markdown",
"metadata": {
"ql_injected": "badge",
"ql_track": "meta",
"ql_role": "exercise"
},
"source": [
"\n",
"
\n",
"\n",
"## Immediate Route\n",
"\n",
"1. Open `notebooks/foundations/module_01_principles_and_circuit_literacy/lecture.ipynb`\n",
"2. Complete the full `lecture -> lab -> problems -> studio` loop for module 1\n",
"3. Repeat the same loop in `module_02_qubit_and_statevector_intuition`\n",
"4. Repeat the same loop in `module_03_gates_and_measurement`\n",
"5. Continue with `qiskit_engineering/module_01_circuit_construction_and_analysis`\n",
"6. Then complete `module_02_transpilation_and_visualization` and `module_03_simulation_and_noise_models`\n",
"7. Continue following the explicit next-notebook handoff until `COURSE_COMPLETE.ipynb`\n",
"\n",
"That is the one official walkthrough.\n"
],
"id": "d8de43bd"
},
{
"cell_type": "markdown",
"metadata": {},
"source": [
"\n",
"
\n",
"\n",
"\n",
"## What To Open Next\n",
"\n",
"Next notebook: [Principles and Circuit Literacy Lecture](foundations/module_01_principles_and_circuit_literacy/lecture.ipynb)\n",
"\n",
"Official walkthrough rule: after you finish the cells above, open the next notebook. There is no facultative material in this notebook.\n"
],
"id": "2cd865fe"
}
],
"metadata": {
"kernelspec": {
"display_name": "QuantumLearning (.venv)",
"language": "python",
"name": "quantum-learning"
},
"language_info": {
"name": "python",
"version": "3.12"
}
},
"nbformat": 4,
"nbformat_minor": 5
}