Governance

Versioning

AI-Me uses semantic-style versioning:

• 0.x — Draft versions. Breaking changes are possible between drafts.
• 1.0 — First stable release. Backwards-compatible changes only after this point.
• 1.x — Additive changes (new optional fields, extensions).
• 2.0 — Breaking changes, if ever needed.

The schema_version field in every vendor card identifies which version the document conforms to.

Proposing changes

Changes to the specification follow this process:

1. 1. Open an issue. Describe the problem, use case, or enhancement on GitHub. Include examples.
2. 2. Discussion. The community and maintainers discuss the proposal. Expect questions about backwards compatibility, scope, and alternatives.
3. 3. Pull request. If the proposal gains consensus, submit a PR with changes to the spec markdown, JSON Schema, and any affected examples.
4. 4. Review. At least two maintainers must approve. For breaking changes, broader consensus is required.
5. 5. Merge and release. Approved changes are merged and included in the next version.

Decision making

During the 0.x draft phase, the project maintainers make final decisions on spec changes, guided by community feedback. The goal is to move quickly while gathering real-world implementation experience.

Before the 1.0 release, a more formal governance structure will be established, likely including an advisory group of early adopters and implementers.

Extension policy

The spec allows custom fields via namespaced prefixes (e.g. x_mcp, x_mycompany). Extensions don't require approval — just follow the naming convention. Popular extensions may be promoted to official recommended fields in future versions.