Skip to content

missions: judge li_positivity (24) and quasicrystal (7 of 8) islands - #627

Draft
DrMurphyIsIn wants to merge 1 commit into
mainfrom
missions/judge-li-qc
Draft

DrMurphyIsIn wants to merge 1 commit into
mainfrom
missions/judge-li-qc

Conversation

@DrMurphyIsIn

Copy link
Copy Markdown
Owner

Extends the independent judge (missions-comparator.yml, see #607) to two more islands. No registry status change, no grant. conjecture1_proved = False.

island nodes shards Comparator tag local validation
li_positivity 24 0/2, 1/2 v4.34.0-rc1 all 24 bridge modules elaborate; RH_zero_free_polylog, RH_li_rungs_lt_five, MM_bragg_bridge pass under Lean kernel + nanoda (2.7-3.6 min each)
quasicrystal 7 of 8 0/1 v4.32.0 all 7 elaborate; MM_twofreq_realrooted_iff (76 s), MM_nt_brick_conditional (22 s) pass

li_positivity guard policy. Its two AxiomGuard libs cannot be imported into one module: ZeroFreeBridge.zeta_sphere_bound is declared in DlvpZetaDisk (in AxiomGuardLiPositivity's closure) and in ZeroFreeElementary (in AxiomGuardZeroFree's). judge.py now has a per-island policy (GUARD_POLICY_ONE_CONTAINING = {"li_positivity"}): each bridge imports only the first guard whose island-local import closure contains its artifact (22 use AxiomGuardLiPositivity, 2 use AxiomGuardZeroFree), and the bundle's root module carries no imports (CI builds bridge modules by name). The shadowing check therefore covers that guard's closure rather than the whole island; documented in the README and AUDIT_INDEPENDENCE section 4.

quasicrystal. MM_leakage_composite_zero is not consumable as registered: its statement declares four local defs before the theorem, and the bridge imports the artifact, so re-declaring them is a duplicate declaration. Judging it needs the statement re-registered against the island's own definitions (an owner decision on a proved node's statement); it is reported by the generator, not silently skipped. The island has no AxiomGuard* lean_lib, so its bridges import only the artifact (no shadowing guard there; AxiomGuardQC.lean runs via lake env lean in the satake job).

Also carries the judge-step ulimit -s raise from #625. bundles-in-sync now checks all five islands. Judge tests: 27.

Shard times from this PR's run will be added here. Once green, the passes get recorded on the nodes with mission comparator-record in a follow-up to #624.

🤖 Generated with Claude Code

https://claude.ai/code/session_017icTazCuXLgRx61VNRAZWU

…7 of 8)

li_positivity: its two AxiomGuard libs cannot be imported together
(`ZeroFreeBridge.zeta_sphere_bound` is declared in DlvpZetaDisk, in
AxiomGuardLiPositivity's closure, and in ZeroFreeElementary, in
AxiomGuardZeroFree's), so a per-island policy imports only the first guard
whose island-local import closure contains the artifact (22 bridges use
AxiomGuardLiPositivity, 2 AxiomGuardZeroFree) and the root module carries
no imports; CI builds the bridge modules by name. All 24 elaborate locally
against the island build; RH_zero_free_polylog, RH_li_rungs_lt_five and
MM_bragg_bridge pass the v4.34.0-rc1 Comparator under both kernels.

quasicrystal: 7 of 8 (MM_leakage_composite_zero declares four local defs
before its theorem; the bridge imports the artifact, so re-declaring them
is a duplicate declaration -- reported, not skipped; judging it needs the
statement re-registered against the island's own definitions, an owner
decision). The island has no AxiomGuard lean_lib, so its bridges import
only the artifact (documented: no shadowing guard there). All 7 elaborate;
MM_twofreq_realrooted_iff and MM_nt_brick_conditional pass the v4.32.0
Comparator.

Also carries the judge-step `ulimit -s` raise from #625 (nanoda main-thread
stack overflow on KWin certificates). Matrix: li_positivity 0/2, 1/2;
quasicrystal 0/1; bundles-in-sync checks all five islands. 27 judge tests.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017icTazCuXLgRx61VNRAZWU
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