> 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/advanced-architecture/advanced-review-checklist.md). # Advanced review checklist * One stable owner per piece of state * One final writer per output * Raw physical, current working, or previous-cycle final output layer selected intentionally * Exclusive modes skip normal logic * State transition precedence documented * Runtime indexes bounded * Fixed-point scale and overflow bounds documented * Save layout versioned and owned * View/edit/save/cancel separated * Dirty flags guard rendering and persistence * BVAR/SPVAR maximum index proven * Controller and console protocols not conflated * Const data uses the narrowest safe type * VM load, bytecode, variable slots, and stack all within limits --- # 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/advanced-architecture/advanced-review-checklist.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.