Why "layers"? The constituents of a Multi-agent System (MAS) [1] are called "agents". BTW: Synecdochical semantic diffusion is not uncommon in software engineering
My take on the post is for engineering disciple where JoeJag wants to create a common word while tackling "Agent" issues.
I like Joe's approach as this disambiguates during troubleshooting without trying to figure out under which "context" other engineers are using Agent vs. Models.
You get lost in context just like AIs do without such disambiguation.
Secondly the confusion is designed to benefit the bull** by using ambiguous language they can do as humpty dumpty did in Alice in Wonderland and say "When I use a word, it means just what I choose it to mean. Neither more nor less" Which benefits whatever they are pushing.
Beware those that attempt to muddle language and avoid precision in speaking.
Often with posts like this I imagine someone had their own confusion and then somehow projected it on everyone else. Like Trump thinking people didn't know about the word groceries or that dumb ends with a b.
> I often hear people use the words agent and model interchangeably
_what_ people. Would I hear one of my colleagues do this, I'll slap them across the face. With a 4 pounds salmon. Alive.
> to help us have more precise conversations.
What problem are you trying to solve. _Why_ you need more precise conversations. I mean, I understand what you aiming at. But is it really worth it to go nitpicking at people's mental models, is the gain worth it?
Eric from alignment and research at OpenAI: https://www.youtube.com/watch?v=87DyyMV0kCY
It honestly bothers me so much when he says "This new model has access to x". No, the harness you allowed it use at runtime has access to x.
No idea what the underlying model is for any of this. More over, I don't ever vibe code, I check and understand the code that is generated by my LLMs. And yet, I use Vibe Code (the product) all day.
Lost the thread yet? I did... Tbh, it also took some time between Anthropic starting the push towards Claude Code and me understanding what is really was. Using terms interchangeably during this time of discovery is absolutely maddening. For Mistral it comes on top of their rename of services from "le Chat" and Mistral Code (still in parts of the UI) to Vibe and Vibe (for) Code.
> When you can name the layer, you can fix the layer. That is the whole point of being precise. It is not about being pedantic. It is about being able to improve things faster and more effectively.
Also, for any given fact, tons of people aren't aware. Anything you already know is news to a sizeable number of people.
Relevant xkcd: https://xkcd.com/1053/
> Also, for any given fact, tons of people aren't aware.
Double points for Gryffindor.