Add community engagement plan

kmishra1204 · kmishra1204 · commit f62c1ef27f4a · 2026-07-04T22:01:25.000-05:00
diff --git a/README.md b/README.md
@@ -61,6 +61,7 @@ Use these starter artifacts:
 - [Twelve month milestone plan](docs/TWELVE_MONTH_MILESTONE_PLAN.md)
 - [Spec change process](docs/SPEC_CHANGE_PROCESS.md)
 - [Security posture plan](docs/SECURITY_POSTURE_PLAN.md)
+- [Community engagement plan](docs/COMMUNITY_ENGAGEMENT_PLAN.md)
 - [AAIF proposal readiness self-audit](docs/AAIF_PROPOSAL_READINESS.md)
 - [AAIF portfolio recognition roadmap](docs/AAIF_PORTFOLIO_RECOGNITION_ROADMAP.md)
 - [Ecosystem contribution ledger](docs/ECOSYSTEM_CONTRIBUTION_LEDGER.md)
@@ -124,8 +125,8 @@ Bad use:
 
 ## Current Status
 
-Version: `0.5.13`
+Version: `0.5.14`
 
-Status: early OSS profile with public flagship examples, adopter guide, boundary template, scoring guide, ecosystem alignment brief, compatibility policy, adoption registry, external review guide, maintainer review kit, AAIF proposal readiness self-audit, ecosystem contribution ledger, security posture plan, and static docs portal.
+Status: early OSS profile with public flagship examples, adopter guide, boundary template, scoring guide, ecosystem alignment brief, compatibility policy, adoption registry, external review guide, maintainer review kit, AAIF proposal readiness self-audit, ecosystem contribution ledger, security posture plan, static docs portal, and community engagement plan.
 
 Next target: external technical feedback from agentic AI maintainers and AAIF/LF-style community forums.
diff --git a/ROADMAP.md b/ROADMAP.md
@@ -86,6 +86,10 @@
 
 - Add GitHub Pages-ready docs portal for profile discovery, reviewer entry points, SEO metadata, sitemap, and public review links.
 
+## 0.5.14
+
+- Add community engagement plan for AAIF/LF-style forum participation, GitHub review issues, adoption-trial outreach, human-reviewed posting, response cadence, and anti-endorsement boundaries.
+
 ## 0.6.0
 
 - Add first external adoption example if a maintainer opts in.
diff --git a/docs/AAIF_PROPOSAL_READINESS.md b/docs/AAIF_PROPOSAL_READINESS.md
@@ -71,7 +71,7 @@ The correct current route is external technical feedback, small upstream contrib
 | Portfolio recognition path | `docs/AAIF_PORTFOLIO_RECOGNITION_ROADMAP.md` | Partial | Turn the 90-day plan into external review and adoption evidence. |
 | Security posture | `SECURITY.md`, `docs/SECURITY_POSTURE_PLAN.md`, no sensitive runtime, dependency inventory | Partial | Enable OpenSSF Scorecard or Best Practices evidence after external review; keep current posture documented without certification claims. |
 | Website or docs portal | GitHub Pages static docs portal and repository docs | Ready | Keep the portal current with releases, reviewer links, and adoption evidence. |
-| Communications channels | GitHub issues and discussion | Partial | Keep Discord/LinkedIn activity as pointers back to GitHub evidence. |
+| Communications channels | GitHub issues, public review comments, docs portal, `docs/COMMUNITY_ENGAGEMENT_PLAN.md` | Partial | Use the engagement plan for AAIF Discord, LinkedIn, and forum posts; keep all outreach as pointers back to GitHub evidence. |
 | Trademark and account transfer | No decision | Missing | User decision required before any formal proposal. |
 | Contact and signatory | Not public | Missing | User decision required before any formal proposal. |
 
