regulatory-templates-gate1

Map placeholders to data sources by converting field names to snake_case, adding required data source prefixes, and validating each field interactively against regulatory dictionaries. Gate 1 ensures minimum 80% confidence before mappings progress to production.

Regulatory template validation requires snake_case field naming, data source prefixes for lineage, interactive per-field dictionary checks from ~/.claude/docs/regulatory/dictionaries/, and an overall confidence threshold of 80% minimum to ensure audit-ready accuracy.

Run Gate 1 after Gate 0 completes the template structure. Gate 1 maps placeholders to backend data sources, enforces naming conventions, and validates field-to-source connections before data moves to production systems.

Yes. Data source prefixes on every mapped field create full lineage traceability. Combined with snake_case naming and dictionary-grounded validation, the mapping produces audit-ready records for compliance verification and field-origin tracking.

Gate 1 prompts for interactive validation when a dictionary is absent. You approve field mappings manually; Gate 1 ensures snake_case and prefix requirements are met before proceeding, maintaining confidence and compliance standards.

Yes. Gate 1 is production-grade: it enforces snake_case conversion, requires data source prefixes, applies dictionary validation, and maintains 80% minimum confidence. The result supports compliance audits and regulatory reporting with full traceability.