What is welcome
Bug reports, documentation feedback, setup problems, design questions, integration ideas, and security reports through the appropriate channels.
Community
Feedback-first contribution model
RuleOak is public so developers can inspect the code, run the examples, evaluate the governance model, and help shape the project through feedback.
Current contribution policy
Issues and Discussions are open. Pull requests are disabled for now
RuleOak Core is AGPL-licensed. Before accepting external code contributions, the project needs a clear contribution governance and licensing process. This protects users, contributors, and the long-term maintainability of the project.
What is not accepted yet
External code pull requests are not accepted yet. Future code contributions may require a Contributor License Agreement or equivalent contribution terms.
Useful feedback tasks
Useful ways to help without code
Test the quickstart
Run npm install and npm run launch. Open an issue if any step is unclear or fails on your platform.
Review the examples
Try the Technical Consultant and Research Brief demos. Tell us where the workflow, policy decision, or report output is confusing.
Improve docs by feedback
Open an issue for unclear wording, missing context, broken links, or setup instructions that need screenshots or examples.
Suggest integration patterns
Share how RuleOak should integrate with existing agent frameworks, Python tools, local LLM workflows, or developer automation stacks.
Challenge the governance model
Ask hard questions about policy, evidence, approval, audit, sandbox boundaries, and where human review should be required.
Report security privately
Do not open public issues for vulnerabilities. Use the security reporting process described in the repository.