Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Hardware & fulfillment·15 in this wave

Approve: Hardware & fulfillmentTo do · blocker Decide how customers buy hardware at launchTo do Select hardware supplier(s) and confirm pricing at real order volumesTo do Place the initial hardware inventory orderTo do Spec the tag programming pipeline: process, throughput, staffingTo do Set up shipping: carrier, rates, zones, trackingTo do Research sales tax nexus for physical hardware salesTo do Secure product liability insuranceTo do Sanity-check fulfillment throughput against the launch forecastTo do Verify real hardware unit economics against the 80-85% margin claimTo do Verification sign-off: order, program, ship, and scan one real unit end to endTo do Design and source hardware packagingTo do Write returns and DOA replacement policy for hardwareTo do Set up inventory tracking for hardware stockTo do feature/hardware-data-model: 66 files unlanded, no PR, never gatedTo do

Wave

Hardware & fulfillment

Thesis pillar 2 — connected physical distribution. TacTile manufactures, pre-programs and ships branded NFC and QR hardware at 80–85% margin. Had no workstream at all despite being a core pillar. Note: the in-app Shop is explicitly NOT a launch feature, so the buying path needs deciding.

TacTile › Launch TacTile › Hardware & fulfillment

0/15 done15 open1 open blocker

Selected taskclear

feature/hardware-data-model: 66 files unlanded, no PR, never gated

To doOwner · ait_a65f3797

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

**feature/hardware-data-model: 66 files unlanded, no PR, never gated** · to do

Where it sits: TacTile › Launch TacTile › Hardware & fulfillment

## The brief on file

`origin/feature/hardware-data-model` carries one commit — 8cbb2e42 "feat: hardware-ready data model — structural, launch path untouched" — that is NOT on main and has no open PR. `git cherry origin/main origin/feature/hardware-data-model` marks it `+`.

CORRECTED SCOPE (an earlier version of this task said "66 files" — that was wrong, it counted files differing in one direction rather than unique content). The real figure, measured at b09acbeb:

    git diff origin/main...origin/feature/hardware-data-model --stat
    → 7 files changed, 1107 insertions(+), 21 deletions(-)

and one of those seven is what makes this non-trivial:

    supabase/migrations/202607291500_hardware_ready_data_model.sql   (225 lines)
    tests/unit/chip-family-catalog.test.ts                           (315 lines)

Same shape as t_eab1e47b — work parked on a branch the verify chain has never run against — except this one has not merged yet, so it is still catchable.

Do, in order:
 1. Read the migration first, not the diff summary. It lands against a database with `pitr_enabled:false` and ZERO stored backups, so any destructive DDL in it is unrecoverable. The commit message claims "launch path untouched"; verify that against the migration rather than trusting it.
 2. Decide whether this belongs in v1.0 at all. It is hardware/fulfillment groundwork, and the in-app Shop is explicitly not a launch feature.
 3. If wanted: rebase on main, open a PR, and let `bash scripts/verify/gate.sh` run locally — note that GitHub Actions is currently walled by billing, so CI proves nothing right now and the local gate is the only real gate.
 4. If not wanted for v1.0: say so explicitly and delete the branch so it stops reading as pending work.

The other four feature branches (android, backend-api, ios, web) were verified content-identical to main on their owned paths as of b09acbeb — feature/web's one commit has a patch-id identical to main's a9962929 (PR #279), and its canvas tree is byte-identical to main's own pre-#280 tree. That check is done, do not redo it. All four are safe to delete.

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

Hardware & fulfillment

feature/hardware-data-model: 66 files unlanded, no PR, never gated