How to read this site
This wiki is organized from the outside in: first what users see, then the domain language, then architecture, data, code paths, operations, and references.
| Page type | What it answers | Best for |
|---|---|---|
| Overview | What is this domain and who uses it? | Everyone |
| End-user view | What does the user do on screen? | Everyone, support |
| Core concepts | What are the main domain objects and terms? | Everyone |
| Architecture | What components and data stores are involved? | Engineers, architects |
| Codebase flow | Which files, APIs, services, and workers handle it? | Engineers |
| Common cases | What practical situations appear in support/debugging? | Engineers, support |
| References | Where are the source specs and code anchors? | Engineers |
Source of truth
This wiki summarizes the system. If it conflicts with reality, trust this order:
openspec/specs/**/spec.md- Actual code in
Topi/,Tuke/, andTux/ - This wiki
Applications mentioned often
| Name | What it is | Role |
|---|---|---|
| Topi | Legacy React/UmiJS frontend | Older admin UI |
| Tuke | Next.js frontend | Modern web UI |
| Tux | .NET 8 backend and workers | APIs, business logic, queues, background processing |