Say exactly what was checked
A finite computation establishes a result only for its stated inputs and range. A pattern in many examples can suggest a conjecture; it does not establish an infinite claim. Proofs must state their assumptions and account for every quantified case.
The archive records mathematical status separately from formal verification and review. An open question stays open when a useful intermediate result is found. A valid argument and a claim of novelty are also separate matters.
Formal verification
A Lean source file is not a blanket certificate for a project. A release should identify the exact theorem, the checked toolchain, its assumptions and the part of the argument that the formal development covers. Computation outside that development needs its own explanation and checks.
AI assistance and review
AI tools help explore ideas, write and inspect code, draft arguments and translate these pages. Internal checks by separate agents are described as internal. External review is claimed only when a named or otherwise documented reviewer has checked the specified version. Peer review requires an actual publication review process.
The English overview pages are the editorial originals. German and Chinese text is AI-assisted translation and remains marked for language review. For a scientific claim, consult the exact source version rather than relying on a translated summary.
Versions and corrections
A published version should connect its text, evidence, files and change note. Later corrections receive a new version, preserving the earlier citation. If a release must be withdrawn, its status and reason remain visible.
No manuscript or research download is released merely because it exists in a working directory. Publication requires a deliberate review of its contents, assumptions, attribution and supporting files.