Paul Cleary

@britneywright, @mitruly right, I updated the paths to just `ABANDON` to make the diagram less busy. The description includes `CANCEL` and `REJECT` I also added a path on `VALIDATE` from...

@britneywright we should not allow `REJECT` in a `Scheduled` state. That is only available in `PendingReview`.

@britneywright updated to put REJECT back in.

I believe that we need to change the way we generate the batch change status and really make it simpler than it is now, where it all lives inside the...

Tracing does infect the code. The solution I have though of would be: 1. Move the system to finally tagless. This allows us to encode all of our business rules...

Recommend closing and revisiting with move to Scala 3 / new observability

The brute force fix for this is to change the SQL to use `LIMIT` and `OFFSET` instead of how it does paging now. The reason we did paging (`LIMIT, OFFSET`)...

This is low hanging fruit and can easily be added. We have traits like `Monitored` that could be tied in when we have failures.

This would be a portal enhancement only. Something small and rather easy to implement. Priority isn't high.

Seems like the solution here involves doing a new "dependent" check. * If an A or AAAA record is created, do not fail right away * First, check to see...