I’ve been experimenting with a spec-first approach to backend development and was curious how something like this would fit into a Rails workflow.

Instead of writing controllers/models directly, the idea is to define a system in a structured DSL (APIs, data models, workflows, auth), and then compile that into runnable services.

Right now it outputs Node (Fastify), Java (Spring Boot), and Rust, but the underlying idea is having a single source of truth that can be regenerated safely — especially when using AI.

I come from running production systems where things tend to drift over time (auth rules, models, workflows), and this approach felt more stable.

Repo: https://github.com/nikoma/carrier

Curious what Rails folks think:

• Would you ever want something like this sitting next to Rails?

• Or does Rails already solve this problem better with conventions?

• Where would this break in a typical Rails app?