sms-10dlc-registrationlisted

# SMS 10DLC Registration Use this skill for US A2P SMS over 10-digit long codes. Separate the compliance evidence packet from the exact Sent API request; they have different schemas and validators. ## Current Sent resource model There is no standalone brand CRUD path in the current v3 API. - Create a dedicated brand inside `POST /v3/profiles` using `brand` and `inherit_tcr_brand: false`. - List/create campaigns with `GET|POST /v3/profiles/{profileId}/campaigns`. - Update/delete with `PUT|DELETE /v3/profiles/{profileId}/campaigns/{campaignId}`. Reject guidance that reintroduces a free-standing brand path. ## Choose inheritance deliberately | Brand | Campaign | Settings | | --- | --- | --- | | Inherit both | Organization brand and campaign | `inherit_tcr_brand: true`, `inherit_tcr_campaign: true` | | Inherit brand, own campaign | Shared legal brand with tenant-specific traffic | brand true, campaign false | | Own both | Dedicated tenant/business | both false and supply `brand` during profile creation | Inherited campaigns are read-only. A profile cannot supply `brand` while brand inheritance is true. ## Two validation layers ### Evidence readiness packet The private packet uses the explicit internal version `sent-10dlc-evidence/v1` and snake_case evidence fields. It is not an API payload. ```bash python scripts/validate_10dlc_packet.py evidence.json ``` Collect legal identity, public website/policy links, consent proof, message flow, opt-in/opt-out/help responses a