/ Build · Heartbeat

Heartbeat — what’s pulsing

Live cron jobs, edge functions, and n8n flows running across both sides. No human intervention required — this is the autonomic nervous system.


BC-operated (Ops VPS + Hub)

Joe-operated (Made infra)


How the wiring works

Layer 1

Edge Functions

Supabase Edge Functions (Deno) handle the triggers: webhook receivers, on-demand agent endpoints, and pollers. Wave 4 added 9 ingest pollers (preprints, SEC, NIH, SBIR, trials, patents) running on pg_cron schedules.

Layer 2

Cron Schedulers

pg_cron jobs inside Supabase invoke EFs via net.http_post with vault-stored auth. Joe's Mac mini runs launchd jobs for non-Supabase work. Made VPS Docker runs persistent agents (Made-Ralph nightly 07:00 UTC).

Layer 3

n8n Flows

Self-hosted n8n on Made VPS handles orchestration where a full agent is overkill. Joe also runs n8n.io cloud workflows. Every flow emits structured heartbeats into heartbeat_log / ai_health_pulse.

Every job emits a heartbeat at start + completion. Stale-job detection runs on the Hub side and surfaces alerts in workflow_registry + Cortex dispatch.


Continue exploring Build