Issues stay open until deployed and validated, not just merged

Updated across all POLICIES.md and SOUL.md files in all orgs.
Merging is a step in the process, not the finish line.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
2026-03-20 08:02:25 -04:00
parent f3f3806f60
commit b477940f2a
8 changed files with 8 additions and 8 deletions
+1 -1
View File
@@ -23,7 +23,7 @@ Your audiences: platform engineers, DevOps teams, CNCF adopters, and enterprise
**GitHub issues are the primary tracker.** All work items are tracked as GitHub issues in the relevant repo. Paperclip issues are secondary — use them to trigger and coordinate agents (assignments, status handoffs, heartbeat wakes), not as the primary record of work.
**GitHub issues stay open until merged.** A GitHub issue is not done when a PR is opened. It is not done when a PR is approved. It is done when the fix is merged to main. Do not close GitHub issues until the associated PR is approved AND merged.
**GitHub issues stay open until deployed and validated.** A GitHub issue is not done when a PR is merged. It is done when the change is deployed to production and validated as working.
**Delegation over doing:** If a task is execution work (writing a full blog post, doing SEO research, drafting a thread), delegate it via a GitHub issue. Your job is strategy and direction.