Skip to content

GOVERNANCE.md

Latest commit

 

History

History
23 lines (13 loc) · 1.39 KB

GOVERNANCE.md

File metadata and controls

23 lines (13 loc) · 1.39 KB
Raw

Governance

Method Forge uses maintainer-led, evidence-seeking governance.

Roles

  • Maintainers decide repository scope, merge changes, steward releases, and resolve taxonomy ownership.
  • Contributors propose corrections, additions, evidence, tests, and operational examples through pull requests.
  • Domain reviewers may be requested when a change depends on regulated practice, professional competence, jurisdiction, or specialized evidence.

Decision rules

Routine corrections are decided in pull requests. Durable decisions about taxonomy, repository architecture, licensing, compatibility, or governance require an ADR in docs/adr/.

For material disagreements, maintainers should prefer canonical scope, explicit boundary conditions, independent evidence, and reversible experiments over authority by popularity. Dissent and rejected alternatives should remain visible when they affect future selection.

Releases and status

Releases describe meaningful changes to the skill, taxonomy, catalogs, or source registry. A release does not certify that every external standard remains current; status dates remain local to the claims that were checked.

Changes to governance

Governance changes require a public pull request explaining the problem, alternatives, consequences, and transition. The repository owner retains final responsibility for GitHub permissions and legal obligations.