LeanEval submissions

production intake is enabled. Sign in with GitHub, review every field, and submit.

GitHub sign-in is required.

Required repository access

Install both read-only GitHub Apps on only the repository you intend to submit:

Install LeanEval Source Reader for intake verification.
Install lean-eval-bot for the archive and evaluation workflow.

The server checks that both Apps can read the named repository and exact commit before accepting or dispatching the submission.

Problem ID LeanEval resolves the problem group and current statement revision from the live catalog. The problem must currently be open for submissions. Declared model Source repository Exact source commit Publication choice Scheduled release is the recommended default because it lets the community inspect and reuse accepted solutions. Choosing it confirms that you are authorized to license the submitted source under the Apache License 2.0. Accepted source is released under that license exactly two UTC calendar months after acceptance. Public repositories must use scheduled release. Keep accepted source private only for a private repository and a specific reason not to publish it; the public result will show the solution as withheld, and you may irreversibly schedule release later. Production metadata JSON

Submission terms

You are authorized to submit this source and the metadata above.
LeanEval may privately fetch, archive, build, and execute the exact commit.
The encrypted source archive may be retained indefinitely, including when evaluation rejects or fails.
The result and submitted metadata may be displayed publicly; do not include secrets.
If scheduled, accepted source will be published under Apache License 2.0 exactly two UTC calendar months after acceptance.
If initially withheld, a later decision to schedule publication is irreversible.

I accept the current LeanEval submission terms.