I'd be interested to see why the author would be unable to use the ports interface to work with the API of his package. My understanding about why the core tea

I'd be interested to see why the author would be unable to use the ports interface to work with the API of his package. My understanding about why the core team is being so controlling over the native modules access is that they're trying to prove that each native module is pure, so they can make assumptions and declarations in the compiler that the code produced is pure. By forcing unblessed/unreviewed modules to use the ports interface they can maintain this assumption. Without doing this you lose all of that assumption and your compiler falls apart, if it's based on that assumption.