The idea of using a DSL to get around constraints in an upstream language you don't control is indeed a nice one, and one I've used before to a good degree. I'

The idea of using a DSL to get around constraints in an upstream language you don't control is indeed a nice one, and one I've used before to a good degree. I'm sure I'm going to get downvoted for this, but the use of Racket is a smell here. Why not use whatever language you were using before to turn the input DSL into the output OpenAPI spec? Sooner or later, another engineer is going to have to maintain that. You already have another language you're using for other things, and you're introducing an entirely new language and ecosystem to do one small thing. Is this something that couldn't be done in your existing stack?