{
  "name": "regulatory-change-operationalisation",
  "domain": "Audit & Assurance",
  "title": "Regulatory Change Operationalisation",
  "description": "A four-stage regulatory change operationalisation workflow over caller-declared change and obligation data. Step 1 builds the 12-month regulatory change calendar, the effort and impact matrix and the change register for the declared institution type, jurisdiction and product scope (tool 318). Step 2 scores the obligations register for owner, control and evidence coverage and returns one verdict, COVERED or GAPS_FOUND, naming every obligation that still lacks an owner or evidence (art-691). Step 3 maps the obligation set onto the compliance control book as a control heatmap, a maturity score and a Policy Mandate control register (tool 158). Step 4 sweeps the dated compliance records into OVERDUE, DUE_SOON, SCHEDULED and DONE bands under the declared weekend and holiday roll rules, so a change programme that still has unowned obligations or already-missed dates is visible rather than implied. Each step computes from its own declared inputs; the order is analytical, not a statutory sequence.",
  "composer_url": "https://ainumbers.co/chaingraph/chains/regulatory-change-operationalisation.html",
  "regulatory_basis_status": "not_assessed",
  "regulatory_basis_decided_by": "REGCHANGE-OPS-CHAIN-2",
  "regulatory_basis_decided_at": "2026-10-22",
  "export_capability": ["json"],
  "steps": [
    {
      "tool_id": "318-regulatory-change-impact-assessor",
      "handoff": "Builds the 12-month regulatory change calendar, the effort and impact matrix and the change register for the declared institution type, jurisdiction and product scope; step 2 then scores the obligations register for owner, control and evidence coverage. Stage 1 of 4."
    },
    {
      "tool_id": "art-691-regulatory-obligations-register",
      "handoff": "Scores the declared obligations register for owner assignment, control linkage and evidence coverage, returning one verdict of COVERED or GAPS_FOUND and naming every obligation that still lacks an owner or evidence; step 3 then maps the obligation set onto the compliance control book. Stage 2 of 4."
    },
    {
      "tool_id": "158-fintech-compliance-control-mapper",
      "handoff": "Maps the declared obligations onto the compliance control book across the declared regimes, producing the control heatmap, the maturity score and the Policy Mandate control register; step 4 then sweeps the dated compliance records for what is already overdue. Stage 3 of 4."
    },
    {
      "tool_id": "art-588-docket-deadline-sweep",
      "handoff": "Sweeps the declared dated records against the caller-declared weekend and holiday roll rules, banding each record OVERDUE, DUE_SOON, SCHEDULED or DONE so a change programme with already-missed dates is visible rather than implied. Final stage."
    }
  ]
}
