CAP defines availability physically: “requests to a non-failing node receive a response”. TigerBeetle ensures logical availability: as long as clients can reach a majority, requests complete with strict serializability, preserving safety and liveness under partitions.

cf. Durability and the Art of Consensus: https://www.youtube.com/watch?v=tRgvaqpQPwE