STEADYWRK · live status
The classroom infrastructure, read live.
Everything below comes from a request made to LiveKit and to this server’s own webhook ledger at the moment the page asked — not from a dashboard someone updates by hand, and not from a number cached at deploy time. Sessions counts and participant counts are counts only: no names, no room labels, no identities. A field this endpoint cannot verify right now says unknown, and stays that way instead of guessing zero.
What this page proves, and what it does not
What it proves
That a request against the live LiveKit server and this app’s own database returned the values shown, at the timestamp shown. The transcription worker’s status is read from LiveKit’s own participant-kind field for whichever sessions were live at the moment of the check — not inferred from a name pattern.
What it does not prove
It does not prove call quality, transcription accuracy, or that a session that just ended went well. “Not detected” on the transcription worker is not the same claim as “the worker is down” — it only joins a room once dispatched, and this page cannot see a dispatch in flight.
Looking for something else?
- Application-level uptime and deploy stamp live at /status.
- Security control verdicts — probes that actually fired, not a configuration badge — live at /trust/live.
- The raw feed behind this page is /api/live/status.