Semantic Version Changelog

The document anchors the core motivation of the entire v0.2 series in one sentence: theorem-producing code must additionally preserve a "mathematical semantic version," not just look at Git commits — even if two commits are only one submission apart, the certificate strength in a mathematical sense might completely change (this is exactly the concrete case document 14 is about to show). The document lists eight specific items that need monitoring for semantic drift: whether the definitions of the $p$-isogeny and $a_3$ gates have changed, whether the twist condition $\gcd(d,3N)=1$ is still present, whether $\operatorname{BSD}(E,2)$ is currently treated as a necessary condition or a full certificate, the verification method for $\Sha[2]$ of $E'$, whether the $\mathcal S$ non-emptiness criterion is a deterministic criterion or reverts to bounded search, the status of testing flags, whether timeouts are currently marked FAIL or UNKNOWN, and whether algebraic rank and analytic rank are still stored in separate fields. The document encapsulates the core principle of the entire piece into a directly quotable maxim: code version ≠ theorem semantics version — the version number might not change at all, but the underlying mathematical semantics have drifted; or it might just be one commit apart, yet the mathematical semantics are completely different.