Governance

OSCO is open and community-driven.

Decision Model

• Routine fixes: maintainer review and merge
• Semantic model changes: proposal-first discussion (issue or RFC-style design note)
• Breaking changes: explicit maintainer approval and documented migration impact

Maintainer Responsibilities

• Preserve capability ID stability
• Enforce schema/model correctness
• Maintain mapping quality expectations
• Communicate release and deprecation policy changes

Contributor Expectations

• Use evidence-based technical rationale
• Keep changes scoped and reviewable
• Run local validation and CI-equivalent checks before PR