> For the complete documentation index, see [llms.txt](https://docs.openagrinet.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openagrinet.global/technical/ai-layer/ai-as-an-orchestration-layer.md).

# AI as an Orchestration Layer

A key design principle of the OAN AI module is that AI does not act as a source of truth. Instead, it determines which systems or data sources to invoke and how to present the resulting information to the user.

All responses generated by the AI are:

* Grounded in knowledge base sourced from trusted institutions (for advisory and schemes)
* Backed by live API calls (for weather, prices, status checks, and grievances)
* Constrained by domain-specific guardrails
* Safe and responsible

This ensures that:

* Information remains verifiable and auditable
* The system avoids hallucinated or speculative outputs
* Source attribution can be maintained where required
* System is free of any biases

This design aligns with OAN’s broader philosophy of building trustworthy digital public infrastructure, where intelligence augments systems rather than replacing them.


---

# 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.openagrinet.global/technical/ai-layer/ai-as-an-orchestration-layer.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.
