edge types when passing messages

Hello,

Is it possible to have multiple types of edges and/or is it possible to distinguish edge types during message passing phase (in model_description)?

thanks in advance.

Start by examining the model_description interface and how message passing currently represents edges. Define whether the goal is to support multiple edge types, distinguish them during message passing, or both; done should include a documented behavior and a clear validation path for the chosen design.

Written by the indexing model from the issue text.