A TSMM binding is more than a list of loose correspondences. It is a bounded translation surface between TSMM and another ecosystem. The binding contract makes that boundary explicit so implementers can tell what the mapping preserves, where it becomes approximate, and what should not be inferred from the mapping alone.
Every binding now includes a bindingContract object with the following elements:
sourceModel: fixed to TSMMtargetSystem: the external ecosystem being alignedbindingVersion: version of the translation contractguarantees: what the binding can preserve with confidencelimitations: what remains ecosystem-specific or only partially capturedbehavioralExpectations: runtime or process expectations that the mapping assumesconstraintSetRef: path to the accompanying constraint setA binding is useful only if readers know what not to conclude from it. Each constraints.json file records:
The current main-branch catalog includes contract-backed bindings for:
These bindings are intentionally semantic. They make systems comparable without pretending to replace each ecosystem’s protocol rules, processing logic, or governance text.