Repository navigation
linear_arithmetic decides long first-match chains (PF-26) - #507
Conversation
afflom
left a comment
There was a problem hiding this comment.
Bounded source triage at01bbb669; existing Claude implementation owner retained. The inspected backend first runs the old simp/split/omega script with done, then uses the ite_eq_iff fallback. The positive band cases and false band_middle refusal correspond to that new behavior. This credits the source structure, not independently executed proof-term/axiom preservation or complete regenerated-product acceptance.
Two integration items need resolution before landing:
- This PR targets main71def. Its own AGENTS release-line contract reserves main updates for a release tag; language identity work lands on the applicable release line. Please reconcile the intended carrier with actual release/v0.4 26e5e0a (and required actual forward history), preserving current workflow and contributor changes. The current main-based CI is not qualification of that resulting release tree. Review resulting-tree impact and reuse applicable existing products; do not blindly repeat all writers.
- PF24 is already allocated by #474 at02d9a29 to the distinct region_check checker/soundness/fragment-refusal contract. This PR adds a different conditional-chain arithmetic contract at model/ids.toml:970, scenario proofs.feature:169 and conformance proofs.rs:993. Coordinate a unique allocation with that owner, consistently through register/spec/scenario/test wiring and necessary projections. Shared account authorship is not permission to overwrite the other scope.
New successful producer43317873461 at7a5ac574 is separate from historical43265649942; earlier masked-exit findings are not attributed to the new run. Its output applicability still needs review against the actual intended landing tree. No logs, proofs, producers or gates were rerun, and no branch/readiness mutation was performed. Full final-head acceptance and actual merged-tree equality remain required.
|
Thanks. Both points are taken:
While doing this I also found that the identity carry-forward had rewritten the 0.4.0 entry's ID in CHANGELOG.md. The rebuild restores that entry, and prose is now excluded from the carry-forward. The branch will be replaced and the PR retargeted once the owner confirms. Generated by Claude Code |
|
The Generated by Claude Code |
|
Generated by Claude Code |
|
The proposed release/v0.4 carrier and PF26 allocation address the two coordination requests in review5884429438; proceed with that reconciliation in the existing owner lane. Preserve #474's PF24 and #303's PF25, actual26e5 ancestry/current workflow, contributor history and retained source/producer evidence. This is direction for the integration, not acceptance of an unpublished tree or blanket approval to replay writers. Please publish the reconciled source and identify the necessary product delta against that tree. Reuse the unchanged laws export and any other applicable completed evidence; a changed base alone does not justify repeating every producer. The live PR still points to01bbb/main, so the reported PF26, census/rustfmt and historical CHANGELOG corrections remain pending publication/review. Keep historical release prose immutable as described. Current-main CI findings are already diagnosed by the owner; no duplicate diagnostic run is requested. Final-head full qualification and actual merged-tree equality remain the landing requirements. |
…nditions [regenerate] When the fixed script leaves a goal open, a second attempt adds LexLeanLaws.ite_eq_iff, which reads an if equal to a value as the disjunction of its branches, and the propositional simplifications that drop a decided branch. A proof the fixed script closes keeps its proof term and axioms. The laws module is the export the #117 oracle wrote (120 declarations, all equal to the compiler's Lean); the runtime modules it imports are the same on this line. fold-laws gains a fourteen-condition band with two theorems. PF-24 belongs to #474, so this is PF-26 (PF-25 is #303's). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3MWG2BeFisFkR1Kebg
|
Generated by Claude Code |
01bbb66 to
147086c
Compare
afflom
left a comment
There was a problem hiding this comment.
Reconciliation credited at147086ca: actual26e5 release ancestry, unique PF26 register/scenario/test wiring,494 census, README capability range, assertion formatting and historical CHANGELOG preservation are now present. The Laws export is byte-identical to prior01bbb and correctly reused. These resolve the previous source/carrier coordination findings without another export. Current15-file commit is source/preparation; owner regeneration43352312619 is active and products/final-head qualification remain pending.
P2 — The current regeneration workflow masks writer failure before publication. In regenerate-ite-law.yml, set +e captures writer exit codes only for printing; the loop and verify-write steps finish through successful status/count commands. The commit step uses if: always() and stages/pushes outputs. A producer can fail while its step ends green and partial products are committed. The before/after identity check cannot establish producer completion.
Please preserve the active run's outputs and per-writer exit evidence, and explicitly disposition them before adoption. For the publication path, accumulate actual writer/verify failures and require success before treating outputs as complete; retaining logs after failure is useful, publishing them as completed products is not. This is a source-control finding, not an assertion that43352312619 failed, and it does not require blindly repeating successful writers. The older masked-exit receipt was not used as proof about this run.
Existing owner retains implementation and qualification. No source, readiness, workflow run or producer was changed by this review. Full final-head gate and actual merged-tree equality remain required.
|
Agreed, the gating is real. As written, a writer or
Generated by Claude Code |
afflom
left a comment
There was a problem hiding this comment.
Bot output publication is now present atd9f532, directly atop147, and regeneration43352312619 is terminal success. Sampled bootstrap/fold manifests and current locks agree on compiler043cd7e5. This credits committed presence/sample consistency, not per-writer completion: the exact workflow still masks writer/verify exits and uses if:always publication.
Please complete the disposition you committed to in comment6842324403: identify every printed writer/verify exit, accept only all-zero outputs, otherwise treat the run as diagnostic while preserving its evidence; then remove the temporary workflow as planned. No blanket rerun of successful writers is requested. The filename inventory was capped3000 against4959 reported changes, so this review does not claim full output enumeration or byte clearance.
Actual release has advanced to #419/b8b6, while this branch still diverges from26e5 and is currently conflicting. Preserve the new actual ancestry and review its renderer/runtime identity impact before deciding which additional work is necessary. The prior PF26/Laws source fixes and unchanged export reuse remain credited. Existing owner retains reconciliation and final qualification; no competing patch, log fetch, producer or gate action was started.
…ate on it [regenerate] RB-24 moved the language-1.2 identity, so the products of d9f532b no longer apply. The merged tree is release/v0.4's with PF-26's sources only; every written output comes from release/v0.4 and is regenerated on this tree. The register count follows RB-24's row: 495. The workflow now fails on any writer or verify-write exit and commits only when all six are 0 (review 5885290049). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3MWG2BeFisFkR1Kebg
|
Disposition of run 43352312619 (bot commit d9f532b): every printed exit was 0: Reconciliation with release/v0.4 at 15d66a7 (RB-24, #419): RB-24 moved the language-1.2 identity (
The workflow is removed in the commit after the adopted regeneration. Generated by Claude Code |
|
Generated by Claude Code |
afflom
left a comment
There was a problem hiding this comment.
The failure-propagation finding from5885290049 is structurally resolved. The five-writer loop now exits nonzero if any captured writer fails; verify-write propagates its captured exit. Publication requires success() and exactly six recorded zero exits. Failure-log upload remains available. This was the explicit set+e/print-only publication finding, distinct from the separately retracted IR Bash-errexit concern.
Actual merge parents d9f532b +15d66a76 preserve release history. The complete15-file net delta against15d66 contains PF26 authored sources/docs/census and the temporary workflow; release-baseline generated products are not yet adopted PF26 outputs. Laws export blobff9a178e is unchanged and correctly reused. Current source census495 is consistent; the body still says26e5/494 and should be refreshed with final adoption evidence.
Owner comment6853487864 supplies the requested six zero-exit/fixed-identity disposition for the old run, credited as owner-reported evidence for that original tree. Current regeneration43428742532 must finish and its outputs be reviewed/adopted, followed by the promised temporary-workflow removal and complete resulting-head acceptance. Current CI/repro failures remain non-acceptance. No old log, export, producer or test was repeated; existing owner retains the work.
afflom
left a comment
There was a problem hiding this comment.
Official regeneration43428742532 succeeded under the corrected failure-propagation/publication guards, and c56c53e is the bot's direct child of8729 with its outputs adopted. This supersedes the prior unadopted-products status. Bounded review4a8d7d13 finds unchanged authored implementation/model/language/config/workflow subtrees; the generated PF26 conformance projection is present. Sampled locks, manifests and export provenance agree on compiler c3160a11 and bootstrap semantic0b78c658. Fold audit records retain the expected band/parity axioms. This is sampled adoption correspondence, not a full byte audit or a repeated proof/producer.
The smallest remaining owner batch is concrete: remove the temporary regenerate-ite-law workflow as promised; update the historical26e5/494 body; reconcile actual release fd7cedd (#474's PF24 source/runtime/identity plus #499), preserving actual merge history and reviewing which completed products remain applicable. This branch is currently conflicting. Preserve the unchanged Laws export and completed evidence; base advancement alone does not justify blindly replaying all writers or measurements.
Current CI43465264398 and reproducibility43465264270 both report action_required with zero jobs, not a semantic test failure or acceptance. Resolve the bot-run approval/qualification handoff as part of the existing owner's resulting-head plan; no log diagnosis or rerun was initiated. Complete final-head full CI, same-run honesty, exact repro and actual merged-tree acceptance remain required. No competing patch, runtime, artifact download or producer was started.
…generate on it [regenerate] #474 moved the language-1.2 identity and took PF-24, so the products of c56c53e no longer apply. The merged tree is release/v0.4's with PF-26's sources only, PF-26 placed after PF-24 in the register, §31, the scenario and the test wiring; the README range is PF-01..PF-26 and the register is 497 IDs. The Laws export is reused: Portable and Collections are unchanged on the line. Every written output comes from release/v0.4 and is regenerated on this tree under the gated workflow. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3MWG2BeFisFkR1Kebg
|
Disposition of run 43428742532 (bot commit c56c53e): Reconciliation with fd7cedd (#474, #499): 74dafed is a merge commit with parents c56c53e and fd7cedd. Its tree is release/v0.4's plus only PF-26's sources and the gated workflow.
The regeneration on this tree is running. The PR body is updated to the current base. Once its outputs are adopted, the workflow is removed by a commit pushed from my session (not the bot's). That push starts the final-head CI normally, which resolves the Generated by Claude Code |
afflom
left a comment
There was a problem hiding this comment.
The actual-release composition is credited at 74dafed: ordered parents c56c53e + fd7cedd preserve #474/#499 history, PF24 and PF26 remain distinct, and the register/body now agree on 497 IDs. The complete 15-path delta against fd7 contains PF26 source/docs/census plus the temporary workflow. The Laws export is unchanged and reused; the corrected six-zero-exit publication guard is retained. Independent bounded review pr507-74d-owner-delta found no new source blocker.
Generated products are currently the release baseline, so the prior c56 adoption remains evidence for its original composition only. Owner disposition 6859974572 records all six zero exits and stable c316 identity for that completed run. Current regeneration 43471700631 is still active; preserve its outputs and finish the existing adoption, then remove the temporary workflow with the promised owner-session push and qualify that resulting head.
Current CI 43471709084 failed the generated-files freshness step, with downstream aggregate failures/skips; repro 43471709044 also failed. These are not acceptance, and no additional cause is inferred from metadata. No log, Laws export, proof, producer or check was repeated. Final-head full CI, same-run honesty, exact repro and actual merged-tree equality remain owed.
afflom
left a comment
There was a problem hiding this comment.
Publication checkpoint: regeneration43471700631 completed successfully for74dafeda, and c3eb8d5 is its direct output-adoption child. Top-level model/language/schema/features/SPEC/VERIFICATION/xtask/workflow objects remain unchanged. Recursive crates-tree comparison finds only the checked1.2 constant in lexlean/src/lib.rs changed, a82990b5→e1b2447a; no authored implementation delta was introduced there. This is bounded source/publication credit, not a recomputation or complete generated-product acceptance; the commit-files API caps its listing at300.
Existing source/history/PF24+PF26/Laws-export credit remains scoped as previously reviewed. The temporary workflow is still present, and bot-head CI43495946313/repro43495946406 are action_required. The next step is the owner's already stated6859974572 workflow-removal/session-push and final product review plus required resulting-head qualification. No new regeneration is needed merely to publish or start that normal final-head qualification. Review current actual release history (be7 automation and6a02 counts-tool delta) for applicability without a blind identity wave. No writer, check, log or producer was repeated.
Neither moves the language-1.2 identity (no change under language/, schemas/ or the embedded golden fixtures), so c3eb8d5's products apply. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3MWG2BeFisFkR1Kebg
Its last run (43471700631) recorded all six writer exits 0 with the identity stable at e1b2447a, and c3eb8d5 is its adopted output. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3MWG2BeFisFkR1Kebg
|
Disposition of run 43471700631 (bot commit c3eb8d5):
Release history since fd7cedd: #517 (be7d2f8) and #462 (6a02d2c) touch nothing under Removal: cce7271 removes the temporary workflow. It is pushed from my session, so the final-head CI, honesty and repro run normally on it. Generated by Claude Code |
afflom
left a comment
There was a problem hiding this comment.
The requested publication steps are now complete at source level. 0634d5e preserves ordered c3eb8d5 + actual6a02 parents; cce7271 then removes only the temporary regeneration workflow. The complete17-path delta from adopted c3 consists of inherited #517/#462 automation/docs/repository-test/xtask changes plus that removal. Language, schemas, model, compiler, bootstrap, stdlib, examples, tests and other product trees remain identical to the adopted output. This supports retaining those outputs without another identity writer. The body now records current ancestry, all six writer exits and stable e1b2447a as owner evidence.
New final-head CI43500311099 and repro43500311100 are queued. Review their terminal resulting-tree acceptance before landing and actual merged-tree equality afterward; the bot-head action_required runs and older gates are not substitutes. No producer or check was repeated.
afflom
left a comment
There was a problem hiding this comment.
The proposal tree has completed qualification: CI43500311099 attempt1 passed all70 jobs and772 steps, including same-run honesty; exact-head reproducibility43500311100 also passed. One newly retained checkout log proves that CI tested synthetic4cf29989, treecb57ae068e896de19dca8dffa192251b608e7029, identical to headcce7271b. Prior source/adoption credit is retained; no completed test or producer was repeated.
This is not yet current-release landing clearance. That synthetic commit has parents[6a02d2c,cce7271b], while the independent release/v0.4 ref is now69de7400. Both the PR base metadata and observed refs/pull/507/merge still describe the older6a02 composition. The current-release comparison contains18 incoming paths and diverges fromcce; no synthetic69de+507 tree was observed. Do not mistake the stale synthetic ref for equality with the actual current-base result.
Smallest owner next step: resolve the actual69de composition and evidence applicability, preserve this completed run and the existing official products, and expose the resulting exact candidate for final review/qualification and actual merged-tree equality. No blanket regeneration, repeat of this completed gate, or competing implementation is requested. Receipt pr507-final-gate-20261114/receipt.json; no issue closure or retrospective merge approval.
|
This resolves the 69de composition from review 5902265757. The head is now 411e0f5, which merges release/v0.4 at 69de740 into cce7271 with a two-parent merge commit.
The completed run 43500311099 and its products are untouched. 411e0f5 is the exact candidate for final qualification and merged-tree equality. Generated by Claude Code |
|
Landing order on release/v0.4: #518 (Lean 4.32.2) first. Both move the language-1.2 identity. Please hold #507's merge until #518 lands. After that, merge release/v0.4 in, regenerate, and land. Generated by Claude Code |
|
CI run 43566437740 on 411e0f5 is red for one reason, and it is not a test result.
No assertion failed against the 69de composition. Once the run settles, I'll re-run its failed jobs once. Generated by Claude Code |
afflom
left a comment
There was a problem hiding this comment.
Bounded integration review credits411e0f53: ordered parents[qualifiedcce7271b,actual69de7400], with the complete18-path delta matching incoming release changes. PF26 implementation and existing generated-product subtrees remain unchanged. Current synthetica2e31b97 has the same4ebcf48c tree as this head, resolving the earlier stale6a02 composition concern.
Preserve old70-job/772-step acceptance atcb57ae06 with its original scope; it is not acceptance of4ebcf48c. Existing CI43566437740 is attempt2 queued; the bootstrap cancellation diagnosis remains owner-attributed, and no canceled jobs are aggregated or logs repeated here.
The explicit owner hold6873483673 controls delivery: #518 lands first, then #507 integrates the actual release and dispositions affected identity products before final acceptance and actual landing equality. No competing integration, producer, retry or merge was started. Receipt pr507-411e-composition-delta/receipt.json.
Lands PF-26 on the Lean 4.32.2 identity (#518 lands first on release/v0.4). The only handwritten conflicts are the language-1.2 ID constant (recomputed next) and fold-laws' README (PF-26 kept, pin 4.32.2). Every generated path is taken from #518 and is regenerated on this tree. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
… follow the combined identity Relocked with the built compiler every project whose lock was current; the two lock-schema mismatch fixtures and the five negative fixtures whose locks do not resolve stay as they are. The combined language-1.2 ID is fdb9f7ec; provenance, manifests and LANGUAGE_1_2_SEMANTICS_ID carry it. The regenerate workflow rewrites the records next, Atlas included. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
The head is #303's with its reviewed follow-up cd0c6b7 (fix/pf25-source-contract). PF-25 and PF-26 are claimed on release/v0.4 (#507), so simplify hypotheses are registered as PF-28. The schemas and the semantic IR keep both lines' proof forms; semantic_ir and proof_lowering move to 17 and 5. Generated outputs are release/v0.5's, rewritten by the landing regeneration. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
The write recipes of SPEC.md §9.2, run by regenerate.yml (https://github.com/UOR-Foundation/lexlean/actions/runs/43636256479), rewrote 4695 paths. The counts writer reported: counts: no count moved
Brings in #431, #535, #519 and #518's merge. No conflicts. #507 already carried #518's change and its regenerated outputs (d954d7b), so the combined 1.2 identity is unchanged; #431 only widens the snapshot nesting the canonical writer accepts and does not change any written bytes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
…krpx Generated manifests taken from the release side; the regeneration rewrites them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3MAztfvN671cYrybev
The write recipes of SPEC.md §9.2, run by regenerate.yml (https://github.com/UOR-Foundation/lexlean/actions/runs/43773927994), rewrote 21 paths. The counts writer reported: counts: no count moved
afflom
left a comment
There was a problem hiding this comment.
Delivered-output custody credited at0fda089e: sole bot child of7715cd3b, producer43773927994 completed all six jobs including counts/delivery. Final artifact14190275798 is nonexpired, names exacte7715 input (7715cd3), and has digestf7b9649622f33f9f84e3e3194efe9f957187c82b243e79c975880160f46a484e. Artifact metadata was checked; ZIP bytes were not downloaded or compared.
Complete21-path delta contains only expected/build manifests. Twenty available patches update compiler_semantics4b3ed237→fdb9f7ec plus corresponding source/input/build/output bindings; compiler.version stays0.4.3. This is identity-output adoption, not merely a version correction. The large bootstrap patch is unavailable and path-classified only. Current fold-laws lock carries fdb9f7ec and Lean4.32.2 consistently with its new manifest. Authored source is unchanged from7715→0fda.
Prior source/70-job gate credit remains bound to its reviewed inputs; this output-only review does not certify the intervening411→7715 integration. Existing owner should expose that applicability/disposition and update the stale body, which still describes cce7271, Lean4.32.1 and the older base history. Final-head CI43786023209 is queued; bot-triggered CI43786042151/repro43786042220 are action_required, not passing gates. Complete final-head qualification and eventual actual merged-tree equality remain mandatory; use the existing route without duplicating the completed producer.
Receipt /workspace/work/pr507-0fda-product-adoption-20261116.json; SHA256 d1ecd18cb5d6f8e7644f7bda73331a5cdfd4349f72cc94ed0c78a0a11dbf6958. This also supersedes the stale local507 status accidentally containing503 text. No source patch, execution, retry, CI control, issue closure or #431/oldTC03 STOP waiver.
…angelog entry to Unreleased The release/v0.4 merge brought the base to 497 rows, so RP-07's checks, SPEC §31's total and the README count move to 498. The merge had placed the PF-26 entry under 0.4.3. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3MAztfvN671cYrybev
|
Gate 43786023209 on 0fda089 failed honesty at RP-07: "the §31 table has 498 rows, not 497" (the v0.4.3 base already has 497; PF-26 makes 498). 144aa76 moves RP-07's two checks, SPEC §31's total and the README count to 498, and moves the PF-26 changelog entry out of 0.4.3 (where the merge placed it) into Unreleased. Generated by Claude Code |
afflom
left a comment
There was a problem hiding this comment.
Count/changelog repair credited at 144aa76. The complete five-file delta updates both RP-07 cardinality checks and SPEC/README totals to 498 while preserving the model/spec bijection checks, and moves PF-26 into Unreleased. No generated product or identity input changed; reuse the completed producer 43773927994 and adopted 0fda outputs.
The intermediate PF-26 comparison also preserves the proof case, Laws and fold example exactly, and preserves the fallback implementation. The only backend difference is the inherited declaration_spans_bounded(body, usize::MAX) call and its depth comments. This narrows source applicability; it does not accept the inherited depth behavior or lift #431/old TC-03 STOP. No repeated PF-26 proof/source review is needed.
The body now records the current integration and producer. Its final qualification paragraph still references 0fda/run 43786023209; the existing owner should point it to 144aa76/run 43790053982. Repro 43790053781 passed; current CI remains pending. Final full acceptance and actual merged-tree equality remain required; the canceled prior run is not aggregated.
Receipts: /workspace/work/pr507-144aa-count-repair-20261116.json (SHA256 7e0086b3051f2c619008716666d55f85ccfa2a5ab51abd4c9af4760c1a1a3f6e) and /workspace/work/pr507-144aa-pf26-applicability-supplement-20261116.json.
|
Merged as 4afb850 after the final-head gate on 144aa76 went all-green: CI 43790053982 and repro 43790053781. The merge commit's tree, db5de5c8, equals the gated head tree. Generated by Claude Code |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
afflom
left a comment
There was a problem hiding this comment.
Actual landing-tree equality is verified: 4afb850 has parents 949cb26 + 144aa76 and tree db5de5c8, identical to the head and checked synthetic 75aafc2. The newly retained plan log establishes that checkout binding.
CI 43790053982 attempt 1 completed 71 successful jobs and 831 successful steps, with three Intel jobs skipped. Head repro 43790053781 and actual repro 43807468921 passed. Actual push CI 43807468956 was canceled and is kept separate. The successful conclusion supports the executed scope; it does not establish full platform qualification.
Prior product, count/changelog and bounded PF-26 source evidence remain reusable. Actual-tree equality is now established, while applicable Intel qualification, inherited-depth applicability and #431/old TC-03 STOP remain unresolved. The existing owner retains those dispositions; no completed producer or gate repeat is requested. The subsequent #557 composition is separate.
Receipt: /workspace/work/pr507-4afb-external-landing-gate-20261116.json; SHA256 7e45eb939f39f09acfe8af99cf00f585d7450ecc380e597d2d4d50d0ec576ed2.
Summary
linear_arithmeticfailed on a first-match chain of more than about ten conditions, which is the shape of a state machine's transition table or a policy's rule list. The script'srepeat' splitused up the simplifier's step bound beforeomegaran.This PR adds
LexLeanLaws.ite_eq_iff : ((if p then a else b) = c) ↔ (p ∧ a = c) ∨ (¬p ∧ b = c)toLexLeanRuntime.Laws, pinned to[propext]. The law is used only as a second attempt:A proof the fixed script already closes keeps its proof term and its axioms. Registering the law as a plain rewrite was tried first and rejected: it gave
fold-laws'sparity_steptheClassical.choiceaxiom (tests/runtime-library/LAWS.md).Carrier:
release/v0.4, per AGENTS.md Release lines. Each identity-moving landing on the line is merged in with a merge commit; no history is rewritten. Bases merged so far: 26e5e0a, 15d66a7 (RB-24), fd7cedd (#474, #499), 6a02d2c (#517, #462), then (2026-11-15) release/v0.4 after v0.4.3 (fa27108), #550 and #554 as 7715cd3. That base moved Lean to 4.32.2 and the version to 0.4.3; 7715 took the release side for the generated manifests only.ID: PF-26. PF-24 belongs to #474 and PF-25 to #303. The register has 497 IDs at the current base.
Source (13 files)
language/runtime-1.2/library/src/Laws.lex.tex.b58f1952) with the law appended: 120 declarations, byte-equal to the compiler's Lean, with the decoder's private import as the only other difference (§17.10).PortableandCollectionsare unchanged on the line.crates/lexlean/src/backend/semantic.rsaddsLINEAR_CASESand the two-alternative script.model/ids.tomlandfeatures/suites/proofs.feature.PF-01..PF-26) and the register line.band_top.LLV7002naming onlyband_middle.fold-lawsgainsband, a 14-condition chain, withband_topandband_middle.Product delta
The language-1.2 compiler-semantics ID changes. A temporary workflow on the branch, removed in the commit after the adopted regeneration:
*.md);model-write,golden-write,fixtures-write,calculus-write,production-export-writeandverify-write(every 1.2 example exceptuor-atlas, which is language 1.0);Run history:
c3160a11…e1b2447a…regenerate.yml)Verification
fold-lawsverified withband,band_topandband_middleat their pinned axioms in every run so far.[propext, Quot.sound];parity_stepkeeps[propext, Quot.sound].https://claude.ai/code/session_013Asa3MWG2BeFisFkR1Kebg
Generated by Claude Code