Discussion about this post

User's avatar
Paul Henry Smith's avatar

Putting the intent layer above orchestration seems so obvious. But some folks think of it as baked into agent instructions or even tool calls. This is already failing in more complex situations involving multiple agents.

There’s enormous need for design to clarify and reify the top layer, perhaps as the place where missions are defined with goals, budgets, constraints — but not with specific steps or methods: Intent clothed in the specifics that steer outcomes within constraints and prevent chaos, perhaps?

This is not prompting.

It’s a new domain for which experiences either will be designed or cobbled together higgledy-piggledy. I call it the mission layer.

No posts

Ready for more?