Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Web›Web → app handoff·12 in this wave

Approve: Web → app handoffTo do · blocker Register the deep-link scheme on iOSTo do Set up iOS Universal Links for the handoff pathsTo do Set up Android App Links for the handoff pathsTo do Build the deep-link routing layerTo do Design the handoff experienceTo do Build the desktop handoffTo do Build the mobile-web handoffTo do Handle the not-installed case gracefullyTo do Build the return path after programmingTo do Make the capability boundary honest in the web UITo do Verify the handoff end to endTo do

Wave

Web → app handoff

Web can't write NFC tags, so programming a physical tag has to hand off cleanly to the native app. Deep-link infrastructure may not exist at all — verify before building on it.

TacTile › Launch TacTile › Web › Web → app handoff

0/12 done12 open1 open blocker

Selected taskclear

Build the desktop handoff

To doOwner · Vivt_7d487377

Viv — Build a scannable code or link on desktop web that opens the app on the user's phone with the right destination pre-loaded. Done when: scanning the code on a phone with the app installed opens TacTile Connect directly to the pre-loaded destination. File: apps/web (desktop app), new handoff component.

Waiting on 2 · 2 still openDesign the handoff experience Build the deep-link routing layer

Unlocks 1Approve: Web → app handoff

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

**Build the desktop handoff** · to do

Viv — Build a scannable code or link on desktop web that opens the app on the user's phone with the right destination pre-loaded. Done when: scanning the code on a phone with the app installed opens TacTile Connect directly to the pre-loaded destination. File: apps/web (desktop app), new handoff component.

Where it sits: TacTile › Launch TacTile › Web › Web → app handoff

## Waiting on 2

- Design the handoff experience — to do
- Build the deep-link routing layer — to do

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

## Unlocks 1

- Approve: Web → app handoff

## The brief on file

Per the handoff-experience design decision, build the desktop-side handoff: a QR code (or shareable link) shown on the desktop web app (apps/web) that, when scanned by the user's phone, opens the native app via the new Universal Links / App Links + routing layer, landing directly on the destination the desktop user was trying to program. This depends on the design task's decision plus the deep-link routing layer task being done first. No existing desktop-side handoff UI exists today — apps/web has NFC-forward marketing copy (features/destinations/pages/DashboardPage.tsx) but no working handoff mechanism.

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

Web → app handoff

Build the desktop handoff