Precise Koi Engine Route information

It would be awesome to have some kind of precise / known tag for the engine route (path) that was followed ot produce a given scenario. Right now there are only so many, so it’s not terribly difficult to discern by looking at the model and the techlib file BUT, because pathways do different things in order to handle data availability issues and/or might also include use of special submodules (CDR or “Soft / Facilitator”) I think it would be valuable to know what route it took to get there so that if it looks funky / buggy, we have a more targeted method by following such markers.