Alphabeta Math
AlgorithmAlgorithm: Literature-sourcedProof: Not applicablePipeline-generated
How statement and proof provenance work

The first chip identifies the source of the statement or construction; the second identifies the source of its local proof or verification.

  • Literature-sourced: the exact statement appears in a cited source; only wording and notation differ.
  • AI-adapted: a semantically identical restatement of literature-sourced material, modulo indexing, notation, and boundary cases adopted by the library.
  • AI-generated: a genuinely novel statement formulated by AI, with no source for the claim itself.

These labels describe origin, not correctness: citations and verification chips remain separate evidence.

Allocate local error budgets through a pipeline

Definition

Inputs: a finite list of L stage compilers C1,…,CL, each accepting a rational local precision and, when it uses randomized verification, a rational local failure budget; rational targets 0<ε,δ<1; and declared stage input/output interfaces T0,…,TL, including encodings or register spaces. Stage j must accept Tj−1 and return Tj at every admissible budget, so adjacent interfaces match. For a channel pipeline these are the matching spaces and channel interfaces of End-to-end channel and output error contract. Each compiler is assumed to terminate with an implemented stage, its output type, and its actual cost record under Classical output, quantum-state output, and access costs. The sequential pipeline is run under the same declared cost-accounting model.

Output: a pipeline from T0 to TL, together with the budget lists and cost records below. If L=0, a single interface T0 is supplied; return its identity procedure, empty budget lists, no stage records, and an auxiliary record charging any identity-interface and allocator work. If L≥1, set εj=ε/L and δj=δ/L for each j. For j=1,…,L in order, invoke Cj(εj,δj) once when stage j uses randomized verification, and otherwise invoke Cj(εj) once and mark its failure coordinate not applicable. Retain each returned implementation, output type, and actual stage cost record, then compose the stages chronologically. Record shared input/preprocessing, allocation arithmetic, and any interstage wiring, control, postprocessing, or final-output costs in a separate auxiliary record, counting each operation once. Return the composed implementation, local budget lists, per-stage records, and auxiliary record. The correctness theorem gives an additive resource bound from these records under its explicit accounting assumptions; a requested precision alone does not determine an implementation or its cost.

The correctness claim is separate: Allocated local errors meet the global budget proves the global channel and failure bounds and composes the recorded cost coordinates under explicit stage and pipeline accounting assumptions. This algorithm does not create implementations or amplify a compiler's error; each compiler's correctness method and cost remain part of its own guarantee.

Depends on

Used by

Dependency tree · two levels

13 results within two dependency steps of this one, each drawn at its shortest distance from it. An arrow runs from a result to what uses it, so the chart reads left to right and ends at this result, which carries a heavier outline. Every node is a link to that result. Click elsewhere on the chart to enlarge it.

Sources