microgate-logo-new.png
MicrogateDecision Layer
The engine · calibrated decision models

Decision models: AI judgment you can actually rely on

The checks inside the gate run on decision models — a different breed of AI, built for one job: answering policy questions with honest probabilities.

What they are

You give a decision model a state (“this email”) plus typed questions (“does it contain a forbidden promise?”) and it returns a calibrated probability — p=0.93 really means yes ~93% of the time. The answer is always one of your options. No free text, no hallucinated answers.

Why they work

The output is a number you set a threshold on: “block if p ≥ 0.8”. Strictness becomes a documented business decision, tunable per rule — not a prompt tweak. Fast, cheap, and they run locally on modest hardware.

How microgate provides it

The company's policies become a decision tree — Vision → Rules → Policies → Departments → People, every node with rules, questions and thresholds. One call checks the whole stack, and the gate returns which rule, what probability, why — for the audit trail.

The stack, checked bottom-up on every action
People
who acts · role limits
↑
Departments
their rules & exemptions
↑
Policies
privacy · security · spend · brand
↑
Rules
code of conduct
↑
Vision
claims, promises, tone

Every rule that fails carries its probability into the audit trail — \u201cproof, not promises\u201d: the deliverable regulators ask for, as a product feature.

CALIBRATION
p = 0.93
means yes ~93% of the time — a number you can set thresholds on
HARDWARE
Local
runs on modest machines — no cloud, no data leaving the building
SWAPPABLE
Any model
Laya default; upgrade = one config change, zero gate changes