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

Make the capability boundary honest in the web UI

To doOwner · Vivt_6e7ebedd

Viv — Make sure web plainly states what it can and can't do (NFC write) everywhere a user might expect to create a physical tag, not just in web-mobile. Done when: apps/web's destination-creation surfaces match the honesty standard already met by web-mobile's NfcExplainerSection, with a link into the new handoff instead of silence. File: apps/web/features/destinations/pages/DashboardPage.tsx, apps/web-mobile/features/nfc/components/NfcExplainerSection.tsx (reference standard).

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

**Make the capability boundary honest in the web UI** · to do

Viv — Make sure web plainly states what it can and can't do (NFC write) everywhere a user might expect to create a physical tag, not just in web-mobile. Done when: apps/web's destination-creation surfaces match the honesty standard already met by web-mobile's NfcExplainerSection, with a link into the new handoff instead of silence. File: apps/web/features/destinations/pages/DashboardPage.tsx, apps/web-mobile/features/nfc/components/NfcExplainerSection.tsx (reference standard).

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

## Unlocks 1

- Approve: Web → app handoff

## The brief on file

Audit finding: apps/web-mobile already does this well — features/nfc/components/NfcExplainerSection.tsx explicitly says "Browsers can't write to NFC chips. The TacTile iOS and Android app handles the full programming flow," and apps/web-mobile/AGENTS.md hard-codes "NFC programming is OUT OF SCOPE for this app" as a governing rule (not just an intention — it's built and enforced, confirmed no NDEFReader/NDEFWriter usage anywhere except the read-only WebNfcScanner.tsx which is explicitly read-only per that file's own doc comment). The gap is on the OTHER web app: apps/web (the desktop app) has NFC-forward marketing copy ("NFC-native orchestration platform") and a dashboard quick action literally labeled "Create NFC destination" (features/destinations/pages/DashboardPage.tsx) with no wired handler and no explanation of what happens when you click it or what the capability boundary is. A desktop user following that CTA has nothing telling them programming needs the app. Bring apps/web up to the same honesty standard as web-mobile's NfcExplainerSection, and link it into the new handoff (task 6, desktop QR handoff) once built.

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

Make the capability boundary honest in the web UI