Week 4 · QR-4 · Glossary studio + worked lab on classical → quantum mapping, optimization, and benchmarking
Quantum Vocabulary and the Classical Baseline
Say the words precisely. Then prove a result the old way before you claim a new one.
Partner: Quantum Global Group · Portfolio Lab · 8–10 hours
Why this week
A readiness program that ends on inspiration is incomplete. Week 4 is the professional habit: language + baseline + mapping + benchmark.
Two jobs share this week on purpose. First, the cohort locks a shared vocabulary — the words that get abused in decks and papers. Second, learners walk the only workflow that makes applied quantum honest: define a classical baseline, map the problem toward a quantum algorithm or quantum computer, optimize, and compare. The Quantum Hybrid Portfolio lab is the reference implementation.
Learning outcomes
- Define the primary vocabulary of the month in writing, with no circular definitions.
- State a classical baseline for a chosen problem, including metric, data, and method.
- Describe how that problem maps (or fails to map) onto a quantum / hybrid algorithm.
- Run or read an optimization and a comparison (quality, cost, runtime, robustness).
- Write a results paragraph that a skeptical engineer would accept.
Modules
Vocabulary studio
2 hours
Outcomes
- Produce exact definitions for the core lexicon (see /learn/glossary).
- Catch three common misuses (quantum supremacy vs advantage, annealing vs gate-model, etc.).
Activities
- Closed-book definition drill.
- Peer review: swap cards and mark vagueness.
Define the classical baseline
2 hours
Outcomes
- Write problem, data, method, metric, and success threshold.
- Explain why a quantum claim without this paragraph is incomplete.
Activities
- Worked example: Markowitz / min-variance / HRP on a small ticker universe.
- Learners draft the same five fields for their own SME problem (or the portfolio example).
Map, optimize, compare
3–4 hours
Outcomes
- Describe QUBO / variational mapping at a conceptual level.
- Compare at least two methods on the same instance.
Activities
- Portfolio Lab: classical objective vs QUBO+SA / VQE / QAOA path (simulator is enough).
- Fill the benchmark table: metric, runtime, feasibility, notes on noise.
- Office hours: “is this a good use case or a demo?”
Where you go next
45 min
Outcomes
- Pick one regional hub and one public project (hackathon, Fall Fest, or GitHub).
- Know the C1000-179 and Advocate gates if you are on a software/algorithms path.
Activities
- Complete /learn/next: LinkedIn headline, hub, and one event.
- Software track: skim C1000-179 objective map; schedule the assessment exam after the month.
Deliverable
Capstone brief (3–4 pages or equivalent slides): vocabulary appendix, classical baseline, mapping, optimization notes, benchmark table, and a go / no-go recommendation.
Assessment
Rubric on definition precision, baseline completeness, mapping honesty, and comparison quality. A beautiful circuit with no baseline cannot pass.