# CON-ART-002 — The consent artifact must actually show a consent surface

> The attached artifact must depict the point of consent collection, not an unrelated page, logo, or product screen.

- **Rule ID:** CON-ART-002
- **Layer:** Consent flow (`CONSENT_FLOW`)
- **Checks:** `consent artifact`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** AI vision over a consent artifact (screenshot, scan, MMS media)
- **Fix type:** Supply evidence only you hold
- **Required by:** TCR, Twilio, Bandwidth, AWS
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-art-002/

## Why this rule exists

The most common evidence failure is not a missing screenshot but the wrong one — a homepage, a logo, or a dashboard. Reviewers read that as an attempt to satisfy the requirement without meeting it, and it costs more credibility than attaching nothing. Catching it before submission avoids a rejection that is embarrassing as well as expensive.

## How to fix it

Replace the attachment with an image of the actual screen or form where the customer gives consent. Three things must appear together in one frame: the phone-number field, the control they act on (checkbox, toggle, or signature line), and the disclosure text beside it.

## Common mistakes

- A screenshot of the confirmation page after signup shows the outcome, not the consent — capture the form itself.