Governance and decisions
AI TRUST ID · Version 1.1 · Effective 2026-10-08
Published by Michael R. McGuire, an individual, Michigan, United States.

Public evidence, accountable roles and the independence target.

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: /#teamwork
Recorded decisions: https://github.com/knwvmbrr/aitrust-id/blob/main/DECISIONS.md

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: /reference/governance-policy.md
Public proposals: https://github.com/knwvmbrr/aitrust-id/tree/main/rfcs

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.