> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/sel-onboarding/getting-started/aboutourdocumentation.md). # About Our Documentation How to find and update ENERCALC SEL documentation through the CHM help file, PDF manual, and online help. Documentation of your software package is essential for your successful and pleasant use of our products. We try hard to supply you, now and on an ongoing basis, with detailed information on all aspects of the software. To support this commitment, we provide documentation of your software in multiple forms: * A **User's Manual** in Adobe Acrobat PDF file format is available for download at any time from our website: [ENERCALC SEL User's Manual](https://media.enercalc.com/pdf/SELManual.pdf). * An **Online Help system** is available at . * [Jack, the ENERCALC AI support chatbot](https://enercalc.ai/), is available 24 x 7 x 365 and can be useful to you in the evenings or on a weekend when you need an answer from our support team before the next business day. ### Printed Documentation Printed documentation is not provided with ENERCALC products. This is in keeping with the nearly universal industry move away from printed documentation. --- # 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://enercalc.com/docs/sel-onboarding/getting-started/aboutourdocumentation.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.