> 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/the-harness.md). # The orchestrator Behind everything in Audience Loop is the Harness — one orchestrator that does the thinking and coordinates your AI team. The Harness reads your [Intelligence](/how-it-works/overview.md) — what the system knows about your business — decides what to do for each audience, and puts the right agent on the job. It works two ways: **on request**, when you ask something in Chat, and **proactively**, running the always-on loop against your goals without being prompted. It's decision-first: the Harness decides *what* should happen before it decides *where* — the channel is the output of the decision, never the input. And it stays inside your guardrails. Anything that needs a human comes to you in [Pulse](/using-audience-loop/overview-2.md), and nothing goes live until you approve it. Every move it makes is recorded as a [Decision Trace](/how-it-works/decision-traces.md), so you can always see the reasoning. --- # 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/the-harness.md?ask=&goal= ``` `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.