> For the complete documentation index, see [llms.txt](https://juris-protocol.gitbook.io/juris-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://juris-protocol.gitbook.io/juris-protocol/juris-protocol-brand-strategy/slogan-and-messaging.md).
# Slogan and Messaging
When you browse our site you will notice a recurring cadence:
“Bank, not a bank, but infused with digital wisdom.”
“Protocol, not just a protocol. But a king in the decentralised world.”
The structure is deliberate. First we anchor you with something familiar—a bank, a protocol, a community. Then we briefly reject the limits of that word, signalling that Juris is not bound by traditional rules. Finally we add a short clause that explains the upgrade: digital wisdom, royal stature, god-like force. The result is a line that is both trustworthy and forward-looking; it promises evolution without abandoning the credibility of the past.
---
# 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://juris-protocol.gitbook.io/juris-protocol/juris-protocol-brand-strategy/slogan-and-messaging.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.