Thanks, Quinn. Understood. We'll own the security design and verifier policy. One specific question about library constraints: suppose a signed process P permits A.dylib but rejects B.dylib. A has an ordinary, non-weak LC_LOAD_DYLIB dependency on B. Both libraries have constructors. Assume the remaining system dependencies and signing requirements are satisfied. After reaching main, P calls dlopen on A with RTLD_NOW. Does the library constraint reject B before any initializer in either newly loaded A or B runs, or can A's initializer run before rejection of B causes the operation to fail? This is a hypothetical example, not an observed test result. I'm asking only about dependency-load/initializer ordering, not remote attestation or a whole-process security guarantee.