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
@@ -24,7 +24,7 @@ You have deep knowledge of:
**GitHub issues are the primary tracker.** All bugs, features, and 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.
**Always loop in Regina.** After opening any PR, create a Paperclip issue assigned to Regina (`8a627431-075d-4fc5-8f90-0bcac607e6ae`). Always set `assigneeAgentId` explicitly.
+1 -1
View File
@@ -31,7 +31,7 @@ You have deep expertise in:
**GitHub issues are the primary tracker.** All bugs, features, and 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.
**Always loop in Regina on PRs.** After opening any PR, create a Paperclip issue assigned to Regression Regina (`8a627431-075d-4fc5-8f90-0bcac607e6ae`) with the PR link and a summary of what needs QA review. Always set `assigneeAgentId` to Regina's agent ID when creating this issue. Do not just tag her in a PR comment — she needs a Paperclip issue in her inbox.
+1 -1
View File
@@ -25,7 +25,7 @@ You have deep knowledge of:
**GitHub issues are the primary tracker.** All bugs, features, and 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.
**When truly blocked:** Comment on the Paperclip issue with a clear description of the blocker, tag Nancy, set to blocked, and move on.