# Page Not Found

The URL `risk-framework/risk-templates/risk-register` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Risk Register](https://duck-initiative.gitbook.io/d.u.c.k.-knowledge-base/risk-framework/templates/risk-register.md)
- [Risk Framework](https://duck-initiative.gitbook.io/d.u.c.k.-knowledge-base/risk-framework/risk-framework.md)
- [Templates](https://duck-initiative.gitbook.io/d.u.c.k.-knowledge-base/risk-framework/templates.md)
- [Incident Response Plan](https://duck-initiative.gitbook.io/d.u.c.k.-knowledge-base/risk-framework/templates/incident-response-plan.md)
- [Reputation (RER)](https://duck-initiative.gitbook.io/d.u.c.k.-knowledge-base/risk-framework/risks/reputation-rer.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://duck-initiative.gitbook.io/d.u.c.k.-knowledge-base/risk-framework/templates/risk-register.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://duck-initiative.gitbook.io/d.u.c.k.-knowledge-base/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://duck-initiative.gitbook.io/d.u.c.k.-knowledge-base/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., `/d.u.c.k.-knowledge-base/risk-framework/templates/risk-register.md`).

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