> For the complete documentation index, see [llms.txt](https://docs-lunar.earthly.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-lunar.earthly.dev/docs/guides.md). # Guides Opinionated guides for rolling out Lunar in a large engineering organization, beyond the reference documentation. The rest of the documentation describes what each part of Lunar does. These guides describe what to actually do with them — the sequencing, the trade-offs, and the failure modes we see most often in large engineering organizations. * [Cataloging Strategy](/docs/guides/cataloging-strategy.md) — how to get from a partial, inconsistent software catalog to one complete and trustworthy enough to scope guardrails with. Covers coverage, cleanup, monorepos, and the guardrails that keep the catalog honest. * [Cancel a Bad Config](/docs/guides/cancel-a-bad-config.md) — what to do when a config change that broke collection or verdicts has already shipped: cancel it to stop its work and re-run what Lunar Hub can for the commits it judged under the fix. Guides assume you have already [installed Lunar](/install.md) and read [Key concepts](/docs/key-concepts.md). --- # 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://docs-lunar.earthly.dev/docs/guides.md?ask=&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.