Public architecture
Ecosystem Architecture
Public product layering, credential boundaries, and collaboration model for TokenDance.
Why this page exists
The organization site is for readers who are seeing TokenDance for the first time. It should explain each product role, which boundaries can be public, and which implementation details belong in product repositories or private operations docs.
This page is not an internal topology diagram or deployment runbook. It describes the public product architecture: entry points, identity, model APIs, the agent workbench, experimental projects, and governance docs.
Public layers
| Layer | Public role | Primary products | Public promise |
|---|---|---|---|
| Brand and navigation | Explain TokenDance and route readers to the right product | tokendance-org | Product matrix, public docs, SEO/llms entry |
| Collaboration workbench | Let multiple agents collaborate on Desktop and Web | AgentHub | Site, docs, Desktop-first direction, and Hub-backed Web boundaries |
| Model API | Provide an OpenAI-compatible model API entry | TokenDance Gateway | API entry is live; keys, quota, errors, and status UX are being productized |
| Unified identity | Own login, third-party providers, and OIDC | TokenDance ID | Identity authority for product login; authorization remains product-local |
| Experiments and proofs | Validate CLI, chat, event stream, and agent interaction ideas | TokenDanceCode / TokenDanceChat | Low-commitment experiments and demos, not replacements for product lines |
Credential and session boundaries
| Scenario | Use | Do not use |
|---|---|---|
| Browsing the site and docs | Anonymous access; optional low-risk TokenDance ID personalization | Model API keys or admin secrets |
| Product login | TokenDance ID OIDC plus product-local sessions | Product apps directly integrating GitHub, Google, or Feishu OAuth |
| Calling model APIs | TokenDance API key plus https://api.vectorcontrol.tech/v1 | TokenDance ID access token |
| Running AgentHub tasks | Runtime configuration owned by Hub, Edge, or adapters | A Web page directly reading local files or starting local CLI processes |
| Deployment and operations | Private server workspace and operator secret store | Public README, llms.txt, issues, or screenshots |
How products cooperate
- tokendance-org is the brand entry and product matrix. It does not host every product's full implementation docs.
- AgentHub is the multi-agent collaboration product line. It may use Gateway through controlled adapters or server-side configuration, but model keys do not belong in the Web frontend.
- TokenDance Gateway serves agents, CLIs, applications, and automation workloads. TokenDance ID handles login identity, not model API authentication.
- TokenDanceCode can capture CLI-agent events, tools, and interaction patterns that may inform future AgentHub runtime adapter design.
- TokenDanceChat is a realtime interaction and event-flow proving ground. Public wording should keep a demo/proof tone.
Not in public architecture
- Production hosts, SSH aliases, nginx web roots, backup directories, and rollback commands.
- Real provider keys, TokenDance API keys, admin tokens, client secrets, or private logs.
- Unreleased admin screenshots, internal database paths, user data, or support-process details.
- Roadmap features written as stable SLA promises.