Alcoholics Anonymous
Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: Where Large Action Models actually fit in real production systems


Newbie

Status: Offline
Posts: 1
Date:
Where Large Action Models actually fit in real production systems
Permalink  
 


Ive been trying to understand where Large Action Models actually fit in real software systems, not just in theory. Most of what Ive seen so far is either demos or very controlled environments, but I recently read this breakdown that explains how theyre supposed to coordinate actions across tools instead of just generating text: https://www.trinetix.com/insights/what-are-large-action-models-and-how-do-they-work . It reminded me of a small internal tool I worked on where we had an AI layer deciding which API endpoint to call next, but it was still very rigid and rule-driven. Im wondering if anyone here has actually seen something like this running in a real production environment where the model has some real autonomy, or is it still mostly just structured automation with a smarter interface?



__________________


Member

Status: Offline
Posts: 15
Date:
Permalink  
 

Ive worked on something close in an enterprise workflow system, but it definitely wasnt fully autonomous. What we did was more like guided execution, where the model could propose a sequence of actions, but each step had to pass validation rules and sometimes even manual approval depending on the risk level. The interesting part is that even that limited version already improved speed for routine tasks like data entry and ticket routing. But we quickly learned that letting the model freely decide actions creates too much unpredictability. So the real value wasnt full autonomyit was reducing the number of decisions humans had to make while still keeping control over execution. I think most real systems today are somewhere in that middle ground.

__________________


Newbie

Status: Offline
Posts: 1
Date:
Permalink  
 

Im not involved in development directly, but I work in a role where we interact with a lot of automated internal tools. From my side, the most noticeable change isnt that systems are thinking more, but that workflows are becoming less visible. Earlier, you could clearly see each step in a process. Now, some tools just return a final result, and its not always obvious what happened in between. Thats convenient, but it also makes troubleshooting harder when something goes wrong. So even if the technology is improving, I think transparency is still a big challenge, especially for teams that rely on these systems daily.

__________________
Page 1 of 1  sorted by
 
Quick Reply

Please log in to post quick replies.