Governance
Cratis is an open-source project, but not every decision belongs in the same channel. Small fixes can move directly through issues and pull requests. Larger design choices need discussion, context, and a durable record.
Decision path
Section titled “Decision path”| Change | Path |
|---|---|
| Small documentation fix | Pull request or documentation issue |
| Reproducible bug | Product issue, then pull request |
| Small feature | Product issue with motivation and expected behavior |
| Cross-product design | Discord discussion, then a durable GitHub issue or design note |
| Architectural decision later work must follow | A decision record in the owning repository, where it keeps one |
| Breaking change | Design discussion, migration notes, release note, and documentation update |
| Security fix | Private report first, public disclosure only after coordination |
How proposals become work
Section titled “How proposals become work”- Start with the problem, not the implementation.
- Discuss early in Community and help when the shape is unclear.
- Capture actionable work in the repository that owns the behavior.
- Link related docs, examples, issues, and pull requests.
- Update documentation and release notes when behavior changes.
Where decisions are recorded
Section titled “Where decisions are recorded”Some repositories keep decision records, for example Chronicle and Arc in a top-level decisions/ folder and Components under Documentation/decisions/. Where a repository has one, a decision that later work must obey is written there and reviewed like any other change. Where it does not, the issue or pull request that settled the question is the record. Check the owning repository before assuming either.
Maintainer judgment
Section titled “Maintainer judgment”Maintainers may ask for narrower scope, more context, tests, documentation, migration guidance, or a different product boundary. The goal is to keep Cratis coherent across Chronicle and its clients, Arc, Components, the CLI, Fundamentals, the tools, and the docs. Review happens on a best-effort basis; there is no guaranteed turnaround for issues or pull requests.
Community standards
Section titled “Community standards”The Code of Conduct applies across repositories, Discord, issues, pull requests, and project spaces. Security reports use the private process on Security.