This policy explains how reviewers can receive public acknowledgement for useful feedback on the Agentic Enterprise Readiness Profile.
The goal is to recognize helpful public review without implying endorsement, adoption, certification, AAIF status, Linux Foundation status, employer approval, or maintainership.
A reviewer can be acknowledged only when all of these are true:
- The reviewer left a useful public issue, discussion comment, pull request, or route signal.
- The feedback is linked from the route signal ledger, contribution ledger, release note, or review issue.
- The reviewer explicitly agrees to public acknowledgement.
- The acknowledgement text avoids employer endorsement unless the employer has explicitly authorized it.
- The acknowledgement does not imply project adoption, foundation status, or production approval.
| Form | Use When | Example |
|---|---|---|
| Release note acknowledgement | A release includes a reviewer-driven correction. | Thanks to @reviewer for flagging the route ambiguity in issue #N. |
| Ledger acknowledgement | A signal is useful but no patch is needed. | Link the signal in docs/ROUTE_SIGNAL_LEDGER.md. |
| Issue acknowledgement | A reviewer leaves a useful short signal. | Reply once with the response protocol shape. |
| Recurring reviewer note | A reviewer provides repeated public feedback and consents. | Mention the lane and public evidence links, not employer endorsement. |
Use this when asking for acknowledgement consent:
Would you like to be publicly acknowledged for this feedback in the release note or route signal ledger?
If yes, I will acknowledge your GitHub handle only and will not imply employer endorsement, adoption, certification, AAIF status, or Linux Foundation status.
Do not acknowledge:
- private feedback without explicit public consent
- private employer or customer information
- security-sensitive detail
- inferred approval
- likes, stars, follows, or private messages
- unmerged PRs as accepted contribution
- adoption unless the maintainer explicitly opts in through a public link
If a reviewer asks to revise or remove acknowledgement, do it in the next small documentation patch and cite the correction as an acknowledgement hygiene update.
If acknowledgement creates endorsement confusion, replace it with a neutral evidence link or remove it.
Reviewer acknowledgement is gratitude for public technical feedback. It is not:
- maintainership
- project adoption
- AAIF endorsement
- Linux Foundation endorsement
- employer endorsement
- security certification
- production-readiness approval