1 Part 1: One agent, five platforms: why I am building the same invoice-exception agent five times
2 Part 2: Why invoice exceptions are a good test for agents ... 28 more parts...
3 Part 3: A platform-neutral reference architecture for enterprise agents
4 Part 4: The 2026 agent protocol stack: MCP, A2A, gateways and identity
5 Part 5: The scorecard: 11 criteria, and why every score needs evidence
6 Part 6: Where should an invoice agent stop and ask a person?
7 Part 7: Design the tools once: one tool contract every platform can reuse
8 Part 8: Named errors every finance agent needs
9 Part 9: Read-only tools first: how an agent earns write access
10 Part 10: The golden set: 30 invoices and what "correct" means
11 Part 11: Build 1 — MuleSoft: Agent Fabric, the MCP Connector and Omni Gateway
12 Part 12: What carried over from series 1 (and what did not)
13 Part 13: Setting up five trial environments: what you need before you build
14 Part 14: Build 2a — Boomi: hosting the tool contract
15 Part 15:…