using kcl as database schema

[aep]

so i'm working on a document database. currently i'm using jsonschema which feels familiar but has terrible performance.
its validation is also way too constrained

instead i'm now looking at cue and kcl. i much prefer the kcl syntax as its immediately familiar to k8s users. kcl seems to be a natural fit because you can store the compiled schema into the db.
it also has expressive validation. but its validation also seems be to not be guaranteed to terminate (or at least with unbounded time/complexity?), so this seems bad for a database?

anyway the bigger question is, is kcls idea of modules really compatible with a database where you'd have your schemas actually in the database. cue can just load schemas via http, so this fits much more natural into their cli, while with kcl the user would have to download the dependencies from the db manually first.

anything else i should consider when using kcl like this?

[Peefy]

cc @zong-zhe @He1pa