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

ndef-format.md section 5 contradicts itself on empty + read-only; NFCTagClassifier.classify and diagnose order them oppositely

To doOwner · Vivt_4ee6054d

The spec diagram checks empty before lock, the spec prose says lock before empty; the scan path ships the first, the encoder-flow path the second.

No dependencies in this wave — nothing gates it, and nothing waits on it.

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

**ndef-format.md section 5 contradicts itself on empty + read-only; NFCTagClassifier.classify and diagnose order them oppositely** · to do

The spec diagram checks empty before lock, the spec prose says lock before empty; the scan path ships the first, the encoder-flow path the second.

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

## The brief on file

[2026-10-15 · Viv] Where the audit doc is: docs/audit/2026-10-ndef-signoff.md exists only on draft PR #759 (branch r31/tooling-docs-ship, https://github.com/TacTile-dev/TacTile/pull/759) until Matthew merges it. Any "r31/tooling-docs draft PR" pointer in this task means #759.

[2026-10-15 · Viv] Found by the NDEF sign-off (t_92603a30), audit doc docs/audit/2026-10-ndef-signoff.md section 3 row D6. Line cites are origin/main 4f2c1d6b.

PROBLEM: docs/nfc/ndef-format.md section 5. The "Canonical classification order" diagram is: 1 notSupported -> error, 2 messageIsEmpty -> empty, 3 locked, 4 TacTile URL, 5 static. The closing paragraph says the flow VM's "empty-before-readOnly check (an empty + read-only tag showing .empty instead of a locked error) is the same class of bug ... status/lock checks must run before content-shape checks". Both cannot be canonical. The code ships both: NFCTagClassifier.classify (apps/ios/TacTileConnect/Features/NFC/Models/NFCTagClassifier.swift:106-125) follows the diagram, so an empty read-only tag is bucket .empty (pinned by test_classify_emptyReadOnly_bucketIsEmpty_perSpecOrder, NFCTagClassifierTests.swift:204). diagnose (:137-160) follows the prose: lock first, so the same tag is .locked (pinned by test_diagnose_emptyReadOnly_isLocked_notEmpty, :345).

IMPACT (partly unverified): classify is the scan/router path and NFCScanRouter.route sends bucket .empty to handleEmpty, which returns .empty (NFCScanRouter.swift:101, :129-131). Whether the UI then offers programming for a tag that can never be written was NOT traced; the writer itself refuses a read-only tag with "This tag is read-only and cannot be reprogrammed." (NFCEncoderWriter.swift:589-596), so the outcome is a late failure, not a bad write.

DONE WHEN: one order is chosen and written into section 5 (recommend lock-before-empty: it is the one the spec's own bug narrative argues for), classify and diagnose agree, and the pinning tests are updated together. Trace what the .empty routing result does in the UI before changing it.

NOTE: spec edit waits for #658 and #687.

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

ndef-format.md section 5 contradicts itself on empty + read-only; NFCTagClassifier.classify and diagnose order them oppositely