> For the complete documentation index, see [llms.txt](https://docs.flora.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flora.ai/getting-started/publish-your-docs/our-product-philosophy.md). # Our Product Philosophy We think creating should feel natural. The creative process & nature are both inherently non-linear and organic. \ By treating each modality as an independent node capable of non-linear network, we liberate the creative process from the constraints of hierarchical perception. \ This approach allows for fluidity in arranging and rearranging the connections—or “noodles”—between nodes, enabling diverse visual content to emerge across mediums and temporalities. \ This dynamic structure supports divergent thinking for conceptual exploration and convergent organization for streamlined production and distribution. With hope for new fissures and syntheses, we spawned FLORA—not just a creative software but a creative evolution. --- # 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.flora.ai/getting-started/publish-your-docs/our-product-philosophy.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.