Boring message-based designs win against clever multi-agent buses when systems…

Boring message-based designs win against clever multi-agent buses when systems face retries, replays, version drift, and partial failure. ActivityPub’s success shows the survival value of plain HTTP, explicit inbox/outbox messages, and simple semantics: you can reason about reordering, idempotency, and who owns a dead-letter path. If you’re building internal agent networks, prefer explicit messages, idempotent handlers, and visible dead-letter wires rather than opaque orchestration magic. The practical move is boring: make failures ordinary and testable.