> 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/publishing.md).

# Publishing: Erring public

When you create information (maybe while [playing the product game](https://www.lightward.guide/product.md)), put the results in as public a place as possible.

{% hint style="success" %}
More-public is better than less-public, [unless it's at the expense of health](https://www.lightward.guide/priorities.md).

The more publicly-accessible a thing is, the greater the odds of someone else incorporating it into what *they're* building.

It's like open-source software: the more people building a healthy home for themselves using open-source code, the more the code itself can be evolved into something that is itself healthier and more capable.

Same deal here: as we share what we make as we work on our health, and as others incorporate it into what *they* make as *they* work on their health, the more stable and healthy the whole network becomes.
{% endhint %}

When evaluating where to publish, run through this list and aim for the *first* viable audience scope:

1. **Audience: The public internet**
   * GitBook documentation
     * Here, at [lightward.guide](https://www.lightward.guide/)
     * App-specific documentation ([locksmith.guide](https://www.locksmith.guide/), [learn.mechanic.dev](https://learn.mechanic.dev/))
   * The product itself (i.e. make the need for documentation moot by extending/evolving/improving the actual product)
2. **Audience: The internal Lightward team**
   * GitBook documentation: [private.lightward.guide](https://private.lightward.guide/)
   * Slack
   * GitHub
   * 1Password in a shared vault
3. **Audience: Just you** :heart:
   * Notes, Keep, 1Password (in a private vault), or whatever delights you

{% hint style="info" %}
This is an exact inversion of [our overall priorities list](https://www.lightward.guide/priorities.md). That is not an accident. Public publishing benefits the world, our team, and you; internal publishing benefits our team and you; and if you don't publish it at all, *no one* but you benefits. (Not directly, anyway! Private information can improve your health, and [that benefits everyone](https://www.lightward.guide/priorities.md).)
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.lightward.guide/publishing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
