How replacement tokens (e.g., [user_login], [passwordcode], [order_id]) work in notification templates: per-type token list declared in mam_notification_list, supplied at fire time, substituted by the channel sender.

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…

How mam-main bridges Gravity Forms into the mobile app: form discovery, the cache layer, mobile-shape transformation, the per-form-id submission hooks, and the route from submission to mam_form_manager_send_notifications.

How mam-main supports multiple form providers (Gravity Forms today, programmatic forms today, additional providers like Ninja Forms via the same extension surface). Explains the two parallel hook namespaces — generic…

A worked example walking a single form from declaration through submission: the mam_gf_get_form_settings entry, slug→field-id admin mapping, cache pre-warm, dynamic data injection, the three row→form surface patterns, and the submission…