I like the requirement to justify a new runtime instead of imposing a blanket ban. A small exception checklist could keep that rule usable: why the current stack is a poor fit, who will maintain the tool, how to install and test it in CI, and whether deployment now requires a new runtime. Logging the choice beside the changed paths makes later cleanup easier too. I work with BOMTOBE, the team behind Orke, and have not tried the author’s workflow.