@autoschedule/userstate-manager

User-state Manager

Manage user-state

needs:

• app update state as tasks finished
• data-io strategy to save change locally or sync with Google Drive (use LokiJS - pull, merge, push; pouchDB hasen't serialize methods)
• fetch original state (main app responsibility)
• lifespan handle: docs can specify an expiration date. Needs can query for docs with an expiration date greater than the given one. Provider can provide docs with specified expiration date, and have a minimal start. Thus, lifespan isn't handle by userstate-manager.
• update and insert satisfaction have to use a specific needResource build for this query, updated with each update/insert handle.
• build this needResource with the first satisfied range.
• update satisfaction: query (like providers) can have non-waiting need. Proposal for non-waiting needs that are updated: if need's find gather docs, use them, else return satisfied. Next turn, a new query will spawn to satisfy needs, and update satisfaction will be able to use docs.

flow dependency:

• mongo-like engine for simulation (LokiJS)

structure dependency:

• queries-scheduler:
  • potentiality
  • material
• queries-fn:
  • query

workflow: promise -> config (start, end) -> queries (to get transformation) -> query + (potential/material) with needs -> promise ranges of possibilities or -> promise [ranges of possibilities, errors] or -> promise resolve to ranges of possibilites, reject to no resources error

operations:

• build state timeline and check query's need / output to construct potential ranges.
• check query's need that wait for this resource
• build available mask (space where this resource is available)
• check query's output that wait to be lacking (provider's query)
• build available mask (space where this resource is lacking)
• intersect masks