Formal verification uses mathematical proof to show that software behaves as specified. The approach has long been reserved for specialists working in proof assistants. An episode of the Latent Space podcast argues that AI is beginning to change that, with tools built on the Lean proof language being used to automate parts of work that once required deep expertise. The discussion is framed as a response to what the show calls "slop", the flood of plausible-looking but low-quality code that AI systems can produce quickly. Conventional tests catch errors only in the cases someone thought to write down, whereas a machine-checked proof aims to guarantee that a property holds across all possible inputs. Based on the episode description, formal verification is an emerging approach rather than standard practice in mainstream software development. For Australian businesses and professionals, this changes nothing day to day. It creates no new cost, obligation or compliance requirement, and it does not directly affect obligations under the Privacy Act. Formal verification remains expensive and heavily specialist today, so the practical step is to watch the space and consider it only for high-stakes components, such as payments, safety systems or regulated software, where a fault would be costly. Teams already using AI coding tools should keep their existing testing and code review in place.