Governance and decisions

Current responsibility

The repository owner accepts product scope and release decisions. Contributors own the implementation and evidence they submit; independent reviewers own their recorded labels and review scope. Public source, decisions and RFCs make those responsibilities inspectable. A proposed owner lane is not a claim that a volunteer has accepted an assignment.

• Owners and open needs
• Recorded decisions

Changing the standard

Taxonomy changes use public RFCs, evidence and the governance document’s minimum 14-day comment period. Version the specification and detector behavior; do not silently change old tag meanings. Conformance decisions affecting a commercially interested maintainer require recusal under the published governance rule.

• Governance source
• Public proposals

Foundation and certification target

The governance document targets an independent foundation for the specification/taxonomy and certification mark, with implementations free to compete. That is a structure to establish, not an assertion that a legal entity, asset assignment or accreditation already exists. Tag-specific testing is active work; formal institutional certification requires its own completed governance and evidence.

Keep a copy

Download plain text · Version 1.1. Read all public policies. Previous version · 1.0.

Changes are versioned in public source history.