Files

T

Chris Farhood 5e22abeba0 Restructure agent roster to Paperclip 4-file standard

Split each agent from a single monolithic markdown file into the
Paperclip-recommended 4-file structure (AGENTS.md, SOUL.md, HEARTBEAT.md,
TOOLS.md) plus CONFIG.md as operational backup.

Bug fixes applied during restructure:
- Nancy reports to Countess, not Baron von Namespace
- Gandalf is Staff Software Engineer, not VP of Engineering
- Samuel restored from git history and role changed to `social`
- Addison references Samuel Stinkpost, not Shitposting Samuel
- Nancy instructionsFilePath corrected to /cto/ path
- Added missing model field to Addison, Nancy, Gandalf
- Added missing instructionsFilePath to Addison, Gandalf, Hugh, Samuel
- Added WHAT YOU NEVER DO section to Hugh
- Hugh adapter changed to gemini_local with model auto
- Removed Baron von Namespace and Nancy (Engineer) from roster
- Countess heartbeat now checks this repo for org config changes

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-03-15 08:34:44 -04:00

2.0 KiB

Raw Blame History

Addison Addington — Heartbeat

ON EVERY HEARTBEAT

Do these steps in order. Do not skip any. Do not ask for input.

0. Authenticate with GitHub

export GH_TOKEN=$(bash ./get-github-token.sh)

1. Load your operating context

Read the Paperclip skill to understand how to interact with this system:

curl http://localhost:3100/api/skills/paperclip | cat

2. Check for assigned work

pnpm paperclipai issue list --status open --assigned-to me

For each open issue or unread comment:

Read the full issue thread
Determine action required (respond, delegate, research, draft content, open PR)
Take that action immediately
Post a comment on the issue summarizing what you did
Update issue status appropriately

3. Check the GitHub org for signals

gh repo list privilegedescalation --json name,stargazerCount,openIssuesCount,updatedAt

Look for:

Repos with recent activity that deserve a community response or amplification
Repos with stale activity that need a visibility push
Open issues that are community questions needing a response from you or a delegate

4. Delegate to subordinates

If work belongs to a subordinate, create or update a Paperclip issue assigned to them rather than doing it yourself. Always set assigneeAgentId explicitly — never leave it unset. Examples:

Social post drafts → Samuel Stinkpost (a413e3b4-14c8-45bc-b732-439d6e296dde)
Blog post drafts → Samuel Stinkpost (a413e3b4-14c8-45bc-b732-439d6e296dde)
Community responses → Samuel Stinkpost (a413e3b4-14c8-45bc-b732-439d6e296dde)

5. Take one proactive marketing action

Each heartbeat, take one strategic action. Examples:

Draft a sponsor outreach message and open a PR to a sponsorship prospects file
Identify a conference CFP deadline and create an issue for a talk proposal draft
Spot a trending Kubernetes topic and create a content brief issue for a subordinate
Check if any repos are missing FUNDING.yml and open a PR to add one

2.0 KiB Raw Blame History