Code of Conduct
August 6, 2026 · View on GitHub
Our standard
This project is part of the U.S. General Services Administration's Technology Transformation Services (GSA TTS). We are committed to providing a welcoming, respectful, and professional environment for everyone who takes part in this community — maintainers, contributors, and members of the public.
We expect all participants to:
- Be respectful and professional in all interactions.
- Use clear, plain language and assume good faith.
- Give and accept constructive feedback gracefully.
- Focus on what is best for the community and the work.
The following behavior is not tolerated:
- Harassment or discrimination of any kind.
- Insulting, demeaning, or derogatory comments, or personal attacks.
- Publishing others' private information without their explicit permission.
- Sexualized language or imagery, or unwelcome sexual attention.
- Any other conduct that would reasonably be considered inappropriate in a professional setting.
Federal Community Addendum
This addendum supplements the standard above; it does not replace it. Where any conflict exists, the stricter expectation applies.
- Federal government community space. This is a U.S. federal government community. Participants include federal employees and contractors, and the professional conduct expectations of the federal workplace apply here.
- Critique the work, never the person. This repository maintains a contribution-quality bar. All feedback on a contribution — including quality and scope feedback — MUST target the artifact (a pull request, document, or idea), never the contributor or any aspect of their identity. Saying "this PR is out of scope for this repo" is fine; making it about the person is not.
- No sensitive data, anywhere. Do not post secrets, credentials, PII, CUI, or non-public government data in any issue, pull request, comment, example, or other interaction. This mirrors the repository's prohibited-content rules.
- Plain language and accessibility are community values. Prefer clear, plain-language communication and accessible content, consistent with GSA norms.
- Assume good faith. Most mis-scoped or low-quality contributions are honest mistakes, not bad-faith conduct. Quality and scope issues are handled through normal review — not through conduct enforcement. Reserve conduct enforcement for conduct, not for contribution quality or scope.
- Accountability is about the artifact, not the person. If a contributor cannot explain a change, that is feedback on the code — the change simply isn't ready to merge yet, and it is handled through normal code review. It is never misconduct and is never a judgment about the contributor as a person. Do not use an accountability or quality finding as a backdoor conduct sanction.
Scope
This Code of Conduct applies within all project spaces (issues, pull requests, comments, and other repository interactions) and when an individual is officially representing the project in public spaces.
Reporting and enforcement
To report a code-of-conduct concern for this project, email
agentic-coding@gsa.gov with the subject prefixed [CONDUCT]. Reports are
read by the repository maintainers, who will review and respond as promptly and
fairly as they reasonably can, and who will respect the privacy of the reporter.
Maintainers are responsible for clarifying and enforcing this standard and may take any action they deem appropriate, up to and including removing content or barring a participant from the project, in response to behavior that violates this Code of Conduct.
Security vulnerabilities are not handled here — see SECURITY.md for how to report those.