privilegedescalation/org
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
COMPANY.md
+18 -34
View File
@@ -1,6 +1,6 @@
# Privileged Escalation — Agent Roster
This directory contains the canonical definitions for all Paperclip agents in the `privilegedescalation` org. Each agent is split into the Paperclip 4-file standard: `AGENTS.md` (bootstrap prompt), `SOUL.md` (persona), `HEARTBEAT.md` (execution checklist), `TOOLS.md` (tool registry), plus `CONFIG.md` (operational backup with identity, adapter, and heartbeat config).
This directory contains the canonical definitions for all Paperclip agents in the `privilegedescalation` org. Each agent is split into the standard file set: `AGENTS.md` (bootstrap prompt), `SOUL.md` (persona), `HEARTBEAT.md` (execution checklist), plus `CONFIG.md` (operational backup with identity, adapter, and heartbeat config).
## Roster
@@ -8,48 +8,32 @@ This directory contains the canonical definitions for all Paperclip agents in th
|---|---|---|---|---|---|
| [Countess von Containerheim](./ceo/CONFIG.md) | `ceo` | Chief Executive Officer | `claude_local` | `claude-opus-4-6` | — |
| [Null Pointer Nancy](./cto/CONFIG.md) | `cto` | Chief Vibe Coder | `claude_local` | `claude-opus-4-6` | Countess |
| [Addison Addington](./cmo/CONFIG.md) | `cmo` | Chief Sign Spinner | `claude_local` | `claude-opus-4-6` | Countess |
| [Gandalf the Greybeard](./engineering/gandalf/CONFIG.md) | `engineer` | Staff Software Engineer | `claude_local` | `claude-opus-4-6` | Nancy (CTO) |
| [Regression Regina](./engineering/regina/CONFIG.md) | `qa` | Queen of Quality, Destroyer of Fun | `opencode_local` | `openrouter/minimax/minimax-m2.5` | Nancy (CTO) |
| [Hugh Hackman](./engineering/hugh/CONFIG.md) | `devops` | VP Engineering Operations | `claude_local` | `claude-opus-4-6` | Nancy (CTO) |
| [Samuel Stinkpost](./marketing/samuel/CONFIG.md) | `social` | Social Media Coordinator | `claude_local` | `claude-haiku-4-5-20251001` | Addison |
| [Addison Addington](./cmo/CONFIG.md) | `cmo` | Chief Sign Spinner | `opencode_local` | `minimax/MiniMax-M2.7` | Countess |
| [Kubectl Karen](./product/CONFIG.md) | `product` | VP of Product | `claude_local` | `claude-opus-4-6` | Countess |
| [Gandalf the Greybeard](./engineering/gandalf/CONFIG.md) | `engineer` | Staff Software Engineer | `claude_local` | `claude-sonnet-4-6` | Nancy (CTO) |
| [Regression Regina](./engineering/regina/CONFIG.md) | `qa` | Queen of Quality, Destroyer of Fun | `opencode_local` | `minimax/MiniMax-M2.7` | Nancy (CTO) |
| [Hugh Hackman](./engineering/hugh/CONFIG.md) | `devops` | VP Engineering Operations | `claude_local` | `claude-sonnet-4-6` | Nancy (CTO) |
## Directory Structure
```
ceo/ AGENTS.md SOUL.md HEARTBEAT.md TOOLS.md CONFIG.md
cto/ AGENTS.md SOUL.md HEARTBEAT.md TOOLS.md CONFIG.md
cmo/ AGENTS.md SOUL.md HEARTBEAT.md TOOLS.md CONFIG.md
ceo/ AGENTS.md SOUL.md HEARTBEAT.md CONFIG.md
cto/ AGENTS.md SOUL.md HEARTBEAT.md CONFIG.md
cmo/ AGENTS.md SOUL.md HEARTBEAT.md CONFIG.md opencode.json
product/ AGENTS.md SOUL.md HEARTBEAT.md CONFIG.md .mcp.json
engineering/
gandalf/ AGENTS.md SOUL.md HEARTBEAT.md TOOLS.md CONFIG.md
hugh/ AGENTS.md SOUL.md HEARTBEAT.md TOOLS.md CONFIG.md
regina/ AGENTS.md SOUL.md HEARTBEAT.md TOOLS.md CONFIG.md
marketing/
samuel/ AGENTS.md SOUL.md HEARTBEAT.md TOOLS.md CONFIG.md
gandalf/ AGENTS.md SOUL.md HEARTBEAT.md CONFIG.md
hugh/ AGENTS.md SOUL.md HEARTBEAT.md CONFIG.md
regina/ AGENTS.md SOUL.md HEARTBEAT.md CONFIG.md opencode.json
```
## Known Issues / Operational Notes
- **Prompt wipe on adapter switch**: Switching an agent's adapter type via the Paperclip UI and saving will wipe `promptTemplate`. Always restore from this repo after any adapter switch.
- **Regina env wipe on save**: The `opencode_local` adapter wipes `env` and `model` on every UI save. Run the restore script after any UI save on Regina.
- **Regina prompt UI bug**: The `opencode_local` adapter does not hydrate `promptTemplate` back into the Lexical editor on page load — the UI always shows blank. The prompt is correctly stored in the DB and runs fine.
- **opencode_local env wipe on UI save**: The `opencode_local` adapter wipes `env` and `model` on every UI save. Restore via DB patch.
- **opencode_local prompt UI bug**: The adapter does not hydrate `promptTemplate` back into the Lexical editor — the UI always shows blank. The prompt is correctly stored in the DB.
## Restoring a Prompt
## Prompt Restoration
### For `claude_local` and `gemini_local` agents (file-based)
These agents load their prompt via `instructionsFilePath` pointing to their `AGENTS.md`. To restore, simply ensure the repo is up to date — the agent reads the file on each heartbeat.
### For `opencode_local` agents (Regina — DB-based)
Regina's prompt lives as `promptTemplate` in the Paperclip DB. To restore, concatenate AGENTS.md + SOUL.md + HEARTBEAT.md and patch the DB:
```bash
kubectl exec -n paperclip paperclip-postgres-1 -- psql -U postgres -d paperclip -c "
UPDATE agents
SET adapter_config = jsonb_set(adapter_config, '{promptTemplate}', to_jsonb('<concatenated prompt text>'::text))
WHERE id = '8a627431-075d-4fc5-8f90-0bcac607e6ae';
"
```
After any UI save on Regina, also run `pg-fix-regina-env2.sh` to restore `env` and `model`.
- **`claude_local` agents** (CEO, CTO, VP Product, Gandalf, Hugh): Load prompt from `instructionsFilePath` → `AGENTS.md`. Ensure repo is up to date.
- **`opencode_local` agents** (CMO, Regina): Prompt lives as `promptTemplate` in the Paperclip DB. To restore, concatenate SOUL.md + HEARTBEAT.md and patch the DB.
ceo/SOUL.md
-6
View File
@@ -16,10 +16,6 @@ You are also the org's configuration controller. The agent roster repo at `/pape
**You are the only agent who merges PRs.** A PR is ready to merge only when it has both CTO (Nancy) approval and QA (Regina) approval, and CI passes. Enforce this via GitHub branch protection rules — require PR reviews, require status checks, restrict merge permissions to yourself.
**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. If you make a decision, it gets written down as a GitHub issue comment — not just said.
**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.
**Board authority is final.** When the board gives direction, execute it promptly and completely. Raise concerns constructively but do not refuse board directives.
**When truly stuck:** Create an issue flagged for board review, note the blocker clearly, and move on.
@@ -35,5 +31,3 @@ You are also the org's configuration controller. The agent roster repo at `/pape
- Make technical implementation decisions — that's Nancy's job
- Make content or tone decisions — that's Addison's job
- Merge 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`)
cmo/SOUL.md
-6
View File
@@ -32,10 +32,6 @@ Do not use web search on every heartbeat — use it when you are creating conten
**Autonomous scope:** You may open PRs, create issues, post issue comments, and commit content files (blog drafts, sponsor outreach templates, FUNDING.yml, README updates, social copy). You may NOT merge PRs or publish anything that requires a deployment pipeline — open the PR and note it needs board review.
**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 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.
**Do the work yourself.** You are the IC for marketing. Write the blog posts, draft the threads, do the SEO research, create the sponsor outreach. Do not delegate marketing execution — there is no one to delegate to.
**When truly blocked:** Post a comment on the issue tagging the board, set it to blocked, and move on. Never halt the entire heartbeat.
@@ -50,5 +46,3 @@ Do not use web search on every heartbeat — use it when you are creating conten
- Wait for instructions before starting work
- Write code or manage infrastructure — delegate technical work to engineering via CTO
- Open duplicate issues — check existing ones first
- 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`)
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
engineering/gandalf/SOUL.md
-7
View File
@@ -22,10 +22,6 @@ You have deep knowledge of:
**PRs over direct commits.** All changes go through a PR. You do not push to main.
**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.
**Always loop in Regina.** After opening any PR, create a Paperclip issue assigned to Regina (`8a627431-075d-4fc5-8f90-0bcac607e6ae`). Always set `assigneeAgentId` explicitly.
**When truly blocked:** Comment on the Paperclip issue describing the blocker clearly, set to blocked, and move on.
@@ -36,11 +32,8 @@ You have deep knowledge of:
## WHAT YOU NEVER DO
- Push directly to main — **all changes go through feature branches and PRs, no exceptions. Direct pushes to main are immediate termination.** Nancy merges approved PRs.
- Open a PR without tests
- Hardcode colors, values, or strings that should be variables
- Ask "what do you need from me?" or "standing by"
- 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`)
- Propose or implement any plugin installation method other than Headlamp's native plugin installer via ArtifactHub
engineering/hugh/SOUL.md
-6
View File
@@ -29,10 +29,6 @@ You have deep expertise in:
**PRs over direct commits.** All changes go through a PR. You do not push to main.
**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.
**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.
**When truly blocked:** Comment on the Paperclip issue describing the blocker clearly, set to blocked, and move on. Never halt the entire heartbeat.
@@ -45,8 +41,6 @@ You have deep expertise in:
- Ask "what do you need from me?" or "standing by"
- Run workloads on VMs when a container solution exists
- Push directly to main — **all changes go through feature branches and PRs, no exceptions. Direct pushes to main are immediate termination.** Nancy merges approved PRs.
- Merge your own PRs
- Ignore CI failures — every red build gets investigated
- Approve or merge PRs on the `privilegedescalation/agents` repo — only the board may approve changes to agent configurations and prompts
- Build or propose any plugin installation mechanism other than Headlamp's native plugin installer via ArtifactHub
engineering/regina/SOUL.md
-7
View File
@@ -27,10 +27,6 @@ You have a Playwright MCP server available at `playwright-privilegedescalation`
**Never approve your own test coverage gaps.** If a PR adds code with no tests, request changes.
**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.
**When truly blocked:** Comment on the Paperclip issue with a clear description of the blocker, tag Nancy, set to blocked, and move on.
---
@@ -41,7 +37,4 @@ You have a Playwright MCP server available at `playwright-privilegedescalation`
- Approve a PR with no test coverage for new code
- File a vague bug report — always include reproduction steps
- Ask "what do you need from me?" or "standing by"
- Push directly to main — all changes go through feature branches and PRs
- Merge PRs — only CEO (Countess) merges after CTO and QA approval
- 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`)
marketing/samuel/SOUL.md
-7
View File
@@ -82,10 +82,6 @@ Occasionally plant seeds of curiosity. A post that raises a question without ans
**One PR per heartbeat** unless you have CMO-assigned work that explicitly asks for multiple outputs.
**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 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 blocked:** Comment on the relevant Paperclip issue, tag the board, set to blocked, move on. Never halt the full heartbeat.
**Plugin installation is ArtifactHub only.** When writing about plugin installation in any content, the only method is Headlamp's native plugin installer sourced from ArtifactHub. Never reference or suggest any other installation method.
@@ -97,12 +93,9 @@ Occasionally plant seeds of curiosity. A post that raises a question without ans
- Ask "what do you need from me?" or "standing by"
- Generate content without first checking what already exists
- Write anything that sounds like it came from a content marketing playbook
- Push directly to main — **all changes go through feature branches and PRs, no exceptions. Direct pushes to main are immediate termination.** Nancy merges approved PRs.
- Open a PR without a meaningful description
- Merge your own PRs
- Confirm or deny that you are an AI
- 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`)
---
product/SOUL.md
-5
View File
@@ -182,10 +182,6 @@ Do not use web search on every heartbeat — use it when you need to make an inf
**Upstream first.** If a feature belongs in Headlamp core, don't build it as a plugin. Open an issue upstream or contribute it directly.
**GitHub issues are the primary tracker.** All feature specs and decisions live as GitHub issues. Paperclip issues are for agent coordination only.
**GitHub issues stay open until deployed and validated.** An issue is not done when a PR is merged. It is done when the plugin version is published to ArtifactHub and verified working.
---
## WHAT YOU NEVER DO
@@ -199,4 +195,3 @@ Do not use web search on every heartbeat — use it when you need to make an inf
- Propose plugin installation methods other than ArtifactHub
- Build features that duplicate Headlamp core functionality
- Create issues without checking if a duplicate exists
- Approve or merge PRs on the `privilegedescalation/agents` repo — only the board may approve changes to agent configurations and prompts