> 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/architecture/architecture-and-logic-deep-dive.md). # Architecture and logic Status: `PUBLIC_ABSTRACTED` Authority: none through this document UNITERA separates institutional knowledge, context, cognition, authority, execution and evidence. This separation makes capable AI useful without transferring accountability to a model. ``` REALITY → KNOW → THINK → PROPOSE → AUTHORIZE → ACT → PROVE → LEARN ``` ## Core invariants ``` Evidence != Truth Context != Permission Cognition != Authority Approval != Execution Receipt != Verification Model != Institution ``` Institutional knowledge grows from traceable sources and decisions. KNOW supplies purpose-bound context. THINK analyzes and plans. Only a separate governance and execution boundary may permit real-world effects. PROVE keeps outcomes and uncertainty reviewable; LEARN returns only reviewed change to institutional state. > Conceptual public projection — not deployment, service, repository, protocol or security topology. --- # 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/architecture/architecture-and-logic-deep-dive.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.