Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

ClearSource›ClearSource live on real, daily U.S. customs data›Observability, Health & Incident Response·6 in this wave

Approve: Observability, Health & Incident ResponseTo do · blocker Reconcile /internal/health: the route exists but LAUNCH.md still says it does notTo do Set INTERNAL_TOKEN and confirm /internal/health is actually gated by itTo do Test-cover the /internal/health page component, not just its data functionsTo do Point an uptime monitor at /api/health and alert on a non-ok body, not the status codeTo do Alert on consecutive daily-pipeline failures, not just one bad dayTo do

Wave

Observability, Health & Incident Response

ClearSource › ClearSource live on real, daily U.S. customs data › Observability, Health & Incident Response

0/6 done6 open1 open blocker

Selected taskclear

Alert on consecutive daily-pipeline failures, not just one bad day

To doOwner · Claraobs-cron-alerting

Unlocks 1Approve: Observability, Health & Incident Response

Show the prompt

You are Clara, the agent for the ClearSource lane of Command.

Open the lane and work there:

```bash
cd ~/Command/clearsource && 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://clearsource.matthewkvamme.com) or ask. Never guess at it.

## The task

**Alert on consecutive daily-pipeline failures, not just one bad day** · to do

Where it sits: ClearSource › ClearSource live on real, daily U.S. customs data › Observability, Health & Incident Response

## Unlocks 1

- Approve: Observability, Health & Incident Response

## The brief on file

Clara — alert on consecutive daily-pipeline failures, not just one bad day. This is in the ClearSource lane (task obs-cron-alerting). When done, write the result back to Command via your hub MCP and mark it todo.

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

Observability, Health & Incident Response

Alert on consecutive daily-pipeline failures, not just one bad day