# Auditor response — 2026-04-25 — watcher started

## Status

Watcher is running and writing cleanly.

| Detail | Value |
|---|---|
| PID | 3170546 |
| Process | `node src/index.mjs` (running as user `arb`) |
| Start time | 2026-04-25 08:50:10 UTC (= 18:50 Melbourne) |
| Output file | `/srv/projects/arb/tools/spread-watcher/data/watcher-2026-04-25.jsonl` |
| Stdout/stderr | `/tmp/spread-watcher.log` |
| Verified | 200 new rows in first 25 seconds (~8 rows/sec = 4 venues × 2 symbols at 1 Hz, as expected) |
| Last quote sample | OKX BTC bid 77615.0 / ask 77615.1, ETH bid 2319.31 / ask 2319.32 |

## Recommended next checkpoints

| Hours from now | Window covered | Quality of signal |
|---|---|---|
| +4h (~22:50 Melb / 12:50 UTC) | 1 US-evening session window | Minimum useful |
| +6h (~00:50 Melb+1 / 14:50 UTC) | US evening + Asia morning | Good |
| +8h (~02:50 Melb+1 / 16:50 UTC) | US evening + Asia morning + late Asia | Best |

Auditor recommends ≥6 hours.

## How to check it's still alive

```bash
ps -p 3170546 -o pid,stat,etime,cmd
sudo -n wc -l /srv/projects/arb/tools/spread-watcher/data/watcher-2026-04-25.jsonl
```

Expected JSONL line count after N hours: ~N × 28,800 rows (4 venues × 2 symbols × 3,600 sec).

## When operator pings to analyze

Auditor will:
1. Stop the watcher cleanly (`kill -TERM 3170546`)
2. Run `npm run analyze` over the captured window
3. Re-run with `--basis-rate 0.999` and `--basis-rate 1.001` to test robustness against USDT/USD basis assumption
4. Deliver the simple-English call on the three questions:
   - Is there real opportunity?
   - Which exchanges look promising?
   - Continue, expand, or pivot?