Authority and nonauthority

What Standards Body can and cannot do

This page states the project's authority boundary exactly. It exists so that no reader has to infer the project's status from its name. Standards Body holds project-level authority over its own research and publications, and nothing more.

Current authority

Standards Body may:

• Conduct and publish research
• Develop frameworks
• Propose standards processes
• Create terminology and taxonomies
• Convene bounded discussions
• Invite review and contribution
• Correct and maintain its own publications
• Operate public knowledge infrastructure

Current nonauthority

Standards Body may not presently:

• Regulate an AI developer or deployer
• Require compliance
• Issue a legal license
• Certify a system
• Accredit an evaluator
• Grant regulatory approval
• Impose a public-law sanction
• Create a legal presumption of conformity
• Claim official international representation

Accordingly, Standards Body is not currently a regulator, governmental authority, certification body, accreditation body, formally recognized standards-development organization, evaluator approval body, or operating assurance institution. Nothing it publishes is a technical standard, a draft standard, a certification or accreditation criterion, a regulatory requirement, governmental guidance, a legal conclusion, a safety determination, an evaluator approval, or a statement of industry-wide consensus.

Future authority

Any future expansion of the project's role would require, at minimum:

• Legal form
• Governance
• Demonstrated competence
• Independence
• Security
• Funding
• Public-interest justification
• External review
• An amendment to the project identity
• Public notice

No institutional progression happens automatically, and no future role is implied by the project's name, publications, or identifiers.

Questions or concerns about status and authority: [email protected]