I would argue it"s part of the application state, if you need that context to be accessed. If you look at the paxos protocol it would create some unwanted coupling between proposers and learners when the application state is distributed.
The next stage in UX is to be untethered from a single display, we have to start thinking what is the architecture of such system.
I'd like to add that tweaking semantics is a game that you are guaranteed to lose. Especially when it is based on a particular use case. Now, you could go back to TLA+ and see if I missed something. (which is likely), but I would advise aligning the way possible with TLA+ and paxos.
@jdubray umm I see, that kind of makes sense that filtering or a list of filtered items doesn't need to belong to the model; I'll try to put it in the state function like my 'animate' function I think that's a good idea. I wonder though if there would be situation where I would need the filtered list to be stored in the model.. Umm
today I looked into using webpack to use css-modules to start applying styles to my application; should be fun this week :)
@lhotari thank you for the pointer, it indeed looks very close to Paxos and TLA+. I had not heard of Runway before. What do you think about adopting a programming style aligned with Paxos and TLA+? What do you think about SAM?
I was looking at the PRPL pattern yesterday and I was thinking that SAM is a great foundation to use that pattern because of it's "step" approach you can easily predict what you will need at every step including the initial one