Thank you for your interest in contributing to the organvm system.
All participants are governed by our Code of Conduct.
This organization covers: Cross-organ coordination, system-wide governance, umbrella documentation.
- Fork the target repository
- Create a branch (
feature/your-featureorfix/your-fix) - Follow existing code style — check each repo's README for stack details
- Write tests — maintain or improve coverage
- Submit a PR with clear description of changes
- Bug fixes with tests
- Documentation improvements
- Performance optimizations
- Security patches (see SECURITY.md)
- Feature proposals via Issues (discuss before implementing)
- System-wide governance changes, cross-organ coordination policies, umbrella documentation structure
Changes to meta-organvm affect all 7 organ organizations. Proposals require broader review and must demonstrate cross-organ impact.
- TypeScript: strict mode, named exports, async/await
- Python: PEP 8, type hints, f-strings
- Tests required for all new functionality
- Commit messages: imperative mood, <72 chars title
- README structure and depth must follow README standards
Look for issues labeled good first issue across our repositories:
- organvm-engine — CLI enhancements, type hints, shell completions
- organvm-corpvs-testamentvm — documentation, diagrams, concordance
- schema-definitions — schema examples, validation improvements
- system-dashboard — UI improvements, new routes
- organvm-ontologia — entity resolution, sensing layer
- GitHub Discussions — ask questions, propose ideas, share feedback
- Issues — report bugs or request features on the relevant repository
- Check existing documentation in each repo's README
Part of the organvm eight-organ system