Law Welcome + Intake Contract

Flow: legal_intake | Phone: +15122777529 / 512-277-7LAW | Updated 2026-07-07

The law line is auth-first for returning callers, but intake-first for useful lead capture. Caller ID may select the returning path; the saved profile facts are not copied into intake slots until the SMS code succeeds.

Path Diagram

New caller

welcome_first
intake_guest_gate
intake_name_ask
intake_legal_topics_ask
intake_sms_optin_gate
intake_send_link if SMS consent is yes
intake_verify_code if a code was sent
intake_pre_save - silent bridge
intake_save
intake_confirm then menu

Known caller with SMS consent

welcome_back
welcome_send_follow_along
welcome_follow_along_sent
welcome_auth_choice: link or code verifies; 0/skip is guest
welcome_verify_code after explicit verify/code retry
welcome_unlock_granted on correct code
intake_verified_prefill
intake_legal_topics_ask
intake_sms_optin_gate skips re-asking consent
intake_pre_save then intake_save

Invariant: opening the unique link or giving the correct four-digit code authenticates the session. 0, skip, or guest continues without authentication.

Why It Regressed

The welcome-auth gate was added, but successful verification reused the old generic option-0 profile entry.
The old entry had no post-auth prefill state, so verified callers could be routed through stale name/SMS prompts or toward the menu.
Code handling was not narrow enough; the regression test now proves codes are accepted only in verification-code states.

Tests

TestLegalWelcomeEntryPathSim::test_known_caller_security_code_requires_zero_before_unlock
TestLegalProfileIntakeCompileShape::test_welcome_module_authenticates_returning_callers_before_intake
TestLegalProfileIntakeCompileShape::test_sms_consent_gate_skips_only_for_verified_on_file_consent

Markdown source: docs/superpowers/specs/2026-07-07-law-welcome-intake-contract.md.