Decision owner
Accountable compliance owner
The named role remains accountable for the consequential decision.
Banking & Capital Markets
Designed for Compliance analyst
Turn incoming regulatory publications into a traceable impact assessment across internal policies, controls, and product documents, so compliance owners approve remediation work with evidence of what changed and why.
Contract BAN-03 · primary aggregate RegulatoryChangeAssessment · mode loading
Decision brief
This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.
The evidence and control points that shape this recommendation.
Decision owner
Accountable compliance owner
The named role remains accountable for the consequential decision.
Governed evidence
5 record types
Structured records and cited text ground the recommendation.
Workflow
5 controlled stages
Each transition records its input, output, status, and audit context.
Human controls
1 approval gate
Approval gates prevent the copilot from making consequential decisions.
A new consumer-credit disclosure amendment is ingested, 23 obligations are extracted with clause references, 18 map to existing controls, 5 show partial or no coverage across card and personal-lending disclosures, and the accountable compliance owner approves a five-item remediation plan ahead of the effective date..
Turn incoming regulatory publications into a traceable impact assessment across internal policies, controls, and product documents, so compliance owners approve remediation work with evidence of what changed and why.
Approved plan issued to change owners gives Accountable compliance owner the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Step 1 of 5
| Field | Value |
|---|
| Field | Value |
|---|
The output appears here immediately. More technical evidence remains available below.
The demonstration keeps deterministic controls, AI assistance, and approval separate.
Source systems enforce identity, workflow order, policy filters, and record updates.
Retrieval and generation assemble relevant evidence into a cited recommendation or draft.
Accountable compliance owner verifies material claims and approves the consequential action.
Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.
Automated stage
What happens: Regulatory intake service performs ingest and classify the publication using Regulator feed document or bulletin and produces Classified instrument with applicability scope. The transition is deterministic and does not require autonomous model approval.
Why it matters: Classified instrument with applicability scope gives Extraction agent the evidence needed to begin Extract atomic obligations with clause references, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/ingest-and-classify-the-publication
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Extraction agent performs extract atomic obligations with clause references using Instrument full text and produces RegulatoryObligation set with deadlines. The transition is deterministic and does not require autonomous model approval.
Why it matters: RegulatoryObligation set with deadlines gives Mapping agent the evidence needed to begin Match obligations to policies and controls, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/extract-atomic-obligations-with-clause-references
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Mapping agent performs match obligations to policies and controls using Obligations, policy clauses, control inventory and produces ControlMapping set with gap summaries. The transition is deterministic and does not require autonomous model approval.
Why it matters: ControlMapping set with gap summaries gives Compliance analyst the evidence needed to begin Draft the remediation plan, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/match-obligations-to-policies-and-controls
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Compliance analyst performs draft the remediation plan using Gap summaries and business-line impact and produces RemediationItem backlog with target dates. The transition is deterministic and does not require autonomous model approval.
Why it matters: RemediationItem backlog with target dates gives Accountable compliance owner the evidence needed to begin Accept impact assessment and plan, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/draft-the-remediation-plan
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Human approval required
What happens: Accountable compliance owner performs accept impact assessment and plan using Assessment pack with gaps and plan and produces Approved plan issued to change owners. A named human approver must review the evidence before the transition completes.
Why it matters: Approved plan issued to change owners gives Accountable compliance owner the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/accept-impact-assessment-and-plan
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Run a stage to see its explanation, evidence, full request, and full response.
Ask a question and receive an answer grounded in retrieved RegulatoryChangeAssessment evidence.
Select a starter question or enter your own.
Loaded live from /api/config, /api/domain/model, and
/api/domain/sample.
regulatoryChangeAssessments/tenantId + /regulationIdA new consumer-credit disclosure amendment is ingested, 23 obligations are extracted with clause references, 18 map to existing controls, 5 show partial or no coverage across card and personal-lending disclosures, and the accountable compliance owner approves a five-item remediation plan ahead of the effective date.
| Container | Role | Hierarchical partition key | Document types |
|---|---|---|---|
regulatoryChangeAssessments |
Primary | /tenantId + /regulationId |
RegulatoryChangeAssessment, RegulatoryObligation, ControlMapping, RemediationItem |
policyStandardsLibrary |
Reference | /tenantId + /policyId |
InternalPolicyClause |
| Type | Container | Partition key | Identifier pattern | Embedding fields |
|---|---|---|---|---|
RegulatoryChangeAssessment |
regulatoryChangeAssessments |
/tenantId + /regulationId |
assessment::{regulationId} |
None |
RegulatoryObligation |
regulatoryChangeAssessments |
/tenantId + /regulationId |
obligation::{regulationId}::{clauseRef} |
obligationVector |
InternalPolicyClause |
policyStandardsLibrary |
/tenantId + /policyId |
policyclause::{policyId}::{clauseIndex} |
clauseVector |
ControlMapping |
regulatoryChangeAssessments |
/tenantId + /regulationId |
mapping::{regulationId}::{clauseRef}::{controlId} |
None |
RemediationItem |
regulatoryChangeAssessments |
/tenantId + /regulationId |
remediation::{regulationId}::{itemId} |
changeSummaryVector |
Read every obligation with its mapped controls for one instrument in a single partition.
regulatoryChangeAssessments
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.regulationId = @regulationId AND c.type IN ('RegulatoryObligation','ControlMapping') ORDER BY c.clauseRef ASC
Isolate obligations whose control coverage is weak or missing.
regulatoryChangeAssessments
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.regulationId = @regulationId AND c.type = 'ControlMapping' AND c.coverageStrength IN ('none','partial') ORDER BY c.coverageStrength ASC
Partition-key fan-out control-plane query: show obligations affecting a business line that fall due inside the planning horizon. It cannot carry the second partition key because a business line is affected by obligations drawn from many different regulatory instruments, so it runs as a tenant-scoped scheduled sweep off the interactive path, bounded by one business line and a 12-month compliance deadline horizon, executed with MaxItemCount paging and continuation tokens.
regulatoryChangeAssessments
partition-key-fan-out
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.type = 'RegulatoryObligation' AND ARRAY_CONTAINS(c.applicableBusinessLines, @businessLine) AND c.complianceDeadlineUtc < @horizonUtc ORDER BY c.complianceDeadlineUtc ASC
Knowledge-container query against policyStandardsLibrary (bounded fan-out across the /tenantId + /policyId partitions named by the shortlist): flag internal policy clauses mapped to this instrument that have not been reviewed inside the governance cycle, fanned out over the policy ids the control mappings reference.
policyStandardsLibrary
partition-key-fan-out
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.policyId IN (@mappedPolicyIds) AND c.type = 'InternalPolicyClause' AND c.lastReviewedUtc < @staleThresholdUtc ORDER BY c.lastReviewedUtc ASC