Skip to content

Contributing to ATP ​

ATP is an open specification. Community feedback is welcome and encouraged.

How to Propose Changes ​

  • Bug reports / clarifications — Open a GitHub Issue describing the problem and the section it affects.
  • Substantive changes — Open an Issue first to discuss the change before submitting a PR. For significant changes, describe the motivation and the impact on existing implementations.
  • Editorial fixes (typos, formatting, broken links) — PRs welcome directly.

What Makes a Good Proposal ​

  • Reference the specific section(s) affected.
  • Explain the problem the change addresses.
  • Consider the impact on existing ATP-compliant implementations.
  • If proposing new normative language (MUST/SHOULD/MAY), justify the compliance level.

Versioning ​

ATP follows semantic versioning. Breaking changes to normative requirements increment the minor version. Editorial changes do not increment the version.

Contact ​

For questions or private feedback, email atp@aiquilibria.com.

Code of Conduct ​

Be constructive and respectful. Disagreements about spec language are welcome; personal attacks are not.