Where a result lives after the job finishes

What is deliberately not kept

Page 3 of 4

Three things, and each absence is a decision rather than a backlog item.

Intermediate state. A worker that reconciles nine ledgers holds a great deal in memory and writes almost none of it. What is kept is what somebody asked for. A store that accumulated every intermediate frame would be a store nobody could afford and nobody could search.

A version history of outputs. Writing the same solution twice replaces what was there. If you need last month's pack next month, the period is part of the path — which is why solution exists as a level rather than being folded into a filename. Runs that want to be compared should be addressed separately, and that is a choice the application's own operations make.

Anything about who read a result. The store records what was written, not who fetched it. A read log joining outputs to people is the kind of thing that sounds free and is not, and it is not there today.

Used in