regulatory-templates-gate2

Validation rules are defined by resolving Gate 1 uncertainties and running transformation tests. The process produces explicit validation rules, cross-field checks, and documented alternatives for any rejected mappings.

The required pass rate for regulatory mapping test validations is strictly greater than 90%. Additionally, 100% of mandatory fields must be successfully validated, with documented alternatives provided for any rejected field mappings.

No, external MCP API calls are strictly prohibited during regulatory field mapping validation. The validation process requires only Gate 1 context to resolve uncertainties and execute test validations internally.

Confirming regulatory mappings outputs validated_mappings, validation_rules, and a test_summary. These outputs resolve Gate 1 uncertainties and provide explicit rules and documented alternatives to feed Gate 3 template generation.

Regulatory templates fail because unverified assumptions from Gate 1 introduce faulty mappings. Gate 2 validation catches these by enforcing mandatory field verification and transformation testing before template generation proceeds.