NUL Systems

Real-Time Compliance Enforcement

NUL compiles written policy into an executable graph, evaluates events in real time, and records every decision with a complete audit trail—so compliance is enforced at the moment of action, not weeks later in a ticket queue.

The problem

Policies live in documents. Controls live in spreadsheets. Reviews happen after the fact. By the time a human approves or blocks, the transaction, access grant, or export has already happened.

What NUL does
Policy indecision outevidence captured
  1. Policy Studio ingests policy text and builds a knowledge graph (Graph RAG) plus searchable chunks (Linear RAG).
  2. Command Center validates transactions, requests, and documents against active policy. NUL returns APPROVED, REVIEW, or BLOCKED with confidence and reasoning in seconds.
  3. Review Queue is for optional human follow-up—borderline or low-confidence cases—not the default path for every decision.
  4. Audit Explorer stores immutable history: engine status, confidence, matched policy context, and human outcome when a case was reviewed.
Status vs outcome
Aligned with how NUL records decisions in Audit Explorer

Statusis the validation engine's decision—what NUL decided in real time when you ran Validate (APPROVED, REVIEW, or BLOCKED).

Outcomeapplies only when a case went through the Review Queue for optional human review (e.g. low confidence or borderline policy match). If NUL's confidence is above your threshold, there may be no separate review outcome at all—the engine status is the final record.

Who it's for
Compliance, GRC, and operations teams that need policy enforcement at the point of action—vendor onboarding, access requests, transaction monitoring, training approvals, and regulated data handling—with evidence ready for audit.