maybe this should be :or schemas, a union of different conforming values

No each rule I have now will restrict the set in some way and all the restrictions need to be valid for the set to be valid. I have the same setup for a map and it works great, however I can not find any good example how to restrict a set/collection using Malli. Or maybe I misunderstand what you mean, can you give some example code that would generate what I want using :or?

For the example you gave, you use :fn schemas to invalidate certain shapes

I filled in ex3 here:

(mc/validate
 [:and
  ;; This is the full domain of the set, all combinations should be generated and then filtered based on predicated as described below
  [:set [:enum 1 2 3 4 5 6 7 8 9]]
  
  ;; ex1 set should include 1 AND 4 but NOT 8 other values are ok
  ;; ex2 set should include 1 AND 4 but NOT 8 other values NOT ok
  ;; ex3 set should include 3 OR 4 but not both
  [:fn (fn [s] (not (and (contains? s 3) (contains? s 4))))]
  ]
 #{3 4})
;; => false

Is there any way to force more then 100 tries when you generate values, looking at the code I get the feeling that this value is not meant to be changed?

for generating tricky datastructures, there are some tools, the simplest is supplying elements with :gen/elements (these all go on the and), or :gen/fmap which would be a function that can return valid sets for you

I think :gen/gen can be a generator. hangon I’ll find the docs

https://github.com/metosin/malli?tab=readme-ov-file#value-generation

The simplest would be just to be able to generate more values, the shape is not that tricky and all combinations would probably be generated for 5000 tries. So would be nice to just be able to increase the number of tries. Currently I do this by not wrapping the first clause in an and, instead I just generate a value and then filter if over the validation of the remaining schema validations. Then I can loop this until I find a match. Since I generate the schema dynamically it is nice to not have not to custom schemas. I am trying to keep them simple as possible and then rather just spend some more time on random generation.

As I understanding if I am to do what you say I would need to dynamically build but generators rather then schemas?

Building a generator dynamically too would make sense here.

If someone has a good proposal for a generator combinator thing in malli, happy to hear. E.g. where :and would collect generator part from it's children and construct a functioning generator out of that automatically.

I am now using m/generator to get the generator then I can use test.check instead. Combining that with malli specs has really been a nice fit for my use case so far.