> For the complete documentation index, see [llms.txt](https://docs.gospace.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gospace.com/overview/our-mission.md).
# Our mission
gospace brings people & teams together, optimising when they go into the office, and ensuring they have the best space for their requirements when they do.
We do this by measuring 2 success metrics:
* Co attendance: Recommending what days to come into the office so that a user is in the office the same day as who they collaborate with.
* Co location: Intelligently allocating a user space with people they collaborate with that best fit their requirements.
Below see a diagram explaining how we derive these metrics:
Our ideal customer profile is a dynamic organisation that wants to move away from booking entirely, however gospace is dynamic enough to work even alongside a booking solution.
Simply put, Aidra (our AI) uses an occupancy integration to forecast what days a user is likely to attend the office, and automatically books them in, from here gospace will automatically identify connections between collaborating individuals or teams, then allocate space to each team and individual that day from the forecasting which best fit their needs.
---
# 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.gospace.com/overview/our-mission.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.
.png?alt=media&token=3045dd1c-a482-4cde-ae55-be4b13e7e419)
