Skip to content

Add rocq-pi-leibniz.1.0.1-1.0.4 (supersedes #3896, #3897, #3898) - #3899

Open
hy7pc8gfmf-dotcom wants to merge 5 commits into
rocq-prover:masterfrom
hy7pc8gfmf-dotcom:pi-leibniz-1.0.4
Open

hy7pc8gfmf-dotcom wants to merge 5 commits into
rocq-prover:masterfrom
hy7pc8gfmf-dotcom:pi-leibniz-1.0.4

Conversation

@hy7pc8gfmf-dotcom

Copy link
Copy Markdown
Contributor

What is this package

rocq-pi-leibniz is a constructive pi for the constructive Cauchy reals of the Rocq standard library, realized by the alternating Leibniz series.
Every statement is premise-free and Set-valued, so the apartness witness against each rational (an explicit positive margin and an explicit convergence modulus) is extractable, with no axioms and no Obj.magic in the extracted OCaml.

What changed from 1.0.0 to 1.0.4

1.0.0 was merged as #3884; the four releases since then are consolidated here, one row each. The branch adds the four package files released/packages/rocq-pi-leibniz/rocq-pi-leibniz.1.0.1/opam through .../rocq-pi-leibniz.1.0.4/opam.

Release Core changes Evidence
1.0.1 Three modules in the pi supply chain: PiLeibnizMargin (unbounded-margin statement for the window family), PiPadeQLeg (rational-level Pade leg), PiSepSearch (generic separation search); CI rebuilt as a single self-hosted trust-cache job Package file pins the sha256 of the v1.0.1 tag tarball (PR #3896)
1.0.2 CI smoke check now asserts the documented witness values (e 0 = 5 # 2, e 1 = 5 # 4, e 2 = 5 # 6; compile-fail on mismatch) Package file pins the sha256 of the v1.0.2 tag tarball (PR #3897)
1.0.3 238 Set-carried twin faces on PiKernelSlack; the window-equality cascade (26 faces) reshaped onto its Set twin; unified carrier block in PiCompareT; Set-carried apartness counterpart PiCRealAppartT; four separation modules; comments normalized, migration provenance in docs/statement-provenance.md Package file pins the sha256 of the v1.0.3 tag tarball (PR #3898); certification and witness assertions rerun over the extended closure
1.0.4 Twin layer completed: PiPascalResidueT puts the band representation of the truncation remainder in extractable form; the documented witness values are asserted as Set-carried identities whose proofs close by vm_compute alone; 681 statement names that carry a twin are suffixed _prop (bare names reserved for the Set-carried faces); the root module no longer re-exports PiWindowCore, so leiblw_id_eq_prop resolves to the PiLeibnizMargin face unambiguously; comments in English throughout Green CI run 40208484473 at c22524e7; package file pins the sha256 of the v1.0.4 tag tarball

Verified

From a clean checkout of the v1.0.4 tag, the package's green criterion is one command:

make -j && bash scripts/pi_ci_chk.sh

The script certifies the whole dependency closure with rocqchk -o and requires every Axioms: section to be <none>; it prints Closed under the global context for both main theorems (Print Assumptions pi_leibniz_strong_irrational_prop and pi_leibniz_appart_all_Q); and it asserts the documented witness values by vm_compute, so a mismatch fails the compile (for q = 22 # 7 the escape-witness triple computes to (22 # 7, 5 # 8, 3%nat) : Q * Q * nat). It ends with COQCHK_ALL_PASS.

The same steps run green in CI on the release head c22524e7: run 40208484473, job "build + coqchk (self-hosted, local trust cache)", conclusion success.

Supersedes #3896, #3897, #3898

This PR supersedes the three open release PRs #3896 (1.0.1), #3897 (1.0.2), and #3898 (1.0.3): it adds the same three package files unchanged plus 1.0.4, so one review covers the whole line. If those PRs are still open, please merge this one and close them; if any has already been merged, this PR is the completed state of the same content.

Who should update

Users of any 1.0.x release should update directly to 1.0.4. Two adjustments may be needed in downstream code: statement names that carry a Set-carried twin now take the _prop suffix on the Prop-level original (681 names, so downstream code states which face it uses), and Require Import pi_leibniz no longer re-exports PiWindowCore (import that module directly if you need its face of leiblw_id_eq_prop).

Metadata

  • License: LGPL-2.1 (unchanged).
  • DOI: the concept DOI 10.5281/zenodo.23527294 covers all versions; cite as before.
  • Derived from the Rocq standard library's constructive Cauchy reals (ConstructiveCauchyReals); depends on rocq-prover >= 9.1 and rocq-stdlib >= 9.1.
  • Tarball checksums in the four package files are computed from the corresponding tag archives.

@hy7pc8gfmf-dotcom

Copy link
Copy Markdown
Contributor Author

Updated this PR to also include rocq-pi-leibniz.1.0.5:

Commit 536fada2 on the pi-leibniz-1.0.4 branch (pushed just now).

rocq-stdlib.9.3.0 is not yet in the released overlay (tops at
rocq-stdlib.9.2.0), so the >= 9.3 bounds made 1.0.5 unsolvable in CI
("can never be installed" on all three legs). Relax to >= 9.1 to match
1.0.1-1.0.4; the modules were originally written and CI'd on Rocq 9.1
and re-verified green on 9.3.0 in the source repo (runs rocq-prover#44-rocq-prover#46).
@hy7pc8gfmf-dotcom

Copy link
Copy Markdown
Contributor Author

Updated to fix the CI failure (596d7af5):

Root cause: 1.0.5 declared rocq-prover >= 9.3 + rocq-stdlib >= 9.3, but the released overlay currently tops out at rocq-stdlib.9.2.0 (9.3.0's stdlib package has not been submitted here yet), so the solver had no solution — all three legs reported rocq-pi-leibniz.1.0.5 as "can never be installed" (1.0.1–1.0.4 installed and compiled fine on the same legs).

Fix: relaxed both bounds to >= 9.1, matching 1.0.1–1.0.4 in this PR. The two modules new in 1.0.5 were originally written and CI'd on Rocq 9.1 (source-repo runs #35/#36/#40) and re-verified green on 9.3.0 (runs #44–#46), so the package should compile on the 9.2 toolchain CI resolves to; the opam description's "compile green on Rocq 9.3.0" tested-at note is kept. The bounds can be re-bumped to >= 9.3 once rocq-stdlib.9.3.0 lands in the overlay.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant