Ingestion status.

The ledger reconciles

The check that decides whether any of this is worth reading. If the gap ledger were decorative, the cycles it claims were missed would not add up to the cycles that are absent.

Those two totals land on each other inside the tolerance, so the missing time is accounted for rather than quietly dropped. The tolerance is 2 percent of the expected count or 5 cycles, whichever is larger, because the cadence is a mean and not a fixed tick.

The publisher's own days_running figure differs from the interval between its two timestamps by 10 seconds, which is the lag between measuring and writing. The elapsed figure above is the interval, so it sits on the same clock as the gap rows.

elapsed = published_at minus first_cycle_at, falling back to days_running x 86400 if either timestamp is unreadable. ingesting = elapsed minus the recorded gaps, with overlapping intervals merged before they are added up. expected cycles = elapsed / cadence_seconds, and cadence_seconds is a mean, so that count is good to a few cycles and not to one. every input is a column the publisher wrote.

Quality gates 4 of 4 passing

The ingestion checks the poller runs against itself: disk headroom, freshness, volume and null rates. The detail below is copied from the snapshot exactly as the machine wrote it.

• ✓ disk 35.1 GiB free on /System/Volumes/Data
• ✓ freshness last poll_runs row -0.0 min ago
• ✓ volume 337871 rows inserted (poll_runs) in the last hour
• ✓ null_rate scheduled_arrival null-rate 4.18% over last hour (14385/344049)

Where this runs

The warehouse is Postgres on a Mac in my apartment. It is not a managed cloud service and this page does not pretend it is. The Mac publishes a snapshot of its own counters to a Cloudflare D1 database on a 5 minute interval. This page reads the newest snapshot and shows how old it is, every time.

That is the whole trick, and the failure mode is the point. If the Mac sleeps, loses power or loses network, the snapshot stops moving, the age climbs, and this page says so in plain words instead of showing an old number as if it were current. The threshold for saying so is 15 minutes.

What these numbers are not

• Uptime here counts from the first poll cycle, not from an install date. Today it is a small number and the page prints it to two decimals rather than rounding it into something rounder.
• The cadence is measured, not configured. The interval is set at 60 seconds, and the work inside each cycle pushes the real spacing above that. The measured figure is the one shown.
• This is a single machine with a single power supply. There is no failover. The gap ledger exists because of that, not in spite of it.