Public governance
Release Evidence
Public evidence required for TokenDance Org releases: routes, SEO, i18n, visual QA, and product-status claims.
Why release evidence exists
Product Status says live entries need current release evidence. This page defines what can be recorded publicly without copying private server paths, rollback commands, or secrets into the website repository.
Public evidence checklist
| Category | Public evidence | Not public |
|---|---|---|
| Routes | HTTP status and rendered keywords for /zh, /en, /zh/docs, /en/docs, and changed docs routes | Deployment directories, nginx paths, SSH aliases |
| Discovery | robots.txt, sitemap.xml, and llms.txt cover changed routes | Private crawler logs |
| i18n | Chinese and English product claims, login boundaries, CTAs, and metadata are semantically aligned | Translation drafts or internal review comments |
| Visual QA | Desktop/mobile screenshot artifact paths and no-horizontal-overflow conclusion | Screenshots with private paths or user data |
| Security | No secrets, no private paths, correct credential boundaries | Real keys, admin tokens, provider payloads |
Current key routes
- /zh and /en: homepage, product matrix, TokenDance Blue design, login entry.
- /zh/docs and /en/docs: docs entry and product navigation.
- /zh/docs/gateway and /en/docs/gateway: Gateway base URL, SDK examples, and credential boundary.
- /zh/docs/gateway-access and /en/docs/gateway-access: API keys, environment variables, and minimal verification.
- /zh/docs/gateway-status-support and /en/docs/gateway-status-support: errors, status, rate limits, and support evidence.
- /zh/docs/release-evidence and /en/docs/release-evidence: public release-evidence rules.
Local verification commands
powershell
pnpm lint
pnpm build
pnpm visual:qa
# From the TokenDance workspace root
.\scripts\verify-public-surfaces.ps1
.\scripts\verify-i18n-parity.ps1
.\scripts\verify-doc-freshness.ps1
.\scripts\verify-design-tokens.ps1
.\scripts\verify-governance.ps1 -SkipDiffCheckStatus upgrade rules
- A public site entry can be called live only when route, discovery-file, i18n, visual-QA, and security-boundary evidence exists.
- Gateway API live does not mean key self-service, complete model lists, quota views, status page, and SLA are all released.
- TokenDanceCode is experimental; release evidence proves only public positioning and trial boundaries, not stable product support.
- Evidence containing private operations details belongs in the server workspace or private release notes, not in the public repository.