This distinction is important because eval-driven development isn’t about achieving perfect (100%) scores like test-driven development is about passing all tests. Instead, it’s focused on continuous improvement always getting better than before, even if some metrics never reach 100%.
Adding this explanation will help readers set the right expectations and understand that not all metrics need to be “perfect” for eval-driven development to be working as intended.