Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Foundations›Database & Supabase·15 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 The RLS fixture expires 2026-09-30 and freezes main — only Matthew can refresh it (Touch ID)Done · blocker Fix v_account_tier security-definer viewDone Fix allow-all RLS policy on checklists tableDone URGENT: 202608081500_guard_analytics_rpc_callers.sql is merged to main and NOT applied to productionDone db_url and db_password now EXIST in 1Password — verify:rls-snapshot can run for the first timeTo do RLS snapshot fixture turns pnpm verify red for every branch on 5 Nov (30-day age limit)To do Hardware-ready data modelDone Document Supabase backup policyBlocked Document RLS test planDone Soft-deleted public destinations stay readableDone 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

9/15 done6 open3 open blockers

Selected taskclear

Confirm scan-event logging is rate-limited per destination

DoneOwner · Vivt_e9582c3e

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

**Confirm scan-event logging is rate-limited per destination** · done

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

## The brief on file

CLOSED AS VERIFIED 2026-08-09 (round 14). Scan-event logging IS rate-limited
per destination — the premise that it is unmetered was wrong.

EVIDENCE (read from the tree, not inferred):
  - apps/api/tactile-api/src/routes/events.ts:153 and :464 both call
    applyBeaconLimit
  - apps/api/tactile-api/src/middleware/public-resolver-guard.ts:326 charges a
    per-IP bucket (BEACON_IP_MINUTE = 120, BEACON_IP_HOUR = 2000, declared at
    :321-322) PLUS a per-destination-hash bucket

THE ONE UNMETERED PATH WAS NOT THIS ONE, and is now tracked elsewhere: calling
public.log_analytics_event directly over PostgREST with the public anon key
skips the Worker — and therefore applyBeaconLimit — entirely. That is a real
limiter bypass and its revoke is written (unapplied) in
supabase/migrations/202608091400_revoke_public_scan_path_fns.sql, tracked on
t_449fbef0. The two are deliberately NOT tracked as one thing.

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

Confirm scan-event logging is rate-limited per destination