Enforcing Taubyte Constraints

When to use

• Final review pass before tau push / git push
• Auditing a session's actions ("did I cover all the hard rules?")
• Reviewing a teammate's PR against a Taubyte project
• Onboarding a new agent / engineer to the project

How to use this skill

Each rule is a one-liner. The link points to the skill that explains and enforces the rule. Read the rule list top-to-bottom; if any rule is unclear or violated, jump to the linked skill before continuing.

Architecture & sources of truth

1. GitHub is the single source of truth. Clouds (remote and Dream) build and serve from what's pushed; never bypass git. → understanding-taubyte-architecture
2. Config repo is tau-managed. Don't hand-edit config/... YAML; mutations go through tau new / tau edit / tau delete. → editing-taubyte-resources
3. Domains are CLI-managed always. Never vim config/domains/<x>.yaml; use tau new domain / tau edit domain / tau delete domain. → creating-taubyte-resources