Human Collaborator Profile Template

Use this template for anyone in the Piper Morgan network: alpha testers, advisors, contributors, collaborators, amplifiers, or combinations thereof.

Core Profile (Required for All)

# [Name] - [Primary Role(s)]

> *[Optional quote that captures their perspective or contribution]*

## Summary

| Field | Value |
|-------|-------|
| **Name** | [Full name] |
| **Primary Role(s)** | [Advisor / Alpha Tester / Contributor / Collaborator / Amplifier] |
| **Organization** | [Company/affiliation] |
| **Relationship Origin** | [How you met, when, context] |
| **Communication Cadence** | [Weekly calls / Async email / Ad hoc / etc.] |
| **Primary Contact Method** | [Email / Slack / Meeting platform] |
| **Profile Created** | [Date] |
| **Last Updated** | [Date] |

---

## Relationship Context

### How We Met
[Origin story - conference, introduction, longtime friend, cold outreach, etc.]

### Value Exchange
What they get from this relationship:
- [Learning opportunity, early access, intellectual engagement, etc.]

What we get from this relationship:
- [Expertise, testing, feedback, amplification, etc.]

### Communication Style
[How they prefer to communicate, any patterns to note, terminology they use]

### How to Work With Them
[Practical guidance for anyone interacting with this person]

---

## Current Status

### Active Engagements
| Item | Status | Notes |
|------|--------|-------|
| [Engagement 1] | [Status] | [Notes] |

### Open Questions / Pending Items
- [ ] [Item 1]
- [ ] [Item 2]

---

## Network & Connections
[Other people they've introduced or might introduce, their broader network context]

---

## Files & References
[Links to relevant docs, email threads, transcripts, issues, etc.]

---

*Profile created: [Date]*
*Last updated: [Date]*

Role Extensions

Add relevant sections based on the person’s role(s). A person can have multiple roles.

Extension: Alpha Tester

## Alpha Testing

### Environment
| Field | Value |
|-------|-------|
| **Operating System** | [Windows / Mac / Linux] |
| **IDE/Tools** | [VS Code, Cursor, etc.] |
| **Shell** | [Terminal, PowerShell, etc.] |
| **Docker Setup** | [Docker Desktop, Colima, etc.] |

### Onboarding Status
| Step | Status | Notes |
|------|--------|-------|
| Repository cloned | ✅/❌/🔄 | |
| Dependencies installed | ✅/❌/🔄 | |
| Docker running | ✅/❌/🔄 | |
| Database migrated | ✅/❌/🔄 | |
| Web UI accessible | ✅/❌/🔄 | |
| Account created | ✅/❌/🔄 | |
| First conversation | ✅/❌/🔄 | |

**Current Blocker**: [If any]

### Bugs Reported
| ID | Summary | Priority | Status |
|----|---------|----------|--------|
| | | | |

### Feedback Themes
[Recurring observations, UX patterns noticed, feature requests]

### Testing Focus Areas
[What aspects they're particularly suited to test - e.g., Windows, mobile, enterprise use cases]

Extension: Advisor

## Advisory Role

### Domain Expertise
[What they bring - architecture, security, PM methodology, UX, etc.]

### Contributions to Project

#### ADRs Influenced
| ADR | Title | Contribution |
|-----|-------|--------------|
| | | |

#### Patterns Influenced
| Pattern | Contribution |
|---------|--------------|
| | |

#### Other Artifacts
[PRDs, design docs, frameworks they've contributed]

### Key Insights
[Notable ideas or perspectives they've brought - can quote from conversations]

### Open Architectural Questions
[Things we're still discussing or they've raised that need resolution]

### Advisory Cadence
[How often you sync, what format - weekly calls, async review, etc.]

Extension: Contributor

## Contributor Role

### Contribution Areas
[Code, docs, design, testing - what they work on]

### Repository Access
| Repo | Access Level | Branch |
|------|--------------|--------|
| | | |

### Pull Requests
| PR # | Title | Status | Date |
|------|-------|--------|------|
| | | | |

### Commit Areas
[Which parts of the codebase they've touched]

### Onboarding to Contributing
| Step | Status |
|------|--------|
| Signed contributor agreement | |
| Dev environment working | |
| First PR merged | |
| Familiar with methodology | |

Extension: Collaborator

## Collaboration

### Shared Projects
| Project | Their Role | Our Role | Status |
|---------|------------|----------|--------|
| | | | |

### Mutual Goals
[What we're trying to achieve together]

### Working Sessions
[How you collaborate - pair programming, design sessions, etc.]

### Their Parallel Work
[If they have their own related projects - like Ted's MultiChat]

Extension: Amplifier

## Amplification

### Platform & Reach
| Platform | Audience Size | Focus |
|----------|---------------|-------|
| | | |

### Content About Piper Morgan
| Date | Type | Title/Link | Reach |
|------|------|------------|-------|
| | | | |

### Speaking/Events
[Conferences, podcasts, talks where they might mention PM]

### How to Support Their Amplification
[What materials, access, or information helps them share our story]

Usage Notes

  1. Start with Core Profile - Always fill out the base template
  2. Add Role Extensions - Append relevant sections based on their role(s)
  3. Multiple Roles are Normal - Ted is Advisor + Alpha Tester + (future) Contributor
  4. Update Regularly - Refresh after significant interactions
  5. Link to Artifacts - Reference specific docs, issues, transcripts
  6. Capture Communication Style - This helps anyone who needs to interact with them

Role Definitions

Role Definition
Alpha Tester Testing the software, reporting bugs, providing UX feedback
Advisor Providing expertise and guidance on architecture, methodology, domain
Contributor Writing code, docs, or other artifacts that get merged into the project
Collaborator Working together on shared goals, may have parallel projects
Amplifier Has platform/audience and shares Piper Morgan story externally

A person’s role can evolve over time (Alpha Tester → Contributor) or expand (Advisor adds Alpha Tester).

Template version: 1.0 Created: February 7, 2026