Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Contacts & Leads·15 in this wave

Approve: Contacts & LeadsTo do · blocker Decide whether a contacts/leads inbox ships in v1.0To do Decide what to do with form_submissions as lead capture (surface, export, retention)To do Decide whether destination sharing / collaborator permissions ship in v1.0To do Build /leads or /contacts inbox UITo do GDPR consent on lead captureTo do Reconcile investor deck's "Contact — SHIPPED" claim with realityTo do Add menu to destination_type ENUM before Square integration shipsDone Architect destination type as a registry / plug-in pattern (not per-type hardcoded routes)To do Audit lead-capture data flow end-to-endDone Add CSV export on leadsTo do Email notification on new leadTo do Confirm public scan landing renders contact card correctlyTo do Lead-data schema for retention policyTo do Verify Android DestinationEditorScreen renders all 7 destination typesDone

Wave

Contacts & Leads

Where scans become leads. Verify what exists before building — prior audits found no standalone contacts feature on any surface, only the ConnectCard destination type and form submissions.

TacTile › Launch TacTile › Contacts & Leads

3/15 done12 open1 open blocker

Selected taskclear

Lead-data schema for retention policy

To doOwner · Vivt_17f02f5b

Unlocks 1Approve: Contacts & Leads

Show the prompt

You are Viv, the agent for the TacTile lane of Command.

Open the lane and work there:

```bash
cd ~/Command/tactile && claude
```

Read that lane's CLAUDE.md and lane.json before you touch anything — they
carry your identity, your scope, and the hazards specific to this lane.
Read state from the hub (https://internal.tactile.to) or ask. Never guess at it.

## The task

**Lead-data schema for retention policy** · to do

Where it sits: TacTile › Launch TacTile › Contacts & Leads

## Unlocks 1

- Approve: Contacts & Leads

## The brief on file

Viv — define a lead-data schema/retention policy for form_submissions and any future leads inbox. Done when: retention rules are documented and enforced (e.g. a scheduled cleanup or documented manual process). File: supabase/migrations/ (retention policy migration or doc).

## How to work this

- Do the work, don't just plan it. If the fix is obvious and safe, make it.
- Surface anything needing Matthew's sign-off instead of deciding it yourself.
- Short replies. Lead with the answer, then stop.
- Finish by saying what changed, what you verified, and what you'd do next.

To doIn progressDoneBlockedPick a wave on the left · tap a task to expand it

Lanes

Contacts & Leads

Lead-data schema for retention policy