> For the complete documentation index, see [llms.txt](https://docs.oscwii.org/guidelines-and-processes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oscwii.org/guidelines-and-processes/introduction.md).

# Introduction

Guidelines and Processes

Our official Guidelines and Process Guides for application review, acceptance policy, and content disclosure are hosted here.

When something is not expressly written in the guidelines, it will be resolved at the discretion of the Open Shop Channel Core and Repository Moderation Team.

Unless otherwise noted, these guidelines do not apply retroactively to inactive apps already on the repository until an update is released by the application author.

The Open Shop Channel Team reserves the right to change these Guidelines at any moment and without notification.


---

# 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.oscwii.org/guidelines-and-processes/introduction.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.
