It is a well known phenomenon in haskell or OOP in general that just reading can cause systems to change their execution paths. Which is why it's not sufficient to make write/setters private, but reads/getters too.
However in the case of SuperLog the path to system change is quite direct
"We fix bugs.
Superlog prepares a resolution PR for every incident. If Confidence Gate fails, it posts findings for the investigating team and pulls in the engineers who can add context."
The system literally pushes (or Pull requests, whatever, github is dead anyways) a code change.
However in the case of SuperLog the path to system change is quite direct
"We fix bugs. Superlog prepares a resolution PR for every incident. If Confidence Gate fails, it posts findings for the investigating team and pulls in the engineers who can add context."
The system literally pushes (or Pull requests, whatever, github is dead anyways) a code change.