ring%3aregulatory-templates-setup（Ring%3a 监管模板设置）

Regulatory Templates - Initial Setup

Overview

This sub-skill handles the initial setup phase for regulatory template creation, including template selection and context initialization.

Parent skill: regulatory-templates

Output: Complete initial context object with all selections and configurations

Foundational Principle

Setup initializes the foundation - errors here propagate through all 3 gates.

Setup is not "just configuration" - it's critical validation:

• Template selection: Wrong template = entire workflow on wrong regulatory spec (hours wasted)
• Context initialization: Incomplete context = gates fail mysteriously downstream
• Dictionary status check: Skipped check = lost automation, unnecessary interactive validation
• User awareness: No alert about validation mode = poor UX, blocked progress

Skipping setup steps means:

• Hard-coded context bypasses validation (typos, wrong versions)
• Missing values cause gate failures (debugging waste)
• Silent dictionary check = user unprepared for interactive validation
• No audit trail of selections (compliance gap)

Setup is the contract between user intent and gate execution. Get it wrong = everything downstream breaks.

When to Use

Called by: regulatory-templates skill at the beginning of the workflow

Purpose: Gather all user selections and initialize the context object that will flow through all gates

NO EXCEPTIONS - Setup Requirements Are Mandatory

Setup requirements have ZERO exceptions. Foundation errors compound through all gates.

Common Pressures You Must Resist

Setup Requirements (Non-Negotiable)

Template Selection:

• ✅ REQUIRED: Use AskUserQuestion for authority and template selection
• ❌ FORBIDDEN: Hard-code based on user message, skip selection dialog
• Why: Validation confirms correct template, prevents typos, establishes audit trail

Dictionary Status Check:

• ✅ REQUIRED: Check ~/.claude/docs/regulatory/dictionaries/ for template dictionary
• ❌ FORBIDDEN: Skip check, assume no dictionary exists
• Why: Determines validation mode (automatic vs interactive = 40 min time difference)

User Alert:

• ✅ REQUIRED: Alert user if interactive validation required (no dictionary)
• ❌ FORBIDDEN: "They'll figure it out in Gate 1"
• Why: User preparedness, UX, informed consent for 40-min validation process

Complete Context:

• ✅ REQUIRED: Initialize ALL context fields (authority, template_code, template_name, dictionary_status, documentation_path)
• ❌ FORBIDDEN: Minimal context, "gates will add details later"
• Why: Incomplete context causes mysterious gate failures

The Bottom Line

Setup shortcuts = silent failures in all downstream gates.

Setup is foundation. Wrong template selection wastes hours on wrong spec. Missing context breaks gates mysteriously. Skipped checks lose automation.

If tempted to skip setup, ask: Am I willing to debug gate failures from incomplete initialization?

Rationalization Table

If You Find Yourself Making These Excuses

STOP. You are rationalizing.

Setup appears simple but errors propagate through 4-6 hours of gate execution. Foundation correctness prevents downstream waste.

Severity Calibration

MUST classify setup issues using these severity levels:

Classification Rules:

CRITICAL = ANY of:

• Template selection cannot be validated against registry
• Authority is not BACEN or RFB (invalid for Brazilian regulatory)
• Context object missing required fields (authority, template_code, template_name)
• Setup steps cannot complete

HIGH = ANY of:

• Dictionary status not checked (determines 40-min vs automatic validation)
• User not informed about interactive validation requirement
• Documentation path not set correctly
• Template metadata incomplete

Blocker Criteria - STOP and Report

You MUST distinguish between decisions you CAN make vs those requiring escalation.

HARD GATES (STOP immediately):

1. Template Not Found: Template missing from registry
2. Ambiguous Selection: User response doesn't match available templates
3. Missing Context: Required context fields cannot be populated
4. Dictionary Check Skipped: Cannot determine validation mode without check

Escalation Message Template:

⛔ **SETUP BLOCKER - Cannot Initialize Context**

**Issue:** [Specific blocker]
**Impact:** [What cannot be determined/initialized]
**Required:** [What needs resolution]

