Skip to main content
Heartbeat is the per-thesis monitor loop. It controls how often SimpleFunctions scans news and social context for a thesis, which model tier evaluates new evidence, the monthly cost ceiling, and whether the monitor is allowed to create closed-loop entry or exit intents. Heartbeat work is independent of thesis lifecycle status. A thesis can be active while its heartbeat is paused, and pausing the heartbeat never archives or closes the thesis.

CLI

API

Auth: Authorization: Bearer sf_live_... (or browser session). 404 if the thesis isn’t owned by the caller.

GET response

PATCH body

All fields optional. Any combination is accepted; unknown fields are ignored. 400 No valid fields to update if nothing recognised is sent.

PATCH response

Errors

Curl

What heartbeat is not

  • Not an order router. It can write evaluations, signals, alerts, and (when closedLoop is enabled) execution intents. Orders still go through the intent / runtime / risk-gate path.
  • Not the same as thesis lifecycle status. To archive, close, or publish a thesis, use the Thesis API. To stop background evaluation only, set paused: true here.
  • Not a global setting. Each thesis has its own heartbeat config, and the dashboard / CLI lets you tune them independently.

Next steps

Thesis API

Full thesis lifecycle HTTP surface.

Portfolio autopilot

Separate portfolio-tick loop and risk gates.