BeedbyteSay 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.
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. Checks by separate AI agents are internal checks. They are not external review or peer review. An external review must identify the version and who checked it, or otherwise document the review. I use “peer reviewed” only for an actual publication review process.
The English overview pages are the originals. The German and Chinese translations use AI and still need language review. For an exact scientific statement, use the 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.
Before publishing a research file, I check its contents, assumptions, attribution and supporting material.