The integration question comes before the protocol detail
For a PVS, KIS, OEM or contact-center vendor, the critical question is where lifecycle, identity, state, errors and updates cross the boundary between the host and the Headless component. The public MEMM model therefore starts with ownership and product contracts.
How the two denominators should be read
- 63/63 is the fixed Messenger-domain denominator for the bound R1001 evidence scope.
- 37/37 is the separate host/native product-operation catalogue.
- 9/9 call domains are evidenced through the existing Messenger operation boundary; they do not inflate the 37-operation product counter.
- Provider interoperability, release approval and complete TI-M specification coverage remain separate questions.
What this page explicitly does not claim: R1001 numbers are source-local evidence statements within fixed denominators. They do not establish full TI-M specification conformance, certification, approval, release maturity or provider interoperability.