tool(
query: Enum[...]# typedon_error: Result | Failure# must handleidempotent: true# safe retry
)
Insight — confirm / replace
The failure that hurts isn't the tool erroring, it's the tool succeeding with wrong data. Give it a third state most schemas can't express: "succeeded, but low confidence."
✓ Takeaway 1 — Reliable Tool Calls
Layer 2 · Memory / the break
RAG retrieves snippets. It misses how they relate.
Your story → drop in during rehearsal
A real case where retrieval missed a relationship and the output looked right but wasn't, the moment you realized RAG alone wasn't enough.
Layer 2 · Memory / the fix
Paradigm: retrieval vs. relationships · RAG = index cards. Knowledge graph = a subway map.
Facts → RAG
Relationships → graph
wrong = a missed connection? → graph
Insight — confirm / replace
You don't need a perfect graph. A shallow one-hop dependency graph on top of RAG catches most silent drops, for a fraction of the effort.
✓ Takeaway 2 — RAG vs. Knowledge Graph, know which, when
Layer 3 · Coordination / the break
More agents is not more reliability.
40%
of agentic projects canceled by 2027 — mostly missing risk controls (Gartner)
Your story → drop in during rehearsal
A real multi-agent moment where one agent's bad output flowed downstream unchecked, or where you resisted adding agents and it paid off.
Layer 3 · Coordination / the fix
Paradigm: the bulkhead — watertight ship compartments; one floods, the ship floats. + least privilege.
Insight — confirm / replace
The human checkpoint is only a bottleneck if it's everywhere. Gate the irreversible ~5% of steps; leave the rest autonomous.
✓ Takeaway 3 — No-Cascade Coordination · delegate the work, never the accountability
What you take home
Three-quarters are adopting agents. Few reach production. These three layers are the gap.