How to contribute

Contributions are welcome under the Apache License 2.0.

Before you start

1. Read the introduction and architecture overview.
2. Search existing issues and pull requests on GitHub.
3. For API or event changes, edit files under contracts/ first.

Suggested workflow

fork → branch → contracts (if needed) → code → tests → pull request

• Keep commits focused; Conventional Commits are appreciated (feat:, fix:, docs:, …).
• Do not commit secrets, personal data samples, or kubeconfigs.
• New dependencies must be MIT or Apache-2.0 (TP-2).
• Every module with executable source must stay ≥ 80% coverage.

Pull requests

• Describe the user-visible change and link any issue.
• Ensure GitHub Actions CI is green.
• Update docs when behaviour or deployment steps change.

Upstream organisations may use additional internal trackers; that is not required to contribute via GitHub. See Upstream maintainers.

Development details

See Development.