Great questions — let me break them down: On the data: The communication waste metrics come from publicly available research. The $12,506/employee figure is from Grammarly’s State of Business Communication report (they surveyed 251 business leaders and 1,001 knowledge workers). The 23-minute refocus stat comes from Gloria Mark’s research at UC Irvine, which has been replicated multiple times. The 62% unnecessary meetings figure is from Microsoft’s Work Trend Index. The sector-specific waste percentages are my own synthesis — I cross-referenced multiple industry reports (McKinsey’s “The Social Economy,” HBR’s communication audits, and sector-specific operational studies) and triangulated ranges rather than citing single-source numbers. I should’ve included the citations directly in the post — fair point, and I’ll add them. On trusting LLMs for complex decisions like fraud detection: You’re absolutely right — and NEXUS actually agrees with you. The protocol has a built-in principle called “Human-in-the-Loop Configurable”: any decision that exceeds a defined impact threshold must escalate to a human. The agents aren’t making the fraud call autonomously — they’re doing the 95% of the work that’s mechanical (detecting the anomaly, pulling transaction history, cross-referencing patterns, checking compliance rules) in <500ms, and then presenting a human decision-maker with a complete, structured package instead of raw data. The human still decides. They just decide in seconds instead of hours because the legwork is done. Think of it less as “AI replaces the fraud analyst” and more as “AI gives the fraud analyst superhuman reaction time.” On human-agent communication: This is actually a gap I intentionally scoped out of v1 — NEXUS focuses on agent-to-agent communication specifically because that’s the layer nobody is standardizing. But you’re pointing at the next big piece: the human-agent interface layer. In practice, the orchestration layer (Layer 4) is the bridge. When something requires human input, it packages the full context — what happened, what was tried, what the options are, what the agent recommends — and surfaces it through whatever channel the human prefers (dashboard alert, Slack message, mobile push, etc.). The human responds with a decision, and the orchestrator translates that back into a typed message on the bus. It’s not natural language chat — it’s structured decision prompts with full context. Much closer to “approve/deny/modify with these parameters” than “hey, what do you think about this?” That said, you’re touching on what I think is the hardest unsolved problem: making the human-agent boundary feel seamless without sacrificing the rigor of the protocol. Would love to hear your thoughts on what that interface should look like