A cautionary tale about refactoring legacy code to Polylith! In our legacy code, we have a number of auto-resolved keywords like ::foo and then they are referred to as ::alias/foo in code outside that namespace. When you refactor that code to Polylith, the ns changes -- which is fine if the keyword is used in the interface since that's what the other code will :require (`:as alias`) so ::alias/foo will continue to work. However, if the keyword is instead used in the implementation, the alias doesn't point to that so the usage will resolve to :top-ns.some-brick.interface/foo but the actual keyword usage inside that brick will auto-resolve to :top-ns.some-brick.impl/foo... Ooops! Two bugs caused by that mistake went to production (for ~24 hours) after a large refactor to Polylith over the last two weeks. It's probably "better style" to not use auto-resolved keywords outside their "home" ns and instead use :explicit/foo qualified keywords for ones that are used across multiple nses.