Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Foundations›Database & Supabase·12 in this wave

Verify point-in-time recovery is enabledTo do · blocker Review anon-executable SECURITY DEFINER functionsDone · blocker Approve: Database & SupabaseTo do · blocker MATTHEW: profiles.visibility is nullable with no default, so any profile created without it reads as publicBlocked · blocker Fix v_account_tier security-definer viewTo do Fix allow-all RLS policy on checklists tableTo do URGENT: 202608081500_guard_analytics_rpc_callers.sql is merged to main and NOT applied to productionTo do Hardware-ready data modelDone Document Supabase backup policyTo do Document RLS test planTo do Soft-deleted public destinations stay readableTo do Confirm scan-event logging is rate-limited per destinationDone

Wave

Database & Supabase

Schema is already built (81 tables, 114 migrations, RLS on every table). This wave is the readiness pass plus three real gaps a live audit surfaced.

TacTile › Launch TacTile › Foundations › Database & Supabase

3/12 done9 open3 open blockers

Selected taskclear

Hardware-ready data model

DoneOwner · Vivt_1dfac020

Keep schema + service interfaces extensible for v1.1 hardware.

Unlocks 1Approve: Database & Supabase

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

**Hardware-ready data model** · done

Keep schema + service interfaces extensible for v1.1 hardware.

Where it sits: TacTile › Launch TacTile › Foundations › Database & Supabase

## Unlocks 1

- Approve: Database & Supabase

## The brief on file

CLOSED as a duplicate 2026-08-08. The live row is **`t_a65f3797`** — "feature/hardware-data-model: unlanded, no PR, never gated" — in the branch-hygiene wave. Work it there.

Measured scope, so it is recorded in one place: `origin/feature/hardware-data-model` carries ONE commit (`8cbb2e42`) that is not on main and has no PR. `git diff origin/main...origin/feature/hardware-data-model --stat` → **7 files, 1107 insertions, 21 deletions**, including `supabase/migrations/202607291500_hardware_ready_data_model.sql` (225 lines) and `tests/unit/chip-family-catalog.test.ts` (315 lines).

Read the migration before the diff summary — it lands against a database with `pitr_enabled:false` and zero stored backups.

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

Database & Supabase

Hardware-ready data model