Загрузка видео...
Не удалось загрузить видео
the loop is not the agent it is one layer of the system LOOP vs GRAPH vs HARNESS ENGINEERING LOOP ENGINEERING controls repetition turns retries budgets exits success checks no progress use durable execution when the run must survive failure → GRAPH ENGINEERING controls topology nodes edges state branches... show more
50,189 просмотров • 2 месяцев назад •via X (Twitter)
Комментарии: 16

The model is not the system. That is the lesson most of the teams learn too late during their journey.

fr the model is just one player the setup decides how the team performs

Exactly. The setup is the coach. The model is just the player.

🫡🫡

controls the blast radius is the best definition of harness engineering

yeah a good harness means one weird move stays one weird move

Everyone talks about models. Few talk about the engineering layer that makes them useful.

把 agent 等同于 while-loop 是当前最大的认知偏差。真正可运维的系统必须显式建模拓扑(节点、边、状态、handoff)并用 harness 限制工具与内存边界,否则 debug 只能靠猜。

Most people debug the model. The real failure is usually somewhere in the system around it.

Agreed

loop as a layer makes sense, but how does it coordinate with the graph layer?

if i were a beginner, the first thing I'd do is learn about loops

The loop is the easy part. I wasted months polishing retries while the mess lived in permissions and what the agent could actually touch. When a long run goes sideways for you, which layer do you open first?

That's a great explanation! It really clarifies how the loop fits into the bigger picture. Well explained.

说得挺对,loop只是agent里最基础的一层,很多人以为写个while循环就是agent了🤔

standard prompt engineering is officially getting old
