KB
Get in touch
All projects
TypeScriptReactViteExpressZen Engine

GoRules AI

Custom decision editor with Zen Engine & Ant Design UI

Open Source — github.com/karan799/gorules-AI·2025 — 2026·2 min read

Full-stack

Stack

Simulate + Evaluate

API

Zod + JDM

Schema

Problem

After integrating GoRules at Care Health Insurance in production, I wanted a standalone sandbox to explore decision graph editing, validation, and evaluation — a reference implementation I could iterate on independently.

What I Built

A full-stack GoRules exploration project with a visual decision editor and API backend:

backend/          Node.js + Express API (Zen Engine)
frontend/         React + Vite + Ant Design editor
shared/jdm/       JDM types, Zod schemas, graph utilities

API Endpoints

  • POST /api/v1/simulate — Evaluate with execution trace
  • POST /api/v1/evaluate — Run decision evaluation
  • POST /api/v1/validate/graph — Validate JDM graph structure
  • GET /api/v1/health — Health check
ADR

Monorepo with shared JDM types over separate packages

Frontend editor and backend evaluator must agree on graph schema. Shared Zod schemas catch validation errors at compile time and runtime.

Alternative considered: Separate repos — cleaner boundaries but schema drift risk between editor and engine

Why This Matters

This project demonstrates initiative beyond day-to-day work — I didn't just integrate GoRules at my job, I built an open-source reference to deepen my understanding of decision engines, JDM formats, and full-stack rule system architecture.

Links

What I'd Do Differently

  • Add automated test suite for graph validation edge cases
  • Docker Compose for one-command local setup
  • Publish shared JDM package for reuse across projects