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

Approve: Contacts & Leads

To doOwner · met_4c3ecdf0Blocker

Waiting on 14 · 11 still openAudit lead-capture data flow end-to-end Decide whether a contacts/leads inbox ships in v1.0 Decide what to do with form_submissions as lead capture (surface, export, retention)Decide whether destination sharing / collaborator permissions ship in v1.0 Build /leads or /contacts inbox UI Add CSV export on leads Email notification on new lead Confirm public scan landing renders contact card correctly Lead-data schema for retention policy GDPR consent on lead capture Add menu to destination_type ENUM before Square integration ships Verify Android DestinationEditorScreen renders all 7 destination types Architect destination type as a registry / plug-in pattern (not per-type hardcoded routes)Reconcile investor deck's "Contact — SHIPPED" claim with reality

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

**Approve: Contacts & Leads** · to do · blocker

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

## Waiting on 14

- Audit lead-capture data flow end-to-end — done
- Decide whether a contacts/leads inbox ships in v1.0 — to 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.0 — to do
- Build /leads or /contacts inbox UI — to do
- Add CSV export on leads — to do
- Email notification on new lead — to do
- Confirm public scan landing renders contact card correctly — to do
- Lead-data schema for retention policy — to do
- GDPR consent on lead capture — to do
- Add menu to destination_type ENUM before Square integration ships — done
- Verify Android DestinationEditorScreen renders all 7 destination types — done
- Architect destination type as a registry / plug-in pattern (not per-type hardcoded routes) — to do
- Reconcile investor deck's "Contact — SHIPPED" claim with reality — to do

11 of those are still open. If one genuinely blocks this, say so and stop rather than working around it.

## The brief on file

me — review the finished Contacts & Leads package (or the recorded v1.0 scope decision if the inbox is cut) before sign-off.

## 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

Approve: Contacts & Leads