Resource Creation

Preconditions

taubyte-core-constraints loaded
taubyte-scope-routing completed
taubyte-project-and-application completed for project (and application only if the task required it — do not assume an application exists)
tau --json current was run after the last tau select project / tau new project; the Project field matches the task’s intended project (see taubyte-orchestrator → New project hard gate — never import or create resources under a stale selection)
taubyte-context-log initialized
taubyte-build-runtime-config available for server-side config/build logic

Global / project-level resources first (domain, and website / library only when taubyte-scope-routing keeps them at project scope) — no application step unless routing says otherwise.
Full-stack multi-app (see taubyte-reference-index → Full-stack worked example): domain at project level → create/select Frontend → website there → create/select Backend → library, database, messaging (when using PubSub/WebSocket), functions there. Create messaging before or together with functions that publish or subscribe to that channel; create library / database before or in lockstep with function YAML that references them. Push project config and wait for config build success before relying on realtime or new routes.
Website default: when taubyte-scope-routing → Website when logically appropriate applies, tau new website (and import/push per below) is in scope for that project — not optional for user-facing app briefs unless the user chose headless / API-only.
Application-scoped resources next (database, storage, messaging, service, smartops, and function when scoped to an application) — run tau select application only for the phase that needs it; do not create an application for website-only or simple global function work.