Skip to main content
The Policy Engine is the core differentiator of DABAR. Instead of trusting an AI model to behave correctly because of a well-written prompt, you codify the rules your organization must follow — and DABAR enforces them on every answer.

​
Why a policy, not a prompt

Prompts are suggestions. In regulated work, suggestions are not defensible:
  • They’re invisible to auditors.
  • They drift when the model changes.
  • They collapse under adversarial input.
A Policy is a structured, versioned, auditable artifact. You define it once, DABAR enforces it forever — across every project that uses it and every agent built on top.

​
What a Policy contains

Every Policy in DABAR is composed of:
​
name
string
Human-readable identifier.
​
description
string
The intent of the policy — what it’s meant to analyze or enforce.
​
rules
Rule[]
The reasoning constraints DABAR must follow. Each rule has a name and a description.
​
knowledgeFiles
File[]
Reference documents the policy is authoritative against (regulations, guidelines, playbooks).
​
outputFormat
object
Optional JSON schema describing the shape DABAR must return.
See Create politics for the full API.

​
How rules are enforced

Every time DABAR produces an output under a policy, the engine:
  1. Grounds the answer in the policy’s authoritative sources.
  2. Scores every claim against the rule set.
  3. Labels each claim as CONFIRMED, NOT FOUND, or ESTIMATED.
  4. Rejects outputs that violate a rule, instead of silently degrading.
This is why DABAR can be used in contexts where a generic assistant cannot — the enforcement is deterministic and inspectable, not probabilistic.

​
Writing good rules

Good rules are specific, testable, and short. They describe how DABAR should reason, not what the answer should be.
“Only evaluate loan applications above 50,000 USD. For any lower amount, respond with OUT_OF_SCOPE.”
“Every finding must cite the exact source document and page number. Claims without citation must be labeled ESTIMATED.”
“Respond in formal Spanish. Never use colloquialisms or abbreviations.”
“Be careful and accurate.”
This is a vibe, not a rule. DABAR can’t enforce it.

​
Policies are reusable

A Policy is written once and applied to many Projects. The same “Credit Risk Policy” can run against:
  • Monday’s batch of applications.
  • A single loan under review.
  • A live agent the committee queries in real time.
Change the Policy and every downstream Project and Agent reasons under the new rules — no retraining, no reprompting.

​
Next

Primary Sources

What kinds of sources a Policy can draw from.

Create a Policy

The full API reference for creating politics.