-
Notifications
You must be signed in to change notification settings - Fork 92
Add an anonymized technical case-study contribution template #228
Copy link
Copy link
Open
Labels
area:communityContributor experience and community docsContributor experience and community docscommunity-ownedSuitable for community ownershipSuitable for community ownershipdocumentationDocumentation improvementsDocumentation improvementsgood first issueSafe for new contributors; docs, fixtures, examplesSafe for new contributors; docs, fixtures, examplespriority:p2Medium priorityMedium prioritystatus:readyReady for contributorsReady for contributors
Milestone
Description
Metadata
Metadata
Assignees
Labels
area:communityContributor experience and community docsContributor experience and community docscommunity-ownedSuitable for community ownershipSuitable for community ownershipdocumentationDocumentation improvementsDocumentation improvementsgood first issueSafe for new contributors; docs, fixtures, examplesSafe for new contributors; docs, fixtures, examplespriority:p2Medium priorityMedium prioritystatus:readyReady for contributorsReady for contributors
Contribution lane: documentation / community
Difficulty: good first issue
Ownership: community-owned
Priority: p2
Milestone: Public Proof & Adoption
Labels:
documentation,good first issue,area:community,community-owned,status:ready,priority:p2Baseline: agent-inspect@6.17.1 → 6.18.0 niche launch
Problem
There is no anonymized technical case-study template for partners to contribute public-safe proof narratives.
Why it matters
Public proof for 6.18 needs structured, anonymized write-ups — not raw traces.
Proposed scope
Out of scope
Suggested files
docs/community/templateAcceptance criteria
Validation commands
Privacy / network notes
Anonymized only. No customer data.
Contributor instructions
Good first docs. Comment first.
Maintainer-review boundary
Maintainers decide which case studies are featured publicly.