diff --git a/docs/COMMUNITY_ENGAGEMENT_PLAN.md b/docs/COMMUNITY_ENGAGEMENT_PLAN.md
@@ -0,0 +1,148 @@
+# Community Engagement Plan
+
+## Purpose
+
+This plan explains how the Agentic Enterprise Readiness Profile should participate in public OSS communities, AAIF/LF-style forums, GitHub issues, GitHub discussions, Discord, LinkedIn, and adjacent maintainer spaces.
+
+The goal is to earn technical feedback through useful artifacts and careful follow-up. The goal is not volume, promotion, endorsement, or artificial visibility.
+
+This is an independent OSS profile. It is not an Agentic AI Foundation project, not a Linux Foundation project, and not endorsed by either organization.
+
+## Engagement Principles
+
+- Lead with a concrete artifact, not a pitch.
+- Ask for technical correction before asking for attention.
+- Keep every public claim linked to repository evidence.
+- Prefer one thoughtful follow-up over repeated reminders.
+- Do not tag maintainers cold unless they already engaged or are the documented owner of the specific issue.
+- Treat open PRs and issues as work under review, not accepted contribution.
+- Keep AI-assisted drafting human-reviewed before posting.
+- Do not post private customer, employer, security, credential, or proprietary material.
+
+## Canonical Public Links
+
+Use these links as the public evidence spine:
+
+- Docs portal: https://kmishra1204.github.io/agentic-enterprise-readiness-profile/
+- Repository: https://github.com/kmishra1204/agentic-enterprise-readiness-profile
+- Current review issue: https://github.com/kmishra1204/agentic-enterprise-readiness-profile/issues/4
+- Current adoption trial issue: https://github.com/kmishra1204/agentic-enterprise-readiness-profile/issues/5
+- AAIF proposal readiness self-audit: https://github.com/kmishra1204/agentic-enterprise-readiness-profile/blob/main/docs/AAIF_PROPOSAL_READINESS.md
+- Ecosystem contribution ledger: https://github.com/kmishra1204/agentic-enterprise-readiness-profile/blob/main/docs/ECOSYSTEM_CONTRIBUTION_LEDGER.md
+- Security posture plan: https://github.com/kmishra1204/agentic-enterprise-readiness-profile/blob/main/docs/SECURITY_POSTURE_PLAN.md
+- Adoption trial protocol: https://github.com/kmishra1204/agentic-enterprise-readiness-profile/blob/main/docs/ADOPTION_TRIAL_PROTOCOL.md
+
+## Community Surfaces
+
+| Surface | Use | Frequency | Boundary |
+| --- | --- | --- | --- |
+| GitHub issues in this repository | canonical review, adoption trials, and change requests | ongoing | public, evidence-first |
+| GitHub discussions in this repository | open-ended ecosystem-fit questions | low cadence | no endorsement claims |
+| AAIF Discord or forum spaces | ask where the profile is useful or duplicative | one initial post, then only reply to engagement | no cold repetition |
+| LinkedIn | human summary that points back to GitHub evidence | occasional, after repository evidence exists | no inflated contributor or foundation claims |
+| Upstream AAIF-adjacent repositories | focused issues or PRs against existing maintainer needs | only when a concrete issue exists | no generic promotion |
+
+## First AAIF-Style Forum Ask
+
+Use this shape when posting in a community forum:
+
+```text
+I am looking for technical feedback, not endorsement.
+
+I maintain an independent OSS Agentic Enterprise Readiness Profile for repositories that need clearer evidence around AGENTS.md instructions, tool/action boundaries, human approval, identity assumptions, audit events, OSS fallbacks, security posture, and reproducible validation.
+
+Docs portal:
+https://kmishra1204.github.io/agentic-enterprise-readiness-profile/
+
+Review issue:
+https://github.com/kmishra1204/agentic-enterprise-readiness-profile/issues/4
+
+I am trying to understand whether this is useful beside AGENTS.md guidance, MCP/server readiness, agent gateway governance use cases, or whether it should stay independent. If there is a better existing effort, I would rather align than create another checklist.
+```
+
+## Response Rules
+
+When someone replies:
+
+- thank them once
+- restate the technical point in neutral language
+- open a follow-up issue only if a concrete change is needed
+- avoid debating endorsement, status, or affiliation
+- update the profile only when the feedback improves the artifact
+- link release notes when a feedback-driven change ships
+
+When nobody replies:
+
+- wait at least seven days before any follow-up in the same venue
+- improve the profile through examples, docs, or accepted upstream work instead of reposting
+- do not tag additional people just to force attention
+
+## Adoption Trial Rules
+
+An adoption trial must be opt-in.
+
+Do not list a repository as an adopter unless a maintainer publicly agrees.
+
+A valid trial can be small:
+
+- one read-only review comment
+- one branch with a boundary model
+- one draft `agentic-readiness.json`
+- one issue explaining why the profile is too heavy or not useful
+
+The adoption registry should record only public links and should distinguish trial, review, and adoption.
+
+## AI-Assisted Posting Boundary
+
+AI assistance may be used to draft a post, summarize feedback, or prepare release notes.
+
+Human review is required before posting.
+
+Do not use automation to:
+
+- mass-post across communities
+- scrape people for outreach
+- impersonate a maintainer
+- claim contributor credit before merge
+- infer endorsement from silence
+- paste private material into public issues or prompts
+
+## Quality Metrics
+
+Useful signals:
+
+- external reviewer comments
+- concrete issue feedback
+- accepted upstream PRs
+- profile changes based on public feedback
+- opt-in adoption trials
+- maintainers reusing an artifact
+
+Weak signals:
+
+- post impressions
+- generic likes
+- open PR count without reviews
+- reposting the same ask
+- self-claimed affiliation
+
+## Escalation Gates
+
+Do not prepare a formal AAIF project or working-group proposal until there is public evidence of:
+
+- external reviewers
+- opt-in adoption trials
+- maintainer engagement
+- a stable governance path
+- clear relation to AGENTS.md, MCP, agentgateway, or another existing effort
+- user decision on trademark, account, signatory, and contribution implications
+
+## Review Cadence
+
+Review this plan after:
+
+- two public external feedback signals
+- one adoption trial
+- a major release
+- a maintainer asks for different engagement behavior
+- a community moderator requests changes
diff --git a/docs/TWELVE_MONTH_MILESTONE_PLAN.md b/docs/TWELVE_MONTH_MILESTONE_PLAN.md
@@ -18,7 +18,7 @@ It is not a commitment from AAIF, the Linux Foundation, or any external maintain
 
 | Window | Milestone | Evidence required | Recognition posture |
 | --- | --- | --- | --- |
