Part I. Mental Model

Probability vs Amplitude

A quantum state is not a list of probabilities, and treating it as one is the fastest way to misread every algorithm in this book. This chapter draws the exact line between amplitude and probability, then shows with a single gate what information you destroy when you cross that line too early.

Listen to this chapter

Interference — amplitudes canceling and reinforcing before anyone measures — is the one genuinely new computational resource quantum mechanics adds to the classical toolkit. Every quantum speedup ever proposed is, at bottom, a scheme for shaping that interference so the right answer survives.

By the end of this chapter you will be able to normalize a qubit state, turn amplitudes into measurement probabilities, and explain why two states that look identical to a measurement can behave oppositely inside a circuit.

Core concepts: complex amplitudes, normalization, the Born rule, relative phase, interference.

Same probabilities, different amplitudes Two states measurement cannot tell apart alpha beta |+> |-> amplitudes: what gates transform 1/2 |+> |-> P(0) P(1) P(0) P(1) probabilities: what measurement returns
Notice that the two distinct states on the left produce identical bars on the right. An immediate measurement cannot tell |+> from |-> — yet the sign difference survives inside the state and decides what the next gate does.

Two kinds of number

A probability is a nonnegative number that directly says how likely an outcome is. An amplitude is a number — often complex — that contributes to a probability only after you take its squared magnitude. Amplitudes can be positive, negative, or complex, which means they can cancel each other or reinforce each other before measurement enters the story.

That cancellation and reinforcement is the heart of every quantum algorithm. A randomized classical algorithm can spread probability mass across many outcomes, but probabilities only ever add. A quantum algorithm can arrange amplitudes so that paths leading to wrong answers cancel and paths leading to right answers survive. Measurement then samples from a distribution that interference has already shaped.

One sentence is worth memorizing: amplitudes are the quantities quantum operations transform; probabilities are what measurement produces from them. Most confused claims about quantum computing violate this sentence somewhere.

The rules, written down

A one-qubit state is written , where and are complex amplitudes. The state is normalized when — total probability must come to one, because measurement always returns something.

Measurement in the computational basis follows the Born rule: the outcome 0 appears with probability , and 1 with probability . Square first, then interpret — never the other order.

Here is the subtlety the rest of the book exploits. Take with , and both outcomes have probability . Now flip the sign so : the probabilities are still each. The relative sign is invisible to an immediate measurement — but it is real, it is stored in the state, and later gates respond to it.

Worked example: one gate separates two states

Compare the two states from the figure:

For both, and . No single computational-basis measurement, and no number of repeated measurements on identically prepared copies analyzed in that basis alone, distinguishes them reliably.

Now apply a Hadamard gate — the workhorse single-qubit transformation this book uses constantly — to each:

Identical measurement statistics went in; opposite, perfectly predictable outcomes came out. The Hadamard converts relative phase into amplitude difference, and the amplitudes that used to cancel now reinforce. This is why a quantum state is more than a probability distribution. If you compress a state to its probabilities too early, you throw away exactly the information quantum algorithms spend their whole budget manipulating.

Where the intuition fails

The first trap is linguistic: saying "the probability of 0 has a negative sign" or "the probability is complex." Probabilities are never negative and never complex. Amplitudes carry signs and phases; probabilities are squared magnitudes. Keeping the two vocabularies separate is not pedantry — it is the difference between describing interference and describing noise.

The second trap is grandeur: assuming that because a state has amplitudes on many basis states, measurement reveals all of them. It does not. The amplitudes shape a distribution; measurement returns one classical sample drawn from it. A register with amplitudes on basis states still yields classical bits per measurement, and the algorithm's job is to make those bits useful.

The engineering view

For a computer scientist, amplitudes behave like internal representation, not output. They are hidden state that affects later behavior but is never returned by the API — the API is measurement, and it returns samples. You would not judge a service by dumping its heap; do not judge a quantum algorithm by staring at its statevector.

This is also why simulators mislead. A statevector simulator will happily print every amplitude, because your classical machine is expensively simulating the quantum state. Real hardware hands you no such thing: it returns measurement outcomes from the bases you chose, at the shot count you paid for. Designs that depend on "reading the statevector" are designs that only work on simulators, and the distinction decides what scales.

What this buys you in diligence

When a pitch says the machine explores states and therefore solves the problem, ask one question: how does the algorithm make the desired answer more likely to be measured? If the answer is only that many amplitudes exist, the claim is incomplete. Amplitudes on every basis state are the default condition of a quantum register, not an achievement.

The serious version of any such claim names the interference structure, the measurement strategy, the error budget, and the classical baseline. Those four items are where the business value either exists or doesn't, and all four are checkable without taking anyone's word for anything.

Exercise

Normalize and interpret. Take the state and work it end to end.

  • Submit: the normalized state, both measurement probabilities, and one sentence explaining why the phase on could matter after a later gate even though it does not change either probability.
  • Check: confirm the probabilities sum to 1, and re-read your write-up to make sure you never called an amplitude a probability.
  • Repair: if you found yourself taking the square root of a probability to get an amplitude, you crossed the line in the wrong direction — redo the worked example and note where the squaring happens.

Check your understanding

Without notes: normalize the state , compute both measurement probabilities, and state what information stays invisible if you only look at those probabilities.

A passing answer divides by , reports , and names the casualty: the relative phase , which a later gate could convert into a measurable difference. An answer that calls the state "50 percent zero and 50 percent one, full stop" has described the measurement and missed the state.

Oral defense: explain to a colleague why "the qubit is 0 and 1 at the same time" is a worse description than "the qubit is a specific weighted combination whose weights can cancel."

If you get stuck

If you catch yourself treating amplitudes as stored classical answers, return to Chapter 1 (Computation Is Physical) and re-read what a state is allowed to be; then redo this chapter's worked example slowly, tracking the sign through the Hadamard. The plus/minus pair is small enough to hold in your head, and once it clicks, the rest of the book's interference arguments follow the same shape.