I’ve recently read the Ash book, and attempted yours (with great difficulty). I have been mulling how these two ideas, together with the core-boundary separation (Bruce Tate) works out in practical system designs.

I feel as if Funx is opinionated about how to model resources behaviour, and Ash is opinionated about resource modeling and working it into the data layer. How do you see these two ideas interact with one another? Pushing all the Maybe Effect Readers into custom calculations?

I think of Ash as providing a blueprint that connects familiar libraries to build an Elixir application.

I think of Funx as providing a functional programming layer that allows arbitrary composition. Like Lego bricks, I can snap pieces together however I want, but there’s no guarantee they’ll form something useful.

How to connect them? I’m still puzzling that out myself. Predicate logic fits naturally in Elixir without needing adapters, so I’ll probably start there.