Skip to content

Concepts

The governance layer

The 12 capabilities that turn the immutable ledger from a system of record into a system of control.

The ledger and certificate system record what happened. The governance layer governs what happens next: the models stay calibrated, vulnerable customers reach the right reviewers, incidents get triaged, bias is caught before it spreads, and every checklist is completed. It is where the platform crosses from “system of record” into “system of control.”

The 12 capabilities

How they fit together

Each capability produces verifiable evidence, either as ledger events or as per-job structured fields anchored to the chain. SLA breaches write SLA_BREACHED. Incident handling writes INCIDENT_LOGGED and INCIDENT_RESOLVED. Impact-assessment sign-off writes IMPACT_ASSESSMENT_APPROVED. Drift detection and bias monitoring read directly from the per-job aiContext.model and clientSegments fields, so the evidence is the underlying data rather than a derived alert event. Vulnerability routing persists vulnerabilityFlags on the job itself. Every capability produces something a regulator or auditor can ask for and get a verifiable answer about.

Mapping to FCA rules

Each capability maps to a specific section of the FCA Handbook: Principles 6 and 12, Consumer Duty (PRIN 2A), SYSC 8, SYSC 22, COBS, and others. See the full mapping in Regulatory coverage.

See also

Hi! I'm Bedrock's AI assistant. I can answer questions about the product, pricing, compliance coverage, and integrations. What would you like to know?