@drewverlee I think the human error messages also need to include a location which is separate from their spec position. Sometimes you need to do validation across keys for humans, but place the error message on a particular key (password & password_confirm must match, but if they don't, the error is in password_confirm)

Is there a rational for the :reason key in the problem map produced by spec/explain-data?. I cant find any discussion on it

is there a function that you can call on a spec to get the code for the spec?

(s/data some-spec) 
;;=> (s/def ::some-spec string?)

https://clojure.github.io/clojure/branch-master/clojure.spec-api.html#clojure.spec/form

(s/form some-spec) in your example should work @drewverlee

It seems to only return part of the spec.

(s/def ::kid (s/keys ::req [::name]))
(s/form ::kid) 
;;> (spec/keys)

I think that keys spec is invalid

try :req instead of ::req

good catch

Hmm, how about something similar for spec functions? those defined using fdef?

(s/form `foo)

s/fdef is using s/def “behind the scenes” to register the spec to the function symbol, so you can use the function symbol to resolve the spec (instead of a namespaced keyword)