This is HUGE: REA's official guide traces any button in an app with ONE sentence, and the path crosses 3 files
Picture a small Electron app with an Export notes button. Nothing on screen says what happens after the click. The guide gives the agent this to chew on
"Use REA to find what happens when I export notes in this app. Where is the CSV created?"
What comes back, in the guide's example
renderer.js calls window.notes.exportCsv()
preload.js sends the message notes:export
main.js catches it and writes notes.csv
REA's summary pairs 1 message with 1 handler and finds 0 ambiguous ones.
Then the guide adds the sentence that makes it trustworthy: the path is inferred from code, and a runtime capture is how you check what really runs
The sheet on the image takes that one sentence and turns it into a routine for any button in an app you own.
My one addition is a demand at every link of the chain: name the file, name the function, give the source location
Your own app has a button like that, and the same sentence works on it