MemoryQueries

A real read side for a processor spec (ProcessorSpec.givenQueries): the query engine of the Manifest the modules on the class path declare, over snapshots held in memory. A handler's reads run as on a node: the filters, the scope and tenant policies and the budgets apply, and the snapshots decode as the aggregates' state classes.

The Manifest and the state classes come from the modules' binding index (ModelProvider): each module's fragment, merged, and each state class the Manifest names by its binary name (#/$defs/<binary name>, as the compiler writes it), so a state is read by its class whatever the model takes, the node's QueryApi or any other service. A state a hand-written fragment names otherwise comes from the module's models, built with the dependencies given, else from the states given to it (snapshot).

sagaSpec(handlers) {
    givenQueries(memoryQueries { snapshots(Stock.TYPE, "mug" to Stock(7), "cup" to Stock(0)) })
    whenEvent(...) { ... }
}

Only the snapshot queries are served, with the state reads by id of the snapshots given; the events and the datasets are not. A spec builds one with memoryQueries or of.