Native modules and the New Architecture

Makes the app's own native code safe to own on iOS and Android: native code only where no package fits, written with the Expo Modules API in a local module under modules/<name>/, reached through one typed, lazy, optional binding in its adapter behind a port, with the binding type and the Swift and Kotlin definitions proven equal; Turbo Modules only where shared C++ or publishing needs them; and every third-party native library either native on the New Architecture or a recorded decision. Two zero-dependency checkers prove it.

Rules that must hold