> 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/reference/public-disclosure-policy.md). # Public disclosure policy UNITERA publishes a curated, deliberately lossy projection of its principles, product behavior and bounded architectural concepts. ``` Public documentation explains WHAT and WHY. Internal owner sources define HOW, WHERE and UNDER WHICH CONTRACT. ``` ## Classes * **PUBLIC\_CORE:** Human Agency, Company Brain, Personal Realm, `/work`, Needs You, Chat, Quick Actions, KNOW/THINK/ACT, governed execution, evidence, verification and continuity. * **PUBLIC\_ABSTRACTED:** authority separation, organizational boundaries, local runtime, model selection, execution control, memory, provenance, portability, review and recovery — only without reconstructable implementation topology. * **PUBLIC\_STATUS:** coarse maturity only: concept, contracted, under implementation, pilot preparation, limited pilot or production. * **RESTRICTED\_SOURCE\_DETAIL:** exact repositories and refs, internal IDs, object/schema/package names, providers, credentials, protocols, routes, state enums, enforcement order, and test/CI topology. ## Composition rule Two individually acceptable facts are not published together when their combination would reconstruct internal ownership, authority, runtime or enforcement structures. Exact sources are verified internally but are not automatically published. Transparency means explainable principles and boundaries, not operational reconstructability. Engineering state changes continuously. Public architectural state changes deliberately when canonical architecture, product commitments or public maturity change — not for every merge or internal gate. --- # 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/reference/public-disclosure-policy.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.