Best Design Pattern for Two-Way Data Communication in C# and C++ WinUI 3

I'm working on a WinUI 3 application that consists of two separate projects—one written in C# and the other in C++/WinRT. I need to establish two-way communication between the two, allowing them to pass variable data or structured objects back and forth. For instance, some data generated by the C++ project will need to be processed by the C# project, and conversely, the C# project has UI state information that the C++ project might need to access. I'm aware of how to set up WinRT interop by designating a project as a WinRT component in the `.csproj` file, making it possible to expose public types between C# and C++ through the generated `.winmd`. My question is: what's the best design pattern to set up this communication? I've considered using the Mediator pattern but I'm open to other suggestions. Here are my main goals: I want a clean separation between the C# and C++ code, the ability to send and receive both events and data, and to keep the architecture as straightforward as possible if there's a simpler approach. Any recommendations? By the way, my project is open to the public on GitHub, so feel free to check it out [here](https://github.com/KrishBaidya/LlamaRun/)!