I think this evolution paradigm is useful to keep in mind when designing the API, but obviously each successive step is more computationally expensive and more complex (see: error-prone)

You should probably generally use the least advanced of these while maintaining a pathway for future refactors into more complex versions of this