> For the complete documentation index, see [llms.txt](https://gitbook.jur.io/jur-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.jur.io/jur-documentation/the-lean-network-state-model.md). # The Lean Network State Model Jur offers a complete, evolutionary, modular and agnostic stack to create societies, Network States and versions in between. To do this, Jur offers a number of self-contained components that can be used independently or together. The constructive approach is based on the need to iterate together with the communities as they evolve. The Network State movement is likely to be very dynamic - ideas and needs will change quickly as experiments succeed and fail. Jur stack will be developed using a “lean development” approach. Efforts will be focused on serving immediate needs with minimal viable products, and rechecking user requirements regularly to match the pace of iteration in network state related social experiments. A general overview of the direction of the project follows below. Technical documentation is included in the [Architecture](broken://pages/WMn2H6ozlvM8JZkfYstY) chapter. Jur is developing some essential functions and continues to grow, following user needs and constantly learning. --- # 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://gitbook.jur.io/jur-documentation/the-lean-network-state-model.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.