track and trace

I'd like to make a change to the way I earlier defined track and trace query naming. My question is about timing: is this an acceptable time to do this related to in-process projects? @pospi @mayel @srfsh

I'd like to change the current track and trace to previous and next. That would be the query on all types within the flows, and would return only one step. (All types mean process, economic event, economic resource.)

Then we would use track and trace to return the entire outgoing or incoming flow(s), starting with a resource. So these queries would recursively call the previous or next logic at each step.

Also, there are probably some further expansions needed at some point.

• There might be bounded versions, like within a plan or scope.
• There are some also some known uses at the recipe or planning level, primarily for graph display.