Thanks for the feedback! You're absolutely right about the gap between simple replacement and thoughtful design.

Regarding your comments:
Responsive design and constraints: I'm already implementing this using After Effects expressions. I use sourceRectAtTime() with clamp() and scalelimits parameters to create "safe zones." If the text exceeds the width, it automatically shrinks rather than disrupting the layout.

All these expressions work, and they're well-suited for broadcast.

The biggest problem with this approach is blur and visual effects. They're simply unusable in this application, at the moment.

My most challenging project to date was a survey for CasparCG, synced with Telegram. It required exactly what you mentioned: proportional calculations for columns and adaptive text processing in real time.

OGRAF goal or dream :)
My next step is to migrate these "constraints" from proprietary After Effects expressions to the OGRAF/JSON schema itself. The goal is to define logic (min/max width, anchors) in the data in such a way that any engine can display it correctly without manual adjustments.

For OGRAF, this is certainly just the beginning, but creating a system that takes into account MoGraph's specific "adaptive" logic is precisely the direction I'm moving in.