> For the complete documentation index, see [llms.txt](https://docs.mtnviewrp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mtnviewrp.com/lore/history/ancient-history/notable-historical-figures.md).

# Notable Historical Figures

The people remembered by Mountain View shaped its laws, secrets, and scars.

Some are celebrated publicly. Others survive only in family stories, sealed records, or supernatural memory.

## What belongs here

Use this section for figures whose choices still affect the present.

Include:

* Founders, leaders, activists, and cultural figures
* Practitioners, protectors, and rivals from the hidden world
* People whose legacy creates a current ally, threat, mystery, or obligation

## Writing a figure

Each profile should establish:

* **Who they were** — their background, role, and public reputation
* **What they changed** — the event, institution, or magical force they shaped
* **What remains** — their living legacy in modern Mountain View

{% hint style="info" %}
Use real historical people with care. Keep documented history distinct from the setting's fictional magical elements.
{% endhint %}


---

# 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://docs.mtnviewrp.com/lore/history/ancient-history/notable-historical-figures.md?ask=<question>&goal=<endgoal>
```

`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.