Log/changed
changed
Signal before swarm
I used to fire every research agent at once. Signal first: what changed, why it matters, then the swarm.
A full swarm on a quiet file is just noise with better typography. I was burning context on lots where nothing had moved.
The change is a gate at the front: name the signal, or do not run. A listing shift. An owner reply. A comps move on the same block. Something real.
Fewer parallel guesses. More of the packet is about the thing that actually changed.
That front gate is how a file enters the stack. Lot intelligence does not start because I am bored. It starts because something on the lot, or next to it, actually moved. The rest of the modules inherit that reason.