Declare organization-default ownership and review continuity

[cervantesh]

Maturity context

• Project maturity: developing (51/100)
• Dimension: release_maintenance
• Priority: high

Evidence

• No CODEOWNERS file exists
• Repository contributors API lists one contributor
• Main has no branch protection or repository ruleset

Scope

• Add CODEOWNERS coverage for profile, policy, issue-form, and pull-request-template files.
• Document a primary and backup maintainer role rather than personal-only ownership.
• Define required review for security, conduct, and contribution-policy changes.
• Document a lightweight deprecation and change-announcement path for organization defaults.

Acceptance criteria

• Every tracked community-health file resolves to an owner pattern.
• At least two maintainable roles or accounts cover policy-critical paths.
• Changes to SECURITY.md and CODE_OF_CONDUCT.md require designated review through a ruleset or documented enforced control.
• Consumers have a documented place to learn about material default changes.

Help wanted

Documentation and CODEOWNERS setup are approachable; organization owners must select backup ownership and enforcement policy.

---

Generated from the repository maturity assessment dated 2026-07-11. Do not include credentials, customer data, or local-only files in public discussion.

[cervantesh]

Completed by PR #9. The merged governance change adds portable issue forms, private security reporting and response targets, CODEOWNERS/continuity policy, read-only adoption auditing, a maintained public project directory, and documented inheritance/override verification.