Every way into the estate on develop.tag.company.
A monitor wants /health — The same picture as a monitor reads it: JSON, 200 while what should be running is running, 503 when it is not.
Somewhere you can go right now — what each one is, and when you would want it. Whether it is working this minute is /status's answer and not this page's.
/aletiaThe TAG app itself — nexuses, marks, arcs and the evidence behind them. This is where the work gets done.
/chatAsk a model a question, with the estate's own key behind it. Go here when you want an answer rather than a record. The browser asks for a password first — the captain has it.
/agentsWatch the nine agents work — what each one is doing and what it has carried. Go here when documents have stopped moving. The dashboard only; the fleet itself stays unpublished.
/clientWhere a client sees their own engagement: what the accountant has asked for, the documents that answer it, and where each one stands.
/firmThe firm's side of the same engagement: requests out, deliverables back, and the queue of who owes what to whom.
/supabaseThe database tier's only public door — the REST, auth, realtime and storage APIs. Go here with a key, or point a Supabase client at it; 401 without one is the correct answer.
Known, and deliberately not open. Nothing here is broken and nothing here is a link — a card saying why not is worth more than a link that 404s, and the reason differs for every one of them.
Assign goals to the agent company and watch what they cost. Org chart, budgets and governance — the harness above the fleet.
The agents' own HTTP endpoints — what the dashboard above drives. Not a page, and nowhere a person goes.
/backofficeInternal administration for the firm itself — the running of the business, rather than the client work it does.
/gatewayOne authenticated API in front of the data tier, so applications stop reaching into the database themselves.
The public face of TAG, for people who are not users yet.
No path points at any of these and none of them is a place you click. They are the parts a published service stops working without, and they are listed and checked on /status.