# Skill: 600f6f80 - Regulatory Justification Requirements

**Version**: 1.0.0
**Skill ID**: 600f6f80
**Category**: Regulatory Compliance
**Last Updated**: 2025-01-10

---

## 1. Description

This skill establishes requirements for justifying regulatory proposals and responding to inquiries. When establishing regulations, the proponent must clearly state expected effects and be prepared to provide justification using either external law or statistical case evidence. This skill also defines rules for handling cross-branch evidence and scope limitations for rule revisions.

## 2. Input Data Structure

```yaml
$schema: https://agentskills.io/schemas/regulatory_justification
type: object
properties:
  justification_id:
    type: string
    pattern: ^[a-f0-9]{8}$
    description: Unique identifier for this justification request
  regulatory_proposal:
    type: object
    properties:
      proposal_id:
        type: string
        description: Unique proposal identifier
        required: true
      proposal_type:
        type: string
        enum: [new_regulation, revision, repeal, interpretation]
        description: Type of regulatory action
        required: true
      title:
        type: string
        description: Proposal title
        required: true
      expected_effects:
        type: array
        items:
          type: string
        description: Expected effects of the proposal
        required: true
      applicable_scope:
        type: string
        description: Scope of applicability
      branch_context:
        type: string
        description: Branch context if applicable
    required:
      - proposal_id
      - proposal_type
      - title
      - expected_effects
  justification_response:
    type: object
    properties:
      responding_party:
        type: string
        description: Identifier of responding party
        required: true
      justification_basis:
        type: string
        enum: [external_law, case_statistics]
        description: Basis for justification
        required: true
      external_law_reference:
        type: object
        properties:
          law_id:
            type: string
            description: Reference to external law
          jurisdiction:
            type: string
            description: Jurisdiction of the law
          provision_reference:
            type: string
            description: Specific provision citation
          binding_effect:
            type: string
            enum: [directly_binding, persuasive, not_binding]
            description: Effect of the law on the proposal
        case_statistics:
          type: object
          properties:
            source_url:
              type: string
              format: uri
              description: Source of case statistics
            methodology:
              type: string
              description: Statistical methodology used
            sample_size:
              type: number
              description: Number of cases in analysis
            outcomes:
              type: array
              items:
                type: object
                properties:
                  outcome_description:
                    type: string
                  frequency:
                    type: number
                    minimum: 0
                    maximum: 1
                  confidence_interval:
                    type: string
                    description: e.g., "95% CI: 0.45-0.55"
        required:
          - responding_party
          - justification_basis
  cross_branch_evidence:
    type: object
    properties:
      evidence_from_other_branch:
        type: boolean
        description: Whether evidence comes from different branch
        required: true
      other_branch_id:
        type: string
        description: ID of the branch providing evidence
      automatic_motion_triggered:
        type: boolean
        description: Whether motion to switch branches was triggered
        required: true
      motion_status:
        type: string
        enum: [pending, addressed, withdrawn, irrelevant]
        description: Status of the triggered motion
  revision_scope:
    type: object
    properties:
      is_revision:
        type: boolean
        description: Whether this is a revision of existing regulation
        required: true
      original_regulation_id:
        type: string
        description: Reference to original regulation
      revision_scope:
        type: string
        enum: [full_replacement, partial_amendment, interpretation]
        description: Scope of revision
      applicability_scope:
        type: string
        description: Scope of entities to which revision applies
      notification_scope:
        type: array
        items:
          type: string
        description: Entities to receive revision notification
  inquiry_context:
    type: object
    properties:
      inquiry_id:
        type: string
        description: Original inquiry identifier
      inquiry_type:
        type: string
        enum: [clarification_request, challenge, feedback, suggestion]
        description: Type of inquiry
      responded_to:
        type: boolean
        description: Whether response has been provided
  submitted_at:
    type: string
    format: date-time
    description: Timestamp of submission
    required: true
```

## 3. Output Data Structure

```yaml
$schema: https://agentskills.io/schemas/regulatory_validation_result
type: object
properties:
  decision:
    type: string
    enum: [COMPLIANT, IGNORE, CLARIFY]
    description: Compliance decision
  justification_id:
    type: string
    pattern: ^[a-f0-9]{8}$
    description: Reference to justification being validated
  expected_effect_stated:
    type: boolean
    description: Whether expected effects are clearly stated
  justification_basis_valid:
    type: boolean
    description: Whether justification is properly supported
  cross_branch_handling_correct:
    type: boolean
    description: Whether cross-branch evidence was properly handled
  scope_limitations_respected:
    type: boolean
    description: Whether revision scope limitations are respected
  findings:
    type: array
    items:
      type: object
      properties:
        severity:
          type: string
          enum: [error, warning, info]
        issue:
          type: string
          description: Identified issue
        recommendation:
          type: string
          description: Recommended action
  metadata:
    type: object
    properties:
      validated_by:
        type: string
        description: Agent ID that performed validation
      validated_at:
          type: string
          format: date-time
          description: Timestamp of validation
      applied_norms:
        type: array
        items:
          type: string
        description: List of skill IDs and versions applied
```

## 4. Error Patterns (Auto-Detection)

### 4.1 Missing Expected Effects Pattern
```
Pattern: Regulatory proposal without clearly stated expected effects
Detection Rule:
  - Check 'regulatory_proposal.expected_effects' is not empty
  - Verify each expected effect has clear description
  - Flag vague or missing effect statements
Natural Language Detection:
  "This regulatory proposal must clearly state all expected effects.
   Please provide specific, measurable outcomes this regulation aims to achieve."
Response: CLARIFY
```

