It's on the Readers Web engineers to provide these requirements.

Obviously, then, it's on me to provide additional context and find a seam to tie this investigation into…

I need a little more context on this as I wasn't in the frontends group meeting and don't really understand what's being asked for.

Is this specifically about MobileFrontend or at a more high level?

This is about using a reactive framework with OOUI. Specifically in Marvin. It is a bit of a follow up to the Hackathon work where @Milimetric was able to use OOUI with Vue, but integration was not as clean as he hoped.

Similarly this work should be about identifying roadblocks to incorporating OOUI into Marvin so they can be translated into tickets. @Jhernandez should also be able to provide some context here.

I think until we're more advanced on the project and have concrete use cases to help define and illustrate what changes we would require from OOUI we are not going to be able to define these.

As we commented, we had concrete use cases why we didn't adopt OOUI in MobileFrontend, but I can't recall. Maybe we could dig them up as use cases.

Feel free to add me back to this task when my input is needed.