For each classical step (data testing, preconditioning such as sifting or advantage distillation, error estimation, error correction, confirmation, privacy amplification) it must be specified whether communication is authenticated, which test thresholds and decisions apply, which exact functions are used and how their parameters follow from the tests, all consistent with the security proof, including whether signals are permuted and whether privacy amplification functions are reused. Finite-size effects must be included with the block size of privacy amplification specified; the error rate threshold from the proof decides whether to continue or abort; unencrypted error correction parity information must be counted in privacy amplification (encrypted parity consumes key); confirmation parameters must fit the target failure probability with its leakage counted; and privacy amplification uses a randomly chosen function from a publicly known 2-universal class with the final key length computed from the proof.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.