Decision Authority

Governance Architecture

Who decides, who can change how decisions are made, and how those changes are controlled and recorded.

01
Where Authority Sits
The institution

Keeps final authority over approval, decline, step-up and review. QUORUM returns a verdict and its evidence; the institution's systems act on it.

The rule engine

Produces the real-time verdict from the institution's own rules combined with a behavioural score. Deterministic for a given rule set and input.

The AI tiers

Analyse cases asynchronously and propose rules. Their output is evidence for analysts; they cannot issue a verdict or change a rule.

02
Verdict Thresholds
VerdictScoreEffect
VERIFIEDbelow 15—
AUTHORIZED15–39—
ELEVATED_RISK40–69Recorded as flagged
ISOLATED70 or moreRejected on the transaction channel; counterfactual certificate issued

When transaction facts are supplied, the score is 60% behavioural and 40% rules; if either part alone reaches 70, the verdict is at least ELEVATED_RISK.

03
Changing the Rules
Shadow

New and AI-proposed rules run in shadow mode and record how they would have performed. They do not affect verdicts.

Review

An operator approves or rejects the shadow rule after reviewing its record.

Promote

Promotion needs the security_admin role, WebAuthn step-up and a FROST threshold approval naming that rule, usable once.

Record

The change is written to the signed audit ledger.

04
Other Controlled Actions
User reinstatement

Requires a FROST threshold approval.

IP blocks

Per-institution blocks and unblocks are written to the ledger.

Insider-threat sandbox

A security_admin can route a flagged console account to decoys for 1–168 hours. Changes are audited; API traffic and decisions are never affected.

KB Analytical Solutions Inc. // Governance Architecture Overview // Describes QUORUM at code baseline e9c2cf7