Skip to main content

​
Morning startup checklist

1

Confirm services are up (API + dashboard)

If you run interactively:
If you run under systemd, confirm:
2

Health check (cron-safe)

What “healthy” typically looks like at the HTTP layer:
Example response:
GET /api/v1/health is intentionally unauthenticated so it can be used by monitors.
3

Verify brain status

You’re looking for:
  • a recent last_cycle_at
  • kill_switch_level: 0
4

Run one cycle (optional but recommended before market open)

5

Review positions

Confirm:
  • what’s open
  • stop loss / take profit (if you use them)
  • any obvious exposure concentration

​
Useful commands (copy/paste)

Health

b1e55ed health --json and GET /api/v1/health

Run the brain

b1e55ed brain --full or POST /api/v1/brain/run

Positions

b1e55ed positions --json or GET /api/v1/positions

​
Monitoring hints

​
1) Watch the event stream (SSE)

The SSE stream is the quickest way to see what the engine is emitting (signals, alerts, etc.).
You’ll receive lines like:

​
2) Use the dashboard

  • Default: http://127.0.0.1:5051
  • Best used for quick visual sanity checks (recent signals, last cycles, producer status)

​
3) Producer health intuition

If a domain looks “silent”, it’s usually because the producer endpoint env var is missing and the producer is emitting no events (often reported as DEGRADED in health metadata).

​
End-of-day checklist

1

Check kill switch status

If it’s non-zero, investigate before letting automation continue.
2

Export (optional)

3

Log review (systemd)