Repository navigation
Pilot A: publish protected prime-parity refutation - #42
Conversation
|
Warning Review limit reached
Next review available in: 53 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Exact-head merge audit:
Manual diff review found no authority-boundary or scope expansion: the change supplies a new exact no-import fixture and selects existing refutation/polarity paths. The release and Pilot A checkboxes remain open pending protected post-merge evidence and later repair/pedagogy/export work. |
|
Post-merge evidence: main commit |
Outcome
Advances Pilot A through the existing protected publication path for the false claim “Every prime number is odd.” The canonical candidate now retains witness
2, publishes a negation-polarity refutation request, and lets the unchanged protected ingestion/fidelity/status path derivedisprovedonly after role-separated review.Closes #41
Changes
PilotARefutation.leanfixture;PrimeandOddpredicates;two_is_prime_and_not_oddand the universal claim's logical negation;refutationpublication request throughmcl;Trueisolation smoke and historical proof evidence;No publication, evidence, fidelity, or status schema/API changed. Counterexample packaging, claim repair, repaired proof, pedagogy, and export remain out of scope.
Local verification
Exact head:
1a5755fa815ca187c594e1d4db0c488d0a5e327cExact tree:
8945fd4746c1f9d9d536dd14d17854da3c9d0bddlean fixtures/publication/PilotARefutation.leanmclCLI playtest: source → claim → negation formalization → elaboration → axiom-free audit → refutation requestMCL_PUBLICATION_OUTCOME_MISMATCHcargo fmt --checkcargo clippy --workspace --all-targets --all-features -- -D warningscargo test --workspace --all-targets— 148 passedgit diff --checkMerge gate
Do not merge until the exact PR head passes all five required jobs and review is clear. After merge, independently audit the protected publication artifact before checking the proof/refutation or Pilot A release criteria.