I Built Regulation Compiler to Translate Regulations Into Engineering Requirements

Regulatory documents are usually written for legal and compliance teams.

But when those requirements reach an engineering team, the questions become much more technical:

• What does this requirement actually mean for our systems?
• What technical controls are needed?
• Which parts of our infrastructure are affected?
• What should developers and security engineers actually implement?

That gap is what led me to build Regulation Compiler.

What is Regulation Compiler?

Regulation Compiler is a desktop-first tool that explores how regulatory requirements can be transformed into structured, actionable insights for engineering and security teams.

The workflow I'm exploring is:

📜 Regulation
→ 🧠 Interpretation
→ ⚙️ Technical Requirements
→ 🔐 Compliance

Why I built it

I wanted to experiment with making regulatory requirements more understandable from an engineering perspective instead of treating compliance as something completely separate from development.

The current version is intentionally an early testing release.

I'm not trying to claim that the workflow is solved yet. I'm putting it in front of developers and security professionals to find out what actually works and what doesn't.

I'm looking for feedback

I'd particularly like feedback on:

• Is the output technically useful?
• Does the workflow make sense to developers?
• What information is missing?
• What would you change?
• Which regulations or security frameworks should be supported?

You can try the current version here:

👉 https://regulation-compiler-web.vercel.app/

If you try it, I'd really appreciate honest feedback — especially if something doesn't make sense or doesn't feel useful.

This is an early testing phase, so the feedback will directly influence what I build next.