Live from Lehvel.

Real signals from Lehvel’s own systems, each with where it came from and when it was observed. If a source has nothing approved to show, it says so.

Right now

5 sources · 4 live · read

  • ReleaseLive

    lehvel.com is serving release 8c1d950.

    · age 6h 49m / live window 3d

    Source: Vercel production deployment serving lehvel.com, commit 8c1d950.

  • Site checkLive

    Weekly check read 2 pages of lehvel.com, the contact page included.

    · age 1d 14h / live window 8d

    Source: Lehvel's own weekly check of lehvel.com.

  • Build noteRecent

    The factory log went live

    · age 7d 11h / live window 7d

    Source: the /drop log, 2026-10-30/the-factory-log-went-live.

  • UptimeLive

    lehvel.com answered 200 in 193 ms · 144 of 144 checks passed in the last 24 hours.

    · age 8m / live window 30m

    Source: Lehvel's ten-minute request to lehvel.com from Vercel Cron.

  • AI findingLive

    Asked ChatGPT 20 questions about Lehvel and its field; 8 answers mentioned Lehvel, 18 claims matched Lehvel's stated facts and 0 conflicted.

    · age 1d 11h / live window 14d

    Source: Lehvel Observatory run 22, Lehvel's own org only; Claude not reached this run.

01 — Sources

How each signal is read.

Release
Read from the hosting provider: the deployment lehvel.com is serving right now, its time and its short commit. Commit messages are never shown, because they can describe client work. It is called live for 3 days after it is observed, recent until 30 days, then stale.
Site check
Lehvel's own observation runner reads lehvel.com once a week: the homepage and the contact page. This is the result of its latest finished run. It is called live for 8 days after it is observed, recent until 15 days, then stale.
Build note
The newest note published on /drop, which the founder approves before it goes up. Notes about client work never appear here. It is called live for 7 days after it is observed, recent until 30 days, then stale.
Uptime
Every ten minutes a scheduled job on Lehvel's hosting (Vercel Cron) requests https://lehvel.com/ over the public internet, with a cache-busting query so no cached copy answers. It records the status code and the time to answer, and keeps seven days of results. A check passes only on a 200. This is Lehvel's own scheduled request, not an independent third-party monitor: if the schedule stops, this row ages to recent, then stale, and never fills the gap. It is called live for 30 minutes after it is observed, recent until 1 day, then stale.
AI finding
Lehvel Observatory asks ChatGPT and Claude the same tracked questions about Lehvel and its field, stores every answer, and grades the claims in answers that mention Lehvel against Lehvel's stated facts. This shows the newest finished run for Lehvel's own organization, never a client's. A run is started by hand, because it pays for every answer. When an engine could not be reached, the source line says so; when grading did not run, no claim count is shown. It is called live for 14 days after it is observed, recent until 45 days, then stale.

02 — Rules

What never shows here.

  • Nothing about a client, and nothing from a source that is not on the approved list.
  • No email addresses, phone numbers, account or project ids, and no links off lehvel.com.
  • No made-up activity: a source that cannot be read says “Not connected”.
  • The time a signal was observed and the time it was published are kept apart.
  • Any signal can be withdrawn, and the whole instrument can be switched off.

The same data, as JSON: /api/live/v1.