Alphabeta Math
ExampleConstruction: AI-generatedVerification: AI-generatedPipeline-generatedverified 2026-10-22 (gpt-6.1-sol)
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.

A solver-invalid FWI iterate

Example

Fix an FWI velocity-model solver S with a declared finite admissibility predicate adm⁡S(v) that checks that solver's coefficient, boundary, mesh, and time-step conditions, including its solver-specific Courant–Friedrichs–Lewy (CFL) condition. If an optimization method proposes a candidate velocity map v~ with adm⁡S(v~)=false, the benchmark records the call as a solver/admissibility failure; its evaluation protocol specifies whether and how that failed trial contributes to any numerical aggregate. In its FWI DAPS experiment, InverseBench reports that a smaller learning rate gave numerically stable but data-ineffective outputs, while a slightly larger learning rate produced a noisy velocity map that violated the PDE solver's CFL condition and failed. The paper gives no exact violating iterate or universal CFL threshold; this example claims neither.

Facts & Assumptions

Given: A chosen FWI solver S, its declared finite admissibility predicate, an optimizer-produced velocity map v~, the Boolean result adm⁡S(v~)=false, and the qualitative DAPS observation reported in the Example.

[F1]

Benchmark risk, compute budgets, and uncertainty records: a failed solver/admissibility call is recorded with its status and is not silently omitted from results.

[F2]

Finite-element PDE solver admissibility and certificate contract: an admissibility predicate tests the specified model's hypotheses, and any CFL condition is method-specific; the definition supplies no universal threshold.

[F3]

Scope of InverseBench findings: InverseBench reports the FWI step-size/CFL behavior as an empirical observation for its named solver and methods.

Verification

1.1F2given

Since adm⁡S(v~)=false, the proposed iterate fails the selected solver's declared admissibility test; it is therefore not an admissible input for that solver call.

1.2F1F2given

By [F1], the benchmark records this call as failure and does not silently omit it. [F1] does not prescribe whether the failed call receives or contributes to a numerical score, so no particular scoring rule is asserted.

2.1F3given∎

The stated smaller-step/larger-step DAPS behavior is the paper's reported FWI observation for its numerical PDE setup, as recorded by [F3]; no inference is made from it to other solvers or parameter ranges.

Depends on

Used by

Nothing in the library uses this result yet.

Dependency tree · two levels

14 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