GSoC 2026 — question about UI direction for OG-Core module

[Kunal-Darekar]

Hi, I'm looking at the Contributor 2 scope and had a couple of questions
before I start writing my proposal.

I spent some time reading the codebase and built a small Streamlit prototype
for the OG-CLEWS coupled mode to understand the data flow better —
branch is feat/ogclews-ui-prototype in my fork if anyone wants to look at it.

Two things I'm not sure about from the spec:

1. For the OG-Core module frontend, is the plan to extend the existing
   Flask+jQuery SPA or start a Python-native layer (Streamlit/Dash)? The spec
   mentions both options and I want to scope the proposal correctly.

2. The CLEWS → OG-Core data exchange — is defining the variable mapping schema
   part of Contributor 1's work, or does Contributor 2 own that interface too?

Kunal Darekar

[SeaCelo]

@Kunal-Darekar We are defaulting to the current infrastructure of MUIOGO to avoid a large rewrite. A new architecture may be considered in the future, but not in this cycle. About the data exchange, we are working to document the variable mapping schema. The priority for now is to onboard the OG model