upvote
What is "formalized intent" supposed to mean?

Isn't the whole advantage of the LLM that it takes plain language intent as its input? Isn't it better to think of what measures you want to move and what safeguards are inviolate?

What is formalized intent? If we take intent to be some mental phenomena, on some weak basis isn't that what natural language already does? It can then be further "formalized" into something like math or coding languages. Which are then already basically "formalized intent"? Maybe you could plot these acts on some spectrum of formalizing, like perhaps natural language gets more "formalized" if you write a spec, akin to some form of pseudocode? Isn't the promise of the new LLM age that instead of being trapped by designers and their "intents" we can compose software at runtime in accordance with said inviolate safeguards? Why ship software "products" if every customer has their own personal LLM? Why not just ship APIs? Why speak of this "human bottleneck" as a necessity rather than something that seems wholly contrived? You don't think whatever software end state your human team stumbles toward through the field of their foggy intents doesn't already exist in the latent space? In a world of LLM clients why not leverage the clients capacity to act on its own intent?

It just strikes me despite your first two paragraphs, the subsequent ones show a profoundly antiquated way of thinking of this problem. I suspect the notion of "intent" is largely unnecessary here. Perhaps you will clarify to me what you mean though that will show I am mistaken, as again I am quite lost as to what you mean by "formalized intent".

reply
[flagged]
reply
[dead]
reply
deleted
reply