Discussion about this post

User's avatar
SinghCoder's avatar

The "brilliant goldfish" framing feels right.

The scheduler layer gets especially interesting once agents are running in the background. "Who goes first" matters, but so does "should this agent even be awake right now?" A lot of agent infra still assumes the agent is polling, checking, or sitting in a loop somewhere. That gets expensive fast, and it burns context on noise.

Feels like the missing piece is agent attention: register what matters once, then wake the agent only when something actually matches.

Taylor Ortiz's avatar

Yeah the orchestration element of it and where those instructions sit to guide the workflow in a series of stages will be critical to get right.

No posts

Ready for more?