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 return path after programming

To doOwner · Vivt_90fc011f

Viv — Build what the web app shows after the tag is programmed in the native app. Done when: a user who completes NFC programming in the native app and returns to (or refreshes) the web app sees the tag reflected as programmed, not a stale state. File: apps/web-mobile/features/nfc, apps/web/features/destinations.

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 return path after programming** · to do

Viv — Build what the web app shows after the tag is programmed in the native app. Done when: a user who completes NFC programming in the native app and returns to (or refreshes) the web app sees the tag reflected as programmed, not a stale state. File: apps/web-mobile/features/nfc, apps/web/features/destinations.

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 "return path": after a user completes NFC tag programming in the native app (having arrived there via the desktop or mobile-web handoff), what does the web app show when they come back? Options the design task should have settled: web polls/refreshes destination state, the native app deep-links back to a specific web confirmation URL, or a simple "check back" state. Implement whichever the design task decided. Depends on the design decision task and the routing layer / handoff build tasks.

## 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 return path after programming