Create your quantum learning series

Eight prepared episodes take you from first principles to a usable teaching product. Scripts, exact capture instructions and original vector thumbnails are ready below. No footage has been recorded or video published.

01. Start with the question

Episode 01: Start with the question thumbnail

What can a quantum learning product honestly do?

Begin with a user, not a claim of quantum advantage. Our user is a beginner who wants to predict and explain a simple result. The product will be a browser teaching tool. It will not create entangled photons or operate a quantum computer. State a measurable goal: after using the demo, a learner can explain a correlation and name one limitation. Record your initial guess, then revisit it at the end.

Capture exactly this

Open the Qentangle homepage, choose Start learning, and read the simulator limitation. Show the six-step roadmap.

Recording steps

  1. Use a clean browser profile and 1920×1080 capture; enable a visible cursor.
  2. Record the introduction, then the listed demo in one deliberate pass.
  3. Pause on each prediction before showing the output; record narration separately if needed.
  4. Review captions, mathematical symbols and scientific claims against the sources.
  5. Check for private data; export a local draft. Publishing requires a separate decision.

Acceptance: A written audience, learning question and success criterion.

Download script and shot list · Download generated thumbnail

02. Learn probability and qubits

Episode 02: Learn probability and qubits thumbnail

More qubits does not mean faster

A probability describes how often an outcome is expected, not a promise for a single trial. A qubit uses amplitudes; their squared magnitudes give measurement probabilities. At ninety degrees this model gives equal probabilities. A qubit count describes the number of qubits, not a speed rating. Performance depends on the algorithm, gates, noise and connectivity. Predict the output before changing each control, then compare.

Capture exactly this

Capture journey steps 1 and 2. Show probability at 0, 50 and 100 percent, then state angles 0, 90 and 180 degrees. Submit the wrong qubit-speed answer and show the explanatory feedback.

Recording steps

  1. Use a clean browser profile and 1920×1080 capture; enable a visible cursor.
  2. Record the introduction, then the listed demo in one deliberate pass.
  3. Pause on each prediction before showing the output; record narration separately if needed.
  4. Review captions, mathematical symbols and scientific claims against the sources.
  5. Check for private data; export a local draft. Publishing requires a separate decision.

Acceptance: Three correct probability predictions and an explanation of why qubit count is not speed.

Download script and shot list · Download generated thumbnail

03. Prepare an entangled state

Episode 03: Prepare an entangled state thumbnail

A pair alone is not enough

Start with two qubits in zero. Applying H to the first creates a superposition. The controlled-NOT then correlates the qubits in a Bell state. This is a mathematical circuit demonstration. A physical photon source must prepare an appropriate joint state; producing two photons does not automatically entangle them. Shorter wavelength means more photon energy, not faster vacuum propagation or guaranteed stronger entanglement. Making a chip and cooling some devices for operation are separate processes.

Capture exactly this

Capture step 3 at start, H, and H followed by CNOT. Frame the four outcome probabilities. Add a title card showing E=hc/λ and “same speed in vacuum”.

Recording steps

  1. Use a clean browser profile and 1920×1080 capture; enable a visible cursor.
  2. Record the introduction, then the listed demo in one deliberate pass.
  3. Pause on each prediction before showing the output; record narration separately if needed.
  4. Review captions, mathematical symbols and scientific claims against the sources.
  5. Check for private data; export a local draft. Publishing requires a separate decision.

Acceptance: Correct preparation sequence, and no claims of creating physical entanglement.

Download script and shot list · Download generated thumbnail

04. Observe without remote control

Episode 04: Observe without remote control thumbnail

Correlations are not instant messages

The two outcomes are related statistically, but each local result remains random. This panel models a polarization singlet, different from the previous Bell state. The formula uses twice the analyzer-angle difference. When both observers later compare records, the correlation varies with their settings. Alice cannot choose Bob’s result to send an instant signal. Do not animate a controllable influence travelling from one photon to its partner.

Capture exactly this

Capture step 4 with A=0 and B=0,45,90. Show the numeric probabilities and graph together. Zoom on each local marginal staying one half.

Recording steps

  1. Use a clean browser profile and 1920×1080 capture; enable a visible cursor.
  2. Record the introduction, then the listed demo in one deliberate pass.
  3. Pause on each prediction before showing the output; record narration separately if needed.
  4. Review captions, mathematical symbols and scientific claims against the sources.
  5. Check for private data; export a local draft. Publishing requires a separate decision.

Acceptance: Explain a joint correlation while preserving random local outcomes.

Download script and shot list · Download generated thumbnail

