Skip to content

lake build is red on two unsolved goals in H4Lagrangian.lean, and Lean proofs ran once in the last 60 workflow runs #3142

Open

Description

@gHashTag

H4Lagrangian.lean has two unsolved goals, and the workflow that catches it ran once in sixty

lake build fails:

error: Trinity/H4Lagrangian.lean:73:59: unsolved goals
error: Trinity/H4Lagrangian.lean:108:46: unsolved goals
error: Lean exited with code 1

Those are the only two error lines in the whole run. Everything else the build emits is a
warning (This simp argument is unused, Variable name \x` is not explicitly referenced`).

Why nobody has seen it

Of the last 60 workflow runs in this repository, exactly one is Lean proofs — and that
one only exists because an unrelated pull request happened to touch three .lean files. The
workflow is paths-filtered, so it does not run on push to master; it has no baseline any green
state has ever been observed against
, which is what tri pr ready reports as NO BASELINE and
VERDICT: CANNOT TELL:

a check that never runs on master has no green state anyone has ever seen.

This is the same shape as a paths:-filtered workflow with no push: trigger: the gate exists,
looks configured, and has effectively never executed. A proof with unsolved goals has been sitting
in the import closure of Trinity.lean — the root — and the build has been red for however long
without anything reporting it.

Two questions, and the second is the owner's

  1. Repair the proof. Two unsolved goals at named lines; that is ordinary Lean work and needs
    somebody who can run lake (I cannot here — Lean is not installed in this environment, which
    is why the header change in gate(commands): a hyphenated sibling is a command the space-separated matchers step over #3138 was deliberately shipped as "CI is the check and I am not
    claiming it locally"
    ).
  2. Should Lean proofs run on push to master? Right now it cannot fail visibly, so it
    cannot protect anything. Adding a push: trigger would make it a real gate and would land red
    until (1) is done — which is the honest sequencing, and is a CI-policy decision, not mine.

Related: the same run's build graph is the subject of the line-count correction in #3137, and
lake check-test / lake check-lint both report failed -> will not run in this log too, which
is a third thing nobody is seeing.

Found while landing #3138; anchored to that run, gh run view 33843156189.

User Scenarios

  • Given proofs/lean4/Trinity/H4Lagrangian.lean contains two unsolved goals at lines 73 and 108, when lake build runs in the Lean project, then it fails with exactly those two error lines and exits non-zero.
  • Given the "Lean proofs" workflow is paths-filtered and lacks a push: trigger for master, when commits land on master, then the workflow does not execute and the red build remains undetected.
  • Given the unsolved goals are resolved and the workflow gains a push: trigger for master, when lake build runs on master via the workflow, then it exits 0 and the gate becomes visible.

Requirements

  • FR-001: The two unsolved goals in proofs/lean4/Trinity/H4Lagrangian.lean at lines 73 and 108 MUST be resolved so that lake build produces no errors.
  • FR-002: The "Lean proofs" workflow specification MUST include a push: trigger for the master branch so it runs on every push and establishes a visible baseline.
  • FR-003: After both changes, lake build in the Lean project MUST exit 0.

Success Criteria

  • lake build executed in proofs/lean4/ exits 0
  • The "Lean proofs" workflow runs on push to master and reports success (exit 0)
  • 2 unsolved goals resolved in proofs/lean4/Trinity/H4Lagrangian.lean

Boundary

  • proofs/lean4/Trinity/H4Lagrangian.lean
  • specs/tri/pipeline/workflow.t27

Activity

  1. added
    needs-boundaryNo '## Boundary' section, so the Queen can reserve nothing for it and no bee can take it
    on Sep 23, 2026
  2. gHashTag commented on Oct 7, 2026

    @gHashTag
    CollaboratorAuthor

    Reopened 2026-10-07: the bulk close of issues without a ## Boundary section was reverted by the owner. Nothing to do here; this comment replaces the earlier close notice.

  3. added
    needs-shapeIssue lacks Boundary/Scenarios/Requirements/Success criteria
    on Oct 7, 2026
  4. removed
    needs-shapeIssue lacks Boundary/Scenarios/Requirements/Success criteria
    on Oct 7, 2026
  5. removed
    needs-boundaryNo '## Boundary' section, so the Queen can reserve nothing for it and no bee can take it
    on Oct 9, 2026
  6. added a commit that references this issue on Oct 10, 2026
    6b73008
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions