one theme, one vocabulary, five words of state.
Systems for models.
tcp.systems is the operating surface for the acumen gateway: the plane where models are catalogued, routed, metered and run — presented through three surfaces that share one theme.
ACUMEN — THE GATEWAY
One API in front of every provider.
Route every model call through one endpoint. Aliases keep routes simple — coding, reason, cheap, fast, vision, long, auto — and the catalogue keeps them honest with canonical ids and a per-project seat map. Free-tier caps are enforced by the gateway, not by hand.
ai.tcp.systems/v1 . schema-versioned migrations . per-request metering
STUDIO — THE WORKSPACE
Manage the platform without the wire.
Projects, catalogue rows, seats and migrations are edited in one workspace and verified against the schema before they move. What the gateway enforces, the studio shows.
catalogue . seats . schema check on write
CONSOLE — THE OPERATOR SURFACE
Sign in, read state, run the runbooks.
The console is the operator plane: status, logs and the runbooks that keep the gateway honest. Identity comes from your provider — the console verifies, it does not store.
OIDC sign-in . journald logs . runbooks
PRINCIPLES
01
Five words
running, pending, stopped, stale, failed — the same words in the UI, the API and the CLI.
02
AA, measured
Every text pair is computed against WCAG 2.x, not eyeballed. The gate re-runs the ratios on every change.
03
System theme
Light and dark follow the system with no script; an explicit choice persists under one key.
04
Square by decree
Radius zero, hairline rules, one overlay shadow. No pills, no circles, no glass.
read the docs, open the api, watch the console.
Read the docs