How I check results
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.
I record a claim's mathematical status, formal verification and review separately. A partial result does not settle the full question. Whether an argument is correct and whether it is new are also separate questions.
Formal verification
For a Lean development, I name the exact theorem, assumptions and checked toolchain. I also state which part of the argument it covers. Computations outside that development need their own checks.
AI assistance and review
AI assisted selected internal code and argument checks, and some version-history wording and translations. For each result, I name the evidence and what was checked. A second AI agent can catch mistakes, but that is still a check within this project. I name external or journal review only when it has actually taken place.
English is the original language of these pages; the German and Chinese versions are AI-assisted translations that still need language review. For the exact wording of a scientific claim, consult its cited source version.
Versions and corrections
For research publications, each published version keeps its text, evidence, any attached files and change note together. Corrections get a new version; earlier publication versions remain available at fixed addresses for citation. If I withdraw a release, its status and reason stay visible.