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

Verify end-to-end scan path for all 14 destination types

To doOwner · Vivt_05087473

Waiting on 3 · all clearFix tap_count hardcoded to 0 in NFC metadata endpoint Add hash-format validation on /t/[hash] scan landing Build the unassigned/orphaned tag landing page

Unlocks 2Approve: NFC/QR Core Pipeline Load-test QR/NFC scan resolution at scale (1M+ events)

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

**Verify end-to-end scan path for all 14 destination types** · to do

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

## Waiting on 3

- Fix tap_count hardcoded to 0 in NFC metadata endpoint — done
- Add hash-format validation on /t/[hash] scan landing — done
- Build the unassigned/orphaned tag landing page — done

## Unlocks 2

- Approve: NFC/QR Core Pipeline
- Load-test QR/NFC scan resolution at scale (1M+ events)

## The brief on file

[2 Oct 2026 overnight — Viv: draft PR #685 https://github.com/TacTile-dev/TacTile/pull/685 — web: drives the /t/[hash] scan path for all 14 destination types (static slice); not merged, not deployed]

CORRECTION (Viv, 2026-10-02): the premise in the original brief below is STALE, not wrong when written. The audit that said route.ts handles only 4 types was true on 2026-07-26; b184285f (2026-07-28) then wired the other 9 into /t/[hash], and on main `GET` in apps/web/app/t/[hash]/route.ts dispatches all 14. Do not hunt for missing branches. What is left is proof and the device half. The static proof (the real GET driven for all 14 types, static tags and dynamic/trigger tags, plus gates that the endpoints exist on the real API Worker) is in draft PR #685, tests/unit/scan-path-all-destination-types.test.ts. STILL OPEN and needs a person with a device: encode and tap/scan one real tag of each type and log any that render wrong as bugs.

ORIGINAL BRIEF (2026-07-26): Viv — verify the full encode-to-scan path for all 14 destination types: encode a tag of each type, scan it, confirm the correct content renders. Done when: every destination type is tap/scan-tested and any that don't render correctly are logged as bugs. This is the single most important customer path in the product — a prior web audit found apps/web/app/t/[hash]/route.ts only explicitly handles 4 types (action, document, notes, menu) plus a contact-card fallback, i.e. 5 of 14. File: apps/web/app/t/[hash]/route.ts. NOTE: depends on the individual per-type render tasks rather than the Web viewer's approval gate — the original wiring created a dependency cycle between the core pipeline and a surface built on top of it.

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

Verify end-to-end scan path for all 14 destination types