Governance

Maintainers

Repository maintainers merge changes, manage releases, and steward the documented compatibility boundary. Maintainer access is granted or removed by the sponsoring organization through its normal repository-administration process. The maintainer and security owner is Nirmit Desai (@nirmit-desai-aintropy), who is also the sole entry in .github/CODEOWNERS. Additional maintainers are recorded there and in this section when they are added.

Decisions

Ordinary changes are proposed through pull requests and accepted after tests, documentation, and compatibility impact have been reviewed. Significant public-API, artifact-format, security, dependency, or roadmap changes should begin with an issue or design proposal so tradeoffs are recorded before implementation.

Maintainers seek technical consensus. When consensus is not possible, the maintainers responsible for the affected area decide and record the rationale in the issue or pull request. Decisions must follow the compatibility policy, security policy, and published deprecation process.

Releases and security

Only maintainers authorized for the protected PyPI environment may publish. Releases use the documented CI and trusted-publishing workflow; contributors should never upload artifacts directly. Undisclosed vulnerability handling stays private under SECURITY.md.

Changes to governance

Governance changes use the same public pull-request process. They should identify affected roles, transition steps, and any new private contact or approval requirements without exposing sensitive information.