> For the complete documentation index, see [llms.txt](https://docs.goharrier.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goharrier.com/functional/documentation.md).

# Documentation

### Diagrams

* [ ] Business Process Diagram

### Rationale & overall documentation strategy

Functional documentation focuses on the narratives of completed stories. When acceptance criteria are clearly defined and articulated, the collective sum of these stories should illustrate a comprehensive behavioral overview.&#x20;

Nonetheless, there exists a necessity for overarching business process documentation. This is accomplished not through written documentation but via flowcharts.

BPMN or alternative notations may be employed, provided they clearly delineate the various stages in a process, including their prerequisites or conditions that are assessed, and the subsequent effects across systems or actors.


---

# 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.goharrier.com/functional/documentation.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.
