pons keystones declare their powers through address flag bits, not through a registry the launchpad can edit later. tame is deployed to an address, mined via CREATE2, whose low-order bits encode exactly the callbacks it uses: postGraduate, postSettle, preSpanOpen, and preSpanClose, and nothing else. the conduit reads those bits on every settlement and refuses to invoke any callback whose flag is absent.
anyone can read the hex address and verify from the bits alone which callbacks the contract can receive. pons cannot grant tame a callback it did not mine, and cannot revoke one it did. the binding between the token, its keystone logic, and the bound span is enforced by the runtime, not by trust.