Has anyone already developed a process for a "trace route" like solution for ICM? The idea being that you put in your initial "cold start" prompt, and rather than it working on the prompt itself, it returns the path it took to get to the logic it needed to fulfill the prompt?
Maybe this is built into ICM-Architect, and I just don't realize it.
This would be great for optimization of path flow and recognizing gaps. I just made a simple prompt on my second brain (ICM-based) against a task for a client that is already in my system. I was then asked for permission to grep a file that was a totally different client... WHY & How did you get there to ask that... Is the question?