> 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/what-is-gpc.md).

# What is GPC?

GPC is the scripting language used to read controller input, maintain state, transform values, schedule timed sequences, control device feedback, and write the outgoing controller report on Cronus Zen.

A GPC script is not a desktop program. Its `main` section runs repeatedly as part of the real-time report loop. That makes three ideas especially important:

{% stepper %}
{% step %}

#### Read the input layer you actually mean.

{% endstep %}

{% step %}

#### Keep one clear final writer for each output.

{% endstep %}

{% step %}

#### Perform expensive display or persistence work only when something changes.

{% endstep %}
{% endstepper %}

This guide begins with those ideas before introducing advanced storage, architecture, and VM details.


---

# 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/what-is-gpc.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.