Regulatory Compliance Mapping Chain

validated legal chain v1.0.0 cc-by-sa

Block ID: 580443ef-d0fa-4b61-93b2-873df9bcaa7f

Community-contributed block. PromptDNA makes no guarantee of output quality or fitness for purpose. This block operates in a regulated domain. Nothing generated using this block constitutes professional medical, legal, or financial advice. User assumes all responsibility for use.

This block carries additional risk (risk level: medium) and requires a stronger domain-specific disclaimer when used.

Template

Map the compliance obligations for the activity in {business_activity} against the regulatory framework in {regulations}. (1) Determine the threshold question: does the regulation actually apply to this activity and entity? Check the definitions, covered-entity criteria, and jurisdictional reach, plus any exemptions or thresholds (size, revenue, volume) — many compliance panics dissolve once you confirm the rule doesn't reach you, and conversely assuming exemption is dangerous. (2) Extract the specific obligations: for each applicable provision, state what the entity must do, must not do, must document, and must report, with the deadlines and triggering events. (3) Map current practice against each obligation, marking compliant, gap, or unclear — an obligation you can't confirm compliance with is a gap until proven otherwise. (4) Assess the consequence attached to each obligation (penalty, enforcement priority, private right of action) to prioritize the gaps by exposure, not just by count. (5) Identify overlapping or conflicting requirements across multiple regulators, since compliance with one can violate another. (6) Produce a prioritized remediation list and note that regulations change and vary by jurisdiction, interpretations evolve, and a compliance professional or licensed attorney must confirm applicability and sufficiency before reliance.

Map the compliance obligations for the activity in {business_activity} against the regulatory framework in {regulations}. (1) Determine the threshold question: does the regulation actually apply to this activity and entity? Check the definitions, covered-entity criteria, and jurisdictional reach, plus any exemptions or thresholds (size, revenue, volume) — many compliance panics dissolve once you confirm the rule doesn't reach you, and conversely assuming exemption is dangerous. (2) Extract the specific obligations: for each applicable provision, state what the entity must do, must not do, must document, and must report, with the deadlines and triggering events. (3) Map current practice against each obligation, marking compliant, gap, or unclear — an obligation you can't confirm compliance with is a gap until proven otherwise. (4) Assess the consequence attached to each obligation (penalty, enforcement priority, private right of action) to prioritize the gaps by exposure, not just by count. (5) Identify overlapping or conflicting requirements across multiple regulators, since compliance with one can violate another. (6) Produce a prioritized remediation list and note that regulations change and vary by jurisdiction, interpretations evolve, and a compliance professional or licensed attorney must confirm applicability and sufficiency before reliance.

Variables

Name	Type	Required	Trust level
business_activity		yes
regulations		yes

complianceregulatory-analysisobligations-mappingchain-of-thought

Ratings

0.0

Overall (0)

0.0

Accuracy

0.0

Consistency

0.0

Clarity

0.0

Efficiency

Benchmarks

Not yet self-validated against any benchmark. Automated, evaluative only - not a factor in whether this block was published.

Submitted by James P FounderMod via mcp · 2026-07-18