Zach Daniel

🤔 that would solve for some of it. But even then, we'd have to limit available filters to things contained in the the protocol until we figure out a way...

I think its worth exploring though and could solve the bulk of the issues though.

Works for me!

I *think* so? At least for most cases, and we can tackle the others one by one. As for autmoatically registering them, honestly that kind of thing is almost universally...

We can do that :) But if we want to get the list of all things that implement `App.Payment`, that is a very hard problem.

Potentially, but they might be cross registry. They might even be cross API? I guess if we prevent that, then yes we can do it that way. Basically require that...

If we start with the restriction that all implementors must be in the API's registry, then its fine. Its easy to filter a list of modules to see which ones...

The protocol (we should figure out what this kind of thing should be named, and really hash this aspect of it out, I'm not sure how I feel about it...

`Ash.Resource.Spec` sounds like a good idea potentially. There is a lot of theory involved with doing this kind of thing declaratively, to the point that I wonder if we should...

I think the declarative validator is even more complex than just overridable or not. It is for basic things but gets complex for more complex applications of this kind of...