> For the complete documentation index, see [llms.txt](https://guide.cronuszen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.cronuszen.com/gpcscripting/gpc-script-guide/start-here/the-report-pipeline.md).

# The report pipeline

Think of each cycle as five layers:

<div align="left"><figure><img src="/files/F6XzNBlsGAvVy03Qjt7W" alt=""><figcaption></figcaption></figure></div>

Active combos execute after the written `main` sections and before `remap` / `unmap` finalization. The compiler makes each active combo step part of the cycle's combined `main` behavior, even though the combo is declared in a separate top-level block. This means a combo can become a later writer than ordinary `main` code for the same identifier.

***

The key consequence is **order**. If two lines write the same output during a cycle, the later write wins:

{% code title="report-pipeline.gpc" %}

```cpp
main {
    set_val(PS5_RX, 25);
    set_val(PS5_RX, -40);  // final outgoing RX is -40
}
```

{% endcode %}

Conditionally writing an output can also leave another system as the final writer. Include active combos when reviewing output ownership instead of looking only at the visible order inside `main`.


---

# 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://guide.cronuszen.com/gpcscripting/gpc-script-guide/start-here/the-report-pipeline.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.
