import { a as CurpValidationActor, c as CurpValidationErrors, d as GenerateCurpFieldDef, f as GenerateCurpFieldType, i as createCurpValidationManagerFromActor, l as CurpValidationRule, n as CurpValidationState, o as curpValidationMachine, p as GenerateCurpForm, r as createCurpValidationManager, s as CurpValidationConfig, t as CurpValidationManager, u as EnterCurpFieldDef } from "./curpValidationManager-DVGr7Fq7.js";
//#region src/modules/curp-validation/curpValidationUtils.d.ts
type MexicanState = {
  value: string;
  label: string;
};
declare const mexicanStates: MexicanState[];
//#endregion
//#region src/modules/curp-validation/curpFields.d.ts
/**
 * Declarative schema for the CURP generation form.
 *
 * `secondLastName` is intentionally optional: many people in Mexico have
 * only a single paternal surname. It carries no validation rules.
 */
declare const GENERATE_CURP_FIELDS: GenerateCurpFieldDef[];
/**
 * Config for the single field on the CURP entry gateway screen.
 *
 * Validation contains only `curpFormat` — there is intentionally no
 * `required` rule. The user can legitimately leave this field empty
 * and use the "I don't have my CURP" button to switch to the Generate
 * flow; surfacing a "required" error on blur of an empty field would
 * be misleading.
 *
 * The Continue button on this screen is gated by a UI-level no-op guard
 * (`curp.length === 0`) instead, which lives in `curpInput.tsx`.
 */
declare const ENTER_CURP_FIELD: EnterCurpFieldDef;
//#endregion
export { type CurpValidationActor, type CurpValidationConfig, type CurpValidationErrors, type CurpValidationManager, type CurpValidationRule, type CurpValidationState, ENTER_CURP_FIELD, type EnterCurpFieldDef, GENERATE_CURP_FIELDS, type GenerateCurpFieldDef, type GenerateCurpFieldType, type GenerateCurpForm, createCurpValidationManager, createCurpValidationManagerFromActor, curpValidationMachine, mexicanStates };