-| Month 1 | External trial readiness | Adoption trial protocol, issue template, public trial issue, release checklist, dependency inventory, security posture plan, docs portal | Independent review request only |
+| Month 1 | External trial readiness | Adoption trial protocol, issue template, public trial issue, release checklist, dependency inventory, security posture plan, docs portal, community engagement plan | Independent review request only |
 | Months 2-3 | First external feedback | At least two external comments, issues, or trial responses | Feedback received, not adoption |
 | Months 3-4 | Portfolio evidence expansion | Four more portfolio repositories with boundary models or readiness JSON | Testbed expansion, not production proof |
 | Months 4-6 | Spec stabilization pass | Spec-change process used for at least one profile or schema change | Process maturity, not standardization |
@@ -35,6 +35,7 @@ Current focus:
 - ask for external trials through issue `#5`
 - keep security posture, secret-safety, and release-gate evidence current
 - keep the docs portal current with release and review links
+- use the community engagement plan before any AAIF/LF-style forum post
 - avoid cold-tagging maintainers
 - convert feedback into profile changes
 
diff --git a/package.json b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "agentic-enterprise-readiness-profile",
-  "version": "0.5.13",
+  "version": "0.5.14",
   "private": false,
   "type": "module",
   "description": "Evidence-first readiness profile for agentic AI repositories.",
diff --git a/scripts/validate-readiness.mjs b/scripts/validate-readiness.mjs
@@ -21,6 +21,7 @@ const requiredDocs = [
   "docs/TWELVE_MONTH_MILESTONE_PLAN.md",
   "docs/SPEC_CHANGE_PROCESS.md",
   "docs/SECURITY_POSTURE_PLAN.md",
+  "docs/COMMUNITY_ENGAGEMENT_PLAN.md",
   "docs/SCORING_GUIDE.md",
   ".github/ISSUE_TEMPLATE/adoption_review.md",
   ".github/ISSUE_TEMPLATE/adoption_trial.md",
@@ -71,6 +72,7 @@ for (const snippet of [
   "https://kmishra1204.github.io/agentic-enterprise-readiness-profile/",
   "SECURITY_POSTURE_PLAN.md",
   "AAIF_PROPOSAL_READINESS.md",
+  "COMMUNITY_ENGAGEMENT_PLAN.md",
   "not an Agentic AI Foundation project"
 ]) {
   assert(siteText.includes(snippet), `Docs portal missing snippet: ${snippet}`);
diff --git a/site/index.html b/site/index.html
@@ -62,7 +62,7 @@ <h1>Make agentic AI repositories easier to review, trust, and extend.</h1>
           <img class="readiness-flow" src="./assets/readiness-flow.svg" alt="Five connected readiness levels from scaffold to foundation candidate.">
           <div class="signal-row">
             <span>Current release</span>
-            <strong>v0.5.13</strong>
+            <strong>v0.5.14</strong>
           </div>
           <div class="signal-row">
             <span>Validation</span>
@@ -145,6 +145,10 @@ <h2>Start from the artifacts reviewers usually ask for first.</h2>
             <span>Security</span>
             <strong>Posture Plan</strong>
           </a>
+          <a href="https://github.com/kmishra1204/agentic-enterprise-readiness-profile/blob/main/docs/COMMUNITY_ENGAGEMENT_PLAN.md">
+            <span>Community</span>
+            <strong>Engagement Plan</strong>
+          </a>
           <a href="https://github.com/kmishra1204/agentic-enterprise-readiness-profile/blob/main/docs/MAINTAINER_REVIEW_KIT.md">
             <span>Maintainers</span>
             <strong>Review Kit</strong>

Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`{`
`2`	`2`	`"name": "agentic-enterprise-readiness-profile",`
`3`		`- "version": "0.5.13",`
	`3`	`+ "version": "0.5.14",`
`4`	`4`	`"private": false,`
`5`	`5`	`"type": "module",`
`6`	`6`	`"description": "Evidence-first readiness profile for agentic AI repositories.",`