We Planned for 10 Ambassadors. We’re Welcoming 138.
🔗 **Source:** [We Planned for 10 Ambassadors. We’re Welcoming 138.](https://aaif.io/blog/we-planned-for-10-ambassadors-were-welcoming-138/)
> [!note]+ Document Notes
> tags: [ambassador-program, agentic-ai, open-source, developer-community, community-building, global-community]
> author: [MISSING]
> source: AAIF (Agentic AI / AI alliance foundation)
> reference: https://aaif.io/blog/we-planned-for-10-ambassadors-were-welcoming-138/
> date created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
>
> # 🏷️ Title: We Planned for 10 Ambassadors. We're Welcoming 138.
>
<!-- deep-read:sections start -->
## 🧭 Table of Contents
- [📝 Summary](#-summary)
- [📖 Main Content](#-main-content)
- [🗒️ Notes](#️-notes)
- [📚 References](#-references)
- [🗣️ Paraphrase](#️-paraphrase)
- [📰 Newsletter](#-newsletter)
- [✅ Action Items](#-action-items)
- [🧪 Hypotheses](#-hypotheses)
- [📊 Methodology](#-methodology)
- [❓ Questions](#-questions)
- [🔮 Future Research](#-future-research)
- [💡 Implications](#-implications)
- [🧠 Learning Styles Assessment](#-learning-styles-assessment)
- [📊 Accessibility Assessment](#-accessibility-assessment)
- [🌍 DEIB Assessment](#-deib-assessment)
- [✅ Logical Validity](#-logical-validity)
- [🛡️ DARVO Analysis](#-darvo-analysis)
- [🎯 Conclusion](#-conclusion)
### 🔗 References
- [AAIF Ambassadors directory](https://aaif.io/ambassadors)
- [AAIF blog post](https://aaif.io/blog/we-planned-for-10-ambassadors-were-welcoming-138/)
## 📝 Summary
- AAIF opened applications for its first Ambassador cohort expecting to pick about 10 people for a pilot. More than 1,000 developers applied.
- The volume, quality, and geographic spread pushed AAIF to drop the planned cap and accept everyone who cleared the bar: 138 ambassadors across 41 countries and 6 global regions.
- Key stakeholders: AAIF, the 138 ambassadors, the AAIF-hosted open source projects (MCP, AGENTS.md, goose, agentgateway), and the developers those ambassadors will teach and support.
- Risks and tradeoffs: scaling 14x past the planned pilot strains onboarding and support capacity; the monthly-contribution commitment needs tracking; "accept everyone who cleared the bar" shifts cost from selection to ongoing program operations.
- Bottom line: demand to help others build with agentic AI is far larger than AAIF expected, so it scrapped an arbitrary ceiling and built a global community it didn't plan for.
## 📖 Main Content
- The core argument is simple: an arbitrary headcount cap made sense as a pilot-risk control, but a 1,000+ applicant pool with high quality and global breadth made the cap the wrong tool. AAIF chose a quality bar over a quantity ceiling.
- Context on terms: an "ambassador program" is a community-relations structure where vetted volunteers represent an org or its projects in public (talks, writing, teaching, direct contribution). The AAIF-hosted projects named — MCP (Model Context Protocol), AGENTS.md (a convention for agent instructions in repos), goose (an open source AI agent), agentgateway — sit in the agentic-AI tooling space.
- The commitment is concrete: one public contribution per month that's "useful to a real developer." 82% of ambassadors opted to represent multiple projects, which AAIF frames as a feature because it surfaces cross-project workflows.
- A stated rationale: open source depends on teaching work that lacks a formal home (personal blogs, local meetups, late-night Discord answers). The program exists to recognize and sustain that labor.
- Uncertainties / contested claims: "cleared the high bar we'd set" is asserted, not defined — the selection criteria aren't published here. The monthly-contribution commitment has no described enforcement or measurement mechanism in this post. "Useful to a real developer" is subjective. None of these are flaws for an announcement, but they're open questions for anyone evaluating program rigor.
### 🗒️ Notes
- Planned target: ~10 ambassadors for a pilot — start small, learn what support is needed, build from there.
- Actual applicant pool: more than 1,000 people worldwide. Quantity AND quality/geographic breadth both cited as the reason for the rethink.
- Decision: forego the "arbitrary ceiling," accept everyone who genuinely cleared the bar. Result: 138 ambassadors.
- Geography: 41 countries across Africa, Asia-Pacific, Europe, Latin America, the Middle East, and North America (6 regions).
- Projects represented: MCP, AGENTS.md, goose, agentgateway, plus future ones. 82% opted into multiple projects.
- Commitment: one public contribution every month useful to a real developer. Forms vary — speaking, blogging, teaching, direct contribution.
- Framing: the program recognizes teaching/contribution work that "doesn't always have a formal home."
- Next steps: onboarding details going out now; profiles will go live at aaif.io/ambassadors. Applications stay rolling; next official intake January 2027.
## 📚 References
- [AAIF Ambassadors directory](https://aaif.io/ambassadors)
- [Model Context Protocol (MCP)](https://modelcontextprotocol.io)
- [AGENTS.md](https://agents.md)
- [goose (Block's open source AI agent)](https://block.github.io/goose/)
- Prefer the primary AAIF post and the live ambassadors directory once published.
## 🗣️ Paraphrase
- AAIF expected to run a small 10-person pilot ambassador group, but over a thousand strong applications from around the world made that cap untenable, so it accepted all 138 who met its bar.
- These 138 span 41 countries and every major region; they'll each make a monthly public contribution to AAIF-hosted agentic-AI projects, and the program's point is to recognize and sustain the often-invisible teaching work open source runs on.
## 📰 Newsletter
- Quick community win worth a look: AAIF planned a 10-person ambassador pilot for its agentic-AI open source projects and got 1,000+ applicants — so it tossed the cap and welcomed 138 ambassadors across 41 countries. If your WordPress or open source project has ever debated "how many contributors should we onboard," this is a clean case study in letting a quality bar replace an arbitrary headcount. Each ambassador commits to one useful public contribution a month — the kind of teaching work (blogs, meetup talks, late-night Discord help) that rarely gets formal recognition. Looking for a speaker or guest writer on agentic AI? Profiles land at [aaif.io/ambassadors](https://aaif.io/ambassadors). Next intake: January 2027.
## ✅ Action Items
#### DevRel
- Developer advocacy: study the 1,000→138 conversion as a model for ambassador-program sizing and pilot design.
- Education: note the "one useful contribution per month" cadence as a lightweight, trackable commitment structure.
- Developer experience: watch how AAIF onboards 138 at once — capture what docs/templates scale and what breaks.
- Community management: model the "quality bar over headcount cap" decision for your own contributor intake.
#### OSPO
- Policy & Governance: document selection-bar criteria explicitly to make "everyone who cleared the bar" auditable.
- Community Engagement: track cross-project participation (82% multi-project) as an ecosystem-health signal.
#### Community
- Maintainers: borrow the recognition framing — name and sustain teaching work that "doesn't have a formal home."
- Contributors: offer a clear monthly-contribution path as an onboarding scaffold.
#### WordPress
- Community: compare AAIF's global-region spread against WordPress contributor-program geographic coverage.
- Training: evaluate a monthly public-contribution cadence for Learn/Training contributor tracks.
#### The WPCC
- Programs: consider an ambassador/fellowship track with a quality bar rather than a fixed cap.
### FAIR
- Policies and covenants: publish ambassador selection criteria and contribution definitions for transparency and anti-capture.
## 🧪 Hypotheses
- Replacing a fixed headcount cap with a published quality bar increases cohort size without lowering average contribution quality.
- Ambassadors representing multiple projects produce more cross-project integration content than single-project ambassadors.
- A "one public contribution per month" commitment yields higher sustained participation than open-ended volunteer asks.
- Geographic breadth in the first cohort predicts faster regional community growth in those 41 countries.
- Public recognition of informal teaching work increases the volume of that work being produced.
### 📊 Methodology
- Compare contribution quality scores (peer/maintainer rated) between capped pilot programs and quality-bar programs.
- Track per-ambassador monthly contribution counts and forms over 12 months; segment by single- vs multi-project.
- Survey ambassadors at intake and at 6/12 months on participation drivers and friction.
- Geo-tag downstream community events/contributions to test regional growth correlation.
### ❓ Questions
- What specifically defined the "high bar," and how was it scored across 1,000+ applications?
- How will the monthly-contribution commitment be measured and what happens when it's missed?
- Can AAIF actually support 138 ambassadors with infrastructure built for ~10?
- What's the retention target, and what counts as a successful first cohort?
### 🔮 Future Research
- Longitudinal study of ambassador-program scaling: where does "accept everyone who clears the bar" break operationally?
- Comparative analysis of agentic-AI open source community growth vs. prior developer-ecosystem programs.
- Whether multi-project ambassador overlap measurably accelerates cross-project tooling adoption.
### 💡 Implications
- Practice: pilot caps may be the wrong default when demand is unknown; a quality bar scales with demand.
- Policy: scaling 14x past plan forces real investment in onboarding, mentorship, and contribution tracking.
- Education: informal teaching is a recognizable, fundable category of open source labor.
- Funding models: ambassador recognition without stipends is a low-cost lever, but sustainability is the open question.
### 🧠 Learning Styles Assessment
- Reading level estimate: roughly grade 8–10 (Flesch-Kincaid Grade estimate); short sentences, plain vocabulary, conversational tone.
#### 👀 Visual learners
- Present: headline numbers (10, 138, 1,000, 41, 6, 82%) that read like a visual story.
- Improve: a world map of the 41 countries, a before/after "planned vs actual" chart, a project-overlap diagram.
#### 🔊 Aural learners
- Present: none.
- Improve: a 2-minute audio summary or narrated version of the announcement.
#### 🗣️ Verbal learners
- Present: relatable analogy ("Discord answers at 11pm") and plain framing of the decision.
- Improve: define MCP, AGENTS.md, goose, agentgateway inline for newcomers.
#### 🧩 Kinesthetic learners
- Present: a clear call to action (reach out to an ambassador; apply next intake).
- Improve: a checklist for "how to become an ambassador" and an application walkthrough.
#### 🧠 Logical learners
- Present: a clean cause→effect chain (cap → flood of applicants → drop cap).
- Improve: a timeline and a criteria table for the "high bar."
#### 🧑🤝🧑 Social learners
- Present: explicit invitation to connect with ambassadors and the community framing.
- Improve: links to a community forum or Discord for the cohort.
#### 🧘♀️ Solitary learners
- Present: self-directed next step (apply on rolling basis).
- Improve: a self-assessment for whether you'd clear the bar.
#### 🌿 Naturalistic learners
- Present: none.
- Improve: frame the cohort as an "ecosystem" with growth/lifecycle language.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: not assessable from plain text; the post uses clear section headers ("A cohort we didn't plan to build," "What they're actually committing to").
- Improve: confirm those headers are real heading elements with logical order on the live page.
#### Keyboard navigation
- Present: not applicable to source text.
- Improve: verify the live page links (aaif.io/ambassadors) are keyboard reachable with visible focus.
#### Contrast and readability
- Present: not assessable from text.
- Improve: confirm 4.5:1 text contrast on the published post.
#### Text resizing and reflow
- Present: not applicable to source text.
- Improve: confirm reflow at 200% zoom on the live page.
#### Media and captions
- Present: no media in the source text.
- Improve: if a world map or chart is added, supply alt text and a data table.
#### Forms and interactions
- Present: the application form is referenced but not shown.
- Improve: ensure the ambassador application has labels, inline validation, and adequate target sizes.
#### Standards reference
- Map live-page gaps to WCAG 2.2 AA (1.4.3 contrast, 2.4.6 headings/labels, 1.4.10 reflow).
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: strong — 41 countries across 6 regions explicitly named, including Africa, Asia-Pacific, Latin America, the Middle East.
- Improve: multilingual versions of the post and ambassador materials; regional spotlights.
#### Inclusive language
- Present: plain, welcoming, gender-neutral language ("people," "developers," "everyone who genuinely cleared the bar").
- Improve: define jargon (MCP, agentgateway) so non-experts aren't excluded.
#### Neurodiversity support
- Present: short paragraphs, consistent structure, clear section breaks.
- Improve: a TL;DR is present; add a bulleted key-facts box.
#### Representation
- Present: emphasis on geographic and contribution-style diversity (speaking, blogging, teaching, contributing).
- Improve: once profiles are live, ensure visible representation across roles, regions, and experience levels.
#### Psychological safety
- Present: respectful, encouraging framing that values informal/invisible labor.
- Improve: publish a code of conduct and clear support/escalation paths for the cohort.
### ✅ Logical Validity
#### Strong reasoning
- Inductive: the 1,000+ applicant pool is read as evidence of broad demand ("The application pool was telling us something") — a reasonable inference from a large, high-quality, globally distributed sample.
- Causal: cap → impossible-to-choose-from-talented-pool → drop the cap. The chain is coherent and the premises (volume, quality, breadth) are stated.
- Clarify further: publishing the bar's criteria would let readers verify "everyone who genuinely cleared the high bar" rather than take it on trust.
#### Fallacies
- Mild appeal to popularity: "huge demand" inferred from application count assumes applicants ≈ committed contributors; applying is cheaper than sustaining monthly work. Fix: report retention/contribution data over time, not just intake numbers.
- No serious fallacies; this is an announcement, not an argument under dispute.
#### Tone of voice
- Enthusiastic, candid, and self-aware ("We got the message loud and clear"; "A cohort we didn't plan to build"). Reads as humble-confident rather than promotional.
### 🛡️ DARVO Analysis
- Not applicable to this source. It's a celebratory program announcement with no accusation, defense, or conflict — there's nothing to deny, no one to attack, and no victim/offender dynamic to reverse.
## 🎯 Conclusion
- Bottom line: AAIF planned a 10-person ambassador pilot, met 1,000+ applicants, and replaced an arbitrary cap with a quality bar — landing 138 ambassadors across 41 countries committed to monthly public contributions for its agentic-AI open source projects.
- Next steps for readers: if you need a speaker, writer, or guest on agentic AI, watch [aaif.io/ambassadors](https://aaif.io/ambassadors) and reach out. If you want in, applications are rolling with the next official intake in January 2027. If you run a contributor program, study the cap-vs-quality-bar decision as a sizing model.
## 🔄 Refactor Appendix — We Planned for 10 Ambassadors. We're Welcoming 138.
> Density: 2–5 Literature atoms (H3), 0–3 Permanent candidates (H4).
> Defaults: 3 Literature, 1 Permanent. Resonance filter: if you can't
> articulate in one line why a claim matters, drop it.
### 📚 Literature Atoms (H3)
#### [H1] Demand to help others build with agentic AI is large
> [!quote]
> There's a huge demand to not only build with agentic AI, but to help others build with it too.
**Context & use**:
- Mid-post, AAIF's read of the 1,000+ applicant pool.
- Reframes a recruiting surprise as a signal about ecosystem-level teaching demand, not just builder demand.
**Tags**: #xref
<!-- atomicity: 1 idea ✓ -->
#### [H2] Open source teaching work lacks a formal home
> [!quote]
> They show up in personal blogs, local meetup talks, Discord answers at 11pm.
**Context & use**:
- Near the end, the program's stated reason for existing.
- Names invisible/informal labor that sustains open source and frames recognition as the intervention.
**Tags**: #xref #aphorisms
<!-- atomicity: 1 idea ✓ -->
### 🧠 Permanent Candidates (H4)
#### [P1] A quality bar scales with demand where a headcount cap fails
**Claim** (one sentence, Courtney's voice): When demand is uncertain, a published quality bar adapts to the real applicant pool better than an arbitrary headcount cap.
**Evidence pointer**: [[#H1]]
**Scope & conditions**: Holds when you can support variable cohort size; breaks when onboarding/support capacity is hard-fixed.
**Links**:
- [[Community program design]] — because applies-in contributor onboarding
- [[Pilot sizing]] — because contrasts on fixed-vs-adaptive limits
<!-- atomicity: 1 idea ✓ -->
### ✏️ Fleeting Queue
- [F1] Watch how AAIF operationally supports 138 ambassadors built for ~10 — capture what scales. — aaif.io/ambassadors #fleeting #inbox
### → Things 3 (max 2 actions)
- [ ] Check aaif.io/ambassadors once profiles go live and note program structure — #things
<!-- deep-read:sections end -->
📄 **Full text:** [[Full Document Contents/Articles/We Planned for 10 Ambassadors. We’re Welcoming 138..md|We Planned for 10 Ambassadors. We’re Welcoming 138. by aaif.io]]
## Highlights
- Trying to choose only 10 people from such a talented pool was pretty much impossible. The application pool was telling us something. There’s a huge demand to not only build with agentic AI, but to help others build with it too. ([View Highlight](https://read.readwise.io/read/01kvwx4ab48qcnaj9p2kwsx37n))
- Note: 1,000+ applicants reframed as ecosystem-level demand to teach agentic AI, not just build with it.
- Tags: ambassador-program, atom/literature/h1
- Open source depends on people who teach. Those contributions don’t always have a formal home. They show up in personal blogs, local meetup talks, Discord answers at 11pm. The Ambassador Program exists to recognize that work and make it easier to sustain. ([View Highlight](https://read.readwise.io/read/01kvwx4cfp7f3t93cbgqgjxd5n))
- Note: The program's reason for existing: recognize and sustain the informal, often-invisible teaching labor open source depends on.
- Tags: atom/literature/h2, community-building