Contributing
Contribution guide
Contributing
Thank you for your interest in contributing to Project Grayscale.
What We Accept
| Area | Examples |
|---|---|
| Plugins & Connectors | GitHub, CRM, industry data connectors |
| Documentation | Fixes and improvements to docs/public/ |
| SDK Examples | Reference implementations using @grayscale/plugin-sdk |
| Bug Reports | Reproducible issues with clear steps |
What Requires Partnership
| Area | Contact |
|---|---|
| Bedrock / core runtime changes | Internal team only — Architecture Lock |
| Executive implementations | Partner Program |
| Enterprise features | sales@projectgrayscale.com |
Development Setup
See Quick Start and Installation.
Pull Request Guidelines
- Scope — One concern per PR
- Documentation — Update
docs/public/for user-facing changes - No secrets — Never commit
.env, credentials, or prompt packs - No internal docs — Do not add constitutional or certification material to
docs/public/ - Tests — Include tests for functional changes (when applicable)
Code of Conduct
All contributors must follow the Code of Conduct.
Community
Join the conversation via Community Guidelines.
Contact
- General: info@projectgrayscale.com
- Security: Report vulnerabilities via Contact