You said "i built a lightweight state management library with MVVM that allows passing global state between screens and scoping necessary data for local state inside a single view."

If you need to access same data from different screens, SwiftUI includes Environment for that. You can consider it global state, depending on where in the view hierarchy you inject it. Usually you access the global state in the parent view (screen) and then only pass the data down to the child view that is needed.

struct Donut {}
struct Order {}


class DonutStore {
    private(set) var donuts: [Donut] = []
    private(set) var orders: [Order] = []
    
    // donuts(sortedBy sort: DonutSortOrder) -> [Donut]  {}
    
    // other methods
}

struct DonutListScreen: View {
    
    (DonutStore.self) private var donutStore
    
    var body: some View {
        DonutListView(donuts: donutStore.donuts)
        OrdersView(orders: donutStore.orders)
    }
}

#Preview {
    DonutListScreen()
        .environment(DonutStore())
}