BeedbyteHow 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.
Research tools and review
Jordi Gartner is responsible for editorial publication through Beedbyte. AI tools assist selected tasks: construction and proof development, code and long computations, targeted source checks and translations. Each article identifies the contributions relevant to its result and the exact verification scope.
Checks by separate AI agents are internal project checks. External review must document the reviewed version, scope and reviewer or review process. “Peer reviewed” is reserved for an actual scholarly review process.
Research entries identify their source language and language-review status. Some German and Chinese research translations use AI assistance and remain marked as drafts until human language review. For the exact wording of a scientific claim, 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.