> For the complete documentation index, see [llms.txt](https://guide.techfleet.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.techfleet.org/policies/community-collective-agreement/reporting-and-resolving-issues.md).

# Reporting and Resolving Issues

## Reporting Issues

1. Outside of clear Violations, please explore tension before reporting Tech Fleet-related issues.
2. Please report clear violations as soon as possible, along with any persistent concerns which develop regarding our community, this Collective Agreement or acts of [Enforcement](/policies/community-collective-agreement/community-enforcement.md).
3. Report issues to <safespace@techfleet.org> and/or submit a ticket in support Discord. If you would like to report something anonymously, [See the details here](/community-code-of-conduct/code-of-conduct-and-anti-harassment-policy.md).
   1. Report exactly what happened, and where. (Screenshots and links help!) If the *Violation(s)* aren’t self-explanatory, explain your complaint.

## Resolving Issues

1. We will strive to resolve all reported issues fairly and promptly, internally or in dialogue with involved parties, using our [Enforcement](/policies/community-collective-agreement/community-enforcement.md) and [Transforming Tension & Conflict](/policies/community-collective-agreement/transforming-tension-and-conflict.md) guidelines.
2. To resolve unclear issues, moderators will defer to Guild leaders, and Guild leaders will defer to the Board.
3. We will prioritize the privacy and safety of any reporters of issues, emphasizing our policy against retaliation.
4. We will provide explanations as soon as feasible of unexpected delays in resolving Issues.

## Head to the Next Section


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guide.techfleet.org/policies/community-collective-agreement/reporting-and-resolving-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.