> For the complete documentation index, see [llms.txt](https://docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intersectmbo.org/intersect-knowledge-base/legal/policies-and-conditions/intersect-internal-policies/intersect-open-source-antitrust-statement.md).

# Intersect Open-Source Antitrust Statement

An antitrust statement for an open-source organization is a declaration made by the organization to ensure that its activities, including collaboration and participation, adhere to antitrust laws and regulations. Antitrust laws are designed to promote fair competition, prevent anticompetitive behavior, and protect consumers and competitors from unfair business practices.

### Purpose:

The purpose of this antitrust statement is to affirm our dedication to upholding fair competition, preventing anticompetitive behavior, and avoiding any activities that may violate antitrust laws.

### Guiding Principles:

The Organization shall adhere to the following guiding principles:

1. No Anticompetitive Agreements: Participants are prohibited from engaging in discussions, agreements, or activities that restrain trade or harm competition.
2. No Exclusionary Practices: The Organization will not engage in any exclusionary practices that may disadvantage or discriminate against any participant or organization.
3. Transparency: All activities, discussions, and decisions will be transparent, and information will be made available to all interested parties to the extent possible.
4. Competitive Discussions: The Organization encourages participants to discuss matters related to the open source project, its development, and its ecosystem in a manner that is consistent with antitrust laws.

### Reporting Concerns:

If any participant believes that any discussion, activity, or decision within the Organization may raise antitrust concerns or violate antitrust laws, they are encouraged to report their concerns to the organization's leadership or legal counsel.

### Compliance with Laws:

The Organization expects all participants to be aware of and comply with antitrust laws and regulations that may apply to their activities within the organization.’

### Conclusion:

By adopting this antitrust statement, Intersect aims to foster a competitive and open environment that benefits the open-source community and adheres to legal and ethical standards.

Please note that it is essential to consult with legal counsel or experts in antitrust law to ensure that the statement aligns with the specific needs and legal requirements of your open source organization and the jurisdictions in which it operates. Antitrust laws can vary by region, and legal advice is critical to navigate this complex area of law. Intersect encourages all participants to seek their own legal counsel if they have any questions or concerns regarding antitrust laws.

\\


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.intersectmbo.org/intersect-knowledge-base/legal/policies-and-conditions/intersect-internal-policies/intersect-open-source-antitrust-statement.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.