Round 44: CONTRIBUTOR-PERSONAS.md — batch 6b of 6 (additive-only)#87
Conversation
10 named contributor archetypes (human + AI) for Zeta first-contact surfaces (issue templates, README, CONTRIBUTING.md, SECURITY.md, AGENTS.md). Companion to docs/README.md §Quick-start (document-reader audiences) and docs/EXPERT-REGISTRY.md (internal reviewers) — contributor personas answer "who just showed up wanting to contribute, and do we lose them in the first 90 seconds?" Scrubbed at pre-commit per drain-PR pre-check discipline: maintainer-name prose replaced with role-refs (BP-L284-L290); memory/ ref replaced with in-tree pointer to docs/BACKLOG.md P3 conversational- bootstrap row. Personas: typo-fixer / busy backend engineer / first-paper grad student / AI coding agent / systems engineer / security researcher / F# enthusiast / maintainer-external peer / factory-reuse adopter / returning contributor. Round-44 speculative-branch drain, batch 6b of 6 (6a skill tune-ups landed via Lucent-Financial-Group#86; this is one of the small additive-only factory surfaces split out of batch 6 to land cleanly; 6c will carry the remaining anchor-doc subset). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Adds a new documentation surface (docs/CONTRIBUTOR-PERSONAS.md) defining expected contributor archetypes (human + AI) so first-contact surfaces (README / issue templates / AGENTS.md / SECURITY.md / CONTRIBUTING.md) can be designed and audited against a concrete set of needs.
Changes:
- Introduces a 10-persona contributor taxonomy with per-persona “Shape / Needs / Loses them / Template fit”.
- Defines an “Applying the list” audit protocol for evaluating first-contact surfaces.
- Adds references tying this list to existing docs and GitHub issue-template surfaces.
|
|
||
| ## Cadence | ||
|
|
||
| Per `docs/FACTORY-HYGIENE.md` row #44, this file is a |
There was a problem hiding this comment.
P1: docs/FACTORY-HYGIENE.md row #44 is currently the supply-chain safe-patterns audit, not the cadence-history/fire-history requirement. This sentence should cite the correct hygiene row (looks like row #47 "Cadence-history tracking hygiene") or otherwise reword to avoid a wrong row-number reference.
| Per `docs/FACTORY-HYGIENE.md` row #44, this file is a | |
| Per `docs/FACTORY-HYGIENE.md`, this file is a |
| When a contributor's needs go unmet (we learn this | ||
| from dropped issues, closed-without-landing PRs, | ||
| follow-up maintainer feedback, or agent retry loops), | ||
| log | ||
| the failure at | ||
| `docs/research/contributor-friction-log.md`. If the | ||
| log does not exist yet, the first friction report | ||
| creates it. The log feeds the next template-audit | ||
| cycle. |
There was a problem hiding this comment.
P1: This doc directs readers to log issues at docs/research/contributor-friction-log.md, but that file does not currently exist in-tree. Consider adding a stub file (with a short schema/append format) in this PR, or adjust the text to explicitly instruct creating it (and link to a template location) so the path reference is not a dead end.
Summary
Adds `docs/CONTRIBUTOR-PERSONAS.md` — 10 named contributor archetypes (human + AI) for Zeta's first-contact surfaces (issue templates, README, CONTRIBUTING.md, SECURITY.md, AGENTS.md).
Companion to:
Contributor-personas answer: "who just showed up wanting to contribute, and do we lose them in the first 90 seconds?"
Personas covered
Each has: Shape, Needs, Loses-them, Template-fit. The file ends with a "Applying the list" protocol for auditing any first-contact surface against named personas.
Drain discipline
Batch 6b of 6
Additive-only file landing. 6a (skill tune-ups) landed via #86. 6c will carry the remaining anchor-doc subset (AGENTS.md additive blocks, ROUND-HISTORY.md).
Test plan
🤖 Generated with Claude Code