# Page Not Found

The URL `files/C6Ef5bw9XJJ6XU47yudi` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Brand, Logos & Usage](https://chtlab-io.gitbook.io/nott-whitepaper/brand-guidelines/brand-logos-and-usage.md)
- [Community](https://chtlab-io.gitbook.io/nott-whitepaper/nott/community.md)
- [Super Power Saving Mode](https://chtlab-io.gitbook.io/nott-whitepaper/nott/nott-products/nott-pulse-pro/features/super-power-saving-mode.md)
- [Text Messaging](https://chtlab-io.gitbook.io/nott-whitepaper/nott/nott-products/nott-charm/features/text-messaging.md)
- [Phase 5: Market Expansion & Customer Support (2027-2028)](https://chtlab-io.gitbook.io/nott-whitepaper/nott/roadmap-and-milestone/phase-5-market-expansion-and-customer-support-2027-2028.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://chtlab-io.gitbook.io/nott-whitepaper/brand-guidelines/brand-logos-and-usage.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://chtlab-io.gitbook.io/nott-whitepaper/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://chtlab-io.gitbook.io/nott-whitepaper/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/nott-whitepaper/brand-guidelines/brand-logos-and-usage.md`).

You may also use `Accept: text/markdown` header for content negotiation.