Perfect strategies reject nothing on the support #
Every completeness argument in the pipeline needs the same step: a strategy of value 1 does
not merely win on average, it assigns probability zero to each rejected answer pair at each
question pair the verifier actually asks. That step was used implicitly inside
MIPRE.tracialValue_le_one and nowhere available as a lemma; this file states it.
sum_re_tracial— at a fixed question pair the outcome probabilities sum to one. This was ahaveinsidetracialValue_le_one; it is the reason the value is at most one, and it is wanted on its own.re_eq_zero_of_tracialValue_eq_one— the characterization: if the value is1thenτ(M^x_a M^y_b) = 0wheneverμ(x, y) > 0and(a, b)is rejected.
Both are at the generic tracial level, so they serve synchronous and commuting strategies
alike; SyncStrategy.re_eq_zero_of_value_eq_one is the synchronous spelling, with the
normalized trace written out as Tr(M^x_a M^y_b)/d.
At a fixed question pair the outcome probabilities sum to one: ∑_{a,b} τ(M^x_a M^y_b) = τ(1) = 1.
A perfect strategy rejects nothing on the support. If the value is 1 then every
rejected answer pair has probability zero at every question pair of positive weight.
The converse: if every rejected answer pair has probability zero at every question pair
of positive weight, the value is 1. Completeness arguments go this way -- one builds a
strategy, checks it never produces a rejected outcome, and concludes.
SyncStrategy.value is the generic tracial value at the normalized trace, by definition.
Named so that the application below need not ask the unifier to see through value, which is
a whnf timeout when it does.
The real part of the normalized trace, written out. Stated once because both the value-one characterization and the faithfulness lemmas below need it.
The synchronous spelling: a value-1 synchronous strategy has Tr(M^x_a M^y_b) = 0 for
every rejected answer pair at every question pair of positive weight.
Faithfulness, and orthogonality of a projective measurement #
The normalized trace on matrices is faithful, which the generic tracial level cannot see. Two consequences that completeness arguments need at the operator level rather than the state level, and which the paper uses without comment: a rejected outcome of a value-one strategy is not merely improbable but the zero operator, and distinct outcomes at one question are exactly orthogonal.
A self-adjoint idempotent whose normalized trace vanishes is the zero operator.
Distinct outcomes of a projective measurement are orthogonal. The tracial statement
ProjectiveMeasurement.consistency says the probability is zero; on matrices, faithfulness
of the trace upgrades that to the operator identity, which is what a commutation obligation at
a repeated question needs.
The value through MIPRE.ntr #
MIPRE.ntr is the real part of the normalized trace, the form in which the closeness calculus
of MIPRE/Foundations/Closeness.lean manipulates outcome probabilities. These four lemmas are
the bridge.
Outcome probabilities are nonnegative.
At a fixed question pair the outcome probabilities sum to one.
Pushing a measurement forward along a map of outcome sets #
Soundness arguments need to relabel outcomes: to group the answers that fail a parse into
one distinguished outcome, or to read an oracle's pair-valued answer as one of its components.
A sum over a fibre is again a projection precisely because distinct outcomes are orthogonal,
which is SyncStrategy.orthogonal above and is unavailable at the generic tracial level.
The projective measurement obtained by relabelling outcomes along f: the operator for
a' is the sum over the fibre of f above a'.