> For the complete documentation index, see [llms.txt](https://www.lightward.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.lightward.guide/product/1-load.md).

# 1. Load the game

So you've picked up the controller. IT BEGINS.

{% hint style="info" %}
Pay attention to the hard parts here. Pay attention to the pieces of context that are hard to retrieve or understand. Any struggle experienced in this stage is worth its weight in gold when gameplay concludes and it's your turn to save.

This whole thing is a loop, and you won't really get good at saving until you've learned what you need while loading. (Or, to use a more common metaphor: you won't really get good at teaching until you've struggled to learn.)
{% endhint %}

## Active context

You picked up the controller for a reason. Start by comprehensively understanding that reason. Ground yourself in it. Maybe the customer handed you the controller, because they're stuck on a hard part. Maybe a system went down. Maybe you had an idea. Whatever it is, mentally run through the reasons you're here, and make sure you understand the core motivation.

The active context is all the stuff that's currently in motion.

## Passive context

The passive context is everything \*gestures\* *out there*. It's all the lore that supports the active context. It's frequently the place where you'll find answers. (Not always, though.)

Places to check for passive context:

* Documentation
* Slack history
* Rollbar
* New Relic
* GitHub (code, issues, pull requests)
* Grafana (for [Fly](/technical/fly.md) stuff)


---

# 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://www.lightward.guide/product/1-load.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.