Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›NFC/QR Core Pipeline·36 in this wave

Approve: NFC/QR Core PipelineTo do · blocker Real scans are never recorded: nothing calls POST /api/events/openBlocked · blocker Verify end-to-end scan path for all 14 destination typesTo do Build the unassigned/orphaned tag landing pageDone Suppress analytics event writes for free-tier accountsDone Unify the four conflicting hash validation patternsDone Assess hash entropy against enumeration and PII scrapingDone Decide and implement Free-tier destination revitalizationDone Rate-limit and cache the public scan resolverTo do Triage the "couldn't connect to the server" preview clusterDone Android NdefUriDecoder accepts any host: anchor it to tactile.to / *.tactile.to or decide custom-domain tagsDone Public scan landing page polishTo do Replace the duplicate web hash-shape copies with one shared import once #658 or #681 landsTo do Android NdefMessageBuilder.build always writes the Text record; spec omits it when the hash is blankDone iOS Program NFC Tag read path rejects 7 and 8 character hashes; spec says accept 7-9Done ndef-format.md is stale: deleted symbols, wrong line cites, duplicate messageIsEmpty, no URI decode tableTo do CI gives no per-suite proof for the NDEF suites: iOS prints totals only, Android's newest main run was a Gradle cache hitTo do Fix tap_count hardcoded to 0 in NFC metadata endpointDone Add hash exhaustion alertingDone Run end-to-end NFC hardware soak testTo do Document NDEF record formatDone Confirm whitelabel.tactile.to DNS + routingDone Add hash-format validation on /t/[hash] scan landingDone Load-test QR/NFC scan resolution at scale (1M+ events)To do Decide: is missing camera QR scanning in iOS/Android intentional?To do Reconcile the three divergent hash generatorsDone Close the check-then-insert race on hash claimingDone Enforce chip compatibility in code, not just docsTo do Handle partially-written and orphaned physical tagsTo do Sign off: NDEF spec and the 111 encoding unit testsDone Free-tier inactivity: R2 media purge job (follow-up to t_9008dc76)To do API: make the visibility gate's fail-closed 404 carry a machine-readable reason, so /d /n /v /a and /t can say "unavailable" for a Supabase failureTo do API: validate the hash shape in the four /content handlers (documents, notes, videos, audio) like destinationsPublic.ts doesTo do Android NfcWriter has no post-write read-back verify (spec 4a step 5)Done NDEF parity corpus: iOS asserts 1 of 5 vectors and no https://www. vector exists; generator and Kotlin disagree on wwwTo do ndef-format.md section 5 contradicts itself on empty + read-only; NFCTagClassifier.classify and diagnose order them oppositelyTo do

Wave

NFC/QR Core Pipeline

The core of the product — encoding tags and resolving scans. Everything else is a surface on top of this.

TacTile › Launch TacTile › NFC/QR Core Pipeline

18/36 done18 open2 open blockers

Selected taskclear

Decide: is missing camera QR scanning in iOS/Android intentional?

To doOwner · met_d884ea32

Unlocks 1Approve: NFC/QR Core Pipeline

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

**Decide: is missing camera QR scanning in iOS/Android intentional?** · to do

Where it sits: TacTile › Launch TacTile › NFC/QR Core Pipeline

## Unlocks 1

- Approve: NFC/QR Core Pipeline

## The brief on file

