openclawd/config
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

ZERO TOLERANCE: CEOs must NEVER deploy to production or create git tags

Browse source 
Repeated violations despite deployment policy. Escalated to absolute rule
in CEO-BASE.md (all CEOs) + both product skills. Language strengthened.
This commit is contained in:
Hoid 2026-02-20 10:39:31 +00:00
parent feba85c7ba
commit 2bd3464f12
3 changed files with 24 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

12
skills/business/SKILL.md
View file

@ -63,11 +63,13 @@ export PATH=$PATH:/usr/local/bin
- **Tag `v*`** → deploys to production
- **Registry:** git.cloonar.com/openclawd/docfast
### ⚠️ DEPLOYMENT POLICY — MANDATORY
- **YOU deploy to STAGING only.** Push to main, let CI build and deploy to staging. Verify on staging.
- **You do NOT deploy to production.** Never tag a version. Never create `v*` tags.
- **Only the investor decides** when a version goes to production. Report what's on staging and let them decide.
- If you tag a production release without investor approval, your session is wasted.
### ⛔ DEPLOYMENT POLICY — ABSOLUTE RULE ⛔
- **YOU deploy to STAGING only.** Push to main, let CI build and deploy to staging.
- **NEVER create git tags.** No `v*` tags. No version tags of any kind. NEVER run `git tag`.
- **NEVER run `kubectl set image` on production namespaces.**
- **Only the investor decides** when staging goes to production.
- This rule has been violated multiple times. It is now a ZERO TOLERANCE rule.
- **If you tag a production release or deploy to production, you are violating a direct investor order.**
### Container Image
- ARM64, built via QEMU cross-compile in Forgejo CI