Does quantification really need to many dependencies?

(Hey lookatthat, I'm doing code things again 0o0 Anyway...)

I just wanted to pull in the Exists type real quick, but instead I also had to wait for the notoriously expensive aeson compile. While it's merely a time-wasting issue, on reflection it seems a little unusual that a type theoretic primitive would require so many dependencies. /understatement I could have just implemented a simple Exists by hand without so much as the prelude!, and it probably would have taken less time than waiting for aeson 🙃

Would you be amenable to splitting out a new quantification-aeson library from quantification? Or even pulling a quantification-core library out that just defines the Exist* types and some instances? Obviously, this will mean creating orphan instances, but the way I see it: that's just what happens when Alice and Bob independently write libraries (the concept of existential quantification, and then aeson), and then Charlie wants to use both of their work meshed together (how quantification currently stands).

No files or tests are named. Start by reviewing the quantification package's dependency on aeson and the existing Exist* types, then determine whether the proposed quantification-aeson split or a quantification-core package is the intended outcome; done means an agreed package boundary with dependencies and orphan-instance implications addressed.