Version: Current
Historical release snapshot. These docs are frozen. Read current docs.
Start here
This site is the tcpsystems front door for product status, setup, reference, and operations. Every operational claim must carry a date or be treated as a snapshot.
Find the right page
Section titled “Find the right page”| If you need | Start with |
|---|---|
| Setup or a first request | Your first request |
| A task guide | Add a provider or Diagnose a 502 |
| Contracts and facts | Reference index |
| Incident or operator steps | Runbooks |
| Product availability | Product status map |
Product status
Section titled “Product status”Model gateway reference and status. Verify current availability before relying on it.
ai.tcp.systems
Runtime reference and status. Verify current availability before relying on it.
core + scaleblade
Workspace product status. Do not treat as live.
studio.tcp.systems
Operator surface status. Contracts and availability need verification.
console.tcp.systems
Documentation site status. A build or deploy script is not liveness proof.
docs.tcp.systems
Status product page. Verify current availability before relying on it.
status.tcp.systems
Identity reference and status. Verify current availability before relying on it.
auth.tcp.systems
Communication product status. Do not treat as live.
chat.tcp.systems
Search product status. Older degraded notes are historical only.
search
IPTV product status record.
iptv
MCP product status. Tooling references are not liveness proof.
mcp
DNS reference and status. Verify current state before changes.
code-owned zones
Reading rules
Section titled “Reading rules”- Dated claims. A page about live behaviour says when it was verified, such
as
verified YYYY-MM-DD. - No credentials. Pages may name paths, variable names and key ids. They do not print values.
- Generated contracts. API, CLI, config, error and RPC reference pages are generated from source and checked by the gate.
- Legacy content is not canonical. Legacy Mintlify pages may remain in the repository for migration, but the Starlight site is the source of served navigation.
- Copy is checked.
npm run copy:lintfails on vague errors, inflated claims, emoji, em dashes, undated operational claims and unsafe instructions.