05. Test the model

Episode 05: Test the model thumbnail

Bell inequality: what it proves and what it does not

A Bell test combines several correlations, not just matching results in one basis. The CHSH expression has a classical bound of two under its assumptions. Our ideal mathematical model reaches two times the square root of two. Reducing visibility reduces the value. This browser computes exact expectations; there are no experimental counts or instrument calibrations. A real Bell experiment requires physical measurements and careful treatment of assumptions and loopholes. A simulation above two is not proof that our computer produced entanglement.

Capture exactly this

Capture step 5 at visibility 100,70,0 percent. Show all four analyzer settings, S, and the classical bound. Display the IBM reference page title without copying its article.

Recording steps

  1. Use a clean browser profile and 1920×1080 capture; enable a visible cursor.
  2. Record the introduction, then the listed demo in one deliberate pass.
  3. Pause on each prediction before showing the output; record narration separately if needed.
  4. Review captions, mathematical symbols and scientific claims against the sources.
  5. Check for private data; export a local draft. Publishing requires a separate decision.

Acceptance: Reference settings reproduce expected S; limitations are spoken and shown.

Download script and shot list · Download generated thumbnail

06. Build your first product

Episode 06: Build your first product thumbnail

A reproducible Bell-correlation demonstrator

A useful product makes its purpose, inputs and evidence clear. Our first version is an educational demonstrator, not a security tool. Write the brief, run the checks, and export the report. Ask another beginner to predict a result and explain a limitation. Record what confused them and revise one thing at a time. Passing model checks does not automatically prove usability, scientific completeness or hardware readiness.

Capture exactly this

Capture step 6. Enter a brief for a beginner audience, run all reference checks, download JSON and open it. Show settings, formula, results and limitations without private account data.

Recording steps

  1. Use a clean browser profile and 1920×1080 capture; enable a visible cursor.
  2. Record the introduction, then the listed demo in one deliberate pass.
  3. Pause on each prediction before showing the output; record narration separately if needed.
  4. Review captions, mathematical symbols and scientific claims against the sources.
  5. Check for private data; export a local draft. Publishing requires a separate decision.

Acceptance: Saved reproducible report plus a separate user-feedback note.

Download script and shot list · Download generated thumbnail

07. Release responsibly

Episode 07: Release responsibly thumbnail

Content, accessibility and operations

Before release, check the entire path, not just the hero image. Confirm that a keyboard user can operate controls and read results. Check phone layouts, logos, favicons and link destinations. Verify account routes and deny access to deployment metadata. Keep a reversible release copy and measure performance before changing settings. Administrative controls must check permission on the server. Demonstrate only synthetic content and never show real inboxes or credentials in the recording.

Capture exactly this

Record public navigation at desktop and mobile widths. Show labeled controls with keyboard focus. In a staging admin session, show page metadata, version history and performance settings; redact email addresses, mail contents, CSRF tokens and authenticator secrets.

Recording steps

  1. Use a clean browser profile and 1920×1080 capture; enable a visible cursor.
  2. Record the introduction, then the listed demo in one deliberate pass.
  3. Pause on each prediction before showing the output; record narration separately if needed.
  4. Review captions, mathematical symbols and scientific claims against the sources.
  5. Check for private data; export a local draft. Publishing requires a separate decision.

Acceptance: A release checklist with measured results, known limits and rollback reference.

Download script and shot list · Download generated thumbnail

08. Research the next version

Episode 08: Research the next version thumbnail

From demonstration to a validated application

Choose a narrow next question: for example, how detector noise affects a learning explanation. Separate an idea, a simulation, a hardware experiment and a validated product. Cite original research and record assumptions. If moving to physical hardware, select a suitable provider or laboratory, understand cost and calibration, and design a controlled experiment. Never infer quantum advantage from qubit count alone. The next milestone is evidence against a clear requirement, not a more dramatic claim.

Capture exactly this

Capture the exported report, a new research-note template, and source citations. Show a proposed hardware comparison table marked “not executed”. End on the product-feedback task.

Recording steps

  1. Use a clean browser profile and 1920×1080 capture; enable a visible cursor.
  2. Record the introduction, then the listed demo in one deliberate pass.
  3. Pause on each prediction before showing the output; record narration separately if needed.
  4. Review captions, mathematical symbols and scientific claims against the sources.
  5. Check for private data; export a local draft. Publishing requires a separate decision.

Acceptance: A research question, source list, experiment plan and explicit unverified assumptions.

Download script and shot list · Download generated thumbnail

Sources: IBM CHSH tutorial · IBM quantum information course.