How settings are scoped per-button (stored inside the button blob) and per-role (stored in role-specific options), how the cascade resolves conflicts, and the gotchas around blob-shaped per-button storage.

MAM_Phone_Data_Pipeline is the canonical builder of the mobile app’s JSON payload. 4 phases (auth → settings → content → finalize), state carried by MAM_Phone_Data_Context, ~70 sibling-plugin subscribers via the legacy…

Per-phase reference for phase_auth, phase_settings, phase_content, phase_finalize. What each does, what each fires, what each reads/writes on the context, and where sibling-plugin hooks land.

How mam_forms_manager_phone_manager normalizes phone numbers, validates them via SMS-delivered codes, and ties into both Gravity Forms phone fields and the user-roles phone-code login flow.

The convention for which priority to use when registering against mam_get_phone_data_before_send. Critical contracts: priority 1000 for home_cats, 1001+ for total overrides, 199 for form-state validation, 10 for the default cohort.