Home · Builds · Sync and drift alerts

Build

Silence is not a status. Alert on it.

The hourly loop logs its runs and the reconciliation view flags drift, but today both wait for someone to look. The bot is already in the group. Give it the bad news to deliver.

Video · 40 sec A failed sync, reported in the group
Placeholder Phone capture: kill the sync service on purpose, wait for the next scheduled check, the alert lands with the error line and the runbook link.

The design

Four states, healthy, stale, failed, and drifting, with the transitions that send a message in ink and the quiet returns in gray.
Small diagram: healthy, stale, failed, drifting, with the transitions that send a message and the ones that stay quiet. Also as a square.

What I expect to learn

The right stale threshold. Three hours is the current guess in the settings row.

All buildsNext build · The same stack for a client

Write to me

I built this for a household. Imagine it pointed at your company.

Fractional CTO and CFO engagements start with a short call. No deck required, no pitch either. Bring the number you do not trust.

Tell me what is stuck