Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Launch & operations·20 in this wave

GO / NO-GO decisionTo do · blocker TacTile v1.0 LAUNCHEDTo do · blocker Remove the Ben Ari simulator auto-loginTo do Strip the iOS device-trust bypass emailTo do Run the cut-list checkpointTo do Verify the full end-to-end customer journeyTo do Freeze the release candidateTo do Write the launch-day runbookTo do Plan the rolloutTo do Audit both apps for purchase links and upgrade CTAsTo do Plan for store rejectionTo do Verify Stripe is production-ready, not test-modeTo do Confirm the legal documents are actually published and linkedTo do Build kill switches for the agent and other risky featuresTo do Rehearse the rollback before launch dayTo do Take a pre-launch backup and confirm the restore pathTo do Verify the production domain map and DNS before cutoverTo do Set up launch-day monitoring watchTo do Prepare customer support for launchTo do Post-launch watch windowTo do

Wave

Launch & operations

Where everything converges. Pre-release hardening, the cut-list checkpoint, store submissions, and the go/no-go call.

TacTile › Launch TacTile › Launch & operations

0/20 done20 open2 open blockers

Selected taskclear

Confirm the legal documents are actually published and linked

To doOwner · Caitlint_9d430e3f

Unlocks 1GO / NO-GO decision

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 the legal documents are actually published and linked** · to do

Where it sits: TacTile › Launch TacTile › Launch & operations

## Unlocks 1

- GO / NO-GO decision

## The brief on file

Caitlin — verify every legal document is live and reachable at launch, not just written. Done when: Terms, Privacy Policy, Cookie Policy, Acceptable Use Policy, DMCA policy, refund policy and the sub-processor list are all published at real URLs, linked from the apps and the marketing site, and the App Store and Play listings point at the live Privacy URL. WHY THIS IS SEPARATE FROM DRAFTING: the Legal wave produces the documents; nothing currently verifies they got published. And there is a live hazard today — apps/web's Privacy and Terms pages are placeholder text, publicly reachable with no auth, so the failure mode is not a missing page but a wrong one that looks official. Also confirm the compliance mailboxes (privacy@, dpo@, legal@, abuse@) actually receive mail, since those addresses are named inside the documents.

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

Launch & operations

Confirm the legal documents are actually published and linked