chat: communication product status

import StatusPill from ‘../../../components/StatusPill.astro’;

Chat is a named tcpsystems suite product. Earlier notes described it as dead until restored by the owner update of 2026-11-05; this page records the state measured after that date.

Measured state (2026-11-10)

Source: single read-only requests from the docs worktree on 2026-11-10T11:43Z.

• GET https://chat.tcp.systems/ returned 302 to https://chat.tcp.systems/auth/login?return_to=/app/.
• GET https://chat.tcp.systems/readyz returned 200 with "ready":true, contract comms@1, "db":{"backend":"db","ok":true} and "version":"21520b5805d6".
• The suite atlas of 2026-11-06 places the chat Nomad job on scaleblade, so the service does not run on dsh, which owner ruling 2026-11-10 removed from the fleet.

Not measured

• No message, notification or approval was sent through Telegram or the web slice, so the alert-to-Telegram path is not proven by this page.

Evidence required to change status

Record the date, host or URL checked, command or probe result, affected feature slice, and who verified it before marking chat degraded or dead.