> For the complete documentation index, see [llms.txt](https://docs.archlogbook.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archlogbook.co/01-industry-basics/understanding-how-the-industry-works.md).
# Understanding how the Industry works
To know how to thrive in the building industry as an Architect, let's try to understand what a supply chain of architecture practice is and and an Architect's role in it is.
## What is a Supply Chain?
A supply chain is the sequence of processes involved in the production and distribution of a commodity.
It consists of a network of entities and the bi-directional flow of materials, information and money.
## Bi-directional Flow of Materials, Money and Information
The supply of architecture can only work when there is three bi-directional flows along the supply chain, material, information, financial.
People pay money in exchange for information and material.
Without either flow, the supply chain will not work.
Knowing and understanding the various parties, products/services and flow will help us understand the opportunities for improving the efficiency of 'supplying' architecture.
*Where are you in the supply chain of Architecture?*
---
# 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.archlogbook.co/01-industry-basics/understanding-how-the-industry-works.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.