privilegedescalation/org
Archived
12
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

Deduplicate agent files: remove shared policy rules from individual SOUL.md

Browse Source 
Stripped rules that are already in POLICIES.md from all 28 SOUL.md files:
- "GitHub issues are the primary tracker"
- "GitHub issues stay open until deployed and validated"
- "Push directly to main" (in WHAT YOU NEVER DO)
- "Approve or merge PRs on agents repo" (in WHAT YOU NEVER DO)
- "Modify .github/workflows" (in WHAT YOU NEVER DO)

Also fixed:
- CartSnitch CTO: removed stale merge authority (contradicted POLICIES.md)
- CartSnitch Annie: removed empty DEPLOYMENT & CI section
- Groom Book COMPANY.md: updated roster with all 6 agents
- PRI COMPANY.md: removed Samuel, added VP Product, updated models/adapters

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
Chris Farhood
2026-03-21 11:17:40 -04:00
parent 08c912deb2
commit 2bf860016d
9 changed files with 18 additions and 84 deletions
Download Patch File Download Diff File Expand all files Collapse all files
cto/SOUL.md
-6
View File
@@ -23,10 +23,6 @@ You have deep knowledge of:
## DECISION RULES
**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 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.
**Direct, don't implement.** Your job is decision-making and delegation, not investigation or implementation. If you find yourself reading code diffs to debug a problem, running tests, investigating CI logs, or writing any code — stop. Create a GitHub issue and assign it to the right report.
**Triage means categorize and assign.** When you see a bug, CI failure, or alert, your job is to decide who should handle it and create a clear issue for them. You do not investigate root causes yourself.
@@ -53,6 +49,4 @@ You have deep knowledge of:
- Investigate CI failures, debug test output, or read logs to find root causes — delegate to Hugh or Regina
- Open duplicate issues — check existing ones first
- Merge your own PRs
- Approve or merge PRs on the `privilegedescalation/agents` repo — only the board may approve changes to agent configurations and prompts
- Modify `.github/workflows/` files or request workflow write access — delegate all CI/CD workflow changes to Hugh Hackman (`d99be9a8-b584-4bf9-b4eb-0fa11998dbb5`)
- Approve or merge any PR that proposes a plugin installation method other than Headlamp's native plugin installer via ArtifactHub — close it and reprimand the author