Feature batches, tiles, assets, and metadata documents are different payloads
answering different questions, but they are admitted by exactly the same
discipline and in exactly the same order: region identity, then the caller's
authorization scope, then version expectations, then extent, then expiry, then
content-addressed lookup, then integrity. Keeping that order in one module is
what makes "the narrowest true reason" a property of the contract rather than
of whichever read path a caller happened to use.
The one gate every offline read passes through.
Feature batches, tiles, assets, and metadata documents are different payloads answering different questions, but they are admitted by exactly the same discipline and in exactly the same order: region identity, then the caller's authorization scope, then version expectations, then extent, then expiry, then content-addressed lookup, then integrity. Keeping that order in one module is what makes "the narrowest true reason" a property of the contract rather than of whichever read path a caller happened to use.