# Product: Playing the game

Our apps are products. The documentation is also a product.

Running a product is a game, and the game is about building the health of the product in response to incoming stimuli.

{% hint style="info" %}
What else can be considered a "product", in the way that term is used here?
{% endhint %}

Imagine our products as members of Lightward themselves. Locksmith and Mechanic and their respective documentation – [they all have the same priorities as you do](/priorities.md). The only difference is, they're not autonomous. They need you to help them make good on those priorities.

That's the game. You're playing *as* the product, and your goal is just to be healthy, respecting the [priorities](/priorities.md) of those three tiers of health.

## How to play

1. [**Load the game**](/product/1-load.md) by seeking out all relevant context, everything that previous players have saved for you to use.
2. [**Play the game**](/product/2-play.md) like only you can. In this moment, you are the protagonist.
3. [**Save your game**](/product/3-save.md), such that someone else can seamlessly pick it up and continue gameplay later from where you left off.


---

# Agent Instructions: 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:

```
GET https://www.lightward.guide/product.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.

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.