Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Backend & Infrastructure›Supabase Edge Functions·4 in this wave

Approve: Supabase Edge FunctionsTo do · blocker Document edge function invocation cadenceTo do Add CF API retry with exponential backoffTo do Pipe edge function logs to centralized destinationTo do

Wave

Supabase Edge Functions

Edge function reliability + observability. Depends on Database.

TacTile › Launch TacTile › Backend & Infrastructure › Supabase Edge Functions

0/4 done4 open1 open blocker

Selected taskclear

Document edge function invocation cadence

To doOwner · Vivt_f9781c8b

Unlocks 1Approve: Supabase Edge Functions

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

**Document edge function invocation cadence** · to do

Where it sits: TacTile › Launch TacTile › Backend &amp; Infrastructure › Supabase Edge Functions

## Unlocks 1

- Approve: Supabase Edge Functions

## The brief on file

Viv — write down when each edge function runs and what it costs. Done when: one doc states the schedule for custom-domain-cleanup and domain-health-check, what each does per invocation, how many Cloudflare API calls each makes, and the expected invocation volume at launch. WHY THIS IS WORTH DOING RATHER THAN SKIPPING: these are the only scheduled jobs touching customer-facing infrastructure, and nobody currently knows their cadence without reading the config — which means nobody can reason about whether a Cloudflare rate-limit problem is caused by them. It also feeds the launch cost picture, since invocation count times API calls is a real line item. Files: supabase/functions/*/ plus their cron configuration

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

Supabase Edge Functions

Document edge function invocation cadence