### 4.2 Missing Justification Pattern
```
Pattern: Proposal without required justification upon inquiry
Detection Rule:
  - Check 'justification_response' exists when inquiry is made
  - Verify 'justification_basis' is specified
  - Confirm supporting evidence is provided
Natural Language Detection:
  "Upon inquiry, you must provide justification using either external
   law or case statistics. Please specify your justification basis
   and provide supporting evidence."
Response: CLARIFY
```

### 4.3 Invalid Justification Basis Pattern
```
Pattern: Justification basis is neither external law nor case statistics
Detection Rule:
  - Check 'justification_response.justification_basis' is valid enum
  - Verify corresponding evidence structure is complete
  - Flag unsupported justification types
Natural Language Detection:
  "Justification must be based on either external law or case statistics.
   Please provide one of these two valid justification types with supporting evidence."
Response: CLARIFY
```

### 4.4 Cross-Branch Evidence Without Motion Pattern
```
Pattern: Evidence from other branch without triggered switching motion
Detection Rule:
  - If 'cross_branch_evidence.evidence_from_other_branch' is true:
    - Verify 'automatic_motion_triggered' is true
    - Check 'motion_status' is appropriately tracked
Natural Language Detection:
  "Using evidence from another branch automatically triggers a motion to
   switch to that branch's regulations. Please acknowledge this motion
   and address it before proceeding."
Response: CLARIFY
```

### 4.5 Revision Scope Limitation Violation Pattern
```
Pattern: Revision notification sent to entities outside scope
Detection Rule:
  - If 'revision_scope.is_revision' is true:
    - Verify 'notification_scope' matches 'applicability_scope'
    - Confirm entities outside scope are not notified
Natural Language Detection:
  "Revision notifications should only be sent to entities within the
   revision's applicability scope. Please adjust your notification list."
Response: CLARIFY
```

## 5. Prompt Templates

### 5.1 Proposal Submission Template
```
Submitting regulatory proposal: {proposal_title}

Required Information:
1. Expected Effects: List all outcomes this regulation aims to achieve
   - Be specific and measurable
   - Prioritize primary effects

2. Justification Basis (for inquiry response):
   - External Law: Cite specific legal provisions
   - Case Statistics: Provide statistical evidence with methodology

3. Scope Information:
   - If revision: Specify original regulation and scope of changes
   - Define applicability scope for notifications

4. Branch Context:
   - If using evidence from another branch, motion to switch may be triggered
   - Confirm awareness of cross-branch implications
```

### 5.2 Justification Response Template
```
Responding to inquiry about: {proposal_title}

Justification Basis: {basis_type}

External Law Reference:
- Law: {law_id}
- Jurisdiction: {jurisdiction}
- Provision: {provision_reference}
- Binding Effect: {binding_level}

OR Case Statistics:
- Source: {source_url}
- Methodology: {methodology}
- Sample Size: {sample_size}
- Outcomes:
  {outcomes_list}

Cross-Branch Status:
- Evidence from Other Branch: {true|false}
- Motion Triggered: {true|false}
- Motion Status: {status}
```

## 6. JSON Example

```json
{
  "justification_id": "600f6f80-001",
  "regulatory_proposal": {
    "proposal_id": "prop-2025-001",
    "proposal_type": "new_regulation",
    "title": "Enhanced Data Protection Requirements",
    "expected_effects": [
      "Reduce data breach incidents by 35%",
      "Increase user consent documentation compliance by 50%",
      "Shorten incident response time by 40%"
    ],
    "applicable_scope": "All member organizations"
  },
  "justification_response": {
    "responding_party": "regulatory_affairs_001",
    "justification_basis": "case_statistics",
    "case_statistics": {
      "source_url": "https://example.org/data-breach-analysis-2024",
      "methodology": "Longitudinal analysis of 500 organizations over 5 years",
      "sample_size": 500,
      "outcomes": [
        {
          "outcome_description": "35% reduction in breaches",
          "frequency": 0.72,
          "confidence_interval": "95% CI: 0.65-0.78"
        }
      ]
    }
  },
  "cross_branch_evidence": {
    "evidence_from_other_branch": false
  },
  "revision_scope": {
    "is_revision": false
  },
  "submitted_at": "2025-01-10T10:00:00Z"
}
```

## 7. Validation Rules

| Field | Rule | Error Message |
|-------|------|---------------|
| proposal_id | Must not be empty | "Proposal identifier is required" |
| proposal_type | Must be valid enum | "Invalid proposal type" |
| title | Must not be empty | "Proposal title is required" |
| expected_effects | Required, minimum 1 | "At least one expected effect is required" |
| justification_basis | Required for inquiry response | "Justification basis is required" |
| evidence_from_other_branch | Must match auto_motion_triggered | "Motion must be triggered when using other branch evidence" |
| notification_scope | Must be subset of applicability_scope | "Notifications must match revision scope" |

## 8. Dependencies and Relationships

### 8.1 Depends On
- **d0111eb4**: Expected Effect Justification - Related justification requirements
- **12119600**: Branch Version Management - Cross-branch handling rules

### 8.2 Related Skills
- **91ff9448**: Regulatory Compliance Infrastructure - Enforcement framework
- **dbe32f79**: Behavioral Verification Methods - Verification of compliance

## 9. Error Handling Behaviors

| Error Type | Handling Behavior |
|------------|-------------------|
| Missing expected effects | REFUSE transmission, require effect statement |
| Missing justification on inquiry | REFUSE transmission, require justification |
| Invalid justification basis | REFUSE transmission, request valid basis |
| Cross-branch evidence without motion | REFUSE until motion is addressed |
| Scope violation | REFUSE transmission, require correction |

## 10. Changelog

| Version | Date | Changes |
|---------|------|---------|
| 1.0.0 | 2025-01-10 | Initial release |

---

**End of Skill 600f6f80**