For teams that built their own agent action ledger: what would make you trust a dependency here?

One answer I keep getting is that the hard part isn't writing the rows. It's living with someone else's abstraction after your workflows change.

That makes sense. The core can be pretty small: an operation ID, the exact request and result, append-only status changes, and a thin adapter for each external system.

But I've also heard from teams that spent most of their agent engineering time on retries, reconciliation, approvals, history and all the other plumbing around the actual agent.

So where's the line for you?

If you built this layer yourself, what would an external primitive have to get right for you to keep it rather than replace it in a year or two?

Open format? Self-hosting? Raw-event access? No opinionated workflow?

Or is this simply too close to the product to outsource?