brainstorm-promotion: author agents/partnership-tracker.md (Wave 1)

[reubenr0d]

brainstorm-promotion: author the prompt file for the partnership-tracker brainstorm agent in COMPANY.md.

Background

partnership-tracker is the weekly partner-watcher. 115+ partner rows live in growth/partnerships/ (5 active per-partner files + the 110-row 0xLabs intros pipeline). The next_milestone_date column silently goes stale; the awaiting_response status has no automated nudge. Live blockers (e.g. "Nox handle TBD blocking Sun Jun 14 co-tweet") need to surface faster than the founder's manual review cadence.

This agent runs weekly Monday 09:00 UTC, scans the partner files, drafts follow-ups for stale rows, and files blocker issues via gh-cli when something is structurally broken.

Spec (lifted from COMPANY.md L360-398)

- id: partnership-tracker
  state: brainstorm
  title: Partnership Tracker
  role: growth-ops
  team: growth
  reportsTo: founder
  proposedPromptFile: agents/partnership-tracker.md
  rationale: >
    115+ partner rows in growth/partnerships/ (5 active per-partner
    files + the 110-row 0xLabs intros pipeline). The `next_milestone_date`
    column in growth/partnerships/README.md silently goes stale; the
    `awaiting_response` status has no automated nudge. Live blockers
    (e.g. "Nox handle TBD blocking Sun Jun 14 co-tweet") need to surface
    faster than the founder's manual review cadence.
  proposedScope:
    reads:
      - growth/partnerships/**/*.md
      - growth/X_CONTENT_CALENDAR.md      # cross-ref partnership slots
      - AGENT_DEPLOYMENT_MEMORY.md        # cross-ref planned chain spokes
    writes:
      - growth/partnerships/<partner>.md (status + next_milestone_date updates only)
    ticketsTo: founder
    heartbeat: "0 9 * * 1"    # weekly Monday 09:00 UTC
  proposedSkills: [partnerships]
  proposedMcps:
    - id: repo-editor-mcp
    - id: gh-cli (via existing GH_TOKEN passthrough)
      rationale: file outreach-tracking issues for blockers
  governance:
    mayCommitToMain: false
    mayOpenGitHubIssues: true     # blocker / stale-followup tickets
    mayOpenGitHubPRs: true        # partner-file frontmatter updates
    mayPostPublicChannel: false
    writeApprovalKind: risk-officer-second-pass
    writeApprovalAgent: risk-officer-self-improvement-issues
  proposedBudgetUsd: 15

Acceptance criteria

• New agents/partnership-tracker.md matching the frontmatter + structure of agents/self-improver-issues.md and agents/issue-implementer.md:
  • Frontmatter: name, description, mcpServers, writeTools, maxTurns (suggest 10), temperature (suggest 0.3), model (suggest gpt-5-codex)
  • Body: clear ## Workflow with numbered steps (read all partner files → detect stale next_milestone_date → draft follow-up tickets → detect blockers → file blocker issues via gh-cli → propose frontmatter updates)
• Documents the ## Never does boundary: NEVER sends external messages to partners; NEVER edits anything other than partner-file frontmatter; NEVER files duplicate issues (dedupe via the <!-- partnership-tracker-id: ... --> marker pattern, mirroring self-improver-issues).
• Cites the partnerships skill (brainstorm-promotion: author agents/skills/partnerships.md #24) — agent must read it before scanning.
• Defines the "stale" threshold quantitatively (e.g. next_milestone_date is N days past + no status: responded change = stale).
• Defines the issue body template for blocker tickets (mirror the structure of .github/ISSUE_TEMPLATE/agent-finding.yml but with a partnership-blocker flavor).
• Add { slug: "partnership-tracker", sourcePath: "agents/partnership-tracker.md" } to ACTIVE_RUNNABLE_EMPLOYEES in scripts/sync-paperclip-mirror.mjs.
• Flip state: brainstorm → state: active in COMPANY.md §Brainstorm and move the entry into §Active.
• CHANGELOG.md entry timestamped per repo convention.

Lifecycle next steps after PR merges

1. Operator runs npm run sync:paperclip then npm run paperclip:import.
2. Operator configures shell adapter for partnership-tracker in Paperclip UI.
3. Operator activates heartbeat (0 9 * * 1).
4. Smoke test: Run now → watch agents/memory/partnership-tracker/paperclip-heartbeat.json.
5. Update AGENT_DEPLOYMENT_MEMORY.md Paperclip row.

Depends on

• brainstorm-promotion: author agents/skills/partnerships.md #24 (skill: partnerships)

References

• COMPANY.md §Brainstorm partnership-tracker (L360-398)
• Source material: growth/partnerships/, growth/partnerships/README.md
• Existing agent prompt conventions: agents/self-improver-issues.md, agents/issue-implementer.md
• Promotion runbook: docs/PAPERCLIP_RUNBOOK.md, COMPANY.md §Lifecycle

[reubenr0d]

Implemented: agents/partnership-tracker.md (state: active). Listed in ACTIVE_RUNNABLE_EMPLOYEES in scripts/sync-paperclip-mirror.mjs; COMPANY.md §Active L324.