> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/getting-started/how-to-build-assembly-pipelines-with-octane-and-the-render-network/assembly-pipeline-principles.md). # Assembly Pipeline Principles {% embed url="" %} The **"assembly" concept** is the foundation for Octane workflows: building modular, reusable scenes without baking assets or pre-merging geometry. Scenes are structured like blueprints: referencing geometry, materials, animations, and light rigs without destructive edits. ***“Octane Standalone is an assembler, not a traditional DCC. It allows for infinite scalability without compromise.”** - Andrey Lebrov* **Key benefits:** * Faster lookdev without destructive overrides * Cleaner scene structure * Easier team-based asset handoffs * Lower render overhead when used with Render Network --- # 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://know.rendernetwork.com/getting-started/how-to-build-assembly-pipelines-with-octane-and-the-render-network/assembly-pipeline-principles.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.