Arbiter — Business Decision Engine

Business Decision Engine

Arbiter

Rules handle certainty. Arbiter is where certainty lives.

The Drools-backed business decision engine. When a workflow reaches a decision point, Arbiter evaluates the facts, applies governed logic, and returns a typed outcome with full explanation.

One-line summary

Typed outputs — APPROVE, REJECT, MANUAL_REVIEW, ESCALATE. Explanation codes and business metrics with every result. Compiled branch maps — Sphinx executes pre-compiled routing.

Part of the Pommala governed platform stack — one architecture where every authority answers exactly one class of question.

What it is

The problem it solves

The Drools-backed business decision engine. When a workflow reaches a decision point, Arbiter evaluates the facts, applies governed logic, and returns a typed outcome with full explanation.

Business decision logic is hard to govern when it lives in code. Hard to audit when embedded in workflow definitions. Hard to evolve when coupled to orchestration state. Arbiter separates business decisions from workflow execution.

Asset classes

APPROVE

Loan approvals, product eligibility, credit scoring — typed affirmative outcomes with matched rule ID, reason code, and supporting business metrics.

REJECT / ESCALATE

Risk classification, fraud band, underwriting rejection — typed negative outcomes with full explanation codes and derived metrics.

MANUAL_REVIEW

Cases requiring human judgment — routed to review queue with full context, matched rules, and recommendation supporting data.

Capabilities