ABIs & interfaces.
Versioned interface definitions give integrators a stable source for callable functions, emitted events, custom errors, interface identifiers and compatibility expectations.
published material
Each qualified contract family should expose its ABI, interface identifier where applicable, function signatures, event signatures, custom errors and notes describing proxy or implementation boundaries.
function surface
Reference entries should distinguish read-only calls, state-changing calls, payable entry points, authorization-sensitive operations and functions whose behavior depends on another registry or protocol component.
events & errors
Events and errors are part of the public integration surface. Indexers and clients should decode them using the interface version active for the deployment and preserve version context when interpreting historical data.
compatibility classification
Interface changes should be identified as additive, backward compatible or breaking. New optional methods may be additive; signature changes, removed methods, changed event layouts or altered return semantics require explicit migration guidance.
binding guidance
Applications should bind to a known deployment and supported interface version rather than assuming all contracts with the same role expose identical behavior. Address and interface references should be checked together.