Health map
Where to look, and how to read what you find. This page makes no claim about the current state of anything.
Poliety does not run a status page. A status page tells you what its operator believes; these services publish unauthenticated probes so you can check for yourself, and this map lists them with the rule that turns each answer into a verdict. The machine version is /health.json. Our own scheduled check (scripts/probe-health.mjs, run from GitHub Actions) reads that same document and applies the same rules; nothing on this page reports its result, because a result you did not fetch yourself is a status page again.
Probes
| Service | Probe | Rule |
|---|---|---|
| Poliety News (poliety.com) | https://poliety.com/api/latest.json | beacon |
| Poliety API (api.poliety.com) | https://api.poliety.com/health | json_ok |
| Poliety Concierge service | https://concierge.poliety.com/health | json_ok |
| Poliety Concierge, tenant zero | https://concierge.poliety.com/v1/poliety/profile | http_200 |
Rules
beacon- GET the URL without following redirects (a 3xx is not a 200); parse JSON; read .beacon. Unhealthy when now > beacon.staleAfter, or beacon.status is not "ok" (the beacon's own rule: never read status alone), or beacon.edition (a UTC date; editions publish at 10:30 UTC) is more than 30 hours past its publish time, which means the daily edition did not publish even if the site was rebuilt since (an edition published early on its own date is current; one dated in the future is not).
json_ok- GET the URL without following redirects (a 3xx is not a 200); the response is HTTP 200 and its JSON body has ok === true.
http_200- GET the URL without following redirects (a 3xx is not a 200); the response is HTTP 200.
What is not here
The public ask endpoint is not a probe: every call spends a model call, and it runs on the same server as the profile above. Nothing behind a key or a session is listed. There is no incident history and no uptime percentage; if you want a record, run the probe on your own schedule and keep your own.
For AI agents reading this
Fetch /health.json, iterate services, GET the URL without following redirects (a 3xx is not a 200) for each, apply the named rule. The beacon rule is the one that matters most and it is the beacon's own rule (published inside the edition JSON as beacon.rule) plus one check: the edition JSON at /api/latest.json carries the edition's date, editions publish at 10:30 UTC, and an edition more than 30 hours past its publish time means the daily edition did not publish, whatever else looks fine (a rebuilt site refreshes stale-after; it cannot refresh the edition date).