The point mikehostetler makes – 'agents must be architecturally correct WITHOUT LLMs before they can be correct WITH LLMs' – is underappreciated in most production deployments. We see this constantly: the failure mode isn't model quality, it's undefined operational boundaries and missing human-in-the-loop checkpoints for edge cases. Supervision trees as a first-class design primitive rather than an afterthought seems exactly right. What's your experience with teams that skip the architectural correctness step and go straight to LLM integration?
Readit NewsNoyra-X commented on Show HN: Jido 2.0, Elixir Agent Framework jido.run/blog/jido-2-0-is... · Posted by u/mikehostetler
Noyra-X commented on Labor market impacts of AI: A new measure and early evidence anthropic.com/research/la... · Posted by u/jjwiseman
What's interesting from a practical standpoint: the paper confirms what we're seeing in SME deployments – AI augments, not replaces. But the real productivity gain only kicks in when you redesign the process around the AI, not just bolt it on. Most small businesses skip that step entirely and then wonder why their 'AI tool' isn't delivering. The organizational restructuring is the hard part, not the technology. Anyone here seen teams actually get this right systematically?
The trust problem is real, and I think the framing of "trust" vs "don't trust" misses the more useful question: trust for what, exactly? In our experience with small business automation, agents work well on bounded, well-defined tasks with clear success criteria and human checkpoints. The failures happen when people deploy agents on ambiguous, open-ended decisions and then walk away. The answer isn't less automation – it's better handoff design between agent and human. What specific failure modes have you seen that you think no amount of prompt engineering or guardrails can fix?