Governance and review

Repository-wide roles and decision procedures are recorded in GOVERNANCE.md and maintainers in MAINTAINERS.md. Follow the code of conduct in CODE_OF_CONDUCT.md.

Open a focused pull request with the problem, public-contract impact, implementation notes, verification commands and results, fixture provenance, and known limitations. Reviewers should be able to identify what happens at unsupported boundaries without reading unrelated code.

Report vulnerabilities through the process in SECURITY.md, not in a public issue. Licensing notices and attribution belong in NOTICE; do not copy third-party code or datasets without recording their license and source.