Get involved
Contribute to ATAH
ATAH is developed in the open as a public-interest specification. The protocol improves through review, critique, reference implementations, and contributions from the people and institutions who will rely on it.
Like other open protocols — OAuth, MCP, Verifiable Credentials, ActivityPub — ATAH is shaped by its community of implementers and stakeholders. Whether you are an AI platform, a professional body, a regulator, an independent verifier, a professional, a researcher, or an individual technologist, your input is welcome.
Ways to participate
Review the specification
Read the spec, OpenAPI 3.1 contract, MCP tool definitions, and Charter. File issues for ambiguities, errors, or missing edge cases.
Read on GitHub →Propose changes
Open an issue or submit a pull request. Substantive protocol changes follow the published amendment process described in GOVERNANCE.md.
Read GOVERNANCE.md →Build a reference implementation
Implement the MCP or REST binding, prototype a Discovery client, or build a partner integration. Apache 2.0 — no licensing fee, no per-query fee at the protocol layer.
See the specification →Partner conversations
If you represent a regulator, professional body, AI platform, review platform, or independent verifier and want to discuss integration, reach out via the repository or press contact.
Press & contact →Raise a concern
Governance, conflict-of-interest, or commercial-neutrality concerns can be raised through the channels described in the Charter and GOVERNANCE.md.
Governance overview →Join the discussion
Discussion threads, RFC-style proposals, and working notes are tracked in the repository. Watch the repo to follow protocol development.
Open discussions →How decisions get made
ATAH is governed by a public Charter with eight entrenched commitments. Day-to-day protocol changes proceed through issues and pull requests; substantive changes — anything affecting the Charter, conformance, or commercial-neutrality guarantees — follow the supermajority amendment process documented in GOVERNANCE.md.
Conflicts of interest are disclosed. Related-party contributions are declared. No contributor — including the founder — has veto rights over Charter-protected commitments.