Divergence from upstream pkg:
jtengstrand.md has the original developer's readme.
"Polylith" is a pun based meme which has been associated with more than one software system. The original systems were lisp and particularly CLOS based, but this one is clojure and thus java based. For background to this point see the #lisp log fragment referred to in the repo about text.
precis of intent in my dev scope
MIL and a "polylith" fit some intentions for downstream applications programming including those for graphical programming as in National Instruments G lang. I would use clj-polylith directly if it were more connected with its tradition, substantial, and less clojure centric. May do so anyway should a java based element of my current interests call for it and one in particular (jitsi) is a likely candidate.
So forked for that purpose, the divergence will be substantial if this engages for the above intended purpose. A later discovery of a working MIL (particularly the original Polylith) could affect this and should the upstream package evolve into more of an MIL, then would want to drop this fork and use the upstream, with my adaptations applied external to it.
Discovery of MIL/Polylith, action up to this fork.