I strongly agree with this.We’ve run into the same issues with realtime segment evaluation behaving in unintuitive and undocumented ways, particularly around relationship joins and how OR logic is applied once related entities are introduced.The fact that segment evaluation semantics (e.g. RELATE vs RELATEOPTIONAL, inner vs optional join behavior, and relationship path handling) can change silently is a serious risk in a production marketing environment. It’s very easy for this to result in the wrong customers being included or excluded from journeys, with real compliance and reputational implications.Like Taavo describes, we’ve had to rely on experimentation and inspection of the underlying msdynmkt_segmentquery just to understand what the platform is doing—only to worry that this behavior may change again without notice.At a minimum, Microsoft should document:How the segment builder translates into the underlying query, andThe formal evaluation rules used by the realtime segmentation engine.Without this, it’s difficult to treat realtime segments as a reliable, enterprise-grade feature.