# Contributing

Thank you for your interest in the Infoconex AI Flywheel Specification.

This repository may accept issues, comments, corrections, examples, research notes, and proposed changes. Submitting a contribution does not make the contribution part of the official specification unless Infoconex accepts it.

## Specification Authority

Infoconex retains authority to define, revise, publish, interpret, and approve the Infoconex AI Flywheel Specification and its conformance requirements.

A proposal, issue, pull request, fork, discussion, or derivative document does not redefine the specification.

## What to Contribute

Useful contributions include:

- Corrections to wording, links, formatting, or diagrams
- Clarifying examples
- Implementation experience
- Conformance feedback
- Research sources and prior-art comparisons
- Questions about ambiguous requirements

## Contribution Terms

By submitting a contribution, you represent that you have the right to submit it and that it does not knowingly include material you do not have permission to contribute.

You are responsible for ensuring that your contribution can be submitted under these terms.

By submitting a contribution, you grant Infoconex a perpetual, worldwide, royalty-free, irrevocable, non-exclusive license to use, copy, edit, adapt, publish, distribute, display, sublicense, and incorporate the contribution into the Infoconex AI Flywheel Specification, documentation, examples, research, websites, and related materials.

Infoconex may accept, reject, revise, or remove contributions at its discretion.

## Attribution

Infoconex may acknowledge contributors in release notes, documentation, or project history, but acceptance of a contribution does not create joint ownership, editorial control, certification authority, or approval rights.

## Pull Requests

Pull requests should be focused and should explain the reason for the change.

Do not submit changes that:

- Rename or redefine the Infoconex AI Flywheel
- Change conformance requirements without explanation
- Add unsupported novelty claims
- Add material copied from another source without permission
- Remove copyright, license, trademark, or notice information

## Research Contributions

Research contributions should cite primary sources when possible and should distinguish evidence from interpretation.

Research notes support the specification but do not define it unless accepted into the official specification documents by Infoconex.

## Questions and Issues

Issues may be used to ask questions, suggest improvements, identify ambiguity, or propose new examples.

An issue discussion does not modify the specification unless the accepted change is incorporated into the repository by Infoconex.

## Related Documents

- [POLICIES.md](POLICIES.md) — Provides an overview of all project policy documents.
- [LICENSE.md](LICENSE.md) — Defines permitted use, restrictions, attribution, warranty, and reserved rights.
- [NOTICE.md](NOTICE.md) — Provides the public ownership, naming, and authority notice.
- [TRADEMARKS.md](TRADEMARKS.md) — Defines naming, branding, and conformance-claim rules.
- [GOVERNANCE.md](GOVERNANCE.md) — Defines specification authority, change process, and interpretation.
- [VERSIONING.md](VERSIONING.md) — Defines specification versions, draft status, releases, and conformance versioning.