**Cannot proceed to Gate 1 until resolved.**

Cannot Be Overridden

NON-NEGOTIABLE requirements (no exceptions, no user override):

CANNOT allow user to:

• Skip template selection ("I already told you CADOC 4010" = NO - validate anyway)
• Bypass dictionary check ("just assume no dictionary" = NO)
• Skip user alert ("they'll figure it out" = NO)
• Initialize partial context ("add missing fields later" = NO)
• Hard-code selections ("same as last time" = NO - run selection)

Pressure Resistance

See shared-patterns/pressure-resistance.md for universal pressure scenarios.

Setup-Specific Pressures

Setup Steps

Step 1: Regulatory Authority Selection

AskUserQuestion: "Which regulatory authority template?"

Open system: The workflow supports ANY regulatory template, not just the pre-defined list. If the template is not listed, select "Novo template" and provide the spec.

Step 1.0: New Template Intake (only if "Novo template" selected)

If the user selects "Novo template", collect the following before proceeding:

AskUserQuestion (sequence):

1. Template name — ex: "CADOC 4030", "DLO", "e-Financeira evtPatrimonio", "DECRED"
2. Regulatory authority — BACEN | RFB | CVM | SUSEP | COAF | outro (especificar)
3. Output format — XML | TXT (fixed-width) | HTML | CSV | JSON
4. Official spec — URL do manual/circular oficial OU caminho de arquivo XSD/PDF (OBRIGATÓRIO)
5. Reporter dev URL (optional) — URL do ambiente de desenvolvimento para validação pós-geração

Context additions for new templates:

is_new_template: true
template_spec_url: "<URL fornecida>"
template_spec_format: "<XML|TXT|HTML|CSV>"
reporter_dev_url: "<URL ou null>"  # for optional Test Gate

Alert user:

"Template novo detectado. Gate 1 irá extrair os campos da spec fornecida, usar pattern matching com templates existentes para sugerir mapeamentos, e salvar o dicionário automaticamente ao final. Na próxima execução deste template, o workflow será automático (~5 min)."

BLOCKER: If no official spec URL/file is provided → STOP. Cannot map fields without the authoritative specification.

Step 1.1: Template Selection (Conditional by Authority)

AskUserQuestion: Show template options based on authority selected:

Template Registry:

Capture: Authority (BACEN/RFB), category, code, name, metadata

Step 2: Optional Deadline Input

If not provided by user, use standard deadline for the template type.

Step 3: Check Dictionary Status and Alert User

CRITICAL: Check dictionary BEFORE initializing context. Path: ~/.claude/docs/regulatory/dictionaries/{category}-{code}.yaml

If NO dictionary exists → AskUserQuestion:

• Question: "Template has no pre-configured dictionary. Gate 1 will use batch approval by confidence level (~10-15 min). Proceed?"
• Options: "Proceed" | "Choose different template"
• Alert user: Gate 1 will query APIs → suggest mappings → batch approval by confidence level → auto-save dictionary for future use

Step 4: Initialize Context Object

Base context structure (ALL fields required):

Template-Specific Extensions:

Documentation Paths:

• CADOC: .claude/docs/regulatory/templates/BACEN/CADOC/cadoc-4010-4016.md
• e-Financeira: .claude/docs/regulatory/templates/RFB/EFINANCEIRA/efinanceira.md
• DIMP: .claude/docs/regulatory/templates/RFB/DIMP/dimp-v10-manual.md
• APIX: .claude/docs/regulatory/templates/BACEN/APIX/{code}/

State Tracking Output

Output on completion: SKILL: regulatory-templates-setup | STATUS: COMPLETE | TEMPLATE: {template_selected} | DEADLINE: {deadline} | NEXT: → Gate 1

Success Criteria

• ✅ Template selected and validated
• ✅ Deadline established (input or default)
• ✅ Context object initialized with ALL fields
• ✅ Dictionary status checked

Output: Return complete context object to parent skill.