I'd like to apply this to writing Kubernetes operators. They run along this line: https://www.usenix.org/legacy/publications/library/proceedings/lisa99/full_pap

I'd like to apply this to writing Kubernetes operators. They run along this line: https://www.usenix.org/legacy/publications/library/proceedings/lisa99/full_papers/couch/couch_html/index.html https://www.usenix.org/legacy/publications/library/proceedin... That is, trying to converge a system from current state to desired state. If it were written with logic programming and were able to run things in reverse, then it would be able to explain exactly why it is unable to converge the system to the desired state, and what other factors it is waiting on to do so. I think that would greatly enhance observability in a complex system. I was also in the process of writing a chat bot accepting commands be able to autocompletion that takes authorization into account. So given what the user has typed so far, and what it is authorized to use, it would be able to show the available commands.