taubyte-scope-routing

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Project / global (default for many tasks):
```
project
```
,
```
domain
```
,
```
website
```
,
```
library
```
— and standalone function or website work when the user does not ask for multiple applications or named app boundaries.
Application-scoped (requires selected application when doing this work):
```
application
```
,
```
service
```
,
```
database
```
,
```
storage
```
,
```
messaging
```
,
```
smartops
```
.
function
: treat as project-level for simple, single-function (or function-only) tasks without a named application or multi-context brief; treat as application-scoped only when the user ties work to an application, or the task is multi-app / multi-context, or the CLI clearly requires an application for the next commands.

项目/全局（适用于多数任务的默认范围）：
```
project
```
,
```
domain
```
,
```
website
```
,
```
library
```
—— 以及当用户未要求多个应用程序或指定应用边界时的独立函数或网站工作。
应用范围（执行此类工作时需选择应用程序）：
```
application
```
,
```
service
```
,
```
database
```
,
```
storage
```
,
```
messaging
```
,
```
smartops
```
。
function
：对于简单的单一函数（或仅含函数）且无指定应用程序或多上下文需求的任务，视为项目级；仅当用户将工作与某个应用程序关联，或任务为多应用/多上下文，或CLI明确要求后续命令必须使用应用程序时，才视为应用范围。

If the request is global-only (website, library, domain, or simple function/site without multi-app), do not force application creation or tau select application
.
If the request includes application-scoped resources (service, database, storage, messaging, smartops, or function explicitly under an app), require application scope when those operations run — create/select an application only per taubyte-project-and-application
triggers, not by default.
If the request is mixed, do global resources first (no application unless needed), then application resources with tau select application
only for that phase.
If ambiguous, ask one short question (e.g. single app vs multiple apps vs project-level only).
Write the scope decision and reason (including “no application”) to taubyte-context-log
.

如果请求仅涉及全局资源（网站、库、域名，或无多应用需求的简单函数/站点），请勿强制创建应用程序或执行**
```
tau select application
```
**。
如果请求包含应用范围的资源（服务、数据库、存储、消息服务、smartops，或明确隶属于某个应用的函数），在执行这些操作时必须使用应用范围 —— 仅在触发**
```
taubyte-project-and-application
```
**时创建/选择应用程序，而非默认创建。
如果请求同时包含全局和应用范围的资源，先处理全局资源（除非必要否则不使用应用程序），再处理应用范围资源，且仅在该阶段执行**
```
tau select application
```
**。
如果请求模糊不清，提出一个简短的问题（例如：单一应用 vs 多个应用 vs 仅项目级）。
将范围决策及理由（包括“无需应用程序”）写入**
```
taubyte-context-log
```
**。