Your software sounds amazing and will probably make you a fortune. I wanted to check my understanding of how Antithesis fuzzed software. The way I understand it from reading the documentation is that you create a "workload" which is sort analogous to a fuzzing harness that will typically make random API calls, and Antithesis will pursue sequences of events that are more interesting as defined by coverage and also inject faults. So something like this could probably be pretty easily be adapted to a workload: https://github.com/grpc/grpc/blob/86953f66948aaf49ecda56a0b9.... Do you use any interesting coverage metrics or just basic blocks?