> For the complete documentation index, see [llms.txt](https://docs.aloop.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aloop.icustomer.ai/how-it-works/overview/knowledge-and-sources.md).

# Knowledge entries & sources

**Knowledge entries** are the things you tell the system directly — notes, documents, URLs, positioning, dos and don'ts. Add them any time to correct or enrich what the Harness knows.

**Sources** are where the rest of your context comes from, so you can see and trust its origin:

* **Web research** — public information gathered at onboarding and refreshed over time.
* **Manual edits** — anything you or your team confirm or change.
* **CRM sync** — customers, contacts, and stages from your CRM.
* **Paid media history** — spend and performance from connected ad accounts.
* **Decision traces** — what the system itself did, fed back as context.


---

# 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://docs.aloop.icustomer.ai/how-it-works/overview/knowledge-and-sources.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.