🏇🐿️ Cache flow needs to be improved

[shnizzedy]

Because we're using a multi-document definition schema to load external content into MindLogger, and because loading a document from the web takes a non-negligible amount of time, we necessarily must cache the definition documents once they are parsed. Because we neglected to plan for this eventuality prior to implementing any versions through 0.7, each checkpoint is at a point where we hit a timeout on the server, and we have no planned or documented strategy for when to update a cached document.

We can and should overhaul when documents are cached and document that strategy before we implement.

Documents that must be cached for minimum functionality:

• applets
• protocols
• activities
• screens
• response summaries (eg, whatever aggregation we need for the "data" tab)
• profiles as viewed by a particular role

Documents for which caching would immediately and noticeably improve useability

• user's applets Array with customizations
• user lists

[shnizzedy]

Current cache points

• When a new external document is loaded
• When an API call with the refreshCache parameter has that parameter set to true