ALZ-F01 Discovery as a sub-agent orchestrator (sub-agents/) and as eight individual declarative agents (individual-agents/), with their KAB workflow exports. Shared check, render and import scripts, the alz-discovery-sample MCP server, the crucible-kab-dev deploy profile, deployment docs, platform issue reports and the source material. Agent steps time out at 20 minutes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
7.1 KiB
PCA-03: Regulatory & Standards Obligations Agent — Business Requirements
Agent Overview
| Field | Value |
|---|---|
| Agent ID | PCA-03 |
| Agent Name | Regulatory & Standards Obligations Agent |
| Workflow | Requirements Gathering & Output To Architecture Design (#3173096) |
| Work Item | #3175075 |
| Phase | Obligation Determination |
| Wave | Wave 3 - Applicability & Obligation Register |
| Activity Mapping | PCA-ACT-03: Framework Applicability & Atomic Obligation Decomposition |
Business Case
Problem Statement
Platform controls are too often designed against a generic checklist rather than the obligations that actually apply to the client. Applicability is decided informally and the reasoning is lost, overlapping frameworks are implemented twice, and when an auditor asks why a control exists — or why a framework was left out — nobody can point to the clause or the rationale.
Business Value
| Value Driver | Impact |
|---|---|
| Right Obligations | Applicability decided per client from industry, entity type, geography and data classes, with the reasoning recorded |
| Control-Ready Register | Atomic, testable obligations that the control model can map one to one |
| No Double Implementation | Obligations shared by several frameworks merged, every citation kept |
| Audit Defensibility | Every obligation traces to a clause; every exclusion to a reason |
Why We Are Doing This (Spec Alignment)
- Determine applicable regulations, industry standards and internal policies from industry, entity type, geographies, data classifications and the client's policy set.
- Record the rationale for each inclusion and exclusion and route it for confirmation by the client's compliance owner.
- Decompose each applicable framework into atomic, testable obligations tagged by control domain and citing the source clause.
- Merge obligations that several frameworks impose into one entry with every citation.
- Publish the confirmed register to the baseline and control-model agents.
Target Users
- Security & Compliance Architect (primary)
- Client Compliance Owner / Data Protection Officer (confirms applicability)
- Platform Architect
- Risk & Compliance Officer
Capabilities
| ID | Capability | Description |
|---|---|---|
| CAP-01 | Framework Applicability Evaluation | Evaluate a curated framework catalogue against industry, entity type, geography and data classes |
| CAP-02 | Applicability Rationale & Confirmation | Record the reason for every inclusion and exclusion and route it for compliance-owner confirmation |
| CAP-03 | Atomic Obligation Decomposition | Break framework clauses and internal policies into single, testable obligation statements |
| CAP-04 | Control-Domain Tagging | Tag each obligation with the control domain(s) it touches |
| CAP-05 | Cross-Framework De-duplication | Merge equivalent obligations and keep every source citation |
| CAP-06 | Obligation Register Publication | Emit a versioned register consumable by the baseline and the control model |
User Stories
US-001: Applicability
As a Security & Compliance Architect
I want the applicable frameworks determined from the client's profile, with the reasoning recorded
So that controls are designed for the obligations that actually apply
Acceptance Criteria:
Given the client's industry, geographies and data classifications.
When the agent evaluates the framework catalogue.
Then it lists the applicable frameworks with a rationale, and the excluded ones with a reason, for compliance-owner confirmation.
US-002: Atomic Obligations
As a Security & Compliance Architect
I want each applicable framework broken into single, testable obligations
So that the control model can map every obligation to a control without interpretation
Acceptance Criteria:
Given an applicable framework.
When the agent decomposes it.
Then each obligation is a single testable statement tagged by control domain and citing its source clause.
US-003: Cross-Framework De-duplication
As a Platform Architect
I want obligations shared by several frameworks merged into one
So that the same control is not designed and implemented twice
Acceptance Criteria:
Given two frameworks that impose the same obligation.
When the register is built.
Then the obligation appears once, with citations to both sources.
US-004: Internal Policy Obligations
As a Risk & Compliance Officer
I want the client's own policies represented alongside regulations
So that internal mandates such as data residency are enforced with the same rigor
Acceptance Criteria:
Given internal policy records supplied by the intake agent.
When the register is built.
Then internal-policy obligations appear with source typeinternal_policyand a citation to the policy section.
Success Metrics
| Metric | Target |
|---|---|
| Rationale Coverage | 100% of evaluated frameworks carry an inclusion or exclusion reason |
| Obligation Atomicity | 100% of obligations are single testable statements (reviewer sample) |
| Citation Completeness | 100% of obligations cite a clause or policy section |
| Confirmed Before Sign-off | 100% of applicability decisions confirmed by the compliance owner before the baseline is signed off |
Agent Dependencies
| Direction | Agent / Source | Data Exchanged |
|---|---|---|
| Consumes | PCA-01 Platform Requirements Intake Agent | Engagement-Context.json, internal-policy candidate records |
| Consumes | PCA-02 Design-Area Selection & Elicitation Agent | Confirmed geographies and data classifications |
| Consumes | Curated framework catalogue (Kyndryl-maintained) | Framework metadata, applicability criteria, clause index |
| Produces | PCA-04 Requirements Baseline & Design Brief Agent | Obligation-Register.json |
| Produces | PCA-06 Unified Control Model Agent | Confirmed obligations with control-domain tags |
Traceability
| Spec Section | BRD Section | Prompt Objective |
|---|---|---|
| "Applicability" | CAP-01, CAP-02 | Obj-1: Evaluate Framework Applicability with Recorded Rationale |
| "Atomic Obligations" | CAP-03 | Obj-2: Decompose Frameworks into Atomic, Testable Obligations |
| "Tag each obligation with the control domain" | CAP-04 | Obj-3: Tag Obligations by Control Domain with Clause Citations |
| "Cross-Framework De-duplication" | CAP-05 | Obj-4: Merge Cross-Framework Duplicates |
| "The agent proposes, a person confirms" | CAP-02, CAP-06 | Obj-5: Publish a Confirmed, Versioned Obligation Register |
Out of Scope
- Legal advice or final legal interpretation; the client's compliance owner confirms applicability.
- Mapping obligations to controls or enforcement points (owned by PCA-06 Unified Control Model Agent).
- Continuous regulatory change monitoring (owned by the CP4 Operate and Continuously Optimize workflow, #3123632).
- Extracting internal policy text from documents (owned by PCA-01 Platform Requirements Intake Agent).