CategoryDocstringLinterTest.lean`

Explanation legend Lean4 Domain Explanation Language (L4DEL)

L4DEL explanations are a separate layer. They do not change the Lean source. Intuition is explanatory prose; numbered items are a reading path; sources link the wording back to evidence.

L4DEL: Lean4 Domain Explanation Language

Annotation provenance. This overlay contains 10 curated AI-written annotations and 7190 mechanical source-derived annotations. They have not been human-reviewed as explanations; treat them as unverified and not mathematical authority. Retained generation history: The 71 original curated annotations were produced in a Claude Sonnet 5.5 session at medium effort; Claude Opus 5.5 is recorded in that session as the advisor model, not the direct author. The bulk source-derived expansion was generated mechanically from pinned source comments by tooling developed in a GPT-5.6 Sol session at ultra reasoning; GPT-5.6 Sol did not originate the quoted source prose. On 2026-10-17 the mechanically generated source-comment annotations of the Formal Conjectures, Carleson, FLT, PFR, CompFiles, Mathematics in Lean and Theorem Proving in Lean overlays were regenerated by the same generator after three corrections made in a Claude Sonnet 5.5 session: titles no longer cut a sentence inside mathematics or end on a dangling word, workflow markers are removed from the quoted prose, and declaration names follow the scanner's namespace resolution. The boilerplate step line was dropped, and comments that were only a row of dashes no longer yield annotations. No new prose was written and no human review is claimed.

Credit: The upstream authors and contributors retain credit for the project and mathematics. lean4-explainer only renders their pinned source and adds the separately disclosed explanation layer.

Project sources: Pinned project documentation, Formal Conjectures paper, arXiv v1

5 declarations, 0 contain sorry, 0 declared as axioms

Tests for the category docstring linter

This file contains test cases for the CategoryDocstringLinter, verifying that research-open, research-solved, and textbook declarations without docstrings are flagged, while declarations with docstrings or other categories are accepted.

Imports (1)

FormalConjecturesUtil.Linters.CategoryDocstringLinter

theorem CategoryDocstringLinter.flagged_open_missing_docstring line 39 source
no axioms what this means
Statement uses: True
Proof uses: True.intro

Tactic trace: 1 steps
Open to load the checked before-and-after goal states.
theorem CategoryDocstringLinter.flagged_solved_missing_docstring line 49 source
no axioms what this means
Statement uses: True
Proof uses: True.intro

Tactic trace: 1 steps
Open to load the checked before-and-after goal states.
theorem CategoryDocstringLinter.not_flagged_with_docstring A documented open problem statement should not be flagged line 55 source
Source documentation
A documented open problem statement should not be flagged.

no axioms what this means
Statement uses: True
Proof uses: True.intro

Tactic trace: 1 steps
Open to load the checked before-and-after goal states.
```
theorem not_flagged_with_docstring : True := by
…
```
theorem CategoryDocstringLinter.not_flagged_test_without_docstring line 60 source
no axioms what this means
Statement uses: True
Proof uses: True.intro

Tactic trace: 1 steps
Open to load the checked before-and-after goal states.
theorem CategoryDocstringLinter.flagged_textbook_missing_docstring line 70 source
no axioms what this means
Statement uses: True
Proof uses: True.intro

Tactic trace: 1 steps
Open to load the checked before-and-after goal states.