> For the complete documentation index, see [llms.txt](https://docs.urbanarray.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.urbanarray.org/social-empowerment-and-management-system/overview-of-seams.md).
# Overview of SEAMS
The Sustainable Empowerment and Management System (SEAMS) is a comprehensive platform developed by Urban Array that serves as the backbone of our operations. It is designed to manage and streamline various aspects of our organization, including project management, skill development, resource allocation, and community engagement. SEAMS is an essential tool that enables us to create and support sustainable, equitable, and self-sufficient communities effectively. By leveraging the power of technology and efficient management, SEAMS is an integral part of the Urban Array ecosystem and helps us make a meaningful impact on the neighborhoods we serve.
{% embed url="" %}
Technical Documentation for SEAMS- Developer
{% endembed %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.urbanarray.org/social-empowerment-and-management-system/overview-of-seams.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.