mirror of
https://github.com/saymrwulf/QuantumLearning.git
synced 2026-05-14 20:58:00 +00:00
93 lines
3.6 KiB
Markdown
93 lines
3.6 KiB
Markdown
|
|
# Mastery Model
|
||
|
|
|
||
|
|
The original five-notebook sequence was a bootcamp, not a profession-sized curriculum. That is why it felt like a toy path. A serious circuit-design program has to be designed backward from the end-state, not forward from a list of topics.
|
||
|
|
|
||
|
|
## Terminal Goal
|
||
|
|
|
||
|
|
The terminal goal is not "understand Qiskit" and not "run example notebooks." The terminal goal is:
|
||
|
|
|
||
|
|
**independent quantum circuit design under constraints**
|
||
|
|
|
||
|
|
That means you can:
|
||
|
|
|
||
|
|
- translate a problem statement into a circuit architecture
|
||
|
|
- reason about state evolution, measurement, and observables
|
||
|
|
- choose between alternative constructions and justify the tradeoff
|
||
|
|
- synthesize reusable subcircuits rather than copy ad hoc patterns
|
||
|
|
- adapt circuits to basis gates, connectivity, and transpilation pressure
|
||
|
|
- evaluate ideal behavior versus noisy or constrained behavior
|
||
|
|
- debug incorrect circuits systematically
|
||
|
|
- benchmark competing designs and defend a final design review
|
||
|
|
|
||
|
|
## Backward Design
|
||
|
|
|
||
|
|
Working backward from that end-state gives the real curriculum:
|
||
|
|
|
||
|
|
1. **Capstone Designer**
|
||
|
|
You can design, compare, benchmark, and defend full circuit families.
|
||
|
|
|
||
|
|
2. **Verifier and Reviewer**
|
||
|
|
You can prove or falsify whether a circuit really implements the intended behavior.
|
||
|
|
|
||
|
|
3. **Hardware-Aware Optimizer**
|
||
|
|
You can redesign circuits for topology, basis-gate, and routing constraints.
|
||
|
|
|
||
|
|
4. **Noise-Aware Experimentalist**
|
||
|
|
You can reason about distortion, robustness, and simulation-vs-reality gaps.
|
||
|
|
|
||
|
|
5. **Synthesis Engineer**
|
||
|
|
You can derive circuits from structure, not just imitate examples.
|
||
|
|
|
||
|
|
6. **Composable Designer**
|
||
|
|
You can build reusable blocks, subcircuits, parameterized templates, and design patterns.
|
||
|
|
|
||
|
|
7. **State and Measurement Thinker**
|
||
|
|
You can predict what a circuit is doing before running it.
|
||
|
|
|
||
|
|
8. **Circuit Literate Builder**
|
||
|
|
You can express circuits clearly in code, drawings, and simple experiments.
|
||
|
|
|
||
|
|
9. **Prepared Beginner**
|
||
|
|
You have the minimum Python, bitstring, and linear-algebra readiness to enter the apprenticeship.
|
||
|
|
|
||
|
|
## Forward Apprenticeship
|
||
|
|
|
||
|
|
The platform now follows that backward logic in forward order.
|
||
|
|
|
||
|
|
Each stage has four required outputs:
|
||
|
|
|
||
|
|
- **Conceptual mastery**: explain what the circuit is doing
|
||
|
|
- **Predictive mastery**: predict behavior before execution
|
||
|
|
- **Engineering mastery**: implement the circuit cleanly in code
|
||
|
|
- **Design mastery**: compare alternatives and justify one
|
||
|
|
|
||
|
|
Every serious stage ends with a mastery gate. Progress is not defined by notebook completion alone. Progress is defined by what you can design, explain, predict, debug, and defend.
|
||
|
|
|
||
|
|
## Why Two Modes Exist
|
||
|
|
|
||
|
|
The clean/ideal mode and dirty/reality mode are not two separate courses. They are two lenses on the same design problem.
|
||
|
|
|
||
|
|
- Ideal mode teaches what the circuit is supposed to mean.
|
||
|
|
- Reality mode teaches what survives contact with hardware constraints.
|
||
|
|
|
||
|
|
Professionals need both. If you only know the clean story, you cannot engineer. If you only know the dirty story, you cannot reason clearly.
|
||
|
|
|
||
|
|
## What Makes This Professional Rather Than Toy
|
||
|
|
|
||
|
|
This platform must eventually train these habits:
|
||
|
|
|
||
|
|
- derive before copy
|
||
|
|
- inspect before execute
|
||
|
|
- benchmark instead of guess
|
||
|
|
- compare multiple designs instead of falling in love with the first one
|
||
|
|
- treat transpilation and noise as first-class design constraints
|
||
|
|
- write reusable circuit builders, not only one-off notebooks
|
||
|
|
- perform design review on your own work
|
||
|
|
|
||
|
|
## Immediate Consequence
|
||
|
|
|
||
|
|
You are not starting a "Qiskit tutorial series." You are starting an apprenticeship in circuit design.
|
||
|
|
|
||
|
|
That means the first notebooks are deliberately basic, but they are basic **because they are prerequisites** for later mastery, not because the course stops there.
|
||
|
|
|