[2026-10-15 · Viv] DECISION: Is it intentional that iOS and Android have no in-app camera QR scanner (people scan with the phone camera or NFC, which opens the public page at tactile.to/t/<hash>), so v1.0 ships without one?
RECOMMEND: Yes, intentional. Reply "intentional". Checked on origin/main 4f2c1d6b: no AVCaptureMetadataOutput, VNDetectBarcodesRequest or DataScannerViewController anywhere in apps/ios, no ImageAnalysis or ML Kit barcode code in apps/android (QrReadabilityGrader.kt only grades generated codes), and git log -S finds none in all 2,755 commits, so nothing was removed. The design points the same way: the settled NFC-native thesis calls QR the camera-ready, no-app on-ramp (context/positioning/INDEX.md:49-51, context/decisions/2026-05-05-nfc-native-thesis-canonical.md:46-48); both apps are deliberately barred from claiming /t/* so a stranger's scan opens the web page (apps/web/features/handoff/lib/aasa.ts:29-46, apps/android/app/src/main/AndroidManifest.xml:159-175); the Play listing sells QR as reachable with just a camera and no app (apps/android/fastlane/metadata/android/en-US/full_description.txt:29); camera strings cover photos and video only (apps/ios/TacTileConnect/Info.plist:29-30). Web-mobile does have a scanner (apps/web-mobile/features/qr/pages/QRScanPage.tsx), so the asymmetry is real, but in-app scanning is a post-launch nicety for owners scanning their own or a contact's code, not a launch path.
IF YES, NEXT: You reply "intentional". I mark t_d884ea32 done with your answer on it, file a post-launch backlog task "In-app QR scanning, iOS + Android (v1.1)" (owner Viv, outside every launch gate), and hand a coding agent one docs PR from a ~/TacTile-dev/TacTile-* worktree to correct the false premises: PROJECT-STATE.md:577 ("Intentional or a gap"), and the "iOS analog: AVFoundation" rows in docs/adr/0005-web-mobile-port-stack.md:53 and docs/proposals/web-mobile-parity-port.md:186,333 (parity/WEB_PARITY_AUDIT.md:111 already says iOS has no scanner). Your answer clears 1 of the 10 open prerequisites of Approve: NFC/QR Core Pipeline (t_c6f78b73), the gate behind 49 open downstream tasks (27 Kaitlynn's); the other 9 stay open (t_7e9c6dc4, t_e2e7e913, t_1ad501c2, t_05087473, t_2451cca5, t_79023544, t_8081b908, t_f39945a0, t_aa2ffb7a), so nothing downstream moves on this alone.
COST IF YES: $0, no app change, no re-release; one docs PR. The gap you accept: at v1.0 an app user cannot scan a TacTile QR or someone's card from inside the app. They use the phone camera (opens the web page by design) or web-mobile /create/qr/scan, whose QA t_5cbf9bf3 is still todo after two skips with no reason given. Tags already in the field encode https://tactile.to/t/<HASH> and do not depend on it, so adding a scanner later breaks nothing.
COST IF NO: Treat it as a gap and build it for v1.0. $0 spend; the cost is schedule and a new surface that can fail review. My estimate: a few agent-days per platform plus tests (Android already ships the ZXing decoder and CameraX PreviewView, apps/android/app/build.gradle.kts:270-279, so mostly wiring; iOS is new), the iOS camera purpose string reworded (Info.plist:30 says photos and video only), and fresh device QA from Kaitlynn on two platforms, with 54 days to the Tue 8 Dec launch and the iOS and Android release approvals (t_1a740ac2, t_5b14eca1) already stacked behind the same gate.
SAFE TO ASSUME: Until you reply nothing is built or filed and t_d884ea32 stays todo. The scan path under test stays phone camera and NFC to tactile.to/t/<hash> (t_05087473; draft PR #685 drives it), and no copy I found (Play listing, positioning docs) promises an in-app scanner. No flags: not money, legal, irreversible or production.

Matthew — decide whether the lack of camera-based QR scanning in the iOS and Android apps is intentional (tags are meant to be scanned via the OS camera app / native QR reader, not an in-app scanner) or a real gap. Confirmed by code check: neither app has camera-based QR scanning (no AVCaptureMetadataOutput/VNDetectBarcodesRequest in iOS; no BarcodeScanning/CameraX analyzer in Android — Android's QrReadabilityGrader.kt only grades generated QR codes, it doesn't scan them). Done when: a decision is recorded — ship without in-app scanning, or add it to the backlog.

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

NFC/QR Core Pipeline

Decide: is missing camera QR scanning in iOS/Android intentional?