> For the complete documentation index, see [llms.txt](https://unitera.gitbook.io/unitera-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://unitera.gitbook.io/unitera-docs/docs/en/product/tenant-discovery-company-brain.md). # Discovery and Company Brain Status: `PUBLIC_CORE` The Company Brain is an organization's versioned institutional context. It is neither model memory, an agent nor execution permission. Discovery gathers and structures traceable foundations. People review uncertainty, conflicts and open decisions. Only explicit activation makes a reviewed state active institutional context. In `/work`, this context appears as an understandable foundation for active work, sources, next steps and Needs You — not as a technical object tree. ## Needs You, Quick Actions and Chat Needs You gathers work that requires a human decision or human participation. The collection is tenant-scoped and access-controlled. Inclusion in Needs You marks required involvement, not urgency; any urgency shown derives from a deadline or concrete impact. Quick Actions provide concise next steps — generally available ones as well as those matching the currently open work. Whether an action can actually be executed depends on current rights, prerequisites and the applicable permission and approval state. The visibility of an action is not a permission. Chat supports free-form questions, requests and refinement of ongoing work — contextual to the current work or tenant-wide. `/work` remains the primary institutional operating surface; Chat is a central, complementary surface, not an unimportant option. Neither Chat nor Quick Actions create their own decision, approval or execution authority. Binding effects remain subject to the same approval and permission rules regardless of the entry point. --- # 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://unitera.gitbook.io/unitera-docs/docs/en/product/tenant-discovery-company-brain.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.