Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›MCP surface·41 in this wave

Approve: MCP surfaceTo do · blocker 13 production secrets overdue for rotation — the gate cannot be green until this is resolvedTo do · blocker Deploy step 2 — verify/rotate production MCP Worker secretsTo do Deploy step 4 — fix the stale "NOT DEPLOYED" banner and deploy docsDone Add action.* and bluetooth.* op groups to the MCP catalogDone Build real handlers for group.* (9 ops)Done Build real handlers for family.* (7 ops)Done Build settings.* MCP tools including custom domain managementTo do Verify/build the Connected Apps management UI for MCP OAuth clientsTo do Add rate limiting, quota, and cost controls to the hosted MCP serverDone Honesty check — reconcile investor deck MCP claims against what shipsTo do Verify "everything a human can do, an agent can do over MCP" end to endTo do staging-api is a day behind main — and writes to the production SupabaseTo do MCP GAP INVENTORY — every unwired op, with the decision attached to eachDone Demo account for screenshots + QA — seeder is live, shape is frozenTo do Build the full medialink.* MCP tool set (3 ops)To do Build the payment.* connector MCP tool set (3 ops)To do Build the full webhook.* MCP tool set (4 ops)Done Build zap.* MCP tools or explicitly cut Zapier from v1.0 MCP scopeTo do Build link.schedule.repoint, link.compound, wizard.suggest or cut themTo do Deploy step 1 — verify DB migration + RLS on OAuth tablesTo do Deploy step 3 — confirm CF route/DNS for mcp.tactile.to is production-gradeTo do Deploy step 5 — formalize the MCP smoke testTo do Build nfc.lock and nfc.unlock MCP toolsTo do Build contact.vcard.export and contact.delete MCP toolsTo do Build linkhub.create and linkhub.delete MCP toolsDone Build videoaudio.create and videoaudio.replace MCP toolsTo do Build document.create and document.replace MCP toolsTo do Build the full social.* MCP tool set (6 ops)To do Build the full paylink.* MCP tool set (4 ops)Done Build wifi.edit MCP toolTo do Build the full form.* MCP tool set (7 ops)Done Build the analytics automation layer MCP tools (6 ops)To do Wire inbox.list and inbox.mcp_approval to real handlersDone Add architecture test guarding against a second tool-handler implementationTo do Publish a public MCP tool manifest / discovery docsTo do Webhook signing secret: add the one surface that can reveal itDone A Website destination's URL cannot be edited through the agent surface at allDone SPEC → backend: webhook secret reveal/rotate endpoints + secret_fingerprint on the listDone NEEDS MATTHEW: decide whether resolve_trigger_destination keeps anon EXECUTEBlocked 5 proposal-only MCP ops are advertised with no task row building themTo do

Wave

MCP surface

Thesis pillar 3 — "Agentic AI + MCP." The investor deck claims first-in-category MCP-native. Audit (2026-07-26) found the hosted server IS live at mcp.tactile.to with real OAuth production traffic (14 clients, 11 tokens) — but the code's own deploy banner still says "NOT DEPLOYED" (stale), and tool coverage is genuinely incomplete: roughly half the 147-op catalog are proposer stubs that never mutate state, and 2 of 14 destination types (Action, Bluetooth) have zero MCP presence at all. Not cuttable: this is a stated structural moat.

TacTile › Launch TacTile › MCP surface

14/41 done27 open2 open blockers

Selected taskclear

NEEDS MATTHEW: decide whether resolve_trigger_destination keeps anon EXECUTE

BlockedOwner · met_41d9835b

Split out of t_449fbef0 in round 14. It is the one anon-executable SECURITY DEFINER function whose call sites could not be settled by grep, and revoking it wrongly breaks the core scan flow against a zero-backup database.

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

**NEEDS MATTHEW: decide whether resolve_trigger_destination keeps anon EXECUTE** · blocked

Split out of t_449fbef0 in round 14. It is the one anon-executable SECURITY DEFINER function whose call sites could not be settled by grep, and revoking it wrongly breaks the core scan flow against a zero-backup database.

Where it sits: TacTile › Launch TacTile › MCP surface

## The brief on file

DECISION NEEDED FROM MATTHEW — do not revoke this unilaterally.

public.resolve_trigger_destination(p_tile_hash text) is SECURITY DEFINER and
carries EXECUTE for PUBLIC, anon and authenticated. It was deliberately LEFT OUT
of supabase/migrations/202608091400_revoke_public_scan_path_fns.sql (round 14,
PR #312) because the evidence points both ways and a grep cannot settle it.

FOR IT BEING LIVE ON THE ANONYMOUS SCAN PATH:
  - scripts/verify/db-grants-allow.json: "The public scan path resolves a
    scanned trigger code to its destination URL before authentication exists"
  - docs/runbooks/rls-policy-tests.md lists it in ANON_CALLABLE_SECDEF
  - supabase/docs/db/INTEGRITY-CHECKS.md:188 carries a LIVE
    rpc/resolve_trigger_destination probe recorded as returning 200

FOR IT BEING DEAD:
  - a repo-wide grep finds NO TypeScript, Swift or Kotlin caller
  - supabase/docs/db-audit-2026-04-21.md:356 calls it "DORMANT — zero callers"

The caller may be a native client or a dynamically-built RPC name, which is why
the grep is not conclusive in either direction.

MITIGATING FACTS: the body is narrow — it returns only (action_hash,
action_visibility) and already filters d.deleted_at IS NULL — and it does carry
SET search_path. So the exposure is enumeration of trigger→destination mappings,
not arbitrary owner-privileged SQL.

TO DECIDE IT PROPERLY, ONE OF:
  a) check Cloudflare/PostgREST logs for real rpc/resolve_trigger_destination
     traffic from the anon key over a representative window, or
  b) revoke it in staging and run the scan flow end to end.

The annotation recording all of this lives in-source at
supabase/migrations/20260503a_fix_post_rename_rpc_bodies.sql, above the CREATE,
as `-- allow-public-execute: ESCALATED TO MATTHEW, NOT ACCEPTED`. It is what
keeps scripts/verify/migration-grants.mjs check D green; deleting the annotation
without deciding turns the gate red, which is intended.

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

MCP surface

NEEDS MATTHEW: decide whether resolve_trigger_destination keeps anon EXECUTE