> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/overview/23q4/govstack-ui-ux-guidelines/10-other-resources.md).

# 7 Other Resources

## 9.1 UX/UI switching guidance

[Technical guidance for implementers looking to understand how screen level switching between GovStack applications/Building Blocks could work](https://govstack-global.atlassian.net/wiki/spaces/GH/pages/270139400/UX+Switching).

## 9.2 Key Decision Log

[A historical log of key decisions regarding this Building Block](https://govstack-global.atlassian.net/l/cp/h99D4wUf).

## 9.3 Future Considerations

[A list of users flows and patterns to add to these UX/UI specifications in the future](https://govstack-global.atlassian.net/wiki/spaces/GH/pages/373752067/Future+scope)

[A list of topics that may be relevant to future versions of this Building Block](https://govstack-global.atlassian.net/wiki/spaces/GH/pages/265027591/Future+Considerations).

## 9.4 Out-of-Scope Assumptions

[A list of functions out of the scope of this Building Block](https://govstack-global.atlassian.net/l/cp/8EvM0Gt9).


---

# 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://specs.govstack.global/overview/23q4/govstack-ui-ux-guidelines/10-other-resources.md?ask=<question>&goal=<user_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.