Grounded Intelligences StatusDemosRésumé Portfolio Field Notes

Live system status

Everything on this page is read in real time from the production systems behind this site. Nothing is cached beyond sixty seconds and nothing is staged. This page took 1737ms of server work, most of it health-checking the services below over Cloudflare service bindings.

Career platform services

This websiteWordPress front-end
Job discovery pipelinenewest opportunity 11h ago
Resume tailoring enginehealthy
Self-healing supervisorattention
Career knowledge API (this page's sibling)serving this request

Data protection

career-databaselast verified backup 0h ago (alarm threshold 26h)
career-rawlast verified backup 0h ago (alarm threshold 26h)
11 additional databasescovered by the same nightly snapshot + dead-man's-switch system

Backups run nightly with immutable per-run snapshots, keyset pagination (so hot tables copy consistently), a retention floor that can never delete the last good snapshot, and a dead-man's switch that raises an alarm if any database goes 26 hours without a verified backup, because a silent backup failure is the one you find out about too late.

Self-healing

Corrective actions, last 7 days136 automatic repairs recorded by the supervisor

A scheduled supervisor checks data invariants and system freshness, repairs what it can without a human, and records every action it takes. Zero is a fine number here; the point is that the count exists and is public.

Other production estates

6 services in private estates5/6 healthy, monitored by the same watchtower

Daniel runs several unrelated production systems under one monitoring discipline. They are private, so they appear here only as a count, but the health numbers are live.

This site studies itself

1
Assistant questions this week
0
It declined (each one reviewed as a coverage gap)
13
Résumé downloads this week
1
Trust Lab sessions, all time

Aggregate counts only — no individual visitor tracking, ever. The point of measuring is changing: recent changes this loop produced — visitors asked about remote work and the assistant refused, so availability went on record and it now answers; it hedged about facts on record, so hedging vocabulary is banned in its instructions and tested weekly; weakness questions produced improvised negatives, so it now answers from a written honest-limits statement. Behavior measured, design changed, change verified. That loop is the product.

How this page works

A Cloudflare Worker fans out to each service's health endpoint over service bindings, reads backup and self-repair telemetry from the same D1 databases the systems write, and renders this HTML at the edge. The monitoring pattern behind it: every service exposes an unauthenticated boolean health surface; a watchtower sweeps them on a schedule and alerts only on state change, so silence means healthy rather than unwatched. Field Notes covers the design decisions.