> For the complete documentation index, see [llms.txt](https://management.lunr.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://management.lunr.tech/how-we-build-processes-and-a-great-product/knowledge-management/company-knowledge-centricity-level.md).
# Company Knowledge Centricity Level
The Company Knowledge Centricity Level is a measure of **how well knowledge is integrated, managed, and utilized within an organization.** It helps to understand the maturity of knowledge management practices and their impact on business performance.\
\
At LUNR, the Company Knowledge Centricity Level reflects **how integrated and essential knowledge is within our operations**. Currently, different departments are at Grade 2 and Grade 3, meaning we have a solid foundation but still have room for improvement. **Our goal is to reach Grade 5 by next year**, where knowledge is fully centralized, easily accessible, and efficiently shared across the entire organization. This ensures everyone can innovate and perform at their best, contributing to our mission of creating secure, ethical mobile technology.
---
# 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://management.lunr.tech/how-we-build-processes-and-a-great-product/knowledge-management/company-knowledge-centricity-level.md?ask=&goal=
```
`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.