mikehostetler
Joined 15 years ago
Joined 15 years ago
The `uncertain` mapping isn't clean. DASP treats it as terminal: the host can't prove whether effects occurred, so it must not retry. A2A's `TASK_STATE_UNSPECIFIED` is indeterminate, but not terminal. The adapter must preserve the DASP outcome in metadata and map it conservatively, likely to `FAILED`.
I came to similar conclusions - what does valuable agentic software look like? It's not OpenClaw (yet)
The game theory then, in my opinion, is to focus on the knowable frontier - implement tools we can trust - and continue working and sharing that work.
I am holding onto the optimistic case - valuable use cases beyond coding agents will emerge.
This will be solved - and I hope that Jido can be a meaningful participant in that wider conversation.
Actions can enforce an output schema: https://hexdocs.pm/jido_action/schemas-validation.html#outpu...
Agents can as well - but it can be implemented a few different ways.
Jido core has zero LLM support for this reason.
There's nearing 40+ years of "Agent" research in CompSci, LLM's came along and we threw out all of it. I didn't like that so I spent time researching this history to do my best at considering it with Jido.
That said, I love LLM's - but they belong in the Jido AI package.
There’s a growing community showcase and I have a list of private/commercial references as well depending on your goals