# Page Not Found

The URL `pages/33f6803d9e32753ba2f788d8054d9c5bad538f52` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Lifecycle & Obsolescence](https://miyabi-threatworks.gitbook.io/miyabi-threatworks-docs/qualys-ai-triage-pack/user-guide/dashboards/lifecycle-and-obsolescence.md)
- [Executive Dashboard](https://miyabi-threatworks.gitbook.io/miyabi-threatworks-docs/qualys-ai-triage-pack/user-guide/dashboards/executive-dashboard.md)
- [Probable Attack Paths](https://miyabi-threatworks.gitbook.io/miyabi-threatworks-docs/qualys-ai-triage-pack/user-guide/dashboards/probable-attack-paths.md)
- [Trend Dashboard](https://miyabi-threatworks.gitbook.io/miyabi-threatworks-docs/qualys-ai-triage-pack/user-guide/dashboards/trend-dashboard.md)
- [Ransomware Assessment & “Probability”](https://miyabi-threatworks.gitbook.io/miyabi-threatworks-docs/qualys-ai-triage-pack/user-guide/dashboards/ransomware-assessment-and-probability.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://miyabi-threatworks.gitbook.io/miyabi-threatworks-docs/qualys-ai-triage-pack/user-guide/dashboards/lifecycle-and-obsolescence.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://miyabi-threatworks.gitbook.io/miyabi-threatworks-docs/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://miyabi-threatworks.gitbook.io/miyabi-threatworks-docs/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., `/miyabi-threatworks-docs/qualys-ai-triage-pack/user-guide/dashboards/lifecycle-and-obsolescence